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/pull-down-buttons. 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.

Pull-down buttons

Best practices

Use a pull-down button to present commands or items that are directly related to the button’s action.

An Add button could present a menu that lets people specify the item they want to add.
A Sort button could use a menu to let people select an attribute on which to sort.
A Back button could let people choose a specific location to revisit instead of opening the previous one.

Avoid putting all of a view’s actions in one pull-down button.

Balance menu length with ease of use.

Display a succinct menu title only if it adds meaning.

Let people know when a pull-down button’s menu item is destructive, and ask them to confirm their intent.

Include an interface icon with a menu item when it provides value.

Pull-down buttons

Pull-down buttons

Best practices

Platform considerations

iOS, iPadOS

Resources

Developer documentation

Change log

Get HIG guidance in your AI