When Not Flutter
Flutter is not the default for every app.
Do Not Choose Flutter When
| Situation | Prefer |
|---|---|
| Android-only app with deep platform APIs | Android Kotlin Compose |
| iOS-only app with native platform feel as core value | SwiftUI/UIKit |
| SEO-heavy content site or marketing site | Astro, Next.js, SvelteKit, or another web stack |
| Admin dashboard with standard web UI | Web app stack |
| Tiny PWA-fit workflow | PWA or web app |
| Desktop utility needing native menus/tray/files first | Native desktop or Tauri-style stack |
| Team rejects Dart/Flutter lock-in | Native or web stack already owned by the team |
| Release budget cannot cover app stores/signing/devices | Web first |
Pushback Prompt
Ask:
What specific cross-platform benefit pays for Dart, Flutter, plugin, and release complexity?If the answer is only “maybe iOS later”, do not default to Flutter. Choose the stack that ships the first real target fastest.