Motion and Interaction · Step 7 · 6 min read
What public motion guidelines teach
Material 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.
Four large design systems, built by different companies for different products, landed on almost the same rules. That's the useful part. When Google, IBM, Microsoft and Atlassian agree that things should enter decelerating and leave faster, you don't need to rediscover it. Where they disagree, you learn which choices are taste and which are physics.
What you'll be able to do after reading:
- Read the motion section of a public design system and find its tokens
- Name what four major systems agree on
- Explain Carbon's productive and expressive motion
- Decide what to borrow and what to make your own
1. Same job, four curves
- Material 3, emphasized decelerate
cubic-bezier(0.05, 0.7, 0.1, 1) - Carbon, entrance (productive)
cubic-bezier(0, 0, 0.38, 0.9) - Fluent 2, decelerate mid
cubic-bezier(0, 0, 0, 1) - Atlassian, ease-out bold
cubic-bezier(0, 0.4, 0, 1)
Your system asks for reduced motion, so the dots jump: the curves only show in the drawings.
curveDecelerateMid; Atlassian ease-out bold. Figure: Marcus Andrey, CC BY 4.0.Each system gives a curve for something that enters the screen. Play them side by side: all four start fast and slow down at the end. The difference is how much of the travel happens early. Material's emphasized decelerate is the most dramatic; Carbon's productive entrance is the calmest.
2. Four systems at a glance
| System | Duration scale | Curves | Idea worth borrowing |
|---|---|---|---|
| Material Design 3 | 16 steps, from short1 50 ms to extra-long4 1000 ms |
Emphasized and standard, each with accelerate and decelerate, plus linear | Springs split into spatial (position, size) and effects (opacity, colour), which shouldn't overshoot |
| IBM Carbon | 6 steps, from fast-01 70 ms to slow-02 700 ms |
Standard, entrance and exit, each productive or expressive | Two modes of motion, chosen by the moment |
| Microsoft Fluent 2 | 8 steps, from durationUltraFast 50 ms to durationUltraSlow 500 ms |
Accelerate, decelerate and easy-ease, each Max, Mid and Min, plus linear | Four principles: functional, natural, consistent, appealing |
| Atlassian | Ranges: 50 to 150 ms for interactions, 150 to 400 ms for transitions | Four named curves, from "ease-out bold" to "ease-in practical" | "If someone will trigger this motion dozens of times a day, keep it under 150ms" |
Sources: Material Components, Motion and the Material Web tokens; Carbon, Motion; Fluent 2, Motion and the Fluent UI token files for durations and curves; Atlassian, Motion.
3. What they agree on
- Bigger and farther takes longer. Material's rule is that duration grows with the area or the distance animated; Fluent gives bigger elements more time; Atlassian says the same. Small things are fast, full-screen things are slow.
- Entering decelerates, leaving accelerates. Every system has a pair of curves for it. Something arriving should land softly; something leaving should get out of the way.
- A short scale, used everywhere. Six to sixteen durations, a handful of curves. Nobody publishes "pick any value".
- Fast for frequent things. Atlassian's 50 to 150 ms for hover and press, Carbon's 70 and 110 ms at the fast end, Material's 50 to 200 ms short steps. Feedback that people trigger all day is quick.
- Motion has to earn its place. Atlassian asks: "if I remove this, does the user lose information or context?" Fluent's first principle is that motion is "applied with purpose and intent". That's When not to animate, written as policy.
- Reduced motion is honoured. Atlassian turns motion off when the user asks for it, and offers low- or no-motion alternatives.
4. Productive and expressive
Carbon's most useful idea is having two kinds of motion on purpose. Productive motion "creates a sense of efficiency and responsiveness, while remaining subtle and out of the way". Expressive motion "delivers enthusiastic, vibrant, and highly visible movement", for moments like opening a new page or a system alert (Carbon, Motion).
The two use different curves for the same job. Carbon's productive entrance is cubic-bezier(0, 0, 0.38, 0.9); the expressive one is cubic-bezier(0, 0, 0.3, 1). Most of a work product should be productive. Expressive is the exception you choose: a first-run moment, a completed order. Atlassian says it differently, keeping expressive motion for key moments like onboarding, with personality shown through "restraint and polish rather than spectacle".
5. What not to copy
- The whole scale. Material's 16 durations fit a platform used by millions of apps. A single product needs four to six.
- The brand. Val Head, writing on animation in design systems, suggests studying public systems but not copying any of them wholesale, because your motion should carry your own point of view (Smashing Magazine, 2019).
- Values without the reasons. A curve from Material without Material's rule for when to use it is just a number.
- Platform conventions on the wrong platform. Android, iOS and the web each have expected transitions. Borrow the principles, then check what your platform's users expect (see Navigation transitions).
6. Common mistakes
- Copying one system's tokens and then using them for jobs they weren't designed for.
- Treating "expressive" as the default because it demos better.
- Reading the tokens and skipping the guidance around them.
- Mixing curves from two systems in one product, so similar things move differently.
- Assuming a published system has handled reduced motion for you. Check each pattern.
7. Vocabulary
| Term | Meaning |
|---|---|
| Duration scale | The short list of durations a system allows |
| Decelerate (ease-out) | Starts fast, ends slow: for things entering |
| Accelerate (ease-in) | Starts slow, ends fast: for things leaving |
| Productive motion | Carbon's quiet, efficient motion for everyday tasks |
| Expressive motion | Carbon's more visible motion for moments that matter |
| Spatial and effects | Material's split between motion that moves things and changes to opacity or colour |
8. Try it (no tools needed)
- Open the motion page of one public system from the table.
- Find three things: its shortest duration, its curve for entering, and one rule about when not to animate.
- Compare them with what your product does today.
Reflection questions: Is your product mostly productive or mostly expressive? Where is one moment that deserves expressive motion, and one where it's used and shouldn't be?
9. If you already practise
- Before you write your own scale, map your current durations against Carbon's or Fluent's. If you're already close to one, borrow it and spend the time on guidance.
- Write down the source of every borrowed value, so the next person knows it was chosen, not guessed.
- Keep two modes, productive and expressive, even if you call them something else. It ends the "can we make it fun?" debate early.
Checklist
Learn more
- Material Components for Android, Motion · Material Web, motion tokens
- IBM Carbon, Motion
- Microsoft Fluent 2, Motion · Fluent UI token files: durations, curves
- Atlassian Design System, Motion
Books, courses and videos to go deeper
- Designing Interface AnimationVal HeadBook · Rosenfeld Media, 2016 (Amazon)
- Including Animation In Your Design SystemVal HeadSmashing Magazine, free article (external site)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Motion tokens · Documenting motion in a design system · Easing curves · Duration: how long is right · When not to animate · Motion principles for interfaces