It strikes me as a little unimaginative to want to improve on smartphone software keyboards but (1) stick with QWERTY, a layout <i>designed to be inefficient</i>, and (2) require multiple taps to enter some letters. It seems like you've invented a way to make smartphone typing even more of a pain than it already is.
Smartphone 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].<p>I wonder if an approach like KKeyboard with larger but statically combined keys leads to faster typing than the current approach with smaller but dynamically "combined" keys.<p>[*] In reality, the context is modeled using a simple Hidden Markov Model with a much smaller effective context window that could not associate "Paris" and "France." But you get the idea.<p>[0] <a href="https://forums.macrumors.com/threads/impossible-to-type-okee-or-oket-on-iphone.664456/" rel="nofollow">https://forums.macrumors.com/threads/impossible-to-type-okee...</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.<p>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.<p>[0] <a href="https://www.fitaly.com/fitaly/fitaly.htm" rel="nofollow">https://www.fitaly.com/fitaly/fitaly.htm</a>
godnyesninhatenthatnthenphonenhasnnonideanhowntonautocorrectnoutnofnwhatnmustnbenancommonnerrornatnall
Unfortunately thats not correct.<p><a href="https://m.youtube.com/watch?v=hksVvXONrIo" rel="nofollow">https://m.youtube.com/watch?v=hksVvXONrIo</a>
I always make the same typos in Gboard. I don't know if they adjust the hotboxes based on common letter sequences, but it would be nice if they adjusted it based on people's typing performance.
Interesting to note is how much typing accuracy decreases if you enable dual-language single-keyboard typing (e.g. Eng + Fr) on an iPhone, since targets end up having to account for two separate dictionaries.
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.
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.
Omg I thought this was just me. How do I turn this off? On iOS, this has been bugging me for a long time.
There is no builtin setting in iOS to disable it. However most 3rd party keyboards don't have it, as implementing it without OS support is a huge pain.
Why is it hard? In principle you render an image instead of discrete buttons, and do your hit testing manually. Sure, it’s more annoying than just having your OS tell you what key got hit, but keyboard makers are doing way fancier stuff just fine (e.g. Swype).
Apple's keyboard receives more information, to put it simply. It doesn't get told that a touch was at a particular point, but the entire fuzzy area. Allowing you to use circular occlusion and other things to choose between side-by-side buttons and override the predictive behaviour when it is the wrong choice.<p>A third-party maker gets a single point - usually several in short succession, but still it requires more math to work out where the edges of the finger are pressing, to help determine which direction you're moving. So most just... Don't.
I would love a way to turn it off as well, this is the source of the majority of my annoying typos.
I'm not following.<p>* Does this still expect you to hit every key but some of them need multiple taps?<p>* Are they doing fancy autocorrect-like magic to decide which letter you <i>meant</i>, and if so why use this instead of taking it one more step and using <a href="http://minuum.com/" rel="nofollow">http://minuum.com/</a> ?<p>* Or is it something else?
Yes, all characters are entered with tap or double-tap, and it also supports simultaneous taps as an advanced option.
It’s fully local, with no autocorrect or prediction.
Minuum compresses QWERTY into one row, but QWERTY mini keeps the QWERTY structure to preserve the familiar typing experience.
Thanks for your interest!
So like, to type "x" a person would hit the dx key twice?<p>I guess that's better for precise typing, but for normal prose it's probably faster+easier to just type blindly and let the machine figure out what you mean.
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.
I just tried this out, and the need to double-tap was a total deal breaker making words like "success" a failure.<p>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 <i>not</i> working once I type faster than a certain speed <i>because of the way double tapping is implemented</i>.<p>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.
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
I mean for one thing Minuum is dead, the play store link is 404 and the last time I tried it it didn't work perfectly with recent Android versions. Which is sad because it was great when it was still maintained.
I believe Minuum is the only app I ever paid for on the Play Store, after having followed it since the Kickstarter campaign. It was the only option that made typing on a small touchscreen feel mostly frictionless for me, contrary to the varying degrees of frustration of other options. As a result, I now hardly type on my phone.
That's odd, it works fine on my Android 15 phone.
Looks 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.<p>1. <a href="https://en.wikipedia.org/wiki/MessagEase" rel="nofollow">https://en.wikipedia.org/wiki/MessagEase</a><p>2. <a href="https://github.com/dessalines/thumb-key" rel="nofollow">https://github.com/dessalines/thumb-key</a>
You might want to throw a CDN in front of this -- the site is realllllly struggling and seems very complex under the hood.<p>Cool idea though.
I threw it at archive.is for them.<p><a href="https://archive.is/gW1rO" rel="nofollow">https://archive.is/gW1rO</a>
Thanks for letting me know! The website isn’t optimized yet, so it’s running slower than usual. I’ll work on improving it soon. Really appreciate your interest!
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
Hmmm. Cute. I use a Bluehand (<a href="https://taoofmac.com/space/blog/2023/08/08/1230" rel="nofollow">https://taoofmac.com/space/blog/2023/08/08/1230</a>), which is physical and has... half the keys, but that relies on chording. I might take a look at the idea of doing a 20-key physical keyboard that looks like this.
Were you inspired by thumb key at all? <a href="https://github.com/dessalines/thumb-key" rel="nofollow">https://github.com/dessalines/thumb-key</a>
i tried it and think it needs at least three improvements for me to use it:<p>normally a sentence starts automatically with a capital but not with this keyboard<p>double space should result in a dot and a space, to end a sentence. Now I need to switch layout for a dot<p>automatic suggestions are not enabled (or implemented)
Do people often thumb letters instead of swiping? And why? Coding or other stuff where you don't have natural language?<p>For her swiping (or glide typing) is the only thing making mobile phones somewhat usable, but I also encounter people who haven't even heard of that feature.
I usually just type with two thumbs and can type pretty quickly. Swiping always felt a bit awkward to me because my phone is too large to use one handed with one thumb swiping, and swiping with a finger felt awkward compared to just holding my phone in both hands and typing with both thumbs.<p>I imagine if you look at how most young people use their phone, it will mostly be the two thumb method and they will likely be very quick with it.
I noticed "International patent (PCT/KR2025/099177), International Publication "<p>Are you truly seeking a software patent for this? If so what is the plan for leveraging ownership over the patent?
I don't really understand how people manage to type with two thumbs while holding their phone securely. I use my left thumb and my right index finger, with my right thumb supporting the base of the phone.
Reminds me of the abominable parking ticket machine keyboards in Rome (<a href="https://www.wantedinrome.com/i/cover/storage/uploads/2018/12/rome-bus-tickets-parking-meters.jpg.webp" rel="nofollow">https://www.wantedinrome.com/i/cover/storage/uploads/2018/12...</a>)
Seems like there's 25% wasted space at the bottom for the language globe icon that could be used for something useful
I really dislike how iOS handles dictation as a keyboard feature.<p>I want to try this keyboard, but I also don't want to give up dictation. If I have to switch back to the iOS keyboard to enable dictation, that's just enough friction that I'm not going to move to something else.
Site seems down, try
<a href="https://archive.is/gW1rO" rel="nofollow">https://archive.is/gW1rO</a>
Nice idea, I might try it!<p>I noticed "copyright info goes here (c) 2025" - which you might want to update!
> I noticed "copyright info goes here (c) 2025" - which you might want to update!<p>It's still 2025, so that's fine :P post-Berne Convention, there are no forms required for copyright protection to vest, merely fixing the work upon a medium is sufficient.
So vibe coded slop that clearly hasn't been reviewed is going to have access to all my input.<p>Interesting idea, but that's a pass from me.
I like it but I wish I can change the size of the keyboard. Buttons are too small on my phone.
Reminds of T9 texting and I did like T9. I'll have to try this.
Looks nice. Can I swipe write with it?