> moving UI elements around is a huge anti pattern that annoys users without any benifits.
Still disagree, and I think you're thinking of really obnoxious examples. I'm imagining about a ~150ms animation for the following:
1. A sidebar sliding out from the side
2. Dialogs swooping in and out from the top of the screen
3. Form panes sliding out when replaced
These quick, almost-no-time visual cues are incredibly important at giving your interface a sense of presence and physicality. Without them, your UI elements are flickering in and out of existence without any perceivable reason, and can often leave the user wondering what changed.
That still just adds perceived lag to the system slowing people down as you can’t read something that’s not yet rendered or sliding around that quickly. 150ms adds up.
“Why did this get so slow?” Is a real and common complaint with such changes and why OS’s allow people do disable so many animations.
The "why did it get slow" complaints happen when the animations aren't fast enough. The brain doesn't need a lot of time to register motion, but many times designers will use a slow and laborious animation to really emphasize something appearing. See Google's material design: it is based on the philosophy that interfaces should behave physically, and you'll see that it feels incredibly snappy.
Example: you can't effectively convey a menu becoming a button without an animation. Without an animation, the menu disappears and a button appears, but there's no reason to believe that they're related. A 100ms tween from one to the other is all you need. Our brains are very good at relating motion, not objects blinking in and out of existence.
100ms * even a minimal 20 actions per minute = 16 minutes wasted in an 8 hour work day.
Remember, those 100ms delay gaining information which also delays every action that happens after them. So, the cost is real.
Worse, people can break 200 actions per minute for well known systems. Which makes this far worse as it’s slowing people down more as they try and get more done.
Still disagree, and I think you're thinking of really obnoxious examples. I'm imagining about a ~150ms animation for the following:
1. A sidebar sliding out from the side
2. Dialogs swooping in and out from the top of the screen
3. Form panes sliding out when replaced
These quick, almost-no-time visual cues are incredibly important at giving your interface a sense of presence and physicality. Without them, your UI elements are flickering in and out of existence without any perceivable reason, and can often leave the user wondering what changed.