Marcus Andrey Study
Ler em português Library

Framework · Motion & interaction · 4 min read

Twelve principles of animation for UI

Frank Thomas and Ollie Johnston's twelve principles of animation, sorted for interfaces: four that do almost all the work in a product, and eight that are spices, so you can review motion with a shared vocabulary instead of taste.

1Timing

Duration gives weight and shows how big the change is.

Core in every product
2Slow in, out

Things speed up and slow down: easing.

Core in every product
3Staging

One thing moves, so people know where to look.

Core in every product
4Follow-through

Parts of a group settle a little after their leader.

Core in every product
5Arcs

Natural paths curve; in interfaces, a true origin matters more.

Sometimes
6Anticipation

A small move before the main one.

Rare moments only
7Squash, stretch

Shape changes to show speed and weight.

Rare moments only
8Exaggeration

More than real, to make a point.

Rare moments only
9Secondary action

A smaller move that supports the main one.

Rare moments only
10Pose to pose

Planned key poses versus drawing frame by frame.

In UI: keyframes
11Solid drawing

Forms that feel three-dimensional.

In UI: your visuals
12Appeal

A character people want to watch.

In UI: your brand

Review every animation with 1 to 4, allow 6 to 9 only on rare moments

Thomas and Johnston's twelve principles, sorted for interfaces: four core ones, four spices, and four that belong to drawing characters.

Use it when

  • A motion review goes in circles ("it feels heavy", "it's too much") and you need words everyone shares.
  • A designer adds bounce, squash or anticipation everywhere and you want to say where it belongs and where it doesn't.
  • You write the motion section of a design system and want principles with a known origin.

How to use it

  1. Start from the four that matter. For each animation, ask about timing (does the duration match the size of the change?), slow in and slow out (does it ease instead of moving at one speed?), staging (does one thing lead, so people know where to look?) and follow-through (do the parts of a group settle a little after their leader?). Output: four answers per animation.
  2. Check the story about space. Motion always says where something came from. Make sure it starts at its cause and goes back the same way. This is staging and arcs read for interfaces. Output: a yes or no per animation, with the wrong origin named.
  3. Treat the spices as exceptions. Squash and stretch, anticipation, exaggeration and secondary action can give a product character, but only on rare moments: a first success, an empty state. Not on a button people press twenty times a day. Output: a short list of where spices are allowed.
  4. Drop the ones that don't apply. Solid drawing, appeal, and straight ahead versus pose to pose are about drawing characters. In interfaces they become "use your design system's visuals" and "use keyframes", which you already do. Output: nothing, once the team agrees.
  5. Turn the result into review questions. Write the four core principles and the space check as questions in your critique template, so every review asks the same things. Output: five review questions.

Worked example

A task app for small teams animates a card when it's deleted from a board: it shrinks with a bounce, jumps up a little, then flies to the bin icon in the top bar in 700 ms. The review, with the principles:

Principle What the team saw Change
Timing 700 ms for an action people do many times a day 200 ms
Slow in and slow out Linear flight Ease out, so it leaves quickly
Staging The card and the whole column move at once The card leaves first, the column closes after
Follow-through The column snaps shut The cards below slide up and settle
Anticipation, squash The jump and the bounce before it leaves Removed: a spice on a frequent action
Space It flies to a bin in the top bar that has nothing to do with the card It fades out in place; "Undo" appears in a toast

The new version is shorter, and it says the true thing: the card is gone from this column, and you can bring it back.

Watch out for

  • The twelve as a checklist. Ticking all twelve gives you a cartoon. Most of them are for characters.
  • Spices on frequent actions. Bounce and anticipation are charming once and slow on the twentieth time.
  • Two leaders at once. If the page slides while the header bounces, nobody knows where to look. One thing leads.
  • Principles without the reduced-motion version. Whatever the principles say, the motion still needs a version for people who asked for less.

Template

Copy these questions into your motion review or critique notes.

Animation: ...
Job (feedback / state change / orientation / relationship / attention): ...

Core four
- Timing: does the duration match the size of the change? ... ms
- Slow in and slow out: does it ease? Which curve? ...
- Staging: what leads? Does anything else move at the same time? ...
- Follow-through: do the parts of a group settle after their leader? ...

Space
- Does it start where its cause is, and go back the same way? ...

Spices (squash, anticipation, exaggeration, secondary action)
- Used? Where? Is this a rare moment? ...

Reduced-motion version: ...
Source
Frank Thomas and Ollie Johnston, The Illusion of Life (1981). Applied to computer animation: John Lasseter (SIGGRAPH, 1987). Applied to user interfaces: Bay-Wei Chang and David Ungar (UIST, 1993)

"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