Meaningful motion design and how to implement it
summary
A practical workflow for bringing Android UIs to life: a photo‑notebook app ships with animated vector drawables exported from Shapeshifter, After Effects exports played via Lottie, and Motion/Constraint techniques (including ConstraintLayout and state list animators) synchronize color, morph and layout transitions. Handover uses Zeppelin, designers export JSON or hotspots, developers cheat with five predetermined random points to simulate randomness, polish takes days not weeks, and implemented features prove readable, performant and good‑enough.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:20Why motion is important
- 3:55Where to use motion
- 4:10Guidelines
- 5:01Conflicts
- 5:28Over Animating
- 6:04Developers Role
- 8:24State changes
- 10:29Shapeshifter
- 13:22Using State
- 17:23Animation Transitions
- 22:08Screen Size
- 23:47Onboarding
- 32:43User Delight
- 34:46Simplify
- 36:27Motion
- 38:08Communication
- 39:41Google
- 41:36Google Best Up
- 42:12Conclusion
related talks
39mMeaningful motion design and how to implement it
29mBringing your app to life - Motion Animations everywhere
34mSmooth Criminals, Android animations and how not to get robbed.
47mLearn Some New Moves: Advanced Android Animation
42mDo the Loco-MotionLayout: Building animations with MotionLayout
38mIn a World of Pure Android Animation 🍭🍫
39mAdvanced & Practical MotionLayout
37mThree Approaches to Animations on Android