Does HIG Doctor expose an MCP server?

Yes. The hig-mcp server exposes hig_list_skills, hig_lookup, and hig_audit so MCP-compatible coding agents can list HIG skills, fetch reference topics, and run project audits.

What frameworks can the HIG audit CLI scan?

The audit CLI scans SwiftUI, UIKit, React, Next.js, Vue, Svelte, Angular, React Native, Flutter, Jetpack Compose, Android XML, HTML, and CSS.

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. HIG Doctor 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. HIG Doctor 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. HIG Doctor 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. HIG Doctor 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. HIG Doctor 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. HIG Doctor provides guidelines for the full notification system including widgets and complications.

Activity views — Apple HIG Design Guidelines

Best practices

Avoid creating duplicate versions of common actions that are already available in the activity view.

Consider using a symbol to represent your custom activity.

Write a succinct, descriptive title for each custom action you provide.

Make sure activities are appropriate for the current context.

Use the Share button to display an activity view.

In iOS and iPadOS, share and action extensions are displayed in the share sheet that appears when people choose an Action button.
In macOS, people access share extensions by clicking a Share button in the toolbar or choosing Share in a context menu. People can access an action extension by holding the pointer over certain types of embedded content — like an image they add to a Mail compose window — clicking a toolbar button, or choosing a quick action in a Finder window.

If necessary, create a custom interface that feels familiar to people.

Streamline and limit interaction.

Avoid placing a modal view above your extension.

If necessary, provide an image that communicates the purpose of your extension.

Use your main app to denote the progress of a lengthy operation.

For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/activity-views

Apple HIG text and imagery are © Apple Inc. This page is a structured index of Apple’s canonical documentation (snapshot 2025-02-02), provided for quick reference and AI-agent consumption — it isn’t affiliated with or endorsed by Apple. Read the original at developer.apple.com.

Activity views

Best practices

Share and action extensions

Get HIG guidance in your AI