A page out of Server driven UI on Android
summary
Claim: a server-driven UI lets a backend JSON state render Android screens so the app can change a home page without a Play Store deploy. Tools actually used: Epoxy + RecyclerView, Jetpack Compose hoisting, Moshi with a runtime polymorphic adapter. Built a rendering engine, a custom FrameLayout wrapper and an open-source Compose design system (Andromeda) and run instrumentation tests; it ships in an app serving about five countries and works in production, diffing only changed rows.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:10Server Driven UI - What to Except
- 2:58Goal
- 5:54UI Logic - Downsides?
- 7:30UI Logic - Change
- 9:32Let's breakdown
- 11:56Frameworks
- 14:08Server response - Checkbox
- 15:10Server Components - Card
- 17:53Epoxy- RecyclerView
- 20:28Epoxy- EpoxyModel
- 21:36Epoxy-Controller
- 32:17Root screen
- 33:26Activity
- 34:28Content
- 38:48References
- 39:19Check out
related talks
41mA page out of Server driven UI on Android
33mA 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
32mLife is too short to develop only for Android – A journey to Server-driven UI
24mUsing Server Driven UI to rapidly iterate on Android and Across Platforms
29mUsing server-driven UI to rapidly iterate across platforms
49mLife is too short to develop only for Android - A journey to Server-driven UI
