Justin Volz
@justinvolz.bsky.social
📍 Senior Motion Designer @ Google, crafting engaging and delightful user experiences through UX motion design. I'm also an avid illustrator and coffee fiend
I need to pick up a copy, this sounds rad
February 13, 2025 at 5:57 PM
I need to pick up a copy, this sounds rad
3. Functional Animation:
UX Animation isn't decoration. Each motion should answer a user question:
- Where did that element go?
- What just happened?
- What can I do next?
The best UX motion design is not noticed—it's felt.
Which principle do you think most apps get wrong? 🤔
UX Animation isn't decoration. Each motion should answer a user question:
- Where did that element go?
- What just happened?
- What can I do next?
The best UX motion design is not noticed—it's felt.
Which principle do you think most apps get wrong? 🤔
November 23, 2024 at 6:19 PM
3. Functional Animation:
UX Animation isn't decoration. Each motion should answer a user question:
- Where did that element go?
- What just happened?
- What can I do next?
The best UX motion design is not noticed—it's felt.
Which principle do you think most apps get wrong? 🤔
UX Animation isn't decoration. Each motion should answer a user question:
- Where did that element go?
- What just happened?
- What can I do next?
The best UX motion design is not noticed—it's felt.
Which principle do you think most apps get wrong? 🤔
2. Temporal Hierarchy
Speed = importance
Critical feedback? 200ms
Basic transitions? 300ms
Complex state changes? 500ms max
Anything slower, and you're wasting your users' time. There's a time and place for longer timing, but most will fall in this range.
Speed = importance
Critical feedback? 200ms
Basic transitions? 300ms
Complex state changes? 500ms max
Anything slower, and you're wasting your users' time. There's a time and place for longer timing, but most will fall in this range.
November 23, 2024 at 6:19 PM
2. Temporal Hierarchy
Speed = importance
Critical feedback? 200ms
Basic transitions? 300ms
Complex state changes? 500ms max
Anything slower, and you're wasting your users' time. There's a time and place for longer timing, but most will fall in this range.
Speed = importance
Critical feedback? 200ms
Basic transitions? 300ms
Complex state changes? 500ms max
Anything slower, and you're wasting your users' time. There's a time and place for longer timing, but most will fall in this range.
1. Spatial Continuity:
Users get lost when elements teleport around your UI. Connect the dots. Show them where things came from and where they go.
Quick win: Next time you hide/minimize a menu, don't just fade it. Slide it in the direction it will return from (with proper easing).
Users get lost when elements teleport around your UI. Connect the dots. Show them where things came from and where they go.
Quick win: Next time you hide/minimize a menu, don't just fade it. Slide it in the direction it will return from (with proper easing).
November 23, 2024 at 6:19 PM
1. Spatial Continuity:
Users get lost when elements teleport around your UI. Connect the dots. Show them where things came from and where they go.
Quick win: Next time you hide/minimize a menu, don't just fade it. Slide it in the direction it will return from (with proper easing).
Users get lost when elements teleport around your UI. Connect the dots. Show them where things came from and where they go.
Quick win: Next time you hide/minimize a menu, don't just fade it. Slide it in the direction it will return from (with proper easing).