Modern Android Development
summary
Google teams are actively smoothing gaps: they coordinate with Paparazzi, Shot, DropShot to make screenshot/snapshot testing easier to set up; Compose and RecyclerView now include a default composition strategy to reduce bridge overhead; Compose libraries already ship baseline profile rules and apps and SDKs should generate and test with them on release builds to see real performance; a new alpha API collectAsStateWithLifecycle lands to address lifecycle-safe flow collection. File repro bugs for edge cases.
AI-written summary · about
chapters (26)
- 0:00Welcome and introduction
- 1:50Snapshot testing plans
- 3:15Compose and View integration
- 5:42Safe args in Compose Navigation
- 6:47ViewModel state in Compose
- 8:55Compose performance in SDKs
- 11:23Unidirectional data flow in Compose
- 16:03Mapping units in UI
- 18:12Displaying HTML in Compose
- 19:19Testing legacy code
- 22:50Refactoring spaghetti code
- 24:58Context usage in architecture
- 26:43Compose in Fragments
- 27:48Collecting flows in Compose
- 29:54Memory leaks in Compose
- 31:38Cross-team collaboration
- 35:08Context class improvements
- 37:57Tracking scrollable content
- 39:44Modularization guidance
- 41:08Stable class annotations
- 43:39ViewModels in Compose previews
- 45:03Using Compose previews
- 46:25Temporary full-screen screens
- 49:18Testing coroutine dispatchers
- 52:50Lifecycle-aware coroutines
- 54:59Closing remarks and Q&A
related talks
44mAutomating Screenshot Testing in Compose Multiplatform
36mCoupling Compose- Interoperability in a Legacy Codebase
35mNext Generation Android UI with Jetpack Compose
18mCompose Adoption at Pinterest: A Postmortem
42mCompose: Beyond Android development
40mCompose Without Flow: Unidirectional State with Snapshots and Coroutines
48mLearning Jetpack Compose By Example
49mBuilding for the future at Snapchat