Native UI with multiplatform Compose
summary
Redwood compiles a Kotlin schema into generated Compose-like APIs and platform widgets so the same composable code drives Android Views, Compose UI, iOS UIKit (and DOM) while keeping native toolkits and view hierarchies. It pairs with Zipline (Treehouse) to download updated Kotlin/JS UI code into a running app so UIs change without relaunch or app-store updates. The system enforces schema-compatibility at compile time, supports incremental adoption, and is production-ready at Cash App though tooling and lazy/paging helpers are still incomplete. Redwood and Zipline/Treehouse are the key components.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:18Live multiplatform demo
- 3:08Redwood overview
- 5:23Motivation and history
- 8:33Design system evolution
- 10:18Schema language
- 14:09Generated code
- 16:55Native UI integration
- 20:09Android implementation
- 21:33iOS implementation
- 23:41Dynamic UI updates
- 26:12Zipline for hot code
- 27:36Treehouse architecture
- 29:43Bootstrapping Treehouse
- 31:28Zipline caching
- 31:50Modifiers and layout
- 35:23Multiple children slots
- 38:33Future of Redwood
- 40:39Adoption considerations
related talks
47mPlaying in the Treehouse with Redwood and Zipline- 47mPlaying in the Treehouse with Redwood and Zipline
58mMultiplatform UI: Compose outside Android
42mWhat’s New in Compose Multiplatform
45mThe Adventures of Kotlin And Compose Through the Multiplatform World
35mBreaking Up with WebViews: Server-Driven UI with KMP + Compose
45mShared mobile UIs with Compose Multiplatform
24mKotlin and Compose WASM for the UI challenged