Marcus Andrey Study
Ler em português Library

Framework · Motion & interaction · 3 min read

Duration scale

Four steps of duration, from about 100 ms for feedback to about 400 ms for full-screen moves, picked by size and then adjusted for frequency and for whether something arrives or leaves, so every animation in a product gets its length from one short list.

  1. About 100 ms
    Feedback
    Feels like part of your finger
    For example
    A toggle, a checkbox, a press
  2. About 200 ms
    Small move
    Seen, but over before you wait
    For example
    A menu, a tooltip
  3. About 300 ms
    Big change
    Long enough to follow where it went
    For example
    A dialog, a side panel
  4. Up to 400 ms
    Full-screen
    The slow end; only for large moves
    For example
    A sheet crossing the screen

Exits about two thirds of entries. At 500 ms it feels like a drag.

Four steps of duration, chosen by how much of the screen changes and shortened for things people meet often.

Use it when

  • You set durations for a new component or flow and don't want to guess.
  • An animation feels slow, and nobody can say whether it's the duration or the easing.
  • You turn a product's scattered durations into a few tokens.

How to use it

  1. Start from size and distance. The more of the screen a change covers, or the further something travels, the higher the step. A checkbox is feedback, a menu is a small move, a dialog or a panel is a big change, a page or sheet crossing the screen is full-screen. Output: a starting step for each animation.
  2. Take the step's value. About 100 ms for feedback, about 200 ms for small moves, about 300 ms for big changes, up to about 400 ms for full-screen moves. Output: one starting duration in milliseconds.
  3. Shorten for frequency. The more often people meet it, the further down its range it goes. A menu opened fifty times a day gets the short end. Output: frequent animations moved down.
  4. Make exits shorter than entrances. An arrival has to be seen; an exit only has to get out of the way. Start with an exit at about two thirds of the entrance and adjust. Output: an entry and an exit duration for each thing that comes and goes.
  5. Check the two limits. Feedback starts within about 0.1 second of the action, and no transition should get near 1 second. Output: nothing late, nothing that stalls the flow.
  6. Write it in milliseconds, from a token. Frames change with the refresh rate; milliseconds don't. Map every duration to a step of your scale. Output: a spec with a duration token per animation.

Worked example

A task app for small teams had 11 different durations, from 150 to 800 ms. The team mapped each animation to a step:

Animation Step Entry Exit
Tick a task as done Feedback 100 ms
Open the "Sort by" menu (used all day) Small move 150 ms 100 ms
Open a task's detail panel Big change 300 ms 200 ms
Switch to another board Full-screen 350 ms 250 ms

Eleven durations became four steps. The board switch had been 800 ms, twice the top of the scale. Nobody had noticed it in reviews, where it looked smooth; people using it every day had.

Watch out for

  • Durations set in a review. In a review you watch each animation once, so long looks good. People meet it a hundred times.
  • One duration for everything. Small things then feel slow and big things feel rushed.
  • Exits as slow as entrances. The person has already moved on; the interface hasn't.
  • Fixing the curve when the duration is the problem. A "faster" easing can't save an animation that is simply too long.

Template

Copy this into the motion section of your design system, and change the values only with a reason.

Duration scale (milliseconds, not frames)

Step          Token                  Entry    Exit (about 2/3)   Use for
Feedback      motion.duration.xs     100 ms   -                  toggles, checkboxes, presses
Small move    motion.duration.sm     200 ms   150 ms             menus, tooltips, small reveals
Big change    motion.duration.md     300 ms   200 ms             dialogs, panels, cards that expand
Full-screen   motion.duration.lg     400 ms   250 ms             pages, sheets crossing the screen

Rules: frequent animations take the short end of their step.
Feedback starts within 0.1 s. Nothing goes past 500 ms without a reason written here.
Source
Duration ranges and shorter exits: Page Laubheimer, Executing UX Animations: Duration and Motion Characteristics (NN/g, 2020). The 0.1 and 1 second limits: Jakob Nielsen, Response Times: The 3 Important Limits (NN/g, 1993), from Card, Robertson and Mackinlay (CHI 1991). Duration tokens: Material Design 3, Easing and duration
Where to find it
Motion and Interaction Design: Duration: how long is right › The duration ladder, Motion tokens

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close