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.
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.