Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

Hacker News · Feb 13, 2026 · Collected from RSS

Full Article

Deadline: end of WWDC 2026. The exact dates haven't been announced yet and this timer is based on the estimated schedule (June 9–13). I'll update it when Apple confirms the dates. They have until the conference ends. Time's up. The iOS keyboard has been broken since at least iOS 17 and it's somehow only gotten worse. iOS 26 has been my breaking point. Autocorrect is nearly useless and often hostile, that part I'm used to. But now the correctly tapped letters aren't even registering correctly. This isn't just me. My Keyboard Grievances Autocorrect fails to correct minor mistakes Autocorrect "correcting" a mistake with another mistake Autocorrect "correcting" correctly typed words Swipe to type is painfully behind Gboard (third-party keyboards are universally under-supported and inferior to Android equivalents) "Select All" is often hidden away Selecting text in general is a pain Keyboard seems to run out of steam after hitting an arbitrary word count in apps like Notes or iMessage and takes forever to register taps Key taps register incorrectly: clearly tapping one letter but a different letter is entered (hot spots poorly calibrated), or a correctly tapped letter (keyboard highlight confirms it) but an incorrect letter is rendered iOS has bugs across the whole ecosystem. But having the keyboard, the thing I interact with hundreds of times a day on my primary device, get progressively worse with every update is absolutely maddening. I randomly tried Android again for a few months last spring. Using a functioning keyboard was revelatory. But I came crawling back to iOS because I'm weak and the orange iPhone was pretty and the Pixel 10 was boring and I caved to the blue bubble pressure. But the keyboard on this beautiful phone is worse than ever. So here's the deal, Apple, if that's even your real name: fix this broken keyboard, or at the very least publicly acknowledge it's broken and commit to fixing it in iOS 27 or earlier. If that countdown hits zero without either of those things happening, I'm switching to Android for good. (Good = at least 2 calendar years) I know losing one customer means absolutely nothing to your bottom line. But I'd like to think it should mean something to the engineers, UX designers, product people, and whoever else had a hand in building this thing. You were the "it just works" company. Now you're just a fruit that I used to know.