Is my vision that bad? No, it's just a bug in Apple's Calculator

On mobile devices, Apple’s Calculator app has always been one of the most frustrating apps I’ve ever used, and I’m surprised it’s a stock app by the company itself. If you press buttons quickly, like you would a normal calculator, many of the key presses simply don’t register at all. I’m not sure if they’re prioritizing some pretty little visual animation over actual functionality, but it’s incredibly surprising from a company that focuses on user interaction, supposedly.

The lock screen is even worse. I have to slow down to input my passcode or button pushes don’t register.

It’s very easy to reproduce this bug, even if you don’t go quickly. Basically, if your tap becomes a “swipe” that leaves the button area, then a previously registered “tap” that’s already shown up in the field will actually “unregister” and disappear from the field. Try it yourself: tap down on a button, watch the dot appear, then without lifting your finger, swipe out of the button, and watch it disappear. This happens a lot when tapping quickly since you are tapping and beginning to move your finger in the direction of the next button. You have to train yourself to make only up and down motions to be able to go quickly. It is indeed very annoying. The way these buttons should work is like telephone buttons (registering on the “mousedown”, not “mouseup”), and not like OK buttons (that register on the “mouseup”), but instead they chose a weird combination of both.

The "keypress" behavior is not a bug in my opinion, it's a well-established behavior across platforms.

You could do the same thing with a button+mouse on a desktop. The dot for the typed character appearing immediately is different from alphanumeric keyboard behavior, because you can't register any key press before releasing the touch (or key) there, due to composition.

In my opinion, this is sensible behavior and your vision sounds like it would be a nightmare in reality to me, accidentally pressing neighbouring keys or tapping instead of swiping all the time.

Is this any different on Android? I've used Android for most of my smartphone life.

And I can't remember how often I was relieved to be able to cancel an accidental tap by swiping away, when I accidentally tapped a link while scrolling for example.

This is even the default for mouse buttons, no?

It happens, while rarely, still regularly, that I notice I pressed the wrong button just after the mousedown, but before the mouseup. And since I can remember, I was happy that the UI was made so I could then just hold the mouse button and move out of that button to cancel.

Just verified your description of the lock screen code buttons. Not a bug, but the behavior you describe would feel buggy to me.

There are plenty of UX annoyances on iOS though, that is not what I want to deny. I also prefer GBoard over apples builtin onscreen keyboard.