How should I design an iPad app using Apple's HIG?

Apple's HIG recommends using sidebars instead of bottom tab bars on iPadOS, supporting split views for multitasking, and adding pointer interactions. Apple HIG Skills provides instant, AI-ready guidance on all iPadOS conventions.

What are Apple's guidelines for adding Apple Pay?

Apple's HIG specifies exact payment button placement, flow design, error states, and UX patterns required for App Store approval. Apple HIG Skills gives your AI agent access to the full Apple Pay design guidelines.

How do I make my Apple app accessible?

Apple's HIG requires support for VoiceOver, Dynamic Type, sufficient color contrast ratios, and motor accessibility features like Switch Control. Apple HIG Skills covers all accessibility foundations and requirements.

How do I design for visionOS and Apple Vision Pro?

Apple's HIG for visionOS covers ornaments, volumes, immersive spaces, eye tracking, and spatial interaction patterns. Apple HIG Skills includes dedicated visionOS platform guidance and spatial layout references.

What are Apple's dark mode design guidelines?

Apple's HIG specifies using system semantic colors, material backgrounds, elevated surfaces, and vibrancy for dark mode. Apps should test in both modes and avoid hard-coded color values. Apple HIG Skills covers the full dark mode specification.

How should I design notifications for iOS apps?

Apple's HIG covers notification grouping, Live Activities, action buttons, and respecting user attention. Apple HIG Skills provides guidelines for the full notification system including widgets and complications.

Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/progress-indicators. This file is a structured index of that content, snapshot 2025-02-02. Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

Progress indicators

Determinate , for a task with a well-defined duration, such as a file conversion
Indeterminate , for unquantifiable tasks, such as loading or synchronizing complex data

Best practices

When possible, use a determinate progress indicator.

Be as accurate as possible when reporting advancement in a determinate progress indicator.

Keep progress indicators moving so people know something is continuing to happen.

When possible, switch a progress bar from indeterminate to determinate.

Don’t switch from the circular style to the bar style.

If it’s helpful, display a description that provides additional context for the task.

Display a progress indicator in a consistent location.

When it’s feasible, let people halt processing.

Let people know when halting a process has a negative consequence.

Progress indicators

Progress indicators

Best practices

Platform considerations

iOS, iPadOS

Refresh content controls

macOS

watchOS

Resources

Developer documentation

Change log

Get HIG guidance in your AI