Seamless Fusion: A Deep Dive into Flutter's Add-to-App Magic
summary
Covers integrating a Flutter module into existing Kotlin and Swift apps using platform channels (method + event), Android via FlutterActivity/FlutterFragment and iOS with CocoaPods, showing a CRED case where add-to-app runs unnoticed in production. Recommends a shared engine with prewarm to avoid blank frames, cautions about state retention on logout and navigation ownership, quantifies tradeoffs: one-time binary size cost vs faster feature delivery, and warns common failures come from engine sprawl and tight coupling.
AI-written summary · about
chapters (18)
- 0:00Flutter Add-to-App intro
- 3:08What Add-to-App is
- 4:55Why Add-to-App in production
- 6:00When to use Add-to-App
- 7:46Add-to-App architecture
- 9:11Flutter engine lifecycle
- 11:35Navigation ownership
- 12:36Platform channel comms
- 14:01Android integration
- 15:05iOS integration
- 16:07Debugging Add-to-App
- 17:59Isolating Flutter features
- 18:20State management
- 19:44Performance optimization
- 21:48App size impact
- 23:40Memory lifecycle
- 26:11Add-to-App pitfalls
- 27:33Summary
related talks
46mAdd Flutter to your existing mobile app
34mAndroid with a side of Flutter, please
30mAdding Flutter to your app - what are they not telling you?
34mHow to add Flutter to your existing app
25mStrategies for Add-to-App
44mAdd a Flutter module to an existing app
36mFlutter Add-to-App: The Good, the Bad and the Ugly
30mAdding Flutter to your Android app