Flutter Add-to-App: The Good, the Bad and the Ugly
summary
Half a million lines on iOS, an even larger Android codebase, and a bank app where a complex business flow is rewritten as a Flutter module that later becomes a full Flutter app in production. Key pieces: Flutter engines (need pre-warming, ~1s on iOS and ~1.5s on Android), Flutter engine group to speed multi-engine launches, background Dart isolate plus a foreground service and a dialog engine, pigeon for platform bindings, patrol for UI tests, binary artifacts (XCFramework / local Maven) and final size ~27MB iOS / ~15MB AAB.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:04Why Flutter Add-to-App exists
- 2:10Add-to-App use cases
- 5:01Add-to-App integration challenges
- 7:52Add-to-App case study
- 9:40Flutter engine in Add-to-App
- 13:18UI in Add-to-App
- 15:08Assets in Add-to-App
- 16:54Networking and API integration
- 19:44Developer experience
- 22:36Native apps with Flutter modules
- 24:46Native code requirements
- 27:12Background processing
- 30:02App size and performance
- 31:53Pre-warming Flutter engines
- 33:00Testing Flutter in native apps
- 33:23Organizational challenges
- 35:13Key takeaways
related talks
50mFlutter — how to make a beautiful app in an hour?
44mFlutter for the Discerning Android Developer
41mWhy is Flutter the mobile SDK developers deserve...
25mFlutter: do more with less code
01h 13mFlutter and a Million Lines of Native Code
45mFlutter: A journey of productivity and happiness
34mAndroid with a side of Flutter, please
41mFlutter under the hood. What makes Flutter tick