Native to flutter: A tale of Tide's transformation
summary
Tide performs a full Greenfield rewrite to Flutter, rebuilding a universal client in under a year with ~40–50 Flutter engineers split into seven subteams and a core team, using Lego architecture packages, code generation, a design system and ~20 screen templates that cover ~70% of screens. 85% of mobile engineers gain hands‑on Flutter experience in six months, releases use ringed rollouts and weekly simultaneous Android/iOS deploys from a single codebase, and lead time and feature parity measurably improve.
AI-written summary · about
chapters (11)
- 0:00Tide’s transformation journey
- 1:28Why Tide needed change
- 3:36Choosing Flutter
- 6:48Managing change
- 8:53Building the team
- 13:27Hands-on learning
- 14:09Scaling team and Lego architecture
- 18:25Lean processes
- 20:31Testing and release
- 21:56Results and benefits
- 22:59Key learnings
related talks
39mImplementing Flutter at Tide
09mFlutter for Enterprise: How your company should be building with Flutter at scale
45mFlutter: A journey of productivity and happiness
28mHow a Nearly-Naive Flutter Team Replaced a Native App with Flutter in Six Months
30mCat-like Development: Flutter for Efficiency
30mMobile tech stack at Tide
32m"Flutter: How we're building a UI framework for tomorrow at Google"
46mAdopting Flutter at Scale