Comment by embedding-shape
1 day ago
After using Android for like a decade, I eventually succumbed and got a iPhone 12 Mini (back when it was new). I still miss the ability of turning off animations as I could do on Android, and I'm 110% my current phone would feel 200% faster if I could just turn off every damn animation that just exists to exists. I'd much rather have a second to process if that's needed (which I don't think it is), than being slowed down by one second every time an app changes the page, everything feels like molasses when you navigate around.
Try "reduce motion"? It's not quite the same thing (prefers cross-fades in many cases), but it might help. Anecdotally some things are noticeably faster, and not having them swing around before settling lets me get a read on their location faster.
Sadly, basically no difference :/ https://news.ycombinator.com/item?id=48520988
Kinda fits with what I remember when I used iOS daily - I suspect it's because there's so much more UI customization compared to Android (where practically everyone uses the stock animation core pieces, of composes stuff from it).
Having been an Android dev who handled this stuff very carefully: yeah it's very error prone to do by hand. You have to keep in mind which animations are generally "desired" (like inertial scrolling and panning) and rebuild the stock stuff by hand to work around it if you have custom views or animations, so they don't jump around weirdly (leaping ahead of where you release, because there's where the inertia would settle).
I kinda wonder if this stuff is part of the reason for the new Jetpack Compose stuff - it makes custom views significantly more difficult, so you're very strongly incentivized to just combine stock components, where this all mostly works correctly by default.