| I have low-motion set on my android device and support for it is let's say highly variable I also have no idea why the system bothers with most of the animations -- the material 'hero animation' where there are two different animations with sequential curves is awful https://docs.flutter.dev/development/ui/animations/hero-anim.... The 'stretch at end of scroll' feature was making people sick if you believe reddit https://www.reddit.com/r/GooglePixel/comments/qcadhq/the_ove... These also take upwards of a second, which is a lot of time when I'm trying to get somewhere. I suspect they're being emulated on the CPU on older hardware, contributing to jank and battery issues Some apps respond to low motion mode by replacing smooth motion with high-frequency flicker, which seems like exactly the wrong thing to do. I kind of wonder if this is the OS battling some framework like Lottie Fancy 'different parts of the layout have different scrolling rules' in e.g. android google maps are deranged and make everything worse Rip it all out and focus your energy on making usable software for people maybe? |
This does have the effect of making Firefox buggy and not showing the content at the top of a page before you scroll down and up again. Which only works on sites you can scroll on.