Motion that explains instead of decorates

By Imran Sheikh · 2026-11-12 · Design · 4 min read

Key points

  • Every animation should answer a question the user has.
  • Short durations and clear easing beat spectacle.
  • Respect reduced motion and keep the interface usable without it.

Most animation on the web and in apps is decoration. Things fade in because they can. Cards bounce. Buttons pulse. It looks lively in a design review and tiring on the fifth visit.

Motion earns its place when it explains. It shows where something came from, what just changed or what will happen next. This post gives you a test for that, plus the practical settings we use when we build motion into a product.

Ask what question the motion answers

Before you animate anything, finish this sentence: this motion helps the user understand ___. If you cannot fill the blank, cut the animation.

Good answers are specific. A sheet slides up from the button that opened it, so the user knows where it will go back to. A deleted row collapses so the list closes the gap and nothing else seems to jump. A number counts to its new value so the eye sees what changed. Each one resolves a small confusion.

Write the answer next to each animation in the design notes. A line such as the sheet rises from the add button so the user can see where it will return is enough. When a developer later changes the timing or someone proposes a new transition, the note tells them what the motion must still accomplish.

This habit also protects you from the loudest voice in a review. An animation that looks great but answers no question has nothing to defend. An animation that clears up a real confusion is easy to defend.

  • Origin: show where a new element came from.
  • Change: show what moved, appeared or disappeared.
  • Continuity: keep an object recognizable across screens.
  • Feedback: confirm that a tap or a save registered.
  • Attention: point at the one thing that needs a response.

Match the motion to the product

Motion carries personality, and it should fit the product. A calm tool wants soft, slow transitions that settle. An arcade game wants snap and punch. A cozy puzzle game wants gentle easing and a little weight. A health app wants steadiness, because the user may be anxious.

We make iPhone apps and games of very different moods, and motion is one of the first things we tune to separate them. The same slide at the same speed would feel wrong in at least two of them. Decide the character in words first, then set the numbers.

Keep durations short and easing honest

Most interface transitions land well between 150 and 350 milliseconds. Small changes, like a toggle, can be faster. Larger moves, like a full-screen transition, can take a little longer. Anything over half a second starts to feel like waiting.

Easing matters more than duration. Things that enter should decelerate, because they arrive and settle. Things that leave should accelerate, because they are going away. Linear motion looks mechanical and is almost never right for interface elements. Spring animations suit touch interfaces well because they respond to the speed of a gesture.

Pick a small set of timing tokens and reuse them. Three durations and two easing curves are plenty. When every transition in the product shares the same few values, the whole thing feels designed by one hand.

Test durations on a real device at real speed. A transition that feels right on a large monitor in a prototype can feel sluggish in the hand. Slow it down only when you need to study it, and always judge the final speed at full pace, the way a user will see it dozens of times a day.

Animate the cause, not the whole screen

A common mistake is to animate everything that changes at once. The eye cannot follow ten moving parts. Choose the one element that carries the meaning and let the rest change quietly.

Stagger with care. A short delay between list items can show order and hierarchy. A long stagger makes the user wait for content they already want. If the sequence takes longer than the user takes to scan the screen, remove it.

Never block the next action. A transition should not stop a user from tapping through. Let them interrupt it, and make sure the interrupted state lands somewhere sensible.

Loading states are motion too. A skeleton that matches the final layout tells the user what is coming and keeps the page from jumping. A spinner on its own says only that something is slow. Where you can, show the structure first and fill it in.

If someone notices the animation, it was probably too long.

Respect people who turn motion off

Some people feel dizzy or sick when large areas of a screen move. Both iOS and the web give you a setting for reduced motion. Read it and honor it. WCAG includes guidance on motion triggered by interaction for exactly this reason.

Reduced motion does not mean no feedback. Replace large movement with a quick fade or a color change. Keep the information and drop the travel. If your interface is understandable only because of the animation, the animation is carrying too much.

Build and review motion in the real thing

Motion cannot be judged in a static frame. Prototype tools help, but the true feel shows up on a device with real data and a real thumb. We build motion in the product code so the timing we approve is the timing that ships. It also makes the timing tokens real, because they live in the same place as everything else.

When you review, turn the animation off and use the product for a minute. Then turn it on. Anything you miss was doing real work. Anything you do not miss was decoration, and you can remove it without a second thought.

Sources

  1. Apple Human Interface Guidelines: Motion
  2. W3C: Web Content Accessibility Guidelines (WCAG) 2.2

Journal · Book a call · Home