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

Sheets

Best practices

Use a sheet to present simple content or tasks.

For complex or prolonged user flows, consider alternatives to sheets.

Display only one sheet at a time from the main interface.

Use a nonmodal view when you want to present supplementary items that affect the main task in the parent view.

Platform considerations

iOS, iPadOS

In an iPhone app, consider supporting the medium detent to allow progressive disclosure of the sheet’s content.

Include a grabber in a resizable sheet.

Support swiping to dismiss a sheet.

Position Done and Cancel buttons as people expect.

Prefer using the page or form sheet presentation styles in an iPadOS app.

macOS

Present a sheet in a reasonable default size.

Let people interact with other app windows without first dismissing a sheet.

Position a sheet’s dismiss buttons as people expect.

Use a panel instead of a sheet if people need to repeatedly provide input and observe results.

visionOS

Avoid displaying a sheet that emerges from the bottom edge of a window.

Present a sheet in a default size that helps people retain their context.

watchOS

Use a sheet only when your modal task requires a custom title or custom content presentation.

Keep sheet interactions brief and occasional.

Change the default label of the dismiss control only if it makes sense in your app.

If you change the default label, prefer using SF Symbols to represent the action.

Sheets

Sheets

Best practices

Platform considerations

iOS, iPadOS

macOS

visionOS

watchOS

Resources

Developer documentation

Change log

Get HIG guidance in your AI