[LollipopYakuza]

I understand your point, but for an issue that's been addressed so many times, it doesn't sound necessary to get into details. The issue doesn't seem to be that Apple doesn't know but that they don't care.

However, if I, as the author cared to justify that "it's not only me", I would have listed more posts and feedback. I feel like I have read at least 4 times about the broken keyboard, it should not be hard to find a few other links.

[DamnInteresting]

Well, presumably the page's intended audience is software developers at Apple. As a software developer myself, I am all too familiar with the unnecessary churn caused by vague bug reports. It saves time when people include details like error messages (when applicable), steps to replicate, expected result vs. actual result, etc.

Besides, users and developers don't always use software the same way, have the same settings, follow the same forums.

[materielle]

This just feels so backwards. Yes, I know recreating ambiguous issues is annoying because it’s a lot of work, but it’s also our job.

Reminder: we are asking users to give us money in exchange for software.

It’s our job to deliver that working software. It’s not the user’s job to hold our hands and pep talk us into fixing problems. Users can and should find another product that will just do it for them without the whining.

I think the real point of the website, besides joking around, is poking fun at the broke state of the software industry where a bunch of whiny developers and managers will make a million tired excuses for why their software doesn’t just work.

Highlighting bug report and bureaucratic process in response to “your keyboard is jank” is exactly the mindset we need to change.

The point isn’t to start a forum or technical conversation with Apple devs. The point is to laugh at them because their software sucks and “just one more Jira ticket” isn’t going to fix it.

[alwa]

Then again, sometimes a big feature is so comprehensively broken that it’s hard, from the outside, to break it down into specific flaws. Even if you can reproduce the complex circumstances where they manifest.

In the case of the iOS keyboard, I remember one bug that made the rounds (in the popular press!) after somebody recorded their typing in slow motion to validate it [0]. Once they documented it, everybody recognized the feeling and felt vindicated; but it took actual work to substantiate.

That’s the work it seems that Apple engineers should be doing. They have the telemetry, the source access, the design documents, the labs, and the time in their day to make a comprehensive study of it. Just as I can say “my car is handling funny around turns” and let it be the mechanic’s job to diagnose what’s wrong in mechanical terms.

There was a time when this humane aspect was Apple’s particular magic: engineering beyond technical requirements to the point of simplicity, ergonomics, “it just works”…

[0] https://www.macworld.com/article/2952872/heres-proof-that-th...

[tuwtuwtuwtuw]

This isn't a bug report.

Do you honestly think that the developers working for apple looks at the "keyboard experience" and thinks "yeah this is good"? Of course, not. They are competent developers.

[Someone1234]

It does make me wonder if Apple's own employees actually dog-food iOS day-to-day.

It just seems like, you could stop any iPhone user in the street and ask them "How do you find the keyboard?" And get a consistently negative response, but yet nobody within Apple seemingly has noticed for YEARS.

Everyone says iOS 26 did it, but I strongly disagree, I disabled most options in General -> Keyboard like three major iOS versions ago, and moved to Swiftkey* in iOS 18 (although iOS keeps changing my keyboard preferences back to the default).

*SwiftKey is also a shit-show with the "Your Tap Map" crap you cannot disable, where it moves the keys and makes the thing inconsistent. Just goes to show how bad Apple's keyboard is, when I'll put up with it.

[jannyfer]

I’ve noticed since iOS 7-ish that some sliding animations have such a long tail-end easing of the animation that it blocks the touch input of the user. Like if you accidentally scroll to the side instead of down, you have to let go and wait for the side scroll to completely stop.

Then I watched Tim Cook have trouble with tapping the screen multiple times for one action at one of the older WWDCs pre-COVID.

I felt validated and exasperated. Does Tim just put up with this?

[bombcar]

It's so bad that I have to assume that Cupertino is filled with people who "hold the phone differently" and tap with their long fingernails or the very tip of their fingers or something.

I'm always mistyping and I don't know how to fix it to do what they want.

[zem]

if my experiences at google are any indication, when it comes to "regular user" facing features management pays very little attention to negative feedback from the engineers. it always seems to be assumed that we are atypical in our dislike for things.

[pegasus]

They must be, I can't imagine they're all on Android. I'm on iOS and didn't know there was an issue with the keyboard. Maybe it's because I've not tried out any competing ones or maybe because I don't type that much on the phone generally.

[jama211]

I think the keyboard is fine. A few small issues here and there but in general I can type quickly and accurately. I must be lucky though, perhaps my typing style is what apple expects.

[neutronicus]

My wife got me to switch over from Android 2-3 years ago and I have fucking hated the iOS keyboard from day one.

She has only been complaining since iOS 26, though.