Accelerating Mobile Development with Server Driven Technologies
summary
Mobile release takes ~four weeks to land and up to two weeks–six months for 99% adoption, so Uber builds a homegrown server-driven platform composed of backend DSL in Go, server-driven layout, logic and actions, and thrift-annotated models. A previewer app plus a Figma-to-DSL integration speeds iteration; snapshot testing and CI ensure parity. Logic supports eight primitive types with SLA timeouts and defaults; actions allow chaining and custom resolvers. Outcome: composable system with 20+ features and snapshot testing across Android and iOS, some launched with no mobile build.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 1:14Why server-driven frameworks
- 3:04Problems with current mobile development
- 4:58Goals for the initiative
- 6:03Solution overview and components
- 8:51Server-driven UI and layout
- 11:36Server-driven logic explained
- 17:35Driving actions from the backend
- 24:25Combining frameworks into one
- 25:47Challenges and learnings
- 26:31Dev tools and testing frameworks
- 28:59Highlights and adoption results
related talks
46mMobile: Past, Present, Future - Tech Choices and Architecture Impact
18mServer Driven UI on Mobile
41mFull-Stack Web and Mobile Development with Cloud Backends
31mBest Practices for Architecting Server-Driven Web/Mobile Apps
06mAccelerate Application Delivery with a Cloud-Native Mindset
49mLife is too short to develop only for Android - A journey to Server-driven UI
38mEmbrace the frontend revolution
46mClient Applications Under Load