[Groxx]

Most shoulder-surfers who see my phone ask me how everything's so fast, and get me to show them the settings. Being able to disable the extremely-excessive animations many things have nowadays is fantastic, and is a great reminder that hardware actually has made progress in the past two decades.

(I use accessibility -> reduce motion, personally. less flaky than the dev options, though also less reliable)

[Kiro]

Finally someone not roleplaying. You're the first person who acknowledges the flakiness of the dev options. People are self-reporting when they claim they set it to 0x without realizing it's unusable due to the bugs.

[lynndotpy]

Denigrating others as "roleplaying" is unnecessary and not serious.

AOSP is not the only operating system that allows you to disable animations, even if its implementation is not the best. And yes, I still use 0x on my Android, because it's still that much better than having animations enabled.

[Groxx]

It mostly works fine, I ran with it for a year or so. Actually needing to disable it is extremely app-specific and rare enough that many people probably never experience it (it's essentially always a sign of buggy code).

Though it does kinda often make inertial scroll/pan very bad feeling, as it jumps ahead of where you released, to where it will settle. "Reduce motion" is dramatically better there, which is a big part of why I use it.

Much MUCH more problematic is that Android (on a Pixel) has had a badly broken "recent apps" view for years now, when you have both a third party launcher and reduce motion enabled. It frequently (literally most of the time) gets stuck in its animations and won't scroll anywhere except to leap to the start or end of the list.