Animate with Purpose—or Not at All

Animations improve UX only when purposeful and fast. For frequent or keyboard-driven actions, avoid animations to keep interactions instant. Use delight sparingly and optimize micro-interactions like tooltips to feel responsive without accidental triggers.

Key Points

• Animate with purpose: to explain, provide feedback, preserve spatial continuity, or intentionally delight—never just for aesthetics.
• Consider frequency: high-frequency interactions (especially keyboard-driven) should be instantaneous; often, no animation is best.
• Favor speed: keep UI animations short (generally under ~300ms) to enhance perceived performance and responsiveness.
• Design micro-interactions thoughtfully: e.g., tooltips should have a slight initial delay but switch to instant, no-delay behavior once active.
• Delight sparingly: animations that wow users should appear in low-frequency contexts; repeated exposure turns delight into friction.

Sentiment

The community strongly agrees with the article's central message that animations should be purposeful and fast. Many commenters take an even more aggressive stance, arguing that most animations are unnecessary and that the default should be no animation at all. Apple — whose design philosophy the article draws from — receives significant criticism for slow, blocking animations. The minority defending animation's value tend to frame it as a tool for non-technical user comprehension rather than aesthetic delight.

In Agreement

• Animation's primary purpose should be communicating state changes, not creating delight — delight is mostly appreciated by designers, not end users
• High-frequency interactions like app launching, space switching, and notification dismissal should feel instantaneous; animation only adds friction to actions users perform dozens of times daily
• Most UI animations should stay well under 300ms, with many developers preferring 150–200ms as the practical sweet spot
• Enterprise and B2B software should prioritize utility over animation polish since users treat it as a productivity tool, not an experience
• The prefers-reduced-motion setting should always be respected, and apps should provide options to fully disable animations

Opposed

• Animations help non-technical users understand spatial navigation and causality in UIs — without transitions, it can be unclear how screens relate to each other or what triggered a change
• Dismissing delight goes too far — iOS vs Android comparisons show regular consumers notice and value the quality feel that well-executed animations provide, even if they can't articulate why
• Hero animations and attention-grabbing motion on landing pages measurably reduce bounce rates, which matters for startups seeking early customers
• Animations serve as learning aids for new users; offering the option to disable them for power users preserves both experiences