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/game-controls. 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.

Game controls

Even though all platforms except watchOS support physical game controllers, not every player might have access to one.
Players appreciate games that let them use the platform interaction method they’re most familiar with.

Touch controls

Determine whether it makes sense to display virtual controls on top of game content.

Place virtual buttons where they’re easy to access.

Make sure controls are large enough.

Always include visible and tactile press states.

Use symbols that communicate the actions they perform.

Show and hide virtual controls to reflect gameplay.

Visible control
Hidden control

Combine functionality into a single control.

Map movement and camera controls to predictable behavior.

Physical controllers

Support the platform’s default interaction method.

Tell people about game controller requirements.

Automatically detect whether a controller is paired.

Customize onscreen content to match the connected game controller.

Map controller buttons to expected UI behavior.

Support multiple connected controllers.

Prefer using symbols, not text, to refer to game controller elements.

Keyboards

Prioritize single-key commands.

Test key binding comfort game using an Apple keyboard.

Take the proximity of keys into account.

Let players customize key bindings.

Game controls

Game controls

Touch controls

Physical controllers

Keyboards

Platform considerations

visionOS

Resources

Developer documentation

Videos

Change log

Get HIG guidance in your AI