Building Server Driven UI in iOS
summary
Claim: the server returns JSON that specifies component type and data and the iOS client maps those to prebuilt views; demo uses a Node and Express server and an iOS client that renders featured image, carousel, text row and a rating row and wires actions for push/sheet navigation. Components must be components already in the binary or they won’t render, versioning breaks new components for old apps, and because views are prebundled there is no App Store review required for layout changes.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:05Server driven UI basics
- 2:28What server driven UI is not
- 5:20Server driven UI architecture
- 10:37Demo setup and server
- 12:20First UI update from server
- 16:37Benefits of server driven UI
- 17:27Client architecture
- 23:00Adding carousel control
- 26:11Implementing actions and navigation
- 30:08Handling user interactions
- 31:10Offline behavior and submission
- 32:34Pet detail screen
- 37:50Adding list view and cells
- 39:18Versioning challenges
- 41:25Lessons learned
- 42:32Resources
- 43:58Upcoming session
related talks
18mServer Driven UI on Mobile
34mServer Driven UIs: the future of cross-platform rendering
33mA page out of Server driven UI on Android
29mServer Driven UI (BFF)
32mLife is too short to develop only for Android – A journey to Server-driven UI
09mServer-Driven UI
18mServer-Driven UI: Building Dynamic React Applications
24mUsing Server Driven UI to rapidly iterate on Android and Across Platforms
