メニュー
How to write and maintain Architecture Decision Records (ADRs) for mobile teams, and the canonical set of decisions every mobile project must record. Use when starting a project or when an architectural change is being proposed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mobile-architecture-decisions |
| description | How to write and maintain Architecture Decision Records (ADRs) for mobile teams, and the canonical set of decisions every mobile project must record. Use when starting a project or when an architectural change is being proposed. |
Most mobile architecture debates repeat across projects. Capture decisions in Architecture Decision Records (ADRs) so the agent and future contributors inherit context instead of re-arguing it.
Keep ADRs short, markdown, and numbered. One decision per file under docs/adr/.
# ADR-0007: Use Coroutines + Flow for Android Domain Layer
## Status
Accepted 2026-04-19. Supersedes ADR-0003.
## Context
- We had RxJava in the legacy Android app; iOS uses Combine.
- New domain logic is being shared via KMP.
## Decision
Use Kotlin Coroutines and Flow in the shared domain and Android presentation.
Bridge to Swift via KMP suspend interop; do not introduce RxSwift on iOS.
## Consequences
+ One async primitive across Kotlin codebases.
+ Structured concurrency is a first-class feature.
- Swift side needs adapter helpers for Flow collection.
- RxJava usages in legacy modules must be migrated or frozen.
Lifecycle states: Proposed, Accepted, Superseded by ADR-NNNN, Deprecated. Never delete ADRs.
Every mobile project should have accepted ADRs covering at least:
mobile-tech-stack-selection).An ADR becomes mandatory when a decision:
Otherwise, a code comment or CODEOWNERS note is enough.
Use this to seed ADRs on day one. Adjust to the chosen stack.
| Concern | Native iOS | Native Android | Flutter | React Native | KMP |
|---|---|---|---|---|---|
| UI pattern | SwiftUI + MV | Compose + MVVM | Widgets + Riverpod/BLoC | RN + hooks + Redux/Zustand | Compose MP or native UI |
| Nav | NavigationStack | Navigation-Compose | go_router | React Navigation | expect/actual + platform nav |
| Async | async/await | Coroutines + Flow | Future / Stream | async/await + RxJS optional | Coroutines + Flow |
| Persistence | Core Data / SwiftData | Room | Drift / sqflite | WatermelonDB / SQLite | SQLDelight |
| DI | plain init + EnvironmentObject | Hilt / Koin | Riverpod / get_it | plain context / DI libs | Koin |
| HTTP | URLSession | Retrofit / Ktor | Dio | fetch / axios | Ktor |
| Errors | typed enums + Result | sealed class + Result | sealed unions (freezed) | discriminated unions | sealed class |
# Architecture Decisions
| # | Title | Status |
| --- | --- | --- |
| 0001 | Mobile stack: KMP + native UI | Accepted |
| 0002 | Minimum iOS 15 / Android 24 | Accepted |
| 0003 | Compose MVVM with unidirectional data flow | Accepted |
| 0004 | Networking via Ktor shared client | Accepted |
| 0005 | SQLDelight for persistence | Accepted |
| 0006 | Crashlytics + Sentry for releases | Accepted |
| 0007 | Coroutines + Flow async model | Accepted |
docs/adr/ exists with the canonical ADR set for the project.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.