Run any Skill in Manus with one click

ios-navigation-and-ia

Stars6

Forks2

UpdatedApril 20, 2026 at 15:39

Use when deciding how an iPhone or iPad app should be organized, including tab bars, drill-down flows, sheets, settings grouping, information architecture, and navigation patterns that should feel native on iOS.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

phrypy

phrypy/ios-app-playbook

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

SKILL.md

readonly

name	ios-navigation-and-ia
description	Use when deciding how an iPhone or iPad app should be organized, including tab bars, drill-down flows, sheets, settings grouping, information architecture, and navigation patterns that should feel native on iOS.

iOS Navigation And IA

Users should understand where they are, how they got there, and how to leave.

Defaults

tab bars for primary destinations
navigation stacks for hierarchy
sheets for focused temporary tasks
settings grouped by user mental model

Use

tabs when destinations are peers
push navigation when moving deeper into one area
sheets when the task is self-contained
full-screen covers sparingly

Avoid

hamburger menus on iPhone without a strong reason
too many primary tabs
actions hidden where users expect structure
modal stacks that trap people

IA Test

can a new user predict where a feature lives
does each tab have a clear job
do screens get deeper only when needed
do actions live near the thing they affect

More from this repository

same repository

app-store-readiness

phrypy/ios-app-playbook

Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.

2026-06-236

app-store-screenshot-pipeline

phrypy/ios-app-playbook

Use when producing App Store screenshots from real app renders instead of faked CSS mockups, covering the headless simulator export stage, the composition-to-device-sizes stage, and the gotchas that quietly waste hours. Pairs with ios-app-store-optimization, which covers what the screenshots should say.

2026-06-236

ios-app-icon-and-brand-system

phrypy/ios-app-playbook

Use when designing or reviewing an iOS app icon, lightweight brand system, launch assets, screenshot consistency, or App Store-facing visual identity choices.

2026-06-236

ios-app-store-optimization

phrypy/ios-app-playbook

Use when shaping the conversion strategy for a real iOS App Store listing: positioning, metadata, the listing promise, and the message each visual asset must convey.

2026-06-236

ios-hig-design

phrypy/ios-app-playbook

Use when establishing or auditing the Apple-platform baseline for an iPhone or iPad interface, especially native conventions, system constraints, and HIG-aligned decisions.

2026-06-236

ios-interface-polish

phrypy/ios-app-playbook

Use after an iOS screen or flow works, when its visual execution, tactile feedback, or optical consistency still feels unfinished.

2026-06-236

name	ios-navigation-and-ia
description	Use when deciding how an iPhone or iPad app should be organized, including tab bars, drill-down flows, sheets, settings grouping, information architecture, and navigation patterns that should feel native on iOS.

iOS Navigation And IA

Users should understand where they are, how they got there, and how to leave.

Defaults

tab bars for primary destinations
navigation stacks for hierarchy
sheets for focused temporary tasks
settings grouped by user mental model

Use

tabs when destinations are peers
push navigation when moving deeper into one area
sheets when the task is self-contained
full-screen covers sparingly

Avoid

hamburger menus on iPhone without a strong reason
too many primary tabs
actions hidden where users expect structure
modal stacks that trap people

IA Test

can a new user predict where a feature lives
does each tab have a clear job
do screens get deeper only when needed
do actions live near the thing they affect