@ozzyphantom: You might consider being more specific about your grievances in the text of your countdown page. As it stands, it's a bit vague, describing the keyboard as "broken" and autocorrect as "nearly useless". Sure, the video you link to is more descriptive, but it's a lot to ask of a visitor to click through and watch a separate video.
As for the underlying issue, I have experienced similar typing issues on my iPhone in recent months. It feels like someone changed the keyboard to optimize for some typing behavior that doesn't match my own, so the "optimizations" work against me. It's reminiscent of when the US Air Force redesigned their cockpits to match pilots' average measurements, only to discover that using averages just made the cockpits bad for everybody.[1]
The recent changes to the iOS keyboard and text editing in general have been very counter productive for me as well. Tap to select doesn't really work the same way anymore and the logic of it isn't clear to me which makes it unpredictable. Typing accurately itself has gotten really difficult. I used to be a pretty quick typist on the iOS keyboard but now I find myself looking for my Mac to send a message from there or using voice to text more.
Folks can thumb their noses at Reddit but the top comment in every post about iOS updates since 26.0 was released is some variation of "fix the keyboard." The problem seems very real for a lot of users.
Select all always appears if you have no text selected and never appears if you have some text selected. Insane UI decision by apple but that's how it is.
It honestly doesn't surprise me. Apple is not some bastion of good design. They are mediocre at best, always have been.
It was pretty hilarious to me that for so many years the keyboard on iOS only had CAPITAL letters. No matter the state of the shift key, the letters on the keyboard just stayed the same. After many years they finally figured it out, but it's one example of many about how Apple just doesn't have the great UX people claim they do.
I have some kind of mental block that prevents me from figuring out the state of touchscreen controls.
"Is that a Play button because it's currently playing, or because it is paused/stopped, and will play when I tap it?"
"Is Bluetooth on or off? That depends if Dark Mode on?"
I end up tapping the control 3 times or so. The latter dilemma could sometimes be worked out by surveying the state of every surrounding control, but tunnel vision and impatience keep winning.
I actually prefer the all caps keyboard and switch it on on iOS. It looks like a physical keyboard and the constant flicking between upper/lowercase is distracting and annoying
they are not bastion of good design. they are the bastion of intentional opinionated design. Meaning they don't listen to feedback. ("we don't have focus groups" - Steve Jobs).
Looking at every UI/UX implementation around be and on my devices... I'm not sure anyone does anymore. Not in a haha way, I actually see so many trivial issues all around, I don't understand how they passed any contact with testing and user feedback.
This was not poor design, but a decision to restrict the user from copy pasting entire articles and the like. Most unfair and this iPhone 3G to iPhone 17 Pro user is seriously considering ditching them over select all
Apple has fantastic UX people. Also really bad ones. It’s a mistake to think a company that size is homogenuous.
In general, IMO they are better than most companies but far from perfect. Maybe 80th percentile. I’m hard pressed to think of a top 10 tech company that’s better. Lots of smaller companies are.
Come on. OSX was a paradigm shift in desktop usability and intuitive design.
My 85 year old grandpa asked me about 20 years ago how he should go about learning how to use computers. We were a windows family at home but I was using Macs in school and OSX was relatively new and I thought it blew Windows out of the water as far as usability.
Didn’t take long for my grandpa to be sending me emails and news links, and becoming an overall competent and comfortable computer user, in his late 80s, and I credit that to Apple’s fantastic design.
I think maybe we forget how using Windows 98 and XP was day-to-day.
This is accurate. Apple’s been losing its soul ever since they spent a billion dollars making a headquarters that’s shaped like the “Home” button that they then immediately got rid of.
I understand your point and have a long list of bitter grievances against Apple, but OS X triggered a large influx of geeks to the Mac world. It was a Unix that just worked, and there were all kinds of important ways that appealed to key tech people.
>Come on. OSX was a paradigm shift in desktop usability and intuitive design.
OSX was born by moving from a real crap OS that couldn't even multitask property, to slapping the same UX paradigms on a Unix base.
The first release of OSX wasn't meaningfully different from OS9 in UX. They had the same goofy window gadgets for minimizing and maximizing a window, and still couldn't resize a window from any corner/side.
Finder is still just as much garbage as it ever was, nothing has really changed there. "About this software" is still the first thing on the first menu, because of course that's the most important thing a user could do with MacOS software is to look at what version they are using.
There's a reason MacOS has never gone above 15% market share - part of that is the extortionate cost of Apple hardware, as well as their shitty UX.
I will gladly take Windows XP over any version of MacOS.
old school apple design stubborness: I remember they insisted on putting the grooves on the "D" and "K" keys instead of the "F" and "J" keys. So you had to find home base on the keyboard with your middle fingers on an apple rather than index fingers like on everything else. No, that place has always been a design shop run amok.
It made sense because the numeric keypad had the dot on the 5. Early IBM keyboards (Model F) didn't have home markers, IIRC. But the PC world standardized on F and J, and eventually everyone else, too.
Did you ever notice that "About this software" is the first thing on the first menu of every application? Is that because people have to know what version of the software they are using every time they start it? It's still like that today, and it's very very stupid. Other OSs get it right and put the version information on the last menu, where it doesn't clutter up the most prominent area in the most used menus.
Finder was crap in the 1980s. Still is crap, but it used to be crap too.
The window system in the 80s and 90s was also crap. Could not resize a window from any side or corner of the window except the lower right. Windows has had resizing from any edge or corner since forever.
Apple "design" is just not as good as people seem to think it is.
They've also had plenty of weird and unloved hardware designs... the infamous trash can, the clamshell laptop, the weird anniversary macs, a mouse with a charging port on the bottom so that you can't use the mouse while it's charging, and the list goes on and on and on.
As someone who has switched from Windows to Apple recently, my God the Finder is terrible. I can't understand how people aren't flipping tables over how bad it is.
Finder has to be used with the Miller columns; otherwise, it doesn't make sense.
But since the switch to the new filesystem, it's kinda slow and annoying.
They have built some proprietary stuff around their filesystem to increase their walled garden height. Which is kind of stupid in the era of cloud computing, because you cannot use any of it if you share files/directories with other people who don't use Macs.
Because Mac OS X Finder has always been kinda terrible. There was a lot of talk about this in the early 2000s and it's just faded away since the people using macOS now probably never experienced the good old Mac OS 9 Finder.
And its Windows competition Windows Explorer has likewise gotten worse and worse each revision of Windows.
lol, directory opus? I was using that on the Amiga way back in the day. I tried it like a decade ago, but it didn't stick for me. It doesn't seem to run on Linux, and it costs $$$, so no chance I'll try it again.
I can't think of a better rationale for the ubiquitous worsening of local search than increasing ignorance of comp sci fundamentals.
There's no reason a senior at undergrad level shouldn't be able to write an efficient, fast, deterministic, precomputed search function.
... and yet, professional developers at major companies seem completely incapable.
Minimum acceptance criteria for any proposed shipping search feature should be "There is no file / object in the local system that fails to show up if you type its visible name" ffs.
The whole window management system is an exercise in contrarianism.
They basically chose to do things in the opposite manner of their competitor and mostly against what intuition would dictate for the sole reason of being different.
macOS is very frustrating to use without utility apps that provide the necessary improvements. But they are never as well integrated, cost money or are a hassle to set up.
Apple just wins because they make good-looking, well-built hardware, and sometimes they win on some performance metrics (in the Apple Silicon era, it's mostly about efficiency and single-core speed, which is not as useful as some like to believe).
Apple only "wins" by charging exorbitant prices that idiots are willing to pay to have a digital status symbol. What they have not "won" is market share. They have always been an "also-ran" in market share.
Android (70%) beats iOS (30%). Windows (68%) beats MacOS (13%).
Well, I agree with that if we are talking about the general population.
But Apple does have some niches it serves very well that make the prices worth it for some. But of course, this is a very tiny minority of their customers.
For example, they always have been focusing on video editing since the PPC days, starting with the iMac DV. And nowadays, Macs are still quite good for video editing; even when you factor in the price, it's not that bad of a deal.
Previously it was about DTP and desktop graphics generally.
But it's always the same playbook; they are first to offer the possibilities of a new usage, but that comes with their high price; over time they lose competitiveness, and they end up switching to something else.
The question is always if the asking price is going to be worth it for whatever you try to accomplish with a computer at the moment.
If you are doing work that doesn't require being on the bleeding edge, the answer is probably no.
However, in general, people buy Apple stuff for the status, very often as an ego trip (to prove they are better) and not infrequently out of ignorance/incompetence (it's crazy how much stupid shit Apple fans believe).
In editable text fields you can tap a word a few times and it'll select the whole paragraph, if that's any help.
What drives me insane though, is double tapping a word is supposed to select that word. But I think starting in iOS 18 it started selecting the word and a random amount of surrounding words, but only about half the time. I couldn't tell you what it could possibly be trying to do but it's maddening.
It’s using AI to try and determine if it’s a proper noun or other scenario where multiple words are really one semantic term. Except it’s really really bad at it and it’s almost never the behavior I want, but there’s no way to turn it off. (I vaguely remember there was a WWDC talk sometime a couple years ago where they went into how this works)
Word segmentation has been a longstanding problem in CJK languages too. Coupled with the terrible text selection in iOS it makes it really hard to select substrings.
It works surprisingly well on Android; expanding to grab a full address, for instance, or complete phone number. Sometimes it needs tweaking, but mostly it's directionally correct and helpful rather than harmful
Just keeping my finger on the word works for me every time to select it. Double tap works only works in the edit fields. Also works reliable for me here in the hacker news post editor, as long as I do it in the middle of the word.
It's still there, it's just difficult to know when it will appear. Sometimes it takes one more tap than expected, or sometimes one must deselect a word and tap again, or change focus away and back again. Very sloppy UI.
Especially because it was working fine and understandable in older iOS versions.
Also for some reason autocorrect seems to have gotten a lot worse. It has become nearly impossible to type a grocery list without all kinds of annoying wrong corrections.
My favorite ( /s) IOS hassle - aside from running around on 12% battery at all times, didn’t I buy a pro max for the extended capacity ? -
… is not being able to paste into an empty box unless I type a letter there and select it/clobber it/overwrite it
And I just LOOOOOVE not being able to tap a URL in safari and get to the end of it to add parameters or change a path anymore…
Just gave my MacBook that hasn’t been turned on in months away(i haaaaate Tahoe) and been using GrapheneOS on a pixel 7a.
so far I’m not in love with it but I’m getting used to it and starting to like downloading apps anonymously (if I name the app, I’ll probably get scolded) anyway this might be the end of the line for me and Apple.
Your statement isn't incorrect - but I think it needs a slight qualification of "And none of them are acceptable". Both Apple and Android have regressed in quality and it's only possible because of a duopoly.
I can't tell about windows - never used autocorrect there - but GBoard became laughable. I don't think I was able to use its suggestions since a few years. For instance, it will NEVER but really never put a uppercase I when I'm talking about myself. Never. I could select it from suggestions if I feel like, but I kinda gave up (this is written in Windows, that's why you see capital Is). Or my name, used quite often right, is also never spelled correctly - although it's there in the suggestions. I am using a yahoo email, GBoard knows the username, but it will ALWAYS suggest a gmail extension, which simply doesn't exist. I don't know any other keyboard which can properly handle multiple languages, so I'm stuck with GBoard, but it's nothing to be proud of.
I have the same email @yahoo.com and @gmail.com (one is mostly for online shops etc), and the amount of time GBoard thinks it needs to recommend @gmail.com, it's obnoxious...
But the correction offers are still okay for me, I can mash keys around my email username and one of the corrections offered will be my username...
No it cannot. SwiftKey has exactly two "languages": one is French, the other is German/English/Italian/Romanian. Yes it's a mash of all four, which makes the default swiped word and the suggestions exactly useless. Who the hell thought that was a good idea... only Samsung keyboard offers separate languages as well, but it's kinda worse in suggestions than GBoard.
It's not just the keyboard. My iPhone 15 is often so unresponsive I am tapping twice as much.
Example but the issue not limited to web browsing; Safari will do nothing, I tap again, it does the thing, then it does the thing again due to the second tap. I have to tap back to get to where I really wanted to go.
Sounds like the liquid glass animations are so heavy that if the system is busy with anything else for a second then everything simply breaks.
I remember seeing the videos about cpu usage spiking over 40% just to show the control center.
And similarly, even on a Mac I find myself clicking on links and button multiple times, just for things to work. It has a dedicated keyboard, how is it that they messed it up so much that a physical keyboard stops working. It's an interrupt based interface, it takes less than a millisecond to process things, how can someone mess things up so freaking stupidly.
Apple makes money selling hardware; they have a vested interest in making things slower/worse to incentivize people to buy newer hardware.
This is why you can never really trust Apple and also why no matter how bad Windows gets, it's still a better deal because at least you can count on the fact that PC businesses will compete on the hardware front to get your money.
Choosing Apple is a lot like being in an abusive relationship; you can't leave because the switching cost are quite high, so you tolerate a lot more abuse than you would be willing to otherwise.
And this is the reason people try to not rely on Apple software too much; if you do, they truly have you by the balls.
Shortcuts run but often do not trigger all the stages in a pipeline. No issues with same shortcuts prior to installing iOS26. These Shortcuts do not trigger UI transitions. They send data over network.
Sounds like Apple management enabled a quality assurance failure that is fostering so many distractions for users it's turning people against Apple.
Extremely common pitfall in UI engineering. If you treat all input as a queue that's divorced from output, you end up with situations like this.
It's kind of a paradox, but in many cases you need to actually discard touch inputs until your UI state has transitioned as a result of previous inputs. This gets extremely nuanced and it's hard to write straightforward rules about when you should and shouldn't do this. Some situations I can think of:
- Navigation: User taps a button that pushes a screen on your nav stack. You need to discard or prevent inputs while the transition animation is happening, otherwise you can push multiple copies of that screen.
- Async tasks: User taps a button that kicks off an HTTP request or similar, and you need to wait on the result before doing something else like navigation or entering some other state. Absolutely you will need to prevent inputs that would submit that request twice. You will also need some idempotency in your API design to handle failure/retries. A fun example from the 1990s is the "are you sure you want to make this POST request again" dialog that Web browsers still show by default.
- Typing: You should never discard keystrokes that insert/delete characters while a text input field is focused, but you may have to handle a state like the above if "Enter" (or whatever "done" button is displayed in the case of a software keyboard) does something like submit a form or do navigation.
Essentially we're all still riding on stuff that the original Mac OS codified in the 1980s (and some of it was stolen from Xerox, yes), so the actual interaction model of UIs is a mess of modal state that we hardly ever actually want to fully realize in code. UI is a hard problem!
This analysis ignores the fact that the user experience has regressed from a previous version which didn’t have these issues.
So it’s not like some longstanding industry-wide UI issues they’ve ignored forever, it’s that Apple has introduced new tradeoffs or lowered their quality standards to the point that some users feel their experience has worsened.
Okay, how long is the debounce window? Where in the input pipeline do you debounce (obviously not immediately on keystrokes)? Will debounce work for long-running requests, which are event-driven and not time-driven?
I have seen, far too many times, naive approaches like wrapping all click handlers in a "debounce" function cause additional issues and not actually solve the underlying problem.
To clarify - I am not stating that simple debouncing is the solution to all the issues you're identifying. I agree with you that handling some of them can be very complex. I just shared the article as a pointer to a broadly similar concept that can be used to help communicate the gist of what you're talking about.
Just to correct a common error, nothing was stolen from Xerox. Apple gave Xerox stock (which they later sold too early) for demos and access to the Parc work on Smalltalk and GUIs.
It turns out he posted a better example in his blog post about it - https://thismightnotmatter.com/a-little-website-i-made-for-a... - which is technically linked to in the bottom of the site. I guess if you spend your life learning UX from Apple this is what you get...
Thats a pretty snarky thing to say about Apple. They were arguably the pioneers in OS UX... granted, its not the end all, be all, but still. You could do worse.
Who is "they"? The employees at Apple when the HIG was first published in 1986, 40 years ago? That Apple is dead, what you see before you is an empty and rotted husk.
When I began at Apple in 1995, we followed "Tog on Interface" to the letter. It was not uncommon to expect arguments over what the Right way was during lunch.
I watched as Steve Jobs came back to Apple—he really took hold of the reins of UX (aided by his team of designers).
Personally, (and I say this as it is often a matter of taste) I didn't care for a lot of it.
A simple example: the URL field of Safari should have been, to my Tog sensibilities, an editable text field only. Perhaps somewhere (below?, to the right?) you might include a progress bar to indicate the page loading. But a designer (I will not name, ha ha) came up with a combined textfield/progress bar. It looked to my eye as though, as the page loaded, the text was being selected!
Jobs loved it though.
It was then I think that Apple departed "Tog" for these "one-off" UX experiments.
I have rationalized this move away from a standard since, with the advent of the web, the customer is now being bombarded with all manner of UX—ought to be comfortable with one-off UX.
(Thankfully I see that now we have a thin line that seems to grow along the lower edge of the URL field.)
First is not the same as best. First is not even the same as good. First is only first. Just because someone was the pioneer doesn't mean they should be considered a positive example.
Introduced a concept decades ago in no way implies that their current implementation of the concept is at all ideal or market leading.
“I would argue that…” is a weaker statement, because it ends with an implied “…but since I don’t care that much, I’m not ‘seriously’ arguing that.” It’s not at all equivalent to the strong statement “I argue that…”, which has no such qualifier.
Why cure yourself of useful conversational nuance?
I see where you’re coming from, this was an impulsive creation after months/years of frustration without any expectations.
For anyone curious of my experience here are my main pain points:
- autocorrect failing 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/unselecting text in general is a pain
- keyboard seems to run out of steam after hitting a certain word count in applications such as Apple Notes or iMessage and take forever to register taps
- The Big Daddy: key taps registering incorrectly in one of two ways: 1. Clearly tapping a letter “taps” a different letter (hot spots poorly calibrated) 2. A correctly tapped letter (keyboard highlight indicates correct letter) but incorrect letter is rendered on document
Anyone irl I’ve discussed the iPhone keyboard with has described frustration so I figured this as more a “some of us are annoyed” flare than a technical manifesto.
As another commenter noted I put a tiny link to my slightly more detailed blog post once this started gaining traction but I’m just having fun here really.
As long as we are ranting: I have many multilingual converstations. At some point iOS started offering the "German/English" keyboard option. I assume it also does "French/Swahili" or whatever, but for some reason it didn't auto-create a combination for "Hungarian/English" which I use more than German/English.
This sounds like a great idea, but in practice it just autocorrects incorrectly in two languages instead of one. Which is a shame, since even the German government uses a lot of Denglish these days, you'd think it would be trainable.
Meanwhile, when the chat gets stuck in the wrong language, it's a comfort to know that selecting another (or trying to press Shift for that matter) will take me to Keyboard Settings at least 80% of the time. Because who knows when you might need to change those!
On top this my own language is Englishifying so it’s understandable it gets confused. But still, the whole thing is infuriating when you type something correct and boom, it becomes a word in another language.
> - autocorrect “correcting” correctly typed words
This brings up so many emotions. I disabled autocorrect. I don't give a damn if my words are spelled wrong but they should not be words that I did not type!
I will add: text prediction was so much better before that I could be very sloppy and it would still figure it out. Now I have learned to be more careful with the keyboard.
I got anxious about autocorrect potentially inserting the wrong words and what kind of social fallout that could cause, so I just disabled it entirely. Takes longer to type everything manually but at least my anxiety has gone down.
> Clearly tapping a letter “taps” a different letter
My iPad Mini 6 sometimes gets into this state, especially after deleting something, when tapping one of the keys in the lower right corner becomes completely impossible, it always registers as this different key (I don't have the iPad nearby to check which one), and it stays broken like this until I press a few other keys. It's incredibly frustrating and it's been there since day 1.
The keyboard actually does this all the time, and many assume they are the problem (making typos, etc.). A few have recorded videos to show what is actually happening and it's wild. If I had a link handy I'd share it. The user directly taps on a letter, and the system picks what it thinks the user actually meant, even when the key hit was dead on.
Turning off slide to type in settings improves the situation, however it still happens.
> Clearly tapping a letter “taps” a different letter (hot spots poorly calibrated)
FWIW I encounter this in Android every so often (using gboard). Anecdotally I don't know what causes it (I swear sometimes it's worse and sometimes it's better), but Android isn't entirely problem free.
I have genuinely considered if my (and perhaps everyone on hn) life calling should be just to make a better touch keyboard.
Bearing in mind the amount of constant pain and torment the current best keyboards inflict upon the world, can there be any more urgent problem to tackle?
Forget climate change guys. Make a keyboard. Save the world.
There already was one. For all its faults, Swype for Android ~12 years ago was better than any swiping keyboard available now - both in its interpretation of swipes, and in its other features like "squiggle over one letter to indicate a double letter", "run your swipe above the keyboard to indicate a capitalized word", and the incredible editing features (it had an editing keyboard!). The Swype key, located in the bottom left? You could Swype-A to select all, Swype-X to cut, Swype-C to copy, Swype-V to paste. Swype-space brought up the editing keyboard.
Sounds great. When you say 12 years ago do you mean newer versions weren’t as good? Or was it discontinued or something?
I think the really puzzling thing about these keyboards is we all seem to remember typing being easier - even though phones back then were so much smaller. It makes no sense!
I still use it on iOS, and I've tried to remove all other keyboards, but Apple still just seems to "make up" keyboards I don't know are installed. Or switch keyboards on me mid-typing a word to a weird native one I also don't show as installed. It used to be very occasionally this would happen but now it's so repeatable since 26 I can almost not use my keyboard.
One caveat, I have an Icelandic keyboard installed on there. Sometimes web controls will force an input box to a US english keyboard (or numpad), which is annoying but at least that's sort of covered by a spec. What really drives me nuts is when I'm mid typing on the swype keyboard and suddely it switches to a completely square grid keyboard with up and down quotes in the autocomplete (which is not actually autocompleting or correcting(which while technically correct has almost completely fallen out of popularity since the dawn of the internet)
I quit using Android ca. 2016 (not because I hated it, had other work-related reasons why) and Swype for iOS was only around for a brief period before Microsoft killed it (and most of the things that made it great).
I never used the much-vaunted tap-only iOS keyboards of the earlier iPhones. I have large hands (the OG Xbox Duke controller was very comfortable) and typing on those small screens always felt painful even though I was so often told it was great.
I have autocorrext turned off on my keyboard and typed this without any corrections. These sre the issues i've faced with the stock keyboard:
- accidental periods when typing URLs in Safari
- key target inaccuracy (though turning off swipe-to-tect gas ikproved this a little, though not enough)
- key latnecy which causes letters innsome words to get swapped or extra unwated letters to appear (this could be a me-getting-older prblem, howeverg
- autocorrect suggesting words that I've never typed before (I turned on autocorrect for this list item to make sure i gave it a fair shake; it didn't suggest anything crazy this time, but the number of times it has in the past has led me to turning it off, even after iOS 18 wherein the keyboard supposedly used a small language model to improve suggestions)
I also type longform on my phone sometimes; the keyboard makes this much more exhausting than it needs to be.
Recent versions of iOS make me feel like it wont let me type spaces anymore, I'm always adding full stops instead!
I've given up bothering to correct it now.
So I just search for why.is.ios.keyboard.broken and google seems to know!
Sure, I can consciously and deliberately hit the spacebar, but for a decade or more I had zero issues with causally typing and not looking.
Is it a result of moving to Pro Max sized phones? It could be, and maybe the spacebar is just now further away. I'm willing to concede it could be that.
But then there are many reports of other people with issues....
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.
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.
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.
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”…
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.
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.
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?
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.
> 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.
Fingernails won't trigger a touchscreen. They do matter, though - as your fingernails get longer, you're forced to tap the phone with the side of your fingertip (so the nail doesn't block you) instead of the front.
I'm someone who never puts any sort of product on my finger nails, and I can confirm that my nails work on my iPhone screen, both when I've lazily forgotten to cut them, letting them get annoyingly long, and if I turn my finger over so that my nail is just about flat on the screen - I checked while writing this, and confirmed the screen was responsive despite my skin definitely not touching it. (I'm a man who doesn't have any experience growing my nails to extend more than a few mm beyond my finger tips so I can't speak to that scenario.)
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.
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.
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.
There are some Apple folks here who keep gaslighting users with their iOS 26 concerns and every other issue by calling them weird names and asking them to not complain.
The damn keyboard is broken, one would've known that if they used it more than a few minutes a day in real life examples. Stop shutting people off and use your own damn products instead of getting them all made in China and sell them.
You get that kind of nonsense when people get an irrational attachment to a technology brand.
I see that a lot with Tesla, there's the group that praises them publicly and makes outrageous claims about self-driving... But remains strangely silent about how the windshield wipers don't work right and Tesla won't fix them.
As an iOS user I don't have any specific grievances, but I can definitely say the keyboard has got shittier and shittier in the past few years.
Apple's problem is their keyboard used to "just work" as the original article says. No one knows what magic they did back then, but it's obvious that they turned it off now.
They're still better than the spell checker in MS Teams, although that's not really positive.
That is assuming the user doesn’t first have to offer incense and whisper a fervent prayer to the Omniscient Deity of USB Devices to seize control of the mouse and click the link in divine intervention.
However for most of us that is uncessary and clicking a link to a video requires no effort at all.
I don't watch video complaints. I don't watch most YT videos except at 2x because by time the person who made the video got started saying what they're trying to say, I could have finished a text article version of the same thing.
Most people speak way too slowly for me to be interested in what they're saying, especially when they could have written an article that is more information dense and it typically shorter in any case.
Videos have value for enhancing reports, but are mostly useless as reports themselves.
So yeah, it's too damned much to ask to watch a video.
It isn't necessarily. A _bad_ video can often be worse than a bad description, because I can read a bad description and reformulate and clarify. This is compounded when the video skips the prerequisite steps that a description often needs to add.
Video-first is generally as ridiculous as SEO-driven recipes where I can't start cooking what I want to cook because I have to go through someone's nonna's best friend's sister's cooking life story.
It's great that this video gets to the point in the first 33 seconds, but make me want to watch your video.
This post made me not care.
I get video bug reports all the time at work -- but it's accompanied with a description of what the problem is that makes it worth my time to watch the video. (Sometimes, with a well-written description, I don't need the video but watch it to make sure my understanding matches.)
I am not sure there is much more to say. I have used an iOS device for many years and "broken and nearly useless" perfectly describes every aspect of the iOS keyboard.
I have always just suspected that it is the same as it was with the lack of t9 dialling. Everybody knew it was awful, but apple just stuck their head in the sand and asked their users to just live with it.
There are many things I dislike about iOS (most notably the settings app), but those are just intermittent annoyances but the keyboards is still so infuriatingly bad.
The reaction at work when I brought a usb keyboard to plug into my phone when I had to write something wasn't "why do you do that?". It was "I have thought about that as well. The keyboard sucks".
I've made a few games over the years[1], but so far I only Show HN'd one of them[2]. When my next one is done (it's already in progress), I plan to post it here again, because the feedback on Omiword was great, and I implemented a lot of requested features.
On MacOS I use multiple desktops, and I have Finder assigned to "All Desktops" since it is useful to interact with so many other apps. For several major OS releases now, this setup causes any open Finder windows to render on top of all other windows for ~1 second when switching desktops. It creates an annoying lag, and pollutes what would otherwise be a smooth, pleasant experience.
As for the underlying issue, I have experienced similar typing issues on my iPhone in recent months. It feels like someone changed the keyboard to optimize for some typing behavior that doesn't match my own, so the "optimizations" work against me. It's reminiscent of when the US Air Force redesigned their cockpits to match pilots' average measurements, only to discover that using averages just made the cockpits bad for everybody.[1]
[1] https://noblestatman.com/uploads/6/6/7/3/66731677/cockpit.fl...
reply