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/windows. 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.

Windows

A primary window presents the main navigation and content of an app, and actions associated with them.
An auxiliary window presents a specific task or area in an app. Dedicated to one experience, an auxiliary window doesn’t allow navigation to other app areas, and it typically includes a button people use to close it after completing the task.

Best practices

Make sure that your windows adapt fluidly to different sizes to support multitasking and multiwindow workflows.

Choose the right moment to open a new window.

Consider providing the option to view content in a new window.

Avoid creating custom window UI.

Use the term window in user-facing content.

Platform considerations

iPadOS

Full screen. App windows fill the entire screen, and people switch between them — or between multiple windows of the same app — using the app switcher.
Windowed. People can freely resize app windows. Multiple windows can be onscreen at once, and people can reposition them and bring them to the front. The system remembers window size and placement even when an app is closed.
Full screen
Windowed

Make sure window controls don’t overlap toolbar items.

Consider letting people use a gesture to open content in a new window.

macOS

macOS window anatomy

macOS window states

Main. The frontmost window that people view is an app’s main window. There can be only one main window per app.
Key. Also called the active window , the key window accepts people’s input. There can be only one key window onscreen at a time. Although the front app’s main window is usually the key window, another window — such as a panel floating above the main window — might be key instead. People typically click a window to make it key; when people click an app’s Dock icon to bring all of that app’s windows forward, only the most recently accessed window becomes key.
Inactive. A window that’s not in the foreground is an inactive window.

Make sure custom windows use the system-defined appearances.

Avoid putting critical information or actions in a bottom bar, because people often relocate a window in a way that hides its bottom edge.

visionOS

visionOS windows

Prefer using a window to present a familiar interface and to support familiar tasks.

Retain the window’s glass background.

Choose an initial window size that minimizes empty areas within it.

Aim for an initial shape that suits a window’s content.

Choose a minimum and maximum size for each window to help keep your content looking great.

Minimize the depth of 3D content you display in a window.

visionOS volumes

Prefer using a volume to display rich, 3D content.

Place 2D content so it looks good from multiple angles.

In general, use dynamic scaling.

Take advantage of the default baseplate appearance to help people discern the edges of a volume.

Consider offering high-value content in an ornament.

Choose an alignment that supports the way people interact with your volume.

Windows

Windows

Best practices

Platform considerations

iPadOS

macOS

macOS window anatomy

macOS window states

visionOS

visionOS windows

visionOS volumes

Resources

Developer documentation

Videos

Change log

Get HIG guidance in your AI