The Human Interface Guidelines (HIG) are Apple’s official body of design guidance that describes how apps should look, behave and communicate on iOS, iPadOS, macOS, watchOS, tvOS and visionOS. In Mobile UX, the HIG serves as the reference standard for iPhone and iPad design, defining navigation patterns, controls, typography, spacing, gestures and accessibility expectations that users already know from the system itself.
The HIG is guidance rather than a rulebook: it explains principles and recommended patterns, and only some of its points are enforced indirectly through App Store review. Its main value is platform consistency, because an app that follows system conventions feels familiar from the first launch.
Principles behind the Human Interface Guidelines
The Human Interface Guidelines rest on a small set of design principles that recur throughout every chapter. Historically Apple framed them as clarity, deference and depth: content comes first, the interface supports it without competing for attention, and layering and motion communicate hierarchy. Later editions extend these ideas with an explicit focus on hierarchy, harmony and consistency across devices.
In practice, these principles translate into concrete expectations. Text must remain legible at every size, controls must look interactive, and visual effects such as translucency or animation must explain structure rather than decorate it. The table below connects each principle to its practical consequence.
| Principle | Meaning | Practical consequence |
|---|---|---|
| Clarity | Every element is understandable at a glance | Legible type, precise icons, plain labels |
| Deference | The interface supports content | Minimal chrome, restrained decoration |
| Depth | Layers and motion show hierarchy | Sheets, transitions, translucent bars |
| Consistency | Apps follow system conventions | Standard controls behave as users expect |
| Accessibility | Everyone can use the app | Dynamic Type, VoiceOver, sufficient contrast |
What the HIG covers for iPhone and iPad
For mobile apps, the HIG is organized into foundations, patterns, components and inputs. Foundations cover color, typography, layout, icons and accessibility; patterns describe tasks such as onboarding, searching or managing notifications; components define standard elements such as tab bars, navigation bars, sheets and alerts.
Several specifications have measurable values that designers apply directly. The most frequently cited is the minimum touch target of 44 by 44 points, which keeps controls reliably tappable. Layout guidance relies on the safe area and layout margins so that content avoids the rounded corners, the Dynamic Island and the home indicator.
| Area | Guidance | Why it matters |
|---|---|---|
| Touch target | At least 44 x 44 points | Reduces mistaps, especially for motor impairments |
| Body text | 17 points by default, scales with Dynamic Type | Readable for users with different vision |
| Safe area | Keep essential content inside insets | Avoids clipping by hardware features |
| Tab bar | Typically three to five top-level sections | Keeps primary navigation scannable |
| Color contrast | Sufficient contrast in light and dark mode | Maintains legibility in all appearances |
The HIG also defines expected gesture behavior. The edge swipe to go back, pull to refresh and swipe actions in lists are system conventions, and overriding them with custom meanings is one of the most common sources of user confusion in iOS apps.
Human Interface Guidelines compared with Material Design
The closest counterpart to the HIG is Material Design, Google’s design system for Android and the web. Both aim at consistent, accessible interfaces, but they differ in scope, philosophy and delivery, which matters for teams that ship one product on both platforms.
| Aspect | Human Interface Guidelines | Material Design |
|---|---|---|
| Owner | Apple | |
| Primary platforms | iOS, iPadOS, macOS, watchOS, tvOS, visionOS | Android, web, Flutter |
| Nature | Platform guidance tied to system frameworks | Design system with tokens and theming |
| Main navigation | Bottom tab bar and navigation stack | Navigation bar, rail or drawer |
| Primary action | Usually in the navigation bar | Often a floating action button |
| Brand customization | Restrained, system look preferred | Extensive theming encouraged |
Cross-platform teams usually adopt a shared brand layer for color, illustration and tone, while letting navigation, controls and gestures follow each platform. Forcing one platform’s conventions onto the other, such as a floating action button on iOS or an iOS-style back label on Android, tends to make the app feel foreign on both.
Applying the HIG in a design process
Teams apply the HIG most effectively by building on system components rather than reproducing them. SwiftUI and UIKit controls implement many guidelines automatically, including Dynamic Type scaling, dark mode, VoiceOver labels and standard spacing, so custom replacements must reimplement all of that behavior.
Apple publishes official design resources for common design tools, containing system components, icons and templates. Using them during wireframing keeps proportions accurate and makes developer handoff simpler, because designs map directly to native elements.
| Situation | Recommended approach | Reason |
|---|---|---|
| Standard navigation and forms | Follow the HIG closely | Users expect system behavior |
| Games and immersive media | Custom interface is acceptable | Content defines the experience |
| Strong brand identity | Customize color and imagery only | Keeps familiarity of controls |
| Accessibility features | Never deviate | Exclusion and review risk |
| New system release | Review updated guidance | Conventions change between versions |
Common misconceptions and mistakes
The HIG is frequently misunderstood as either a strict checklist or an optional style suggestion. Both readings cause problems: the first produces generic apps, the second produces apps that ignore user expectations and accessibility.
- Treating the HIG as static: Apple revises it with each major operating system release, so older screenshots and blog summaries become outdated.
- Equating HIG compliance with App Store approval: review enforces the App Review Guidelines, which overlap with but differ from the HIG.
- Ignoring Dynamic Type: fixed font sizes break layouts for users who choose larger text.
- Shrinking touch targets below 44 points to fit dense toolbars.
- Copying Android patterns directly into iOS builds of a cross-platform app.
A further limitation is that the HIG describes what good looks like but rarely prescribes measurable acceptance criteria. Teams therefore combine it with usability testing and accessibility audits to confirm that a design actually works for real users.
The idea in brief
The Human Interface Guidelines are Apple’s handbook for making apps that feel at home on an iPhone, iPad or Mac. They explain where buttons should go, how big they should be, how text should look and how gestures should behave.
Think of them as the local customs of a country. A visitor who follows them blends in and is understood easily. An app that follows them feels familiar from the first minute, because people already know how the rest of their device works.
A practical scenario
A small team is redesigning a banking app for iPhone after users complained that it was hard to navigate. The previous version used a hidden side menu, custom buttons about 30 points tall and fixed 14-point text that ignored the system text size setting.
Following the Human Interface Guidelines, the designers replace the side menu with a tab bar of four sections, enlarge every control to at least 44 by 44 points, switch to system text styles that support Dynamic Type and keep the standard edge swipe for going back. Transfers move into a sheet so that users can dismiss the flow with a familiar gesture.
In the following usability test, participants complete a transfer faster and with fewer wrong taps, and users with larger text settings can now read every screen without truncated labels.