Skip to content
Ben Serkan Zararsız

Every animation is a micro experience

Animations and transitions have one job: help people understand what just happened. Here are some examples of how this matters, and you can try them out.

On this page
  1. Intro
  2. Motion answers a question
  3. Start where the user acted
  4. Fast, or it feels like waiting
  5. Ease out
  6. The more often, the less motion
  7. Never block the user
  8. Less motion, same meaning
  9. Make waiting understandable
  10. Before you ship

Thousands of tiny lines drift across my weather map. Take the motion away and you are left with numbers. Leave it in and you see a storm front rolling in before you have read a single value.

That is what animation is for: understanding. A good transition tells people what just happened, where something came from and what they can do next. Everything else is decoration, and decoration has a price: a few hundred milliseconds of attention, every single time.

These are the eight rules every animation in my projects follows. Each one is backed by research, and each one comes with a demo you can try right here.

Motion answers a question

Did my click work? Where did this come from? Where did it go? People ask these questions all the time, mostly without noticing. Usability has a name for the answer: visibility of system status. Without feedback, people hesitate, tap twice or assume they made a mistake.

Shoppers who miss a quiet update of the cart counter often add the same item twice. A short response on press is enough: a little smaller, a little darker, a quick pulse on the badge. Feedback is the cheapest animation there is: it happens during the action, so nobody has to wait for it.

Responds on press

No feedback

Start where the user acted

An animation implies a cause. When a menu grows out of the button you just tapped, the connection is obvious: this came from there. When it appears out of nowhere, the brain has to rebuild that link on its own.

Motion works like a map of space: zooming in suggests going deeper, sliding sideways suggests the next step. And it has to keep its promise. A sheet that slides down from the top should not leave to the side. Whatever the curve, the reaction has to start within 0.1 seconds, or cause and effect fall apart.

Share this board

Anyone with the link can view. Editors need an invite.

From the button

Share this board

Anyone with the link can view. Editors need an invite.

From the centre

Fast, or it feels like waiting

Animations are almost never too short, almost always too long. It is the most common mistake in motion design, and an easy one to make: in a design tool, slow looks smooth. In daily use, slow feels like waiting.

The numbers are surprisingly precise. Around 100 ms for simple feedback like a toggle, 200 to 300 ms for bigger changes like a modal. From 500 ms on, an animation starts to drag, and even the step from 250 to 300 ms is noticeable. Exits can be shorter than entrances, because the user has already decided to move on. Brief and precise beats big and impressive.

Ease out

Nothing in the real world moves at a constant speed. Objects speed up and slow down, which is why linear motion looks mechanical on screen.

Ease-out starts fast and lands softly. The interface reacts the moment you act, and the eye has time to settle on the result. That makes it the right curve for almost everything that enters or responds. Ease-in has exactly one good use: leaving the screen. On anything you are waiting for, it starts slow at the worst possible moment.

Orders

Ease-out: moves the moment you click

Orders

Ease-in: hesitates, then rushes

The more often, the less motion

A transition can be charming the first time, tiresome the tenth and annoying the hundredth. Think of a menu animation that replays every single time and cannot be skipped. The rule is simple: the more often people see an animation, the shorter and quieter it should be. For interactions people repeat all day, the best motion is often none at all.

Onboarding can afford a moment of personality. A command menu that people open eighty times a day cannot. And keyboard actions should not animate at all: whoever presses an arrow key has already decided where to go.

  • New document⌘N
  • Recent files⌘R
  • Invite teammate⌘I
  • Switch project⌘P
  • Settings⌘,
  • Sign out⇧⌘Q

Instant highlight

  • New document⌘N
  • Recent files⌘R
  • Invite teammate⌘I
  • Switch project⌘P
  • Settings⌘,
  • Sign out⇧⌘Q

Lagging highlight

Never block the user

In 2013 I gave a petition its face. The whole demand fit into three words: We want undo. People change their minds, click twice and take a step back. Without a way out, they feel trapped.

Animations can trap people too. A transition that has to finish before anything else works takes away control, a few hundred milliseconds at a time, and every time again. Animations that only fill time are a reliable source of frustration. Good motion can be interrupted. Click again while a panel is still opening, and a CSS transition turns around right where it is. An animation that locks the interface ignores every click until it is done.

Order 1042 2 items

Carrier
DHL Express
Arrives
Tue, 18 Nov
Address
12 Market Street, Berlin

Total €48.00

Turns around when you change your mind

Order 1042 2 items

Carrier
DHL Express
Arrives
Tue, 18 Nov
Address
12 Market Street, Berlin

Total €48.00

Ignores you until it is done

Open a panel and click again while it is still moving.

Less motion, same meaning

For people with vestibular disorders, parallax, zoom and large movements can cause dizziness or nausea. That is why every major operating system offers a setting to reduce motion, and why respecting it is part of accessibility. In my projects, motion gets the same care as contrast, keyboard and focus.

Respecting the setting does not mean switching everything off. Motion should never be the only way to say something important, and a toast that simply pops up is easy to miss. Replace the slide with a short fade, tighten the bounce, and the message stays while the movement goes. Less movement, same meaning.

Profile

Display name: Serkan Z.

Changes saved

Your project is up to date.

Fade only

Profile

Display name: Serkan Z.

Preference ignored

Your system: checking…

Feedback can also stay inside the button. It turns into a small spinner with “Saving…”, then into a check with “Saved”, and after a moment it is a button again. The answer appears exactly where the click happened. With reduced motion, only the words change.

Profile

Display name: Serkan Z.

Experimental. Click Save changes: the answer appears where you clicked.

Make waiting understandable

In 2016 I wrote that what I hate most about my work is the spinning rainbow wheel. I still do, and research explains why. Below 0.1 seconds a reaction feels instant, up to one second people keep their train of thought, after ten seconds their attention is gone. These limits have held for decades.

Motion makes waiting understandable. In one study, people waited about three times longer when they saw an animated progress bar instead of nothing. Show something as soon as possible, because a blank screen looks like an error. Spinners work for two to ten seconds, longer waits need real progress. And a progress bar should start slow and speed up towards the end. The opposite, fast at first and then stuck at 99 percent, is the most frustrating version of all.

Uploading report.pdf 0%

Accelerates towards the end

Uploading report.pdf 0%

Stalls near 99 %

When a page or a list loads, people ask something else: what will be here? A spinner is familiar and says “wait”, but it shows nothing, and then everything pops in at once. A skeleton that mirrors the final layout answers early. People see where the title and the text will be, and the content lands exactly there.

Q3 report

12 charts · updated today

Skeleton: you know where things will be

Q3 report

12 charts · updated today

Spinner: familiar, but nothing to read until it pops in

Before you ship

Before any animation goes live, it has to answer seven questions:

  1. Which question does it answer for the user?
  2. Does it start where the user acted?
  3. Is it as short as it can be without feeling abrupt?
  4. Does it ease out?
  5. How often will people see it?
  6. Can people interrupt it?
  7. What remains when motion is reduced?

Motion is part of how an interface explains itself, so it belongs in the first sketch, not in the last week.

Sources

  1. Apple Human Interface Guidelines: Motion
  2. Nielsen Norman Group: Response Times: The 3 Important Limits (1993)
  3. Nielsen Norman Group: Executing UX Animations: Duration and Motion Characteristics (2020)
  4. Nielsen Norman Group: Progress Indicators Make a Slow System Less Insufferable (2014)
  5. W3C: Understanding SC 2.3.3: Animation from Interactions