When not to animate
Anything a person does forty times a day should be instant. The animation that delighted you in the demo is the one they will come to hate.
A 300ms transition on a menu opened twice a session is fine. The same transition on a row expanding in a table an operator opens two hundred times a day is 60 seconds of their working day spent watching an easing curve. High-frequency actions want to be instant, and the correct amount of motion there is often none.
The other case for no motion is when the movement competes with reading. Anything that animates while text is on screen pulls attention away from the words, which is why scroll-triggered fade-ins are so widely disliked by people who came to read something.
You should now be able to
- Identify high-frequency interactions that should not animate
- Weigh delight against repetition
Loading…