Transitions without Activities or Fragments
summary
Shows how to run Android Transitions without Activities or Fragments by wiring TransitionManager.beginDelayedTransition with custom TransitionSets (Fade + ChangeBounds + ChangeTransform) and using ConstraintLayout + ConstraintSet to record states; demonstrates hacks like keeping the old view in the container until the overlay animation finishes, using a “slot” parent to avoid weight jumps, and the requirement to actually remove the source view for a shared element to work. Highlights beginDelayedTransition and the trouble-prone changeBounds, overlay lacks elevation, and Conductor is recommended.
AI-written summary · about
chapters (11)
- 0:00Introduction to transitions
- 4:34Why use transitions framework
- 8:48Simple layout transitions
- 14:18Debugging transition issues
- 19:10State changes vs screen navigation
- 24:44Shared element transitions
- 31:06Search screen example
- 36:03Common transition pitfalls
- 37:27Debugging tips for transitions
- 38:07Takeaways and recommendations
- 39:13Q&A session
related talks
27mA window into transitions
29mMaking Beautifully Animated Transitions
25mGet It Running
29mFROM 0 TO MATERIAL MOTION: CREATING ANIMATIONS AND TRANSITIONS
48mSmooth transitions to Android - how and why to do this?
41mA Moving Experience
33mShared Element Transitions in Jetpack Compose: examples, adoption and how they work
19mMotionLayout: Animation made easy