Life is too short to develop only for Android – A journey to Server-driven UI
summary
A server-driven UI is built: polymorphic JSON drives a RecyclerView of components so a backend change rearranges or swaps carousel/grid without app releases, cutting a planned month of work down to shipping in two days for a Black Friday → month-long promotion. Implementation uses Moshi custom adapters with fail‑soft parsing, DTO→view‑entity→view mapping via a view‑factory map, deep links and tracking for navigation and A/B, CMS for content, and a “vaccine” pattern to inject cross‑domain UI. Tests: contract, unit, and screenshot (Paparazzi) planned.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:16Real-world problem solved
- 8:45What is Server-driven UI
- 13:29Foundation of the system
- 23:29Testing strategy and tips
- 25:54Cross-team collaboration
- 29:49Android development simplified
- 31:12Conclusion and future work
related talks
35mLife 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
24mUsing Server Driven UI to rapidly iterate on Android and Across Platforms
33mA page out of Server driven UI on Android
18mServer Driven UI on Mobile
29mUsing server-driven UI to rapidly iterate across platforms
35mBreaking Up with WebViews: Server-Driven UI with KMP + Compose