Life is too short to develop only for Android - A journey to Server-driven UI
summary
A multi-platform server-driven UI powers a polymorphic JSON -> DTO -> view-entity -> view pipeline with a view-factory map and adapter so a change in backend order or type moves UI without a release; this lets the team ship a new campaign feature in two days. Kotlin serialization fails to ignore unknown components so the implementation uses Moshi with a fallback adapter. Lacking backend versioning causes pain; a self-contained vaccine view lets one team inject components into another screen and enables AB tests and CMS-driven content.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:53The Month of November
- 3:18Api Response (not SDUI)
- 4:12Api Response (SDUI)
- 12:31Atomic design (code)
- 13:31Foundation
- 15:45Polymorphic JSON + Data Models Libraries
- 16:55Moshi Setup
- 20:10Data Models + View Entities
- 22:353. View Entities + View (ViewFactory Map)
- 24:573. View Entities + View (RecyclerViewAdapter)
- 25:26Test strategy
- 27:17HTTP Debugging Proxy
- 28:23Content management system
- 32:09Vaccine
- 34:02Not so hypothetical situation
- 35:39Android-less
- 37:38Zhenlei Ji
related talks
35mLife is too short to develop only for Android – A journey to Server-driven UI
32mLife is too short to develop only for Android – A journey to Server-driven UI
41mA page out of Server driven UI on Android
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
29mUsing server-driven UI to rapidly iterate across platforms
35mBreaking Up with WebViews: Server-Driven UI with KMP + Compose