Workshops · Free, for designers

Motion design in UX: a field guide

Everything you need to know about motion in UX: why it exists, a mental model, spring or easing, timing, choreography, space and accessibility. By the end you have the rules, the numbers, and the questions to ask before you animate anything.

Published Updated 6 min read

Format
Field guide · workshop
Length
20 minute read
Audience
Designers and design engineers
Hands-on
Figma Smart Animate practice
On this page
  1. Why motion exists
  2. The pen on the table
  3. Spring or easing
  4. Duration that works
  5. The 100 ms rule
  6. Choreography
  7. The spatial model
  8. Accessible motion reaches more people
  9. The whole guide in three rules
  10. What people said
  11. Keep reading

Why motion exists

Start with biology, then get to craft.

Nothing in the world holds still. Motion is how we have always read change. Long ago, movement meant predator or prey, so our eyes learned to catch it before we even think. That same wiring fires in a product. If you animate something, the user will notice. Every time.

So every animation spends attention. To spend it well, make sure each one does one of the six jobs below. If it does none of them, it is decoration, and decoration takes without giving anything back.

Feedback

We got your action

A button squashing on press confirms the tap landed.

Status

Here’s what the system is doing

A loading card moving through named states.

Spatial orientation

Here’s where you are

A card flip showing the profile on its back.

Relationship

These things are connected

A dropdown opening out of the button that triggered it.

Focus

Look here next

An error field shaking to catch your eye.

Continuity

Same thing, it just changed

A shared element carrying across two screens.

The pen on the table

One mental model holds the whole guide together.

Picture every animation as a pen sliding across a table toward a spot. Push the pen. Friction slows it down. Put a wall at the end and it bounces back. That is a spring. Three numbers describe every interaction you will ever animate.

Mass

Weight of the pen

How heavy the element feels and how hard it snaps. Buttons are light. Modals are heavy.

Damping

How sticky the table is

How fast the motion loses energy. Too little and it bounces forever. Too much and it drags.

Stiffness

The wall at the end

How eagerly the element comes to rest. High stiffness snaps. Low stiffness drifts.

Damping, as a share of critical
60 to 80 percentInteractive (buttons, toggles)
85 to 95 percentNavigation (modals, sheets)
95 to 100 percentFunctional states (errors)
Where to start
Stiffness300
Damping25
Mass1
Fits80 percent of UI

Spring or easing

One question tells you which to reach for: did the user touch it directly?

Yes, use a spring. Buttons, drags, toggles, sliders. Anything that reacts to how fast you move. No, use easing. Page changes, loading states, timed transitions. Anything that needs a set duration.

Spring

  • Button press
  • Drag and drop
  • Toggle, pull, pinch
  • Anything driven by how fast you move

Easing

  • Page transitions
  • Loading states
  • Modal in, modal out
  • Anything that has to stay in sync

Ease-out

Arriving

Fast start, slow finish. Use it for entrances. Feels like a bowling ball rolling to a stop.

Ease-in

Leaving

Slow start, fast finish. Use it for exits. Feels like a rocket launch. The user asked for it, so commit.

Ease-in-out

Travelling

Slow, fast, slow. Use it when something moves between two known points. Like a train pulling into a station.

Duration that works

The 150 to 250 millisecond rule.

Under a hundred milliseconds, the user misses it. Over four hundred, the user is waiting. The band in the middle handles about eighty percent of UI work. Two rules size the rest, and one more sets how entrances relate to exits.

By size of element
Badge, icon, chip100 to 150 ms
Button, toggle, card150 to 250 ms
Modal, drawer, sheet300 to 400 ms
Full screen transition400 to 500 ms
By direction
Entranceease-out, 300 ms
Exitease-in, 150 ms
Ruleexits are always faster
Whythe user already decided

The 100 ms rule

Where direct manipulation lives.

100 msThe window where the user feels they caused it

Flip a light switch and the bulb seems to fire the instant your finger moves. It doesn’t. Your brain glues the two events together because the gap is short enough to feel like cause and effect. That is direct manipulation.

Press feedback has to begin within a hundred milliseconds of the tap. It only has to start there; it can finish later. Past that window, the user stops feeling like they are touching the interface and starts feeling like they are waiting on software.

60 frames per second

16.67 ms per frame. Stay under that and the eye sees smooth motion. Go over and it sees jank. Animate only transform and opacity. Width, height, top, and left repaint the whole layout every frame.

Attention budget

One main animation at a time. When several things move at once, they cancel each other out. The eye should always know where to look.

Choreography

Order, timing, and the eye.

When more than one element moves at once, the order and timing decide whether it feels deliberate or chaotic. Three patterns cover everything you will build.

Simultaneous

Move as one

Use it when the elements really are one thing. A button label and its background. A card and its shadow.

Sequential

Wait, then go

Each step waits for the one before it to finish. Loading badge, finding profile, ready. The order shows what depends on what.

Staggered

Offset, overlapping

Elements start a beat apart. Lists, grids, parallel groups. Space them 20 ms to 60 ms apart, top to bottom.

The spatial model

Where things live decides how they move.

Every element on screen lives somewhere. Its motion has to match that spot. A modal that slides in from the left and leaves out the top reads as broken, even if the user can’t say why. The three axes give you the vocabulary.

X axis

Left is back, right is forward

Navigation, onboarding, step flows. Moving right reads as progress. Moving left reads as going back.

Y axis

Top is navigation, bottom is action

Notifications drop from the top. Sheets and modals rise from the bottom. Action lives where the thumb is.

Z axis

Front is focused, back is dismissed

Modals come forward and the background dims behind. Z shows hierarchy and where the user should look.

Accessible motion reaches more people

Accessibility is scale.

35%of adults over forty have vestibular disorders

The vestibular system is your inner ear balance system. When the motion your eyes see clashes with what it expects, the brain gets mixed signals. That brings on nausea, dizziness, and headaches. Real symptoms, set off by animation on a screen.

Reduced motion still leaves you plenty. Color transitions, opacity changes, type changes, and icon swaps are all still fair game. What you cut is staggered timing, parallax, big scale transforms, and bouncy springs.

Swap this for this
Slide transitionCrossfade
Scale or zoomOpacity fade
ParallaxStatic layers
Bouncy springNear-critical or instant
Auto-playing loopPause on load, play on tap
WCAG guardrails
2.2.2 (AA)Auto-play over 5 s needs pause
2.3.3 (AAA)Let users turn off interaction motion
DefaultHonor prefers-reduced-motion
PrincipleMotion is a language not everyone reads

The whole guide in three rules

If you remember three things.

Rule 01

Entrance ease-out, exit ease-in.

Apply this to every animation you already have. It makes them better on the spot.

Rule 02

Press feedback under 100 ms.

That window is what makes touch feel real. Begin inside it. Finishing can take longer.

Rule 03

Name what the motion says.

If you can’t name it, cut it. If you can, make the motion say exactly that and nothing else.

What people said

“Thank you for today’s session on motion design in UX. I feel like a Figma physicist now.”
Product Designer, from the room
“Yes! So informative in such a short amount of time. Part two when?”
UX Designer, from the room

Topics: motion design, accessibility, workshops. Also as plain markdown.