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

Hierarchical Navigation
Make one choice per screen until you reach a destination. To go to another destination, you must retrace your steps or start over from the beginning and make different choices. Settings and Mail use this navigation style.

Flat Navigation
Switch between multiple content categories. Music and App Store use this navigation style.

Content-Driven or Experience-Driven Navigation
Move freely through content, or the content itself defines the navigation. Games, books, and other immersive apps generally use this navigation style.

Some apps combine multiple navigation styles. For example, an app that uses flat navigation may implement hierarchical navigation within each category.

Navigation

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.

iOS App Settings Guidelines

University of Michigan - Ann Arbor

IOS - Human Interface Guidelines are "software development documents which offer application developers a set of recommendations." Their goal is to improve the user experience by making more intuitive and consistent application interfaces. 

Learn Before

Related

Learn After