Marcus Andrey Study
Ler em português Library

Motion and Interaction · Step 1 · 7 min read

Motion principles for interfaces

Disney's twelve principles of animation were written for characters, not buttons, and only some of them carry over. Which ones do, what interface designers added, and six working principles you can use in any review.

Animators spent decades learning what makes motion believable. Interfaces borrowed the part that makes motion readable. A cartoon has to convince you a drawing is alive. An interface only has to make a change easy to follow. That's why some of the classic principles, timing, easing and staging, are everywhere in good products, and others, like squash and stretch, mostly belong in films. Knowing which is which saves you from both stiff interfaces and cartoon ones.

What you'll be able to do after reading:

  • Name Disney's twelve principles and say which matter for interfaces
  • Know the principles interface designers added, like origin and continuity
  • Explain why where something comes from matters as much as how it moves
  • Use six working principles to review any animation

1. Where the principles come from

In The Illusion of Life (1981), Frank Thomas and Ollie Johnston, two of Disney's senior animators, wrote down the twelve principles the studio had worked out since the 1930s. In 1987, John Lasseter, then at Pixar, showed how they apply to computer animation (Lasseter, SIGGRAPH 1987). In 1993, Chang and Ungar brought them into a user interface, and their list is short and practical: objects should move solidly, "arrive and depart smoothly, without sudden materializations and disappearances", and pace the middle of a transition faster than its ends (Chang and Ungar, UIST 1993).


2. The twelve, read for interfaces

PrincipleIn a filmIn an interfaceUse it?
Squash and stretchA ball flattens when it lands and keeps its volumeA button that gives a little under the fingerRarely, and small
AnticipationA wind-up before the actionA tiny move back before something leavesOnly if it doesn't delay the person
StagingMake the one important action unmistakableOne thing moves at a time; the rest stays stillAlways
Straight ahead and pose to poseDraw frame after frame, or the key poses firstKeyframes: you set start and end, the software fills inIt's how the tools work
Follow-through and overlapping actionHair and clothes keep moving after the body stopsContent settles a moment after its containerYes, by a few tens of ms
Slow in and slow outMore drawings near the poses, fewer in betweenEasingAlways (Step 2)
ArcsLiving things move in curvesA long diagonal move along a gentle arcSometimes
Secondary actionA small gesture that supports the main oneThe icon inside a button reacting to the pressSmall and rare
TimingHow many frames an action takes gives it weightDurationAlways (Step 2)
ExaggerationPush past realism so it readsOvershoot and bounceSparingly, where play fits
Solid drawingForms with weight, volume and depthLayers, shadows and depth that agree with each otherYes (Step 4)
AppealA character you want to watchMotion with the product's characterYes, quietly
Disney's twelve principles, read for interfaces. Four of them do most of the work in a product: staging, timing, slow in and slow out, and follow-through. The rest are spices.Principles from Frank Thomas and Ollie Johnston, The Illusion of Life (1981). Interface column: Marcus Andrey, CC BY 4.0.

Four of them do almost all the work in a product:

  • Timing is duration: how long a change takes gives it weight and tells people how big it is. That's Duration: how long is right.
  • Slow in and slow out is easing: things speed up and slow down instead of moving at one speed. That's Easing curves.
  • Staging is focus: one thing moves, so people know where to look.
  • Follow-through and overlapping action is how parts of a group settle a little after their leader. That's Choreography and stagger.

The others are spices. A squash on a button press, a little anticipation before a card flies away, an overshoot when something lands: they can give a product character, but used everywhere they turn a tool into a cartoon, and they cost time on every use.


3. What interface designers added

Disney's list is about characters. Interface designers have written their own, about how objects relate. The best known is Issara Willenskomer's twelve principles of UX in Motion (2017): easing, offset and delay, parenting, transformation, value change, masking, overlay, cloning, obscuration, parallax, dimensionality and dolly and zoom. He argues against treating Disney's principles as the rules for interface motion, and groups his own under four needs: expectation, continuity, narrative and relationship (Willenskomer, The UX in Motion Manifesto, 2017).

You don't need to memorise the list. Most of it says one thing: motion should keep the link between before and after. The button that becomes a card (transformation), the item that's created from another (cloning), the layers that slide over each other (overlay): in each, the person sees that the new thing came from the old one.


4. Things come from somewhere

Watch where each one comes from.
A cutFine, and honest. Easy to miss if you looked away
From the wrong placeIt moves, but it says the menu lives at the bottom
From its buttonIt grows out of what you pressed: cause, origin and way back
Three ways for the same menu to arrive. Motion always says where something comes from, so a move from the wrong place is worse than no move at all. Live CSS: scale(.85) from transform-origin: top right, 200 ms, ease-out.

Tick the switch and compare the three menus. The cut is fine. The one that flies up from the bottom is worse than the cut: it moves, and the movement says something false, that the menu lives at the bottom of the screen. The one that grows from its button says the true thing: it came from what you pressed, and it will go back there.

That's the most useful principle in this lesson. Motion always tells a story about space, so the story has to be right. Apple puts it in terms of gestures: "if someone reveals a view by sliding it down from the top, they don't expect to dismiss the view by sliding it to the side" (Apple, Human Interface Guidelines: Motion). Step 4 builds a whole spatial model on it, in The spatial model of an interface.

In CSS, the origin is one line. This is the rule the third menu uses:

.mo-a-near .mo-a-pop { transform: scale(.85); transform-origin: top right; transition: opacity 200ms ease-out, transform 200ms ease-out; }

5. Six working principles

For reviews, this course uses six. Each one is a question you can ask of any animation:

  1. It has a job. Feedback, state change, orientation, relationship or attention (What motion does in an interface).
  2. It comes from somewhere true. It starts where its cause is and goes back the same way.
  3. It starts at once. Within about 0.1 second of the action, so it reads as caused by it (Aurora Harley, NN/g, 2014).
  4. It eases. It doesn't start or stop at full speed; linear motion "looks weird and unnatural" (Page Laubheimer, NN/g, 2020).
  5. One thing leads. One element carries the change; the rest follow it or stay still.
  6. The same move means the same thing. If sliding from the right means "deeper", it means that everywhere. Apple asks for feedback motion that "follows people's gestures and expectations" (Apple HIG: Motion).

And under all six, from the last lesson: it's brief, it can be interrupted, and it has a reduced-motion version.


6. Common mistakes

  • Treating Disney's twelve as a checklist for interfaces and adding squash, stretch and bounce everywhere.
  • Motion that starts from the wrong place: a menu that comes from the centre of the screen, a dialog that drops from the top when its button is at the bottom.
  • Two leaders at once: the page slides while the header also bounces.
  • The same gesture animated three different ways in three parts of the product.

7. Vocabulary

Term Meaning
Timing How long an action takes; in interfaces, duration
Slow in and slow out Speeding up from rest and slowing into rest; in interfaces, easing
Staging Making the one important action clear, so the eye knows where to go
Follow-through Parts that keep moving a moment after the main body stops
Origin The place an element seems to come from; in CSS, transform-origin
Continuity The link between before and after that motion keeps visible

8. Try it (no tools needed)

  1. Open three menus, dialogs or panels in apps you use.
  2. For each, say where it comes from and where it goes when you close it.
  3. Check: does that match where its button is?

Reflection questions: Did any of them come from somewhere that made no sense? Would you have noticed if you hadn't been looking?


9. If you already practise

  • Add "origin" to your motion specs: which element or edge the motion starts from, and where it returns.
  • Use the six principles as the motion part of your critique template, one line each. Reviewing motion in critique has a fuller version.
  • Decide, as a team, which "spice" principles your product uses at all. Writing "we don't bounce" in the design system is a decision too.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

What motion does in an interface · Audit the motion in your product · The spatial model of an interface · Shared element transitions · Gestalt principles · Twelve principles of animation for UI

Saved only on this device.

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