Marcus Andrey Study
Ler em português Library

Framework · Motion & interaction · 3 min read

Motion spec sheet

A one-table handoff for a piece of motion: for every layer that moves, the trigger, the property, the start and end values, the delay, duration and easing, the reduced-motion version and what happens if it's interrupted.

1Trigger

What starts it, said as an event the code can wait for.

"The save request succeeds"
2Layer, property

What moves, and which property changes.

Toast · opacity, transform
3From, to

Start and end values, in the units the code uses.

translateY 16px → 0
4Timing

Delay, duration and easing in milliseconds, or the token name.

0 ms · 200 ms · ease-out
5Reduced motion

The calmer version, on the same row.

Fade only, 150 ms
6Interruptions

What happens if the trigger fires again mid-animation.

Replace the text, don't stack

One row per layer and change · a timeline under the table when steps overlap

A motion spec is a table a developer can build from without guessing: six answers per moving layer, with the numbers.

Use it when

  • You hand a microinteraction, a transition or a choreography to a developer.
  • A built animation "doesn't feel like the prototype" and nobody can say why.
  • You document a motion pattern in the design system, so every team builds it the same way.

How to use it

  1. Name the trigger as an event. "The save request succeeds", not "on save". It tells the developer what to wait for. Output: the first line of the spec.
  2. List every layer that moves, and its properties. One row per layer and per property that changes. Prefer transform and opacity; anything else needs a reason. Output: the rows of the table.
  3. Fill in the numbers. From and to, in the units the code uses; delay, duration and easing in milliseconds, with the exact cubic-bezier() or the token name if your system has motion tokens. Output: a row a developer can type in without asking.
  4. Write the reduced-motion version on the same row. Usually a fade, or no movement at all. Not a note at the end that gets lost. Output: a reduced-motion column with no empty cells.
  5. Say what happens when it's interrupted. The trigger fires again, the person navigates away, the request fails halfway. Output: one sentence per pattern.
  6. Add a timeline when steps overlap, and the video. Bars in milliseconds, not frames. Then review the build against the spec, not against memory. Output: the spec, the timeline and a short recording, in one place.

Worked example

A task app for small teams shows a toast when someone saves a task. The designer's spec:

Layer Property From → to Delay Duration Easing Reduced motion
Toast opacity 0 → 1 0 ms 200 ms ease-out opacity only, 150 ms
Toast transform translateY(16px) → 0 0 ms 200 ms ease-out none
Toast (exit) opacity 1 → 0 4,000 ms 150 ms ease-in same

Trigger: the save request succeeds. Interruption: if the person saves again while the toast is showing, replace its text and restart the 4-second timer; don't stack a second toast. The developer builds it in an afternoon and asks one question, about the exit, which goes into the spec for next time.

Watch out for

  • A video as the spec. Developers rebuild it from guesses, frame by frame. Give the numbers; the video is for feel.
  • "On click". Click on what, and before or after the answer? Name the event.
  • Reduced motion in a footnote. It gets skipped. Put it in the row it belongs to.
  • Raw numbers when tokens exist. "200 ms" in the spec and duration-short in the code drift apart. Use the token names.

Template

Copy the table into the ticket or the component page, one row per layer and change.

Pattern: ...
Trigger (an event): ...
Interruption: if ... happens mid-animation, then ...

| Layer | Property | From -> to | Delay | Duration | Easing | Reduced motion |
|-------|----------|------------|-------|----------|--------|----------------|
| ...   | opacity  | 0 -> 1     | 0 ms  | ... ms   | ...    | ...            |
| ...   | transform| ...        | ... ms| ... ms   | ...    | ...            |

Timeline (only if steps overlap): ...
Video: link ...
Source
Timeline in milliseconds, not frames, with a video for feel: Page Laubheimer, Executing UX Animations (NN/g, 2020). Spec fields: the course's motion spec (Lottie, Rive and handing off motion)

"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