'Nitrogenize' your project with Mvvm, Compose, UTP - A killer combination for successful deliveries
summary
Compose integrates with unidirectional data flow patterns like MVVM and MVI by exposing snapshot state from ViewModels, using remember/rememberSaveable for small local state and effect APIs for side effects, while the compiler uses a slot table/gap buffer so recomposition runs in parallel and only updates changed nodes. The new Gradle test runner / Unified Test Platform (UTP) aka Nitrogen unifies IDE and CLI results, adds automated test devices managed by Gradle and collects emulator snapshots for failing tests, though snapshots aren’t fully supported for those lightweight devices and sometimes require manual reload to debug.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:08Legacy UI systems
- 4:03Jetpack Compose basics
- 15:20Architectural patterns comparison
- 18:34Testing with Jetpack Compose
- 22:07Gradle test runner updates
- 27:54Debugging test failures
related talks
26mNitrogen in your (test) pyramid.
46mTesting Compose Anew: Simplicity, Reliability, Flexibility
37mBlazing Fast UI Development with Compose Hot Reload
38mCompose UI Testing beyond layouts
29mModern Android Development using MVI architecture
37mAdopting Jetpack Compose Safely
40mTesting Android apps at scale with Nitrogen
05m5 ways Compose improves UI testing