A Journey to Building a Server Driven UI Framework
summary
SiriusXM and Pandora build a server-driven UI to unify duplicated stacks and serve 150 million listeners across mobile, TV and embedded automotive head units, defining UI as a JSON component contract (page/container/item) so servers send key/value component data. A custom markup attempt for cars is cancelled; team pivots to Jetpack Compose, a modular MVVM approach and SDK split (services, design system, SDUI core), cutting some feature delivery from months to days while improving theming and dev feedback.
AI-written summary · about
chapters (9)
- 0:00Introduction and journey
- 3:44Similarities across brands
- 5:53Defining server-driven UI
- 8:01Mission and limitations
- 12:19Overengineering detour
- 14:05Reflecting on the approach
- 17:16Rebuilding the framework
- 23:20Architecture and view models
- 26:31Demo and summary
related talks
33mA page out of Server driven UI on Android
41mA page out of Server driven UI on Android
34mServer Driven UIs: the future of cross-platform rendering
35mLife is too short to develop only for Android – A journey to Server-driven UI
48mA page out of Server driven UI on Android
35mBreaking Up with WebViews: Server-Driven UI with KMP + Compose
01h 03mEvolving compositional user interfaces
18mServer Driven UI on Mobile