Separate iOS and Android to Flutter Blueprint
Merge separate native iOS and Android apps into a single Flutter (Dart) codebase using add-to-app and platform channels, migrating screens incrementally and reusing native SDKs via type-safe channels.
What and Why
Flutter renders its own UI with the Skia/Impeller engine, giving pixel-identical, high-performance widgets across iOS and Android from one Dart codebase. Unlike bridge-based approaches, Flutter does not rely on platform UI widgets, which yields consistent visuals and smooth animations. This blueprint consolidates two native apps into Flutter while reusing native code through platform channels and the add-to-app integration.
Phases
Assessment. Inventory screens, native SDKs, and platform behaviors. Choose between a full rewrite and add-to-app (embedding Flutter modules into the existing native apps). Evaluate widget availability against your design system and Impeller readiness.
Foundation. Set up the Flutter project, state management (Riverpod or Bloc), routing (go_router), a typed API client, and a widget library implementing your design tokens. Configure CI with Fastlane/Codemagic.
Screen migration. Using add-to-app, embed Flutter screens inside the native shells and migrate flows incrementally behind feature flags. Keep native screens until each is ported.
Platform channels. Bridge remaining native SDKs (payments, biometrics, Bluetooth, push) via MethodChannel/EventChannel or Pigeon-generated type-safe interfaces. Reuse existing Swift/Kotlin implementations.
Cutover. Once all flows are Flutter, collapse the native shells, unify the release pipeline, and ship a single Flutter app per store.
Key Risks and Mitigations
- Skills gap: Dart and the widget model are new; budget ramp-up and use established architecture patterns.
- Platform parity: Test on real iOS and Android devices; verify channel behavior and lifecycle handling.
- Performance on older devices: Profile with DevTools; prefer Impeller and avoid expensive rebuilds.
Recommended Tooling
Flutter with Impeller, Dart, go_router, Riverpod or Bloc, Pigeon for type-safe channels, Fastlane/Codemagic for builds, and integration_test/Maestro for end-to-end testing.
Success Metrics
Faster cross-platform lead time, improved team efficiency, stable crash-free rate, and consistent UI across platforms.
Prerequisites
A design system, mobile CI/CD, store credentials, and a decision on add-to-app versus full rewrite based on native SDK complexity.