native-vs-flutter-decision
Use when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz task
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 122
- Forks
- 18
01 前言 Front Matter
- name
- native-vs-flutter-decision
- category
- architecture
- description
- Use when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz task
03 SKILL.md 正文
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
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 Android) — always follow it.
- The analiz task specifies native.
Hard Rule
Never introduce a second UI stack into a single-stack app. A Flutter app that "needs one native screen" embeds it via a platform view (PlatformView/AndroidView/UiKitView) or talks to it through a MethodChannel/Pigeon — it does not gain a parallel SwiftUI module on your initiative. Going the other way (a native app needing a Flutter module) is Flutter add-to-app, not a rewrite. Flag genuine cross-stack needs in a task comment for the architect.
Common Mistakes
- Picking your preferred stack over the app's.
- Reaching for native for something a Flutter plugin already does.
- Adding native modules to a Flutter app for a capability a platform channel covers.
Red Flags
- Your choice has no reason beyond preference.
- You're scaffolding a new Xcode target inside a Flutter repo.
04 同仓库更多 Skills
visual-craft
暂无简介
ux-copy
Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check
screen-mockup-html
Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task
performance-awareness
How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.
design-variants
Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision
design-system-authoring
Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns