A page out of Server driven UI on Android
summary
Argues that adopting Server Driven Architecture for the UI layer lets teams push layout and content changes without app updates by shipping a JSON-driven renderer that maps components to either JetPack Compose or Epoxy (Airbnb's library). Shows a working prototype that parses a compact JSON schema into composables or Epoxy models, supports feature flags and A/B variants at runtime, and cuts layout release cycles from weeks to days while keeping binary size and performance within acceptable bounds.
AI-written summary · about
chapters (6)
- 0:00Introduction to Server Driven UI
- 3:35What is Server Driven UI
- 10:57Why use Server Driven UI on Android
- 19:40How to implement Server Driven UI
- 28:41Real-world examples and benefits
- 31:59Q&A
related talks
41mA page out of Server driven UI on Android
48mA page out of Server driven UI on Android
35mLife is too short to develop only for Android – A journey to Server-driven UI
24mServer-Driven UI with Jetpack Compose and GraphQL
29mUsing server-driven UI to rapidly iterate across platforms
24mUsing Server Driven UI to rapidly iterate on Android and Across Platforms
18mServer Driven UI on Mobile
32mLife is too short to develop only for Android – A journey to Server-driven UI
