Adopting Flutter at Scale
summary
Universal rewrites its legacy iOS/Android apps into a single Flutter codebase serving Orlando, Hollywood, and Japan, completing a feature‑for‑feature rewrite over ~6–8 months and releasing ~10 Epic Universe features in weeks; the move doubles engineering capacity, sharply reduces crashes, and boosts preordering and spend via mobile and self‑service kiosks. Deployments include a Flutter kiosk on Windows image (SCCM/Oracle Symphony) that reuses ordering business logic and runs reliably at scale.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Flutter ecosystem overview
- 5:35Decision to adopt Flutter
- 7:42Greenfield vs brownfield
- 12:32Impact on UX and business
- 16:00Multi-platform development
- 19:52Team structure and code sharing
- 22:16Design and engineering collaboration
- 23:40Business impact and revenue
- 28:33Epic Universe launch role
- 33:50Reducing risk with Flutter
- 36:16Flutter and AI future
- 39:05Training engineering team
- 42:37Windows kiosk deployment
- 45:01Flutter abundance platform
related talks
37mFlutter at scale
31mFlutter with 50+ Engineers
45mFlutter: A journey of productivity and happiness
42mOur Journey to Flutter
09mFlutter for Enterprise: How your company should be building with Flutter at scale
25mNative to flutter: A tale of Tide's transformation
39mImplementing Flutter at Tide
49mWhat's Awesome about Flutter