Navigation should reflect the user's mental model of the information. Use a hierarchy when people move from broad categories to detail, peer destinations when several top-level areas have equal importance, and temporary presentation when a short task should not change the user's place. Each screen needs a recognizable destination, a clear way back, and a small set of next actions. Preserve location and unfinished state when users switch sections. Favor established iOS controls and gestures because their behavior is already learned, but validate the structure with realistic tasks: users should reach important content without guessing, unnecessary detours, or multiple conflicting routes to the same state.

Designing Predictable iOS Navigation

iOS apps can use three navigation styles. Hierarchical navigation presents successive choices that lead to a destination; reaching a different destination may require retracing the hierarchy or starting again with different choices. Flat navigation lets users switch among multiple content categories. Content-driven or experience-driven navigation allows free movement through content or lets the content itself determine the path. An app may combine these styles, such as using flat navigation between categories and hierarchical navigation within each category.

University of Michigan - Ann Arbor

Google

App Architecture

A loading state should answer two questions for the user: whether the application is still working and what can happen next. Show the destination layout promptly, reserve space for content that has not arrived, and replace placeholders without shifting the page unexpectedly. Use a determinate progress indicator when completion can be estimated; otherwise use a restrained activity indicator and a specific status message. Keep navigation and cancellation available when the underlying operation permits them. For recurring workflows, caching and prefetching are usually more valuable than elaborate loading animation because they reduce the wait itself.

Designing Useful Loading States

The launch experience of an iOS application should be fast and seamless to positively impact user perception. Key guidelines for a delightful launch include providing a responsive launch screen, launching in the appropriate device orientation, and avoiding upfront requests for setup information so the app can function immediately.

iOS App Launch Experience

To build user trust and ensure a seamless experience, iOS apps should follow key guidelines when requesting permissions:

* **Contextual Requests:** Ask for personal data only when a feature clearly needs it, rather than upfront.
* **Explain the Purpose:** Provide a clear, short, and polite custom purpose string (usage description) within the system alert to explain why the data is needed, using sentence case and avoiding repeating the app name.
* **Launch-time Requests:** Only request permissions at launch if the app cannot function without them.
* **Check System Settings First:** Check if services (like Location Services) are enabled globally before triggering permission prompts to avoid unnecessary alerts.
* **Use Standard Alerts:** Always use system-provided alerts rather than custom prompts that mimic them.

iOS App Permission Request Guidelines

Modality is a design technique that presents content in a temporary mode separate from the user's current context and requires an explicit action to exit.

Modality helps users focus on a self-contained task or set of closely related options, and ensures they receive and act on critical information.

In iOS, modal content is provided through Alerts, Activity Views (or Share sheets), and Action Sheets. iOS supports specific presentation styles for custom modal content, such as sheets and full-screen views.

iOS App Modality

Onboarding in iOS applications should welcome users and help them get the most out of the app. To design an effective onboarding experience, developers should:

* **Get to the action quickly:** Allow users to skip tutorials and avoid showing them to returning users.
* **Avoid setup details:** Exclude licensing, configuration, or setup details from the onboarding flow.
* **Anticipate help needs:** Look for moments where users might get stuck, and allow them to replay tutorials.
* **Encourage interactive learning:** Use animations and interactivity to teach gradually and in context rather than using static screenshots or text instructions.
* **Prioritize intuitive design:** Keep tutorials minimal, as education should not substitute for intuitive app design.

iOS App Onboarding Guidelines

To design a seamless user experience, iOS apps should minimize the need for configuration settings by prioritizing defaults and querying system information. Key guidelines include:

* **Minimize Settings:** Design the app to work well out-of-the-box, inferring user environment or location from the system rather than requesting manual entry.
* **Prioritize Options:** Place essential, frequently changed options on the main screen, and secondary options on secondary screens. Expose rarely changed options in the system Settings app.
* **Facilitate Access:** Keep configuration direct and convenient within the app when possible. If users must go to the system Settings app, provide a direct shortcut.

Learn Before

Related

Learn After