Motion with meaning: animation principles for interfaces
Good interface motion explains what's happening. Bad motion just gets in the way. Here's how to tell the difference.
Creative Pouch · · 1 min read

Animation in interfaces isn’t decoration. At its best, it answers questions users didn’t know they had: where did that come from, where did it go, did my action work?
Motion should explain
Every animation should have a job. Common good reasons:
- Continuity. A card expands into a detail view, so users understand they’re looking at the same thing in more depth.
- Feedback. A button press responds instantly, so users know the tap registered.
- Attention. A new notification slides in, so users notice it without being startled.
- Orientation. Panels slide from the side they belong to, building a mental map of the app.
If you can’t name the job, cut the animation.
Keep it quick
Most interface transitions should take between 150 and 300 milliseconds. Small elements move faster, large ones slightly slower. Anything longer than about 400ms starts to feel like waiting.
Use natural easing
Real objects speed up and slow down. Use ease-out for things entering (fast start, gentle stop) and ease-in for things leaving. Linear motion looks mechanical, except for things like progress bars and spinners.
Choreograph, don’t flood
When several elements animate, stagger them slightly so the eye can follow. Twenty things moving at once is noise.
Respect user preferences
Some people get dizzy or distracted from motion. Honour the operating system’s “reduce motion” setting by replacing big movements with simple fades, or removing them entirely:
@media (prefers-reduced-motion: reduce) {
* { animation-duration: 0.01ms !important; transition-duration: 0.01ms !important; }
}
Prototype it
Static mockups can’t show motion. Prototype key transitions, even roughly, and test them on a real device. What feels right on a big monitor often feels slow on a phone.


