Motion and Interaction · 9 min read
Motion and Interaction Design
Timing, easing, feedback and transitions: how movement explains an interface instead of decorating it, in CSS, in Figma and in a design system. With labs.
Seven steps in order, then five labs and a part for people who lead design teams. Every demo is live in the page, and every claim links to its study or standard.
Step 1 · Why motion
- What motion does in an interfaceMotion is not decoration: it's how an interface shows a change instead of leaving people to spot the difference between two screens. The five jobs motion does, why the eye can't ignore it, and what the research says it improves.
- When not to animateThe most useful motion skill is knowing when to leave it out. Five questions to ask before any animation, why the third time matters more than the first, and the motion that makes some people physically unwell.
- Motion principles for interfacesDisney'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.
- Audit the motion in your productMotion 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.
Step 2 · Timing and easing
- Duration: how long is rightMost interface motion should last between 100 and 400 milliseconds, and most of it is too slow. Where those numbers come from, the three things that change them (size, frequency, and whether something arrives or leaves), and how design systems turn them into tokens.
- Easing curvesEasing is how motion speeds up and slows down, and it changes how an animation feels more than its duration does. How to read an easing curve, what the CSS keywords really are, which curve to use for things arriving, leaving and moving, and how to write easing so a developer builds what you meant.
- Springs and physicsA curve describes a motion; a spring describes a force, and the motion follows. Why Apple and Android now use springs by default, how one spring is described with duration and bounce or with damping and stiffness, how to fake one in CSS with linear(), and when a bounce is worth it.
- Choreography and staggerWhen several things move at once, someone has to lead. How to choose the leader, offset the rest, stagger a list without making people wait for the last row, and write it all down as a timeline a developer can build.
Step 3 · Feedback and microinteractions
- Anatomy of a microinteractionA microinteraction is one small moment with one job: mute, like, save, switch on. Dan Saffer's four parts (trigger, rules, feedback, loops and modes) turn it from a nice animation into a design you can spec, test and hand off.
- Interactive states: hover, press, focusEvery control answers before it acts: hover says "you can press me", press says "I felt that", focus says "you are here". What each state is for, how fast it should appear, how Material builds them all from one layer, and why the focus ring is the one you can never drop.
- Feedback while waitingWaiting is part of every product. What to show at 0.1, 1 and 10 seconds, when a skeleton beats a spinner, why a progress bar should be honest, and what forty years of research say about making waits feel shorter without lying.
- Gestures and direct manipulationWhen you drag, swipe or pinch, the interface should move with your hand, not after it. What direct manipulation means, the feedback each gesture owes, why a gesture is always a shortcut and never the only way, and what WCAG 2.2 asks for dragging and multi-finger gestures.
Step 4 · Transitions and space
- The spatial model of an interfacePeople remember where things are, even on a flat screen. Motion is how an interface tells them where a screen came from and where it went. How to map an app as a space, the three directions most products use, and the one promise every transition has to keep.
- Navigation transitionsMoving between screens is the biggest motion in most products, and the one people see most. How to choose a transition from the relationship between two screens, why entering is slower than leaving, the real durations and curves, and a push-and-back sketched in CSS with no script.
- Shared element transitionsWhen the photo on a card becomes the photo on the next page, people don't have to look for it. What a shared element is, when Material's container transform fits, how the View Transition API does it in a browser, and how to keep it short, honest and safe for reduced motion.
- Scroll and motionScrolling is the movement people make most, and the one they expect to own. Which scroll effects help (a reading bar, a short reveal, snapping), which ones hurt (parallax, scrolljacking), and how CSS scroll-driven animations tie motion to the scroll itself, with reduced motion built in.
Step 5 · Motion in code and tools
- CSS transitions and animationsCSS has two ways to move things: a transition between two states, and keyframes that run a sequence on their own. What each is for, the few properties that matter, how to animate an element appearing, and why every animation needs a reduced-motion answer from the first line.
- Web Animations and View TransitionsTwo browser APIs that go past CSS alone: the Web Animations API, which lets code play, pause and reverse an animation, and View Transitions, which animate between two states of a page, or two pages. What each does, what a designer needs to know to spec them, and where they work as of November 2026.
- Prototyping motion in FigmaFigma now has two ways to make things move: prototype transitions with Smart animate, and the Figma Motion timeline with keyframes. How Smart animate matches layers, which easing and spring presets it offers, when to use the timeline instead, and how to make a prototype that tells the truth about the motion you'll ship.
- Lottie, Rive and handing off motionSome motion is code, some is a file. When CSS is enough, when an illustrated animation should ship as a Lottie, when it needs Rive's state machines, and how to hand off any of them with a motion spec a developer can build from without guessing.
- Motion performanceSmooth motion is a budget: about 10 milliseconds of work per frame. How the browser draws a frame, why transform and opacity are cheap and width and top are not, what will-change really does, and how to check an animation instead of hoping.
Step 6 · Motion and accessibility
- Vestibular disorders and reduced motionFor some people, motion on a screen causes dizziness, nausea or migraine, sometimes for hours. What the vestibular system does, which kinds of on-screen motion are most likely to trigger symptoms, where the reduce-motion setting lives on each device, and how a page can hear it.
- WCAG and motionFour WCAG success criteria cover motion: pausing things that move by themselves, flashing that can cause seizures, and turning off motion that interactions trigger. What each one asks in plain words, its level, how to test it, and the techniques W3C lists to meet it.
- Designing a reduced-motion versionA reduced-motion version is a design, not a switch that turns everything off. How to keep what each motion means while dropping the travel, a table of common motions and their reduced versions, two ways to write it in CSS, and how to test it.
Step 7 · Motion systems
- Motion tokensA duration typed by hand is a decision nobody can find again. How to turn durations and curves into a small set of named tokens, in three tiers, in the W3C community format and in CSS, with reduced motion built in.
- What public motion guidelines teachMaterial Design 3, IBM Carbon, Microsoft Fluent 2 and Atlassian all publish their motion rules. What their duration scales and curves have in common, where they differ, and which ideas are worth borrowing for your own system.
- Documenting motion in a design systemMotion is the hardest part of a design system to write down, because a still page can't show it. What a motion section contains, how to document one pattern on one card, why every spec needs a live demo and a reduced-motion line, and how to start small.
Labs
- Animate a button's statesA guided lab: write a state sheet for one button (rest, hover, press, focus), give each state a duration and a curve from tokens, build it in CSS, and make a reduced-motion version. About an hour, with a code editor or CodePen.
- Build a page transitionA guided lab: pick two pages with a clear hierarchy, decide the direction and the tokens, build a cross-document view transition in CSS only, give it a reduced-motion version and test it. About an hour and a half, with two HTML pages on any local server.
- Write a set of motion tokensA guided lab: collect every duration and curve a product uses, group them by job, reduce them to a small scale, name semantic tokens, add reduced-motion values, and write the set in the DTCG format and in CSS. About two hours, with a codebase or a set of screens and a spreadsheet.
- Audit a page for reduced motionA guided lab: list every motion on one page, switch on Reduce motion and walk it again, match each motion to the WCAG criterion that covers it, and write a prioritised fix list. About an hour, with a browser and the system setting.
- Prototype a microinteraction in FigmaA guided lab: map a Save button's microinteraction on paper, build it as one interactive component with five variants, wire the triggers with Smart animate and your motion tokens, make a reduced-motion version and hand it off. About an hour and a half, with a free Figma account.
For leads
- Motion in design system governanceFor leads: how to keep a product's motion consistent after the tokens ship. Who owns motion, how a new animation gets into the system, which rules keep the set small, and how to audit and retire motion over time.
- Reviewing motion in critiqueFor leads: how to run a design critique on something that moves. What to ask people to bring, six lenses to look through, how to turn "it feels off" into a change someone can make, and how to see motion clearly enough to judge it.
- Motion, performance and budgetsFor leads: motion costs frames, main-thread time and page weight, and users pay for it on their slowest phone. How motion relates to Core Web Vitals (INP and CLS), what a performance budget is, and how to write and enforce a motion budget a team can check.
Reference
- Glossary143 terms defined in this course's lessons, A to Z.
- Frameworks10 frameworks and techniques this course's lessons use, by area.
- Library143 books, articles, videos and courses cited in this course, grouped by the step they appear in.
Saved only on this device.