Unity Integrating with Flutter and Native Apps
summary
A Unity 3D character is embedded into a 50+ module Flutter mono repo used by 20 million users, requiring Unity->Flutter->native Android/iOS layers, CI hooks and a model downloader to avoid a 200 MB Play Store cap. Integration exposes concrete problems: a 500 MB Unity export that grows to 1–2 GB, six platform build variants, NDK/Gradle/Xcode version mismatches, lifecycle crashes, and slow dev cycles; estimates of 3 weeks vs 3 months become real. AI helps generate scripts but does not debug cross‑platform build issues.
AI-written summary · about
chapters (11)
- 0:00Introduction to the project
- 1:31Understanding project scope
- 3:20Why Unity for 3D content
- 6:13Architecture and integration
- 8:53Unity and Flutter workflow
- 12:28Challenges with Unity
- 17:01Challenges with Flutter
- 21:15Android and iOS integration
- 26:35Platform lifecycle management
- 29:10AI role in the development
- 31:50Future improvements and conclusion
related talks
44mAdd a Flutter module to an existing app
36mFlutter Add-to-App: The Good, the Bad and the Ugly
22mEmbedding Flutter In Your App for Fun and Profit
01h 13mFlutter and a Million Lines of Native Code
23mFlutter For The Discerning Android Developer
28mAMA with Brian Egan and Filip Hracek
36mWhat I learnt by building the exact same app in Kotlin (Native Android), Nativescript and Flutter
44mFlutter for the Discerning Android Developer