2 ms·
I think that jquery animations on the web broke UX designers brains. It's bad enough having a 300 ms animation. But when two, or even three get chained togethe
by epistasis 6y ago
I think that jquery animations on the web broke UX designers brains.
It's bad enough having a 300 ms animation. But when two, or even three get chained together, in addition to whatever lag there is for building the new UI elements, it's unbearable. And then there are the piss-poor apps on iPhone that seem to also depend on network data at some point, and delay all info display until the update comes through.
And the other issue with animations is that you're never sure when it's safe to tap a visible UI element, because it's not clear when that button that's sliding onto the screen will actually become active and responsive to user input. So the animation introduces tons of uncertainty about intersections too.
Animations should be capped to 100ms for any interaction. No chaining if one thing slides out, then another slides over. 100ms total, slide both those panels at once if you want to animate them, devs. Or bette yet, skip the stupid animation.
- Shared404 6y ago> Or better yet, skip the stupid animation. I agree -- mostly. I think that animations can make some things more usable, in the form of drawing attention to a change happening on screen. I do agree whole-heartedly about the lengths of the animations though. If you're going to do an animation, make it fast enough I don't have to wait on it.