Neo's Adventure: Leveling Up with Server-Driven UIs
summary
Neo replaces a brittle client-heavy onboarding with a server-driven UI stack that moves from 2 products (2019) to 7 products then to 18 products by centralizing data and ownership, using Kotlin multiplatform + Ktor and JSON serialization and rendering via Jetpack Compose mappings. Two API contracts handle kickoff and step progression, app releases drop from days to ~30 minutes, one developer can tune cross‑platform flows, and engineering tackles latency, caching, monitoring and substantial developer retraining.
AI-written summary · about
chapters (12)
- 0:00Introduction to Neo's journey
- 1:00Phase one: Simple Sam
- 3:30Phase two: Grotesque George
- 9:01Phase three: Smart Sally
- 13:12Phase four: Bulletproof Betty
- 16:49Basics of server-driven UI
- 23:13Implementation examples
- 25:41Why not React Native
- 28:13Challenges of SDUI
- 31:00Team impacts and agility
- 33:46Future vision and closing
- 34:07Q&A session
related talks
49mLife is too short to develop only for Android - A journey to Server-driven UI
35mLife is too short to develop only for Android – A journey to Server-driven UI
29mUsing server-driven UI to rapidly iterate across platforms
32mLife is too short to develop only for Android – A journey to Server-driven UI
48mA page out of Server driven UI on Android
24mUsing Server Driven UI to rapidly iterate on Android and Across Platforms
33mA page out of Server driven UI on Android
35mBreaking Up with WebViews: Server-Driven UI with KMP + Compose
