Trio- Compose Architecture with Mavericks
summary
Airbnb describes Trio as a Compose-first feature framework built on Mavericks that moves navigation into view‑model state and guarantees type-safe cross‑module routing via KSP and Dagger. It stores parcelable Trio instances in state (allowing preloading and atomic nav+state changes), runs in a 1,800‑module codebase, and already ships on 125 Trio screens in production. Tooling includes KSP-generated routers, Paparazzi screenshot tests plus automated interaction testing and Robolectric-friendly unit tests; the system is reported to work and speed development.
AI-written summary · about
chapters (25)
- 0:00Introduction and speakers
- 1:34Mavericks state management
- 2:57Why build Trio architecture
- 3:38Trio architecture overview
- 5:04Trio implementation details
- 7:32Rendering Trio UI
- 9:35Trio lifecycle and animations
- 10:16Storing Trios in state
- 12:19Navigation hierarchy benefits
- 13:23Activity intents in Trio
- 14:04Trio navigation system
- 16:48Router and type safety
- 18:10Props for parent-child communication
- 20:39Updating state from props
- 22:07UI presentation types
- 24:12Screen flow for navigation
- 25:16Default screen scaffolds
- 26:20Trio testing approach
- 28:25Screenshot testing
- 29:30Automated interaction testing
- 30:32Custom UI Espresso tests
- 31:35Manual testing tooling
- 32:18Trio adoption at Airbnb
- 33:00IDE tooling for Trio
- 34:02Future plans and Q&A
related talks
31mModern Compose Architecture with Circuit
29mNavigation and Dependency Injection in Compose
34mBeyond the UI: Compose as a Foundation for Multiplatform Apps
46mMultiplatform UI with Compose
33m3D content with Compose Multiplatform
38mViews, Compose, Multiplatform - Oh My!
45mThe Adventures of Kotlin And Compose Through the Multiplatform World
42mCompose: Beyond Android development