BDUI — Pleasure or Pain?
summary
Backend-Driven UI (BDUI) — where the server defines screens and navigation as well as data — and Cian’s team experience building their own BDUI tool. The talk explains why they built the tool, key implementation details, demo of how it works, challenges encountered during development, and suitable use cases such as reducing time-to-market, simplifying A/B testing, and delivering changes without app updates.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:08What is BD UI
- 3:14Project context and problems
- 7:32Solution: switch to BD UI
- 8:58Form structure and components
- 10:03Widgets and modifiers
- 12:28Action types
- 14:36JS Action and state
- 16:41Interdependent elements
- 18:09Formatting and validation
- 20:16Validation and errors
- 21:21Client-server interaction
- 23:53Screen transitions
- 26:09Standard component library
- 26:52Flexibility and trade-offs
- 27:58Error strategy and versioning
- 29:44Versioning and compatibility
- 30:47Integration with native screens
- 31:30Sandbox and debugging
- 32:35Implementation challenges
- 33:37Testing and Open 2.0
- 34:18Results and metrics
- 35:24Product achievements
- 36:29BD UI applicability criteria
- 37:34Task redistribution
- 38:18Conclusion
- 40:03Q&A
related talks
46mBDUI as a Mobile App Strategy
43mSDUI Patterns
29mServer Driven UI (BFF)
50mData-driven UI: Unlimited Power
34mServer Driven UIs: the future of cross-platform rendering
50mLet's Design UI the Right Way
12mWhat Shared UI Is and How It Helped Us
43mServer-driven UI on the Web — Describe Your Frontend, Don’t Write It