Stop animating everything

Motion is the easiest way to make a new interface feel expensive. It’s also the fastest way to make it feel exhausting. The line between the two is almost never about the technology. It’s about editing.

I’ve watched more than one project where every element arrived with a fade, every card lifted on hover, every list item cascaded in with a forty-millisecond stagger. Individually, each decision was defensible. Together, they turned a simple page into a fireworks display that never ended.

If everything is animated, nothing is emphasised. Attention only exists where stillness does.

Start with stillness

The most useful exercise I know is to build the page with no motion at all. Let it sit there, static and unremarkable. Then ask what feels abrupt.

Usually the list is shorter than expected. A panel that appears from nowhere. A state change with no transition. A route change that feels like a hard cut. Those are the moments that earned motion, because something about them was genuinely disorienting.

Everything else can stay still until you have a reason.

A small checklist

When I’m deciding whether something should move, I run through a few questions:

• What changed, and did the user cause it?
• Does the motion explain the change, or just decorate it?
• Would the screen be clearer if this happened instantly?
• Can it be interrupted, skipped, or turned off?

That last one matters more than people think. Motion that can’t be escaped is motion that eventually becomes an accessibility problem.

Speed over spectacle

The animations that age best tend to be short and confident. Two hundred milliseconds, a gentle ease, no bounce. They don’t announce themselves. They just make the interface feel like it noticed you.

The web doesn’t need more spectacle. It needs more moments that feel inevitable — as if the pixels had no other choice.