Our Journey to Flutter
summary
BMW chooses Flutter as the company UI platform, replacing duplicated native work with a single widget tree and hot reload, and runs a CI that enforces 100% test coverage goals across unit/widget/integration layers. Teams ship via backend-for-frontend APIs and move feature flags server-side, use Flutter BLoC for predictable state, log with a central client and OC integration test + perf screenshots to verify 60 fps and rollout—several open source packages and brand apps are already running.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 2:05Digital Transformation
- 3:03The Challenge
- 5:02What can we do better
- 7:36What are our goals
- 9:29The developer experience
- 11:26What if we work on native side
- 12:29Technology Solutions
- 14:23Ribs
- 14:42What happened to Flutter
- 17:12Breaking the silos
- 18:19Uberribs
- 18:44UI Design
- 20:13We Need More Time
- 20:30Cross Platform Development
- 22:07What is Flutter
- 23:51Picasso
- 24:38Dart
- 26:41Simple Network
- 27:42Google Maps
- 28:47Flutter Community
- 30:22Benefits of Flutter
- 31:43Frederick Community
- 32:07GitHub
- 32:37Flutter Packages
- 33:13Backend
- 34:16Architecture
- 34:42State Management
- 35:12Flutter Blog
- 35:27How does it work
- 36:49Lambert
- 38:25Automated Pipeline
- 38:52OC Player
- 39:43Selfpromotion
- 40:24Droidcon
- 40:48Questions
related talks
37mFlutter at scale
45mFlutter: A journey of productivity and happiness
32m"Flutter: How we're building a UI framework for tomorrow at Google"
22mIntroduction to Flutter
33mShould We Flutter?
31mFlutter with 50+ Engineers
24mKeynote: Flutter
49mFirst Flutter, then Fly: Build Reactive & Performant Cross-Platform Apps