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.
<BFINN/#debian> ALL BIG LETTER ON KEYBOARD HERE!!
<CosmicRay/#debian> haha
<BFINN/#debian> TO NO LITTLE LETTER!
https://groups.google.com/g/comp.sys.amiga.misc/c/7AdXvE7KQz...
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.
And its Windows competition Windows Explorer has likewise gotten worse and worse each revision of Windows.
Last Mac I was on still had OSX on it.
Thank goodness for Dopus.
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.
Always seemed like an apple sort of idea.
I'm surprised you went for that over the puck. At least when you unplugged it, you could use it. The puck was just terrible. And old.
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.
But I swear if that's what they're trying to do here, I've never seen it work properly once. It's always just a random substring of the sentence.
If you tap while a word is selected, it won’t appear. If you tap on the cursor while a word isn’t selected, it will appear.
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.
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.
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.
Sounds like Apple management enabled a quality assurance failure that is fostering so many distractions for users it's turning people against Apple.
Tim Cook handing his replacement a dumpster fire.
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!
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.
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.
If it's 1st or 2nd, then it's ok.
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...