The Good, the Bad and the Ugly side of selecting Flutter
summary
Company moves merchant tooling from native iPad Swift and a phone-specific picker to a unified Flutter codebase, expanding from 180,000 to 650,000 lines in 12 months while growing the team from 2 to 8 engineers. The picker app in Flutter ships with native feel and no user complaints; test coverage rises by 30 percentage points in five months after shifting away from too many end‑to‑end tests (initially a diamond instead of a pyramid). Responsive UI across phone, tablet and dock and Flutter hiring are ongoing challenges.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:17Why consider Flutter
- 5:27Merchant apps transition
- 8:18Scaling Flutter adoption
- 13:56Team growth and challenges
- 17:52Architecture and team structure
- 21:04Proud achievements and lessons
- 25:44Testing strategy and advice
- 27:08Reasons for choosing Flutter
- 29:38Q&A
related talks
43mDangerous Flutter... Or Not?
30mCat-like Development: Flutter for Efficiency
33mShould We Flutter?
49mFirst Flutter, then Fly: Build Reactive & Performant Cross-Platform Apps
01h 03mProfiling Flutter Apps: Undeservedly Forgotten Heroes
36mFlutter Add-to-App: The Good, the Bad and the Ugly
38mFlutter: A Path of Vines and Flowers
25mFlutter and the Dart Side