Skip to content
Book a call
UI Design

Micro-interactions that inform, and how to respect reduced motion

Good motion tells people what changed. We share timing ranges, easing choices and how to respect the reduced-motion setting without losing feedback.

MD Rakib Shekh5 min read
Cover illustration for the article "Micro-interactions that inform, and how to respect reduced motion"

Motion can make a product feel clear, or it can make it feel slow and noisy. The difference is simple. Good motion answers a question: what just changed, where did it go, did my click work?

This post is the short list we use when we design small animations for product UI. It also covers the reduced-motion setting, which too many sites ignore. You can see some of our own interface experiments in the Lab, and motion is part of what we cover in our design and build services.

Give every animation a job

Before adding motion, ask what job it does. Here are the jobs that are worth it.

  • Show a change of state. A toggle slides. A row fades out after delete.
  • Show where something came from or went. A menu grows from its button. A card flies to the cart.
  • Confirm an action. A button briefly shows a check mark after saving.
  • Guide attention. A new item gets a short highlight so the eye finds it.
  • Show that the product is working. A small loader, a progress bar.

If an animation does none of these, it is decoration. Decoration is fine in moderation, such as on a marketing page. In a tool people use all day, it turns into a tax. The hundredth time someone sees a slow fade, it costs them time.

Timing ranges that usually work

There is no single right number, and the best duration depends on the distance and the size of the element. But these ranges are a good starting point for web UI.

What movesTypical duration
Hover and press feedbackabout 100 to 150 ms
Small changes: toggles, tooltips, dropdownsabout 150 to 250 ms
Larger elements: modals, side panelsabout 250 to 400 ms
Full page or large layout change400 ms at most, usually less

These are our rules of thumb, not a standard. The idea behind them is well known: people read a response under about a tenth of a second as instant, and longer waits start to feel like waiting. So feedback on a click should be near that edge, and big movements can take a bit longer because they cover more distance.

Closing should be faster than opening. When something leaves, the user has already moved on.

Easing: pick by what the element is doing

Easing is how speed changes during the movement. Three choices cover most work.

  • Ease-out (fast start, slow end): for things that enter. They arrive quickly and settle gently. This is the default for most UI.
  • Ease-in (slow start, fast end): for things that leave. They pick up speed and get out of the way.
  • Linear: for things that run at a constant rate, like a progress bar or a looping spinner.

Avoid bouncy springs in serious tools such as finance or admin screens. A little overshoot can feel friendly in a consumer app, but it also feels unsteady when someone is checking numbers.

Feedback on actions

The most useful micro-interaction is the quiet answer to "did that work?"

  • A pressed button should change at once, even if the real work takes a second.
  • A save should show a clear result: "Saved" for a moment, or an error that stays.
  • An item added to a list should appear in place and be easy to spot.
  • A form error should appear next to the field, not only at the top.

Do not make users wait for an animation to finish before they can continue. Animations should run alongside the next step, not block it.

Respect prefers-reduced-motion

Some people get dizzy or sick from on-screen movement, especially large slides, zooms and parallax. Operating systems have a setting for this. Browsers pass it to your CSS as prefers-reduced-motion. MDN documents it at developer.mozilla.org.

@media (prefers-reduced-motion: reduce) {
  * {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    scroll-behavior: auto !important;
  }
}

That block is a blunt tool, and it is better than nothing. A more careful approach is to keep the feedback and drop the movement:

  • Replace slides and zooms with a quick fade.
  • Keep colour changes and small state changes. They do not cause motion sickness.
  • Stop auto-playing video, looping animation and parallax.
  • Do not remove the information the motion carried. If an item used to fly into the cart, show a clear "Added" message instead.

"Reduce" does not mean "none". It means less movement.

WCAG 2.2 also has a related success criterion, 2.3.3 Animation from Interactions, at level AAA. Most teams aim for AA, but the idea is a good one to follow. This is design guidance and not legal advice.

Performance

A smooth animation is also a cheap one. In CSS, changing transform and opacity is usually handled by the browser's compositor and stays smooth. Animating width, height, top or left forces the browser to recalculate layout on every frame, and that is where jank comes from.

  • Animate transform and opacity where you can.
  • Use will-change sparingly, only on elements that really will animate.
  • Test on a mid-range phone, not only on your laptop.
  • Keep the number of things moving at once small.

If an animation drops frames on a cheap phone, shorten it or remove it. A missing animation is better than a stuttering one.

A short checklist

  1. Can you say what job each animation does?
  2. Is it under about 400 ms?
  3. Does it ease out when entering and ease in when leaving?
  4. Does it still make sense with reduced motion turned on?
  5. Does it run smoothly on a phone?

If you would like a review of the motion in your product, we can include it in a UX review or design project. Tell us what you are working on at the contact page.

Want a second pair of eyes on your product?

Send your site or app and get a free design review from Rakib. No sales call, no cost.