Server Driven UI Workflow
summary
A system is built where the server-driven blockers own which screen, text and action appear next; the server sends descriptors and a generic “thumb rocker” vertical layout so clients just render elements. It uses Wire + protobuf for cross-platform messages. The codebase accumulates ~100 blockers, and backporting bites: 0.7% ≈ 50k stuck users on old releases. It mostly works — one server codepath ships behavior fast — but enum/optional-field mismatches, complex server load and tricky bug triage remain.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:09Cash 1.0
- 4:08Steps
- 4:49Cash 2.0
- 10:22Cash 3.0
- 11:58Form Blocker
- 12:55Data Format Sharing
- 13:45square / wire
- 14:24Challenges
- 21:19Pros
- 23:24Server Driven Design System?
related talks
23mBuilding Distributed Systems with Node.js
57mMigrating from a monolith to a new service
20mMonolith Thick Client Apps to Microservices! Best Practices
53mPowering 100+ million daily users
27mMass Hysteria: Clients and Servers, Living Together
30mClient and server need to talk
42mHow to design the perfect interactive media content planning tool using Hexa- and CQRS architectures
25mTaming Client-Server Communication