zlacker

>>jakela+(OP)
Apple could learn a thing or two from this. Too often I'm waiting for their silly animations to finish. Just a moment ago I swiped to scroll the view to the bottom, then immediately tapped the button when it came into view, but I had to tap it multiple times until the bouncing stopped.

That's just one example because it just happened, but this happens ALL the time. I know Apple can do better. My Android phone felt so much more responsive (the 120hz screen helped, I'm sure), simply because the animations were snappier.

Other examples that come to mind real quick:

- Swiping up to switch apps. That one is awfully slow. (Actually, most gesture-based activities are painfully slow!)

- Dismissing notifications (esp. on Mac)

- Opening the drawer thing

- Revealing the dock

- Sometimes I see animations stacked upon each other. One animation has to fully complete, then another one, THEN I can finally use my computer again.

It's ironic that I have to go to Accessibility settings and disable these things to make my device accessible.

>>mholt+Ho
You don’t have to wait for the iOS navigation animations to finish, they’re designed to be fully interruptible.

>>void-p+nC
Not all of them. For example if you open a conversation in messages it slides left, and you have to wait before you can scroll. When you cancel a route in Maps it zooms back on your position and you have to wait before you can move the map again (and it’s really slow).