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

Segmented controls — Apple HIG Design Guidelines

Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/segmented-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.

Best practices

Use a segmented control to provide closely related choices that affect an object, state, or view.

Consider a segmented control when it’s important to group functions together, or to clearly show their selection state.

Keep control types consistent within a single segmented control.

Limit the number of segments in a control.

In general, keep segment size consistent.

Content

Prefer using either text or images — not a mix of both — in a single segmented control.

As much as possible, use content with a similar size in each segment.

Use nouns or noun phrases for segment labels.

Platform considerations

iOS, iPadOS

Consider a segmented control to switch between closely related subviews.

macOS

Consider using introductory text to clarify the purpose of a segmented control.

Use a tab view in the main window area — instead of a segmented control — for view switching.

Consider supporting spring loading.

tvOS

Consider using a split view instead of a segmented control on screens that perform content filtering.

Avoid putting other focusable elements close to segmented controls.

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

Segmented controls