メニュー
Decision framework for choosing between native iOS/Android, Flutter, React Native, and Kotlin Multiplatform for a new or migrating mobile project. Use when the stack is undecided or being revisited.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mobile-tech-stack-selection |
| description | Decision framework for choosing between native iOS/Android, Flutter, React Native, and Kotlin Multiplatform for a new or migrating mobile project. Use when the stack is undecided or being revisited. |
Stack choice is a one-way door for most of the codebase. Use an explicit decision framework rather than taste. The goal is to pick the stack whose strengths match the project's constraints.
Score each stack against the project on these dimensions:
| Dimension | Weight signal |
|---|---|
| Time-to-first-build on both platforms | Small team, tight deadline -> high |
| Platform API reach (Bluetooth, ARKit, CameraX, HealthKit) | Deep native integration -> native wins |
| UI fidelity with platform conventions | Banking, productivity apps -> native or KMP+native UI |
| Shared business logic reuse | Complex domain, multiple clients -> KMP shines |
| Hot reload / iteration speed | Rapid design iteration -> Flutter, RN |
| Binary size sensitivity | Emerging markets, tight APK -> native |
| Team skillset | Existing Kotlin team -> KMP/Android; web team -> RN |
| Hiring pool in your geography | Plain Android/iOS typically deepest |
| Long-term maintenance risk | Stack longevity, vendor neutrality |
The same "show a user name" problem in each stack, so the agent can reason about equivalence:
// Swift / SwiftUI
struct UserView: View {
let name: String
var body: some View { Text(name).font(.headline) }
}
// Kotlin / Jetpack Compose
@Composable
fun UserView(name: String) {
Text(name, style = MaterialTheme.typography.titleMedium)
}
// Dart / Flutter
class UserView extends StatelessWidget {
const UserView({super.key, required this.name});
final String name;
@override
Widget build(BuildContext context) =>
Text(name, style: Theme.of(context).textTheme.titleMedium);
}
// TypeScript / React Native
export function UserView({ name }: { name: string }) {
return <Text style={{ fontSize: 20, fontWeight: '600' }}>{name}</Text>;
}
Write the outcome as an ADR. Do not let it live in Slack.
# ADR-001: Mobile Stack
## Status
Accepted 2026-04-19.
## Context
- Team: 3 engineers (2 Android/Kotlin, 1 iOS/Swift).
- Product: B2C fitness tracker, heavy HealthKit/Google Fit integration.
- Constraints: 4-month MVP, both platforms at launch.
## Options considered
1. Native iOS + Native Android
2. Flutter
3. React Native (Expo)
4. KMP + native UI
## Decision
KMP shared domain + native UI on each platform.
## Consequences
+ Native HealthKit / Health Connect access with no plugin lag.
+ Domain rules written once.
- Initial setup cost; KMP toolchain maturity on iOS requires attention.
- Hiring for iOS + KMP is narrower than pure iOS.
Revisit the stack decision when:
Navigation patterns for mobile apps (stack, tab, modal, drawer, nested flows) with platform conventions across SwiftUI, Compose, Flutter, and React Native. Use when structuring navigation or handling deep links.
Comparison of mobile state management patterns (MVVM, MVI, TEA, Redux, BLoC, Observable, Compose state, SwiftUI state) and how to choose. Use when designing state flow or evaluating a state library.
Canonical mobile UI patterns (list, detail, tab, sheet, master-detail, search, form) with platform-aware guidance across SwiftUI, Compose, Flutter, and React Native. Use when designing or reviewing screens.
Mobile app lifecycle across iOS and Android (foreground, background, suspended, killed), state restoration, process death, and cross-platform parallels in Flutter and React Native. Use when handling background work, persistence of in-flight state, or resume flows.
Implementing and testing deep links on mobile - Android App Links, iOS Universal Links, custom URL schemes, attribution providers, and sunset guidance for Firebase Dynamic Links. Use when adding, debugging, or migrating deep link behavior.
End-to-end push notifications on mobile - FCM and APNs architecture, payload shapes, notification vs data messages, permissions, and cross-platform handling in Flutter and React Native. Use when adding, debugging, or rearchitecting push.