Native mobile interaction

Adapts shared mobile product flows to familiar iOS and Android interaction conventions without changing their business meaning.

ios-android-design-guidelines

Team members using this skill

AgentMira

See how it helps

When is it useful?

Use it when the same feature ships on both platforms but navigation, sheets or system interactions need native behavior.

What does it help you do?

Keeps business logic consistent across iOS and Android.
Adapts back navigation, sheets, pickers and permission interactions.
Respects safe areas and platform expectations before custom controls.

Try asking this

Design the same booking flow with appropriate iOS and Android navigation. Choose a date, open a sheet and return without confirming. The booking data should persist while Back and dismissal follow each platform's expected behavior.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

iOS & Android Design Guidelines

Balance a cohesive cross-platform product identity with the native interaction conventions users expect on iOS and Android.

Shared Logic vs Platform Conventions

Preserve shared product logic: Keep core domain terminology, business rules, user journeys, information hierarchy, and brand visual identity consistent across platforms.
Adapt platform-native interactions: Respect platform conventions where users have ingrained muscle memory (back navigation, sheet behaviour, pickers, system dialogs, permission prompts, share sheets, and system settings links).
Justify custom patterns: Only deviate from native platform conventions when the custom interaction delivers a clear usability advantage that outweighs its learning cost.

iOS Conventions (Human Interface Guidelines)

Navigation & hierarchy: Bottom tab bars for top-level destinations; standard navigation bars with large-title-to-inline transitions where appropriate; interactive leading-edge swipe-back gesture.
Modality: Pull-down dismissible sheets with optional detents (medium/large) and grabber indicators; explicit Cancel and Done/Save actions when edits require confirmation.
Controls & pickers: Native-style wheel or compact inline date/time pickers, segmented controls for closely related views (2–4 segments), and context menus on long press with visible primary action alternatives.
Safe areas: Respect Dynamic Island / notch top insets and the bottom Home Indicator area.

Android Conventions (Material Design)

Navigation & back handling: Bottom navigation bar (3–5 destinations), top app bars, and full support for the system predictive back gesture across screens, sheets, and dialogs.
Modality & actions: Modal bottom sheets, standard Material dialogs, snackbars anchored above bottom navigation or FABs, and Floating Action Buttons (FAB) only when a single primary creation action dominates the screen.
Edge-to-edge layout: Design for edge-to-edge rendering with proper status bar and gesture/3-button navigation bar insets.

Documenting Platform Divergences

Whenever a flow or component differs between iOS and Android, document both variants side by side so the mobile developer does not have to guess how to adapt the design.

Included files 1

SKILL.md