Server-Driven UI in Flutter
summary
Server-driven UI here claims rapid iteration and no app store dependency and cites NewBank running SDUI at scale with 10 million users, 2,000 engineers to enable backend teams to ship UI changes. Three concrete Flutter options appear: remote_flutter_widgets, swap, stack — stack is JSON based and preferred for readability. Tradeoffs: fewer IDE errors with Dart layers but remote widgets lack custom third‑party widget loading, client handles interactions, and SDUI suits dashboards and configurable content not heavy animations.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:26Mobile UI challenges
- 3:12How server-driven UI helps
- 3:54History of server-driven UI
- 5:16New Bank’s success story
- 6:40Server-driven UI frameworks
- 8:49When to use server-driven UI
- 9:57Q&A
related talks
29mServer Driven UI (BFF)
34mServer Driven UIs: the future of cross-platform rendering
18mServer Driven UI on Mobile
42mA fresh perspective on multi-platform UI
18mFlutter Design
22mIntroduction to Flutter
32m"Flutter: How we're building a UI framework for tomorrow at Google"
06mFlutter: Falling in Love Again with Mobile and Web Dev