Life is too short to develop only for Android – A journey to Server-driven UI
summary
A server-driven UI system that ships entire screens by changing backend JSON, not app binaries, is described with concrete choices: Moshi polymorphic JSON for resilient parsing with an UnknownDTO fallback, a view-factory + RecyclerView adapter (migrating to Compose later), and per-component deep link per component plus tracking. A “vaccine” pattern isolates cross-team features by letting a component call its own microservice. No backend versioning causes front-end hacks; the result enables A/B tests and deploys new screens without Play Store releases.
AI-written summary · about
chapters (12)
- 0:00Introduction and outline
- 0:48The problem with traditional UI
- 2:33What is Server-driven UI
- 7:30Benefits of Server-driven UI
- 7:53Our journey to Server-driven UI
- 8:56Foundation of Server-driven UI
- 12:48Key decisions and implementation
- 25:16Testing strategy and tips
- 27:46Content management system integration
- 28:49Introducing the Vaccine tool
- 31:57Android development without Android
- 34:24Conclusion and Q&A
related talks
32mLife is too short to develop only for Android – A journey to Server-driven UI
49mLife is too short to develop only for Android - A journey to Server-driven UI
48mA page out of Server driven UI on Android
33mA page out of Server driven UI on Android
24mUsing Server Driven UI to rapidly iterate on Android and Across Platforms
35mBreaking Up with WebViews: Server-Driven UI with KMP + Compose
18mServer Driven UI on Mobile
29mUsing server-driven UI to rapidly iterate across platforms
