native-vs-flutter-decision

# Native vs Flutter Decision ## Overview Flutter is the default for cross-platform mobile; native (SwiftUI / Jetpack Compose) is chosen when a task needs deep platform integration or the app is already native. Decide at the start — you cannot half-migrate an app mid-task. **Core principle:** The existing app's stack wins by default. Only greenfield apps or the analiz task's direction open the choice. ## Decision ```dot digraph m { "App already single-stack?" [shape=diamond]; "Follow the app's stack" [shape=box]; "Needs deep platform integration?" [shape=diamond]; "Native (SwiftUI / Compose)" [shape=box]; "Flutter (default)" [shape=box]; "App already single-stack?" -> "Follow the app's stack" [label="yes"]; "App already single-stack?" -> "Needs deep platform integration?" [label="greenfield"]; "Needs deep platform integration?" -> "Native (SwiftUI / Compose)" [label="yes"]; "Needs deep platform integration?" -> "Flutter (default)" [label="no"]; } ``` ## Choose Flutter when - Cross-platform (iOS + Android) from one codebase, standard UI + platform-channel-level device access. - Greenfield app with no hard native requirement. - The app is already Flutter — always. ## Choose native when - The task needs platform capabilities Flutter exposes poorly: advanced widgets/animations tied to the OS, deep HealthKit/CarPlay/WidgetKit, App Clips, live activities, tight ARKit/CameraX use. - The app is already native (SwiftUI for iOS, Compose for ...