iPhone Typos? It's Not Just You – The iOS Keyboard Is Broken [video]

Posted by walterbell 12/11/2025

iPhone Typos? It's Not Just You – The iOS Keyboard Is Broken [video](www.youtube.com)

709 points | 436 commentspage 7

alfiedotwtf 12/12/2025|

Maybe it’s just me, but it’s not just typing - I’ve found that after I type a message in iMessage, it takes SEVERAL pressed to acknowledge a send?!

I don’t know wtf it thinks I’m doing because it doesn’t do any other action.

Aachen 12/11/2025||

Swiftkey on Android does this also and it's a very nice feature. I sometimes see a key lighting up that I didn't mean to press. I was just barely on that key, and it figured out that I didn't mean to press it

Not sure how it works. Maybe it looks at touch surface area movements during the couple milliseconds that I'm pressing down for? Or dynamically adjusts hitboxes as this video says iOS does? Whatever the method, it works very well after like fifteen years of training (I copy the data folder between devices and never update it or let it access the internet, so I'm sure it's just me training it and not anything else, nor incompatible versions ever throwing data away)

Note that this is different from the context-based autocorrect since that only triggers on spacebar or suggestion selection

AbstractH24 4 days ago||

What is me though is neglecting to proofread before hitting send!

herbturbo 12/11/2025||

I assumed it was just me getting worse at typing but combined with aggressively wrong autocorrect and mysterious blue lines under everything I type they seem to have ruined yet another perfectly good UX.

Ensorceled 12/11/2025|

Yeah, the blue lines under a random word in a perfectly correct sentence is such a waste of time ... did I mistype? Nope.

petercooper 12/11/2025||

Another long running one is duplicateduplicate words: https://www.reddit.com/r/ios/comments/mpo20r/iphone_will_occ... .. been happening for me for years and still does from time to time, but it's only once every few days so I just let it bebe.

crazygringo 12/11/2025||

OMG yes. Pretty sure that bug has been around for something like a decade. Insane they haven't prioritized it, or I wonder if they hide behind the fact there doesn't seem to be any way to reliably reproduce it?

Someone just has to look really hard at the code and find the bug. Surely the relevant code can't be that long?

summerlight 12/11/2025||

I just hope them to provide an option to get rid of all those predictive models and just use a static, consistent layout. At least I can blame myself if my typo is from my own mistake.

kbd 12/11/2025||

I type in Dvorak and frequently the iOS keyboard's swipe typing bugs out and acts as if the layout is in QWERTY. I kind of don't believe it will ever be fixed...

cuteLittleOwl 7 days ago||

The best touch keyboard on a phone for me was always on the Blackberry Z10 phone. The phone UI is also one of the best I used. Unfortunately, Blackberry went to shit.

languagehacker 12/11/2025|

I've wondered for a while whether it's a dark pattern where they're trying to optimize for more text to speech in this post-literate world.

The iOS keyboard "just not working" is something I gripe about pretty much every day as a symptom of the world getting quantifiably worse than even five if not ten years ago, alongside a whole laundry list of enshittification transgressions.

jerf 12/11/2025|

I remember back in the late 90s that, if you ignored the matter of hardware driver quality (and that is a big "if", no question) that open source software tended to be higher quality in general than a lot of commercial software. Not because of any moral characteristic per se, but just the "many eyes make bugs shallow" sort of thing. Since it was mostly only programmers using open source anyhow, if someone hit an annoyance, statistically speaking, there was a good chance that someone who could fix the problem had hit the same annoyance.

Then maybe in the 2010s commercial software at least caught up.

But it seems to be swinging back around to, if I want my software to effing work I want to be seeking out open source again. Statistically speaking, fewer of the users who may encounter problems can fix any problems they find, as the systems have gotten much larger, but it is still possible, and on the compensating side, no one on the emacs team is figuring out how to stuff AI where it doesn't belong [1] or how to monetize it via ads or any of the other exciting ways to arbitrage long-term software quality against short-term money.

It's an opinion, it is clearly highly path-dependent, and I won't deny this is just my impression... but it is something I've been noticing again lately. Especially as Windows seems to be heading down the catastrophe curve and this time I'm not sure they can stop it.

[1]: I'm not anti-AI at this point... but there are places where it belongs, and there are places it just doesn't, and stuffing it where it does not belong is not a win.

More comments...