Flutter Integration Strategies for iOS Projects: Source Code and Product Approaches

The article begins by introducing Flutter as Google's open-source mobile UI framework for building high-quality native interfaces on iOS and Android.

It outlines two main integration methods: source code integration, recommended by Flutter, and product (binary) integration, which packages Flutter as a Pod.

Source code integration requires adding Flutter to the Podfile, running pod install, and disabling bitcode, while product integration generates Flutter.framework and App.framework after pod install.

The author identifies challenges with source code integration: all native developers must install and match Flutter versions, inconsistent paths via CocoaPods, and frequent submodule updates affecting native workflow.

Product integration aims for low intrusion, easy local debugging, and no impact on native build processes, but still requires obtaining the Flutter Pod via other means.

Analysis of the pod install process reveals two key scripts: podhelper.rb, which installs Flutter framework, plugins, and assets, and xcode_backend.sh, which builds and assembles Flutter resources into the appropriate locations.

The article details the build steps: running flutter packages get, building AOT and bundle, copying flutter_assets into App.framework, and copying Flutter.framework and related files into the product.

To support both source code debugging and product‑based integration without modifying the Podfile, the team introduces environment‑variable‑driven configuration: a flutter-debug.sh script sets FLUTTER_TYPE=debug and FLUTTER_APPLICATION_PATH before pod install, and a flutter-build.sh script reads a flutterConfig file to decide whether to invoke the debug build flow.

The Podfile is updated to read FLUTTER_APPLICATION_PATH and FLUTTER_TYPE from the environment, conditionally calling install_all_flutter_pods for debug builds.

A flutterConfig file (ignored by git) stores the selected Flutter path and debug flag, generated by the helper scripts.

The final solution enables native developers to integrate Flutter via a simple pod install, while Flutter developers can switch to source‑code debugging by running flutter-debug.sh, preserving native workflows and reducing integration overhead.