Love the sick burn at the end:

>Who knows? Maybe they're just trying to simulate the butterfly keyboard in software.

Apple truly has some incredibly incompetent people working for it, obsessively focused on cosmetic style instead of substance and usability.

Alan Dye voluntarily leaving certainly won't solve the root problem that they didn't fire him years ago.

Bad Dye Job:

https://daringfireball.net/2025/12/bad_dye_job

Gruber: Apple employees ‘giddy’ about Alan Dye’s departure:

https://9to5mac.com/2025/12/04/gruber-apple-employees-giddy-...

I always end up pressing the `.` instead of enter when trying to search somethin on Safari.

The 3rd letter is the key here. If you are going to look up a possible word that a user is typing, iOS waits until the third letter typed to do the lookup. Too many possibilities before then. So at the third letter typed, in the video it displayed the U, but his finger was low on the button. It displayed, then did the lookup, and while it was doing that lookup the u was still displayed, but the input moved to J without the display being updated. Maybe the lookup being spawned on the background thread caused enough delay on the main thread to not update the highlighted key before the touchUp event fired?

I thought it was my own problem

I am surprised that there isn't a comprehensive test suite of (at least) virtual button presses replaying actual typed sentences for a product used by so many people that apple would run on a daily basis against each device.

This has been driving me up a wall. I was seriously considering if I had just gotten 'old' or something. I've had every iPhone since the first one, and suddenly I feel like I'm typing with mittens on.

The issue is that when you press down, the key you pressed down on first is not the registered character, it's where you release your finger at. When you type fast and you slide your fingers around, it misregisters.

As a bilingual/trilingual user (I have English, Portuguese, Italian, Spanish, French and Chinese keyboards enabled, and use the first three on a daily basis), I have had surprisingly few issues with either swiping or pecking at the keyboard, perhaps because I automatically switch to pecking the instant I spot swiping going down the “wrong” decision tree.

But I also think having this many keyboards enabled makes iOS basically throw up its tiny virtual hands in frustration and nullifies most fancy predictions.

(This was mostly swiped in on an iPhone 15 Pro running iOS 26 with very minor hiccups)

I can't help but feel like some product manager is behind all this...

Why would it go from what felt like a predictable error to what feels like someone moving the keys around? I am guessing someone presented aggregate research that showed higher accuracy overall, but ignored the case that the errors feel like the voices are getting louder :D.

Hopefully they come up with a setting to change this, but knowing apple it probably won't happen. Is it time for custom keyboards to come back?

One-handed finger swiping to type doesn’t work as reliably as it used to either. I am not sure why.

My recent experiment has been very disappointing. Mostly post upgrading to iOS 26? I’ve had to painfully change my behaviour to two-handed typing by default.

My suspicion— they’ve changed the ML system that inferred words based on swipes, and the new one isn’t as good in real world use.