native-mobile-designlisted

# Native Mobile Design Own one product-specific visual thesis while respecting genuine platform behavior. Native mobile is not responsive web at a smaller width. ## Start with product and platform evidence Inspect product goals, audience, tasks, content, brand, incumbent screens, navigation, components, tokens, assets, accessibility, repository stack, platform versions, and current changes. Establish a support matrix covering target OS versions, phones/tablets/foldables, orientations or window sizes, input methods, accessibility commitments, offline/high-latency behavior, and permitted cross-platform divergence. Identify whether delivery is native iOS, native Android, or cross-platform native mobile. Treat SwiftUI, UIKit, Jetpack Compose, Android Views, React Native, Expo, and Flutter as implementation contexts, not design styles. Do not infer a visual identity from the framework. ## Choose the interview mode Proceed when product, platform, and direction are clear. Otherwise ask one focused batch about target platforms, audience, primary job, identity, navigation, offline needs, device range, and non-negotiable conventions. Offer materially different directions only when creative direction remains unresolved. If direction is delegated, state assumptions and choose. ## Load detailed platform guidance progressively Read [references/platform-behavior.md](references/platform-behavior.md) when establishing navigation, system integration, gestures, lifecycle, accessibility,