How a Nearly-Naive Flutter Team Replaced a Native App with Flutter in Six Months
summary
A mostly Flutter-inexperienced Android team rewrote a Kotlin/Swift cosmetics e‑commerce app to Flutter in six months and shares lessons and failures. The talk covers why they replaced the native app, cost-saving experiments (automated testing attempts including GoldenTest issues and future Appium plans), trying three state-management frameworks before settling on GetX, setting up CI/CD with Codemagic, how the team learned Flutter, and the final results (how much was implemented in Dart and pros/cons of Flutter development).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:17Why Flutter for rewrite
- 6:15Key Flutter decisions
- 13:03State management choice
- 18:05CI/CD for mobile
- 21:34Team collaboration
- 23:43Results and challenges
- 27:16Final thoughts
related talks
25mNative to flutter: A tale of Tide's transformation
30mThe Struggles of Migrating to Flutter and What We Gained
33mShould We Flutter?
39mImplementing Flutter at Tide
25mFlutter: do more with less code
27mFast Prototypes with Flutter + Kotlin/Native
45mFlutter: A journey of productivity and happiness
30mCat-like Development: Flutter for Efficiency