Just tried it out, how do you accelerate disambiguating a double key 'nn' in 'dinner' vs alternate? This doesn't feel very usable compared to the existing keyboard to me
Show HN: A 2-row, 16-key keyboard designed for smartphones
41–50 of 70 posts
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#42I'm not following. * Does this still expect you to hit every key but some of them need multiple taps? * Are they doing fancy autocorrect-like magic to decide which letter you meant , and if so why use this instead of taking it one more step and using http://minuum.com/ ? * Or is it something else?
I just tried this out, and the need to double-tap was a total deal breaker making words like "success" a failure. The other problem with the way this double tapping works is that I encountered missed spaces or other weirdness if I type too quickly. It's as if it's having trouble detecting new keydown events when another key is still down for a split second.
yeah, I agree. It feels pretty rough to me. On older feature phones, you could accelerate this with a right arrow key which would lock to the key for key duplicates like 'cc' in success. Definitely feels like this needs a dedicated key for doing that
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#43Looks nice. Reminds me of MessagEase[1] and clones, such as ThumbKey[2]. I use the latter for my mobile text input needs. However, that method is sometimes prone to typos, since one key may have up to 9 different characters assigned to it, and it is easy to swipe slightly wrong way. QWERTYmini could be better in that aspect, since there are only 2 characters per key. 1. https://en.wikipedia.org/wiki/MessagEase 2. htt…
Also this: https://codeberg.org/natkr/flickboard
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#44Earlier quoted context omitted.
Omg I thought this was just me. How do I turn this off? On iOS, this has been bugging me for a long time.
I would love a way to turn it off as well, this is the source of the majority of my annoying typos.
Seriously this explains so much. I thought I was going crazy, or just becoming an old man who can't type on a phone any more.
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#45Smartphone keyboards dynamically adjust the "hitbox" of each key based on what's previously been typed and overall letter frequencies of the language. So when typing "Paris is the capital of Fr..." [*], the A key becomes much easier to hit than its neighbors. Fun fact: back in the day, when this tech was less refined, certain letter contexts made the hitboxes of some keys effectively nonexistent [0]. I wonder if an a…
Need Liquid Keys to make this behavior visible, which will lead to requests for turning it off, joining the iOS Accessibility Settings Hall of {F|Sh}ame.
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#46Smartphone keyboards dynamically adjust the "hitbox" of each key based on what's previously been typed and overall letter frequencies of the language. So when typing "Paris is the capital of Fr..." [*], the A key becomes much easier to hit than its neighbors. Fun fact: back in the day, when this tech was less refined, certain letter contexts made the hitboxes of some keys effectively nonexistent [0]. I wonder if an a…
Thanks for the thoughtful point! Hitbox behavior is largely constrained by OS -level policies from the manufacturers, so major improvements on that side are difficult for now. At this stage, I'm mainly trying to evaluate the layout and the input method itself - and hopefully, in the future, issues like hitbox tuning can be improved as well.
Not it's not.
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#47Smartphone keyboards dynamically adjust the "hitbox" of each key based on what's previously been typed and overall letter frequencies of the language. So when typing "Paris is the capital of Fr..." [*], the A key becomes much easier to hit than its neighbors. Fun fact: back in the day, when this tech was less refined, certain letter contexts made the hitboxes of some keys effectively nonexistent [0]. I wonder if an a…
Not successfully though. Half the time I hit b or n in place of space. I can type numerous words before I notice. I've thought about just making a new iPhone keyboard app with just a big space bar. The iPhone keyboard is the least successful tech I use each day.
I did a fun experiment once to confirm it’s not me sausage-fingering but the stupid iOS keyboard. There’s an app called xKeyboard which lets you design your own keyboard. I remade the FITALY[0] keyboard in it and even though the keys are slightly smaller than on the original iOS keyboard, I can type without making any error. Yet the iOS keyboard often detects the wrong key because of those stupid hitboxes. I wish there was a way to turn them off.
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#48I'm not following. * Does this still expect you to hit every key but some of them need multiple taps? * Are they doing fancy autocorrect-like magic to decide which letter you meant , and if so why use this instead of taking it one more step and using http://minuum.com/ ? * Or is it something else?
This could be a good alternative to Minuum when mixed together. The single line was great in theory, but in practice I often preferred the regular keyboard layout. Maybe the autopredict did not work all that well, at least with the multiple languages I mixed then? Going to two lines might improve it, and devices are bigger now than back then.
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#49Earlier quoted context omitted.
I just tried this out, and the need to double-tap was a total deal breaker making words like "success" a failure. The other problem with the way this double tapping works is that I encountered missed spaces or other weirdness if I type too quickly. It's as if it's having trouble detecting new keydown events when another key is still down for a split second.
There is, understandably, a slight delay with double-tapping, so using simultaneous key presses can help improve speed when typing quickly. Thank you for your feedback.
Sorry if I was unclear, but that's the opposite of what I'm saying. It feels as if simultaneous keypresses are not working once I type faster than a certain speed because of the way double tapping is implemented.
I think I'd prefer tap and hold for the secondary character. Right now spelling is getting totally mangled no matter the technique of the user.
Re: Show HN: A 2-row, 16-key keyboard designed for smartphones
#50Were you inspired by thumb key at all? https://github.com/dessalines/thumb-key