Adding Flutter to your app - what are they not telling you?
summary
A team migrates to Flutter using the add-to-app approach (Flutter 1.2 → 2.5), building feature packages and a gallery runner, and ships onboarding first while keeping native home until later. They use VS Code, Mason templates to generate boilerplate, and pigeon for typed platform channels; amplitude is called via platform channels to avoid double-init. Tests remain split (Espresso works, iOS/Appium less reliable), monorepo reduces triple-PR churn, and adoption saves money and unifies teams.
AI-written summary · about
chapters (11)
- 0:00Introduction to Flutter integration
- 3:59Convincing team to adopt Flutter
- 7:10Teaching Flutter to the team
- 12:36Building pages and state management
- 15:50Planning feature migration
- 19:00Starting with onboarding feature
- 20:09Native-Flutter integration tips
- 24:54Handling dependencies and platform channels
- 26:41Testing in Flutter add-to-app
- 27:02Repository and team workflow
- 29:12Was it worth it? Results
related talks
28mSeamless Fusion: A Deep Dive into Flutter's Add-to-App Magic
34mAndroid with a side of Flutter, please
46mAdd Flutter to your existing mobile app
34mHow to add Flutter to your existing app
33mShould We Flutter?
44mRe-Platforming The Path For Betterment
45mFlutter: A journey of productivity and happiness
30mAdding Flutter to your Android app