Flutter Add-to-App: The Good, the Bad and the Ugly
summary
Proof of concept for a large Polish bank rewrites a complex flow into Flutter and ships it to production while keeping the host apps native, demonstrating engine pre-warm 860 ms iOS 1.5 s Android is essential because multiple Flutter engines are often required for interleaved native and Flutter navigation and background isolates. Asset reuse works on iOS via platform_images but not Android yet. Binary impact is tangible at 27 MB iOS 48 MB APK and performance can be improved with Flutter Engine Group and method channel contracts generated by Pigeon contract generator.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 1:51What is Flutter Add-to-App
- 3:59Reasons to use Add-to-App
- 6:51Proof of concept case study
- 8:40Navigation and Flutter engines
- 13:58UI considerations in Add-to-App
- 17:27Networking in Flutter modules
- 20:00Developer experience impact
- 22:14Building Flutter modules
- 24:20Native code integration
- 26:30Background processing with Flutter
- 27:57App size and performance impact
- 29:49Testing Flutter in native apps
- 31:19Legacy code and technical debt
- 33:44Team dynamics and adoption challenges
- 34:28Final takeaways and conclusion
related talks
36mFlutter Add-to-App: The Good, the Bad and the Ugly
28mSeamless Fusion: A Deep Dive into Flutter's Add-to-App Magic
50mFlutter: The Wizards of Widgets
38mFlutter: A Path of Vines and Flowers
49mFlutter In Practice – Tips and tricks for writing Flutter apps, from Start to Finish
25mStrategies for Add-to-App
34mAndroid with a side of Flutter, please
34mGoogle Flutter: The Next Frontier in Mobile Development