Marcus Andrey Study
Ler em português Library

Motion and Interaction · Step 1 · 6 min read

Audit the motion in your product

Motion piles up: one designer adds a slide, another a bounce, a library brings its own fades, and nobody owns the whole. How to record, list and judge every moving moment in a task, measure its timing without special tools, and decide what to keep, fix or cut.

Nobody designs a product's motion all at once. It piles up, one animation at a time, until nobody knows what moves or why. One designer added a slide to the menu three years ago. A component library brought its own fades. A developer copied a bounce from a tutorial. Each one made sense alone. Together they make a product that moves in five different ways. An audit is how you see the whole, and it takes about an hour for one task.

What you'll be able to do after reading:

  • Record and list every moving moment in a real task
  • Measure a duration from a screen recording, frame by frame
  • Judge each moment by its job, its frequency and its reduced-motion version
  • Turn the audit into a short list of decisions people can act on

1. Six steps

  1. 1Record

    Screen-record one real task, start to finish.

  2. 2List

    Every moment something moves.

  3. 3Describe

    Trigger, what moves, duration, easing.

  4. 4Name the job

    Feedback, state, orientation, relationship, attention, or none.

  5. 5Count and check

    How often it happens; what reduced motion does.

  6. 6Decide

    Keep, fix or cut, with one reason.

A motion audit in six steps, about an hour for one task. The recording matters: you can't judge timing from memory.Diagram: Marcus Andrey, CC BY 4.0.

Start with one task, not the whole product. A task that people do every day shows the motion that matters most: the moments they meet dozens of times. Pick something like "find an item, save it, come back to it".

The recording is the important part. Memory is bad at timing: you remember that the menu slides, not that it takes 600 ms. And watching a recording at normal speed, you feel the waits the way users do.


2. What to write for each moment

For every moment something moves, fill one row:

  • Moment: a short name people will recognise.
  • Trigger and what moves: the tap, hover, scroll or system event, and which element changes how.
  • Duration and easing: measured, not guessed (next section).
  • Job: feedback, state change, orientation, relationship, attention, or none (What motion does in an interface).
  • How often: once, a few times a session, or all the time (When not to animate).
  • Reduced motion: what happens with the setting on.
  • Decision: keep, fix or cut, with one reason.

Here's a filled-in example:

MomentTrigger · what movesDuration · easingJobHow oftenReduced motionDecision
Save a recipe (heart)Tap · heart grows to 140% and bounces450 ms, bounceFeedbackMany times a sessionSame bounceFix: 150 ms, scale to 115%, a fade with reduced motion
Side menuTap menu icon · panel slides from the left600 ms, ease-in-outOrientationSeveral a sessionSame slideFix: 300 ms in with ease-out, 200 ms out; a fade with reduced motion
Card to recipeTap card · card grows into the page350 ms, decelerateOrientation, relationshipManyCrossfadeKeep
Home carouselPage load · slides change every 4 s, forever500 ms slideNoneEvery visitKeeps movingFix: no autoplay, or a visible pause (WCAG 2.2.2)
Cooking timerStart timer · ring fills as time passesThe timer's length, linearState (time left)While cookingSameKeep: the movement is the information
"Saved" messageSave · bar slides up, stays 4 s200 ms, ease-outFeedbackA fewFadeKeep; check it doesn't cover the button
Headings on scrollScroll · each heading fades and rises400 ms eachNoneEvery scrollSameCut
A filled-in motion audit of one task in a recipe app: find a recipe, save it, start cooking. Seven moments, two jobless. The two numbers that decide the most are the job and how often it happens.Example app and audit: Marcus Andrey, CC BY 4.0.

Read the decisions column and you can see the method. The card that grows into its page does two jobs and has a reduced version: keep. The heart that bounces does a real job, but too slowly for something people do all the time: fix the timing. The headings that rise on scroll do no job and play on every scroll: cut. The carousel is the most urgent, because it fails an accessibility rule: anything that moves on its own for more than five seconds next to other content needs a pause (W3C, Understanding 2.2.2).


3. Measuring without special tools

You don't need motion software to get real numbers.

  • Count frames. Record the screen at 60 frames per second. Each frame is about 16.7 ms. Pause the recording where the motion starts, step frame by frame to where it stops, and multiply: 18 frames is about 300 ms. Many video players step one frame with the arrow keys when paused.
  • On the web, use the browser. Chrome's DevTools has an Animations panel that captures animations as they play, so you can "slow down, replay, or inspect the source code" of each one (Chrome for Developers, Inspect animations). The source gives you the exact duration and easing.
  • On Android, slow everything down. The developer options have animation scale settings that change the playback speed of window and transition animations, so you can see what's happening (Android Developers, developer options).
  • Check reduced motion. Turn the setting on in the operating system and record the task again. Compare the two recordings side by side.

Easing is harder to measure than duration. For an audit, a word is enough: "slows into place", "starts slow", "even speed", "bounces". The exact curve comes from the code or the design file.


4. From findings to decisions

An audit that ends as a spreadsheet changes nothing. Sort the rows into an order people can act on:

  1. Harm first. Anything that fails WCAG or ignores reduced motion, anything large that moves on its own. These are bugs, not taste. See WCAG and motion.
  2. Then frequency times cost. A slow animation people meet fifty times a day costs more than a showy one they see once. Fix the frequent ones first.
  3. Then consistency. If the same kind of move, like "a panel opens", has three different timings, pick one. That choice is the start of your Motion tokens.
  4. Then the jobless. Cut them, or ask what they were for. Sometimes the answer is a real job done badly, and that's a fix, not a cut.

Write each decision as a change someone can make: "side menu: 300 ms in, 200 ms out, ease-out in, fade with reduced motion". Not "make the menu feel snappier".


5. Common mistakes

  • Auditing the whole product at once, and never finishing.
  • Guessing durations instead of measuring them.
  • Judging every animation by watching it once.
  • Leaving reduced motion out of the audit.
  • Ending with "the motion feels inconsistent" instead of a list of changes.
  • Cutting motion that does a real job because it's done badly.

6. Vocabulary

Term Meaning
Motion audit A list of every moving moment in a task, with its job and a decision
Moment One thing that moves, from its trigger to its end
Frame One picture in a recording; at 60 fps, about 16.7 ms
Frequency How often one person meets the moment
Jobless motion Motion that does none of the five jobs

7. Try it (no tools needed, or your phone)

  1. Pick one everyday task in a product you work on, or one you use.
  2. Record it with your phone's screen recorder.
  3. Watch it back and list every moment something moves, with its job.
  4. For the three you meet most often, count frames and work out the duration.

Reflection questions: How many moments had no job? Which one would you fix first, and why that one?


8. If you already practise

  • Run the audit with a developer. They can read the real values from the code in minutes, and they'll know which fixes are cheap.
  • Repeat it after every big release, on the same task, so you can see whether motion is getting more consistent or less.
  • Use the audit's "how often" column to argue for fixes: frequency is the number that convinces product managers.
  • The lab Audit a page for reduced motion goes deeper on the accessibility side.

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.

When not to animate · Motion tokens · Audit a page for reduced motion · Heuristic evaluation · Duration: how long is right

Saved only on this device.

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