Add a Flutter module to an existing app
summary
A Flutter module integrates into an existing Kotlin/Swift app as a UI-only feature and ships to stores after a 1–2 day POC and normal development, serving one module in a mid‑large app with ~1–2M MAU. Development uses method channels for native–Flutter communication and either direct source linking or the Android AAR output (Flutter build AAR produces a Maven repo), with iOS frameworks handled manually; build-time cost is measurable (+8% from source, +2% with AAR) and integration works but requires extra cross‑team coordination.
AI-written summary · about
chapters (18)
- 0:00Intro
- 5:15Crossplatform frameworks
- 10:20Flutter generalities
- 15:18Flutter project strategy
- 20:44How does it work
- 22:27How to integrate
- 25:25Flutter build types
- 27:01Flutter module responsibilities
- 27:39Metal Channels
- 28:16How it works
- 29:13Development process
- 30:36Native developers
- 32:19Other team members
- 35:15Design
- 36:44Conclusion
- 40:06Other features
- 40:52Expectations
- 42:16Final word
related talks
46mAdd Flutter to your existing mobile app
47mHow to add Flutter to your existing app
26mAdding Flutter to Your Android App
30mAdding Flutter to your Android app
34mHow to add Flutter to your existing app
28mSeamless Fusion: A Deep Dive into Flutter's Add-to-App Magic
30mAdding Flutter to your app - what are they not telling you?
22mEmbedding Flutter In Your App for Fun and Profit