Server-Driven UI: Building Dynamic React Applications
summary
Claim: shifting UI logic to the backend lets teams push layout and content changes without redeploys. Demonstration uses React, Node, Express where the server returns a JSON schema that declares schema-driven header/product/banner/footer composition; changing banner text and color on the server immediately updates the page in the demo. Covers state tradeoffs: higher server load and latency, harder offline support, but enables realtime personalization and A/B changes without shipping client code.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:29What is Server-Driven UI
- 2:50Traditional UI adaptability challenges
- 4:15Server-Driven UI in practice
- 5:43React for Server-Driven UI
- 8:13Server-Driven UI vs data fetching
- 9:57E-commerce example
- 10:40Building SDI with React
- 12:02Live demo: dynamic UI
- 13:50Flexible schemas for SDI
- 15:59SDI pros and cons
- 17:03Companies using SDI
- 17:46Q&A
related talks
34mServer Driven UIs: the future of cross-platform rendering
29mServer Driven UI (BFF)
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
38mBuilding Isomorphic Web Applications with React
33mA page out of Server driven UI on Android
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
43mReact Applications on the Server
24mUniversal Applications
