After this lesson you can:
Previous lesson:
✅ Timing
✅ Easing
✅ Anticipation
✅ Continuity
✅ Spatial Relationships
✅ Shared Element Transitions
Today:
➡️ Evaluate
➡️ Systematize
➡️ Apply
Not:
"When does it look nicer?"
But:
"Which UX friction is being solved?"
As a designer, you must be able to evaluate motion.
Not:
But:
We need a framework to analyze and evaluate motion.
Always ask these questions:
Motion should make change visible.
Possible reasons:
If there is no reason:
➡️ remove the animation.
Most important question.
Without animation:
Yes → useful motion
No → decoration
Timing influences:
Too fast = invisible
Too slow = frustrating
Easing should correspond to the physical world:
Work in pairs.
Analyze:
Discuss:
Not all movement is equally important.
Just like typography:
H1 → H2 → Body
Motion also has levels.
Most important movements.
Examples:
Must be clearly visible.
Supportive.
Examples:
Less emphasis.
Micro-feedback.
Examples:
Short, subtle movements.
When everything moves:
➡️ Nothing is important.
Motion demands attention.
Use that attention consciously.
Identify the motion below and assign it to a category:
🟥 Primary Motion
🟨 Secondary Motion
🟩 Tertiary Motion
Discuss differences.
Professional teams do not design individual animations.
They design systems.
A collection of fixed agreements.
The motion equivalent of:
Problem:
Every designer invents something different.
Advantages:
✅ Consistent
✅ Reusable
✅ Efficient
✅ Scalable
Slide Up
Fade Out
Scale + Fade
Slide In Right
Like design tokens. Not fully supported in Figma yet, but you can use them purely as documentation.
Motion Tokens
Duration
---------
Fast = 150ms
Medium = 300ms
Slow = 450ms
Easing
---------
Standard = Ease Out
Emphasis = Ease In Out
Exit = Ease In
Distance
---------
Small = 8px
Medium = 24px
Large = 64px
``
Not:
"Pick something that feels right."
But:
"Use duration-medium."
Consistency always wins!
Design a motion system for:
📱 Tinder-like App
Define:
Commonly used motion patterns.
Not just trendy, but proven to work.
Popular in:
Advantage:
Context remains visible.
The user does not lose the current page.
Motion clarifies:
Widely used.
Often designed incorrectly!
Panel appears instantly.
Result:
Content grows along with it.
User follows the evolution.
Continuity is maintained.
FAB uses motion to:
Don't show everything at once.
Motion helps to reveal information gradually.
User processes information step by step.
Less cognitive load.
Build an Onboarding with Figma and Motion based on the following design:
A checklist for every designer.
Why is this moving?
Does it help the user?
Does it clarify a relationship?
Does it provide feedback?
Does it direct attention?
Is it fast enough?
Is it consistent?
Does it respect accessibility?
Does the UX get worse without this animation?
Can this become a reusable pattern?
You are given an interface without motion.
Goal:
Add a maximum of 3 animations.
No more.
Every animation must have a purpose.
Ask yourself:
What problem am I solving?
Do not use multiple animations for the same problem.
Simplicity wins.
Consistency over spectacle.
Professional motion is usually subtle.
Defend every animation.
Not:
"It looks nice."
But:
"This clarifies the relationship between screens."
Design motion for one flow:
✅ Timing
✅ Easing
✅ Anticipation
✅ Continuity
✅ Shared Element Transition
2 minutes per team.
Show:
Do not show:
"cool effects"
Do show:
"solved user problems"
Good motion:
✅ Informs
✅ Orients
✅ Guides
✅ Strengthens UX