When content is loading, a blank or static screen can make it seem like your app is frozen, resulting in confusion and frustration, and potentially causing people to leave your app.

Make it clear when loading is occurring. At minimum, show an activity spinner that communicates something is happening. Even better, display explicit progress so people can gauge how long they’ll be waiting.

Show content as soon as possible. Don’t make people wait for content to load before seeing the screen they're expecting. Show the screen immediately, and use placeholder text, graphics, or animations to identify where content isn't available yet. Replace these placeholder elements as the content loads. Whenever possible, preload upcoming content in the background, such as while an animation is playing or the user is navigating a level or menu.

Educate or entertain people to mask loading time. Consider showing hints about gameplay, entertaining video sequences, or interesting placeholder graphics.

Customize loading screens. Although standard progress indicators are usually OK, they can sometimes feel out of context. Consider designing a more immersive experience through custom animations and elements that match the style of your app or game.

Loading

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

Some apps may need to provide a way to make setup or configuration choices, but most apps can avoid or delay doing so. Successful apps work well for most people right away, while also offering some convenient ways to adjust the experience. When you design your app to function the way most people expect, you decrease the need for settings.

Infer what you can from the system. If you need information about the user, device, or environment, query the system for it whenever possible instead of asking the user. For example, instead of asking someone to enter their zip code so you can present local options, ask permission to use their current location. Gracefully fall back to manual entry if the user denies access to their information.

Thoughtfully prioritize configuration options within your app. Your app’s main screen is a good place for options that are essential or that change frequently. Secondary screens are better for options that change only occasionally.

Expose infrequently changed configuration options in Settings. The Settings app is a central location for making configuration changes throughout the system, but people must leave your app to get there. It’s far more convenient to adjust settings directly within your app. If you must provide settings that rarely require change, see Implementing an iOS Settings Bundle in Preferences and Settings Programming Guide for developer guidance.

Provide shortcuts to Settings when appropriate. If your app includes text that directs users to Settings, such as “Go to Settings > MyApp > Privacy > Location Services,” provide a button that opens that location automatically. For developer guidance, see openSettingsURLString in UIApplication.

Settings

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

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