iOS Human Interface Guidelines: A Practical Summary
The iOS Human Interface Guidelines summarized: layout, safe areas, type sizes, color, navigation, controls, gestures and accessibility, with specs and a.

Apple's Human Interface Guidelines (HIG) are long, spread across hundreds of pages and written for every Apple platform at once. This summary is for founders, developers and designers building iPhone apps who want the rules that actually change how a screen is designed, with real numbers, without reading the whole thing first. Use it as a working reference, then go to Apple's site for the detail on any topic.
TL;DR: Design for the device: respect safe areas, keep tap targets at least 44 × 44 pt, use SF Pro with Dynamic Type, and use semantic system colors so dark mode and accessibility settings work. Navigate with tab bars, navigation stacks and sheets the way built-in apps do. Use system components and SF Symbols wherever you can, never override standard gestures, and test with VoiceOver and the largest text sizes before you ship.
What the Human Interface Guidelines are, and how they are organized
The HIG is Apple's official design guidance for all its platforms. App Review enforces the separate App Review Guidelines, but apps that ignore the HIG feel foreign, are harder to make accessible and take longer to build because they fight the system frameworks.
The current HIG is organized into sections:
| Section | What it covers | Read it when |
|---|---|---|
| Foundations | Layout, color, typography, icons, motion, accessibility, privacy, writing | Setting up your visual system |
| Patterns | Onboarding, launching, modality, searching, feedback, settings, loading | Designing flows |
| Components | Bars, buttons, lists, sheets, menus, pickers, text fields and more | Designing individual screens |
| Inputs | Touch gestures, keyboards, Apple Pencil, game controllers | Handling interaction |
| Technologies | Sign in with Apple, Apple Pay, widgets, Live Activities, HealthKit and others | Adding a system feature |
| Platforms | Platform-specific considerations | Targeting more than iPhone |
With iOS 26, Apple introduced a new design language called Liquid Glass: translucent, refractive controls and bars that float above content and adapt to what is behind them. If you build with standard SwiftUI or UIKit components, your app picks up much of this automatically. Check the HIG's "What's new" page for changes in the latest iOS release.
The principles behind the rules
Apple's guidance keeps returning to four ideas: content comes first and controls stay lighter than it; hierarchy is clear through size, weight and position; the app stays consistent with the platform so there is nothing to learn; and the person's settings for text size, motion, contrast and appearance are respected.
Layout and safe areas
iPhones come in several sizes with different hardware cut-outs. The HIG asks you to design adaptively, not for one screen.
Key layout numbers
| Item | Value |
|---|---|
| Common design base | 393 × 852 pt (iPhone 15/16 class) |
| Small iPhone to test | 375 × 667 pt (iPhone SE) |
| Large iPhone to test | 440 × 956 pt (iPhone 16 Pro Max class) |
| Standard side margin | 16 pt, wider on larger widths |
| Minimum hit target | 44 × 44 pt |
| Status bar | Varies by device; read the safe area inset, never hard-code |
| Home indicator | Keep interactive content out of the bottom safe area inset |
Points are not pixels: at 3x scale, 1 pt is 3 px. Design in points, export at 2x and 3x. Our detailed guide to safe areas and the Dynamic Island explains how insets behave on each device.
Layout rules worth memorizing
- •Extend backgrounds edge to edge, keep content inside safe areas. Images and colors can fill the whole screen; text and buttons cannot sit under the Dynamic Island or home indicator.
- •Align to a consistent grid. Use the system layout margins and keep spacing on a regular increment. Most teams use an 8 pt base with 4 pt half-steps.
- •Support both orientations where it makes sense. iPhone apps can be portrait-only, but iPad apps are expected to support all orientations and multitasking sizes.
- •Do not put critical content at the edges. Corners are rounded and gestures live near screen edges.
Typography
The system font on iPhone is SF Pro, which switches between Text and Display optical sizes automatically. New York is the system serif. Using them is not mandatory, but custom fonts should support Dynamic Type just as well.
Dynamic Type default sizes (Large, the default setting)
| Text style | Size | Weight |
|---|---|---|
| Large Title | 34 pt | Regular (bold in navigation bars) |
| Title 1 | 28 pt | Regular |
| Title 2 | 22 pt | Regular |
| Title 3 | 20 pt | Regular |
| Headline | 17 pt | Semibold |
| Body | 17 pt | Regular |
| Callout | 16 pt | Regular |
| Subheadline | 15 pt | Regular |
| Footnote | 13 pt | Regular |
| Caption 1 | 12 pt | Regular |
| Caption 2 | 11 pt | Regular |
These styles scale when users change their preferred text size, including much larger accessibility sizes. Practical rules:
- •Use text styles rather than fixed sizes, so your type scales.
- •11 pt is the smallest size Apple recommends for legible text.
- •Let layouts reflow at large sizes: stack horizontal rows vertically, wrap labels, and never truncate essential content.
- •Avoid light and thin weights for body text.
Build your own scale with the type scale generator, and see our mobile app typography guide for pairing and hierarchy.
Color and dark mode
iOS provides two families of colors you should use before inventing your own:
- •System colors such as systemBlue, systemGreen and systemRed, which adjust slightly between light and dark appearances and for increased contrast.
- •Semantic colors that describe purpose rather than hue: label, secondaryLabel, tertiaryLabel, systemBackground, secondarySystemBackground, separator and others.
Semantic colors are what make dark mode work without designing every screen twice. In dark mode, iOS uses a pure black base background on iPhone and lighter grays for elevated surfaces, so layering reads as depth.
Color rules from the HIG:
- •Pick one tint color for interactive elements and use it consistently. Do not use the same color for interactive and non-interactive elements.
- •Never rely on color alone to convey state. Pair it with an icon, label or shape.
- •Meet contrast minimums. Apple points to WCAG-style contrast; aim for at least 4.5:1 for body text and 3:1 for large text. Test with our contrast checker.
- •Test in both appearances and with Increase Contrast turned on.
For the full approach to dark palettes, read our dark mode app design guide.
Navigation
The HIG describes three main navigation structures. Most apps combine them.
| Structure | Use it for | Example |
|---|---|---|
| Flat (tab bar) | 3 to 5 peer sections users switch between often | Music, App Store, Instagram |
| Hierarchical (navigation stack) | Drilling from list to detail | Settings, Mail |
| Content-driven | Free movement through media or a game | Books, games |
Tab bars
- •Use tabs for top-level navigation only, not for actions like "Compose"; put actions in a toolbar or the content.
- •Keep tabs visible across the app, except in modal or full-screen experiences.
- •Each tab keeps its own navigation state; switching back returns to where the user left off.
- •Use SF Symbols with short one-word labels. On iPhone, more than five tabs is a sign the information architecture needs work.
Navigation bars
- •Show the current screen's title; use a large title on top-level screens that collapses as content scrolls.
- •The back button shows the previous screen's title or "Back" and sits on the leading edge.
- •Put no more than a couple of actions in the bar; move the rest into a menu.
Sheets and modality
Modality interrupts the current context, so use it for a focused, self-contained task: composing a message, adding an item, filtering, or a short form.
- •Sheets can use detents: medium (about half height) and large. A medium sheet is ideal when users need to see the content behind it, as in Maps.
- •Always provide an obvious way to dismiss, such as "Cancel" and "Done" buttons, plus swipe-down where safe.
- •If dismissing would lose data, confirm first.
- •Use full-screen modals sparingly, for immersive tasks like editing a photo or recording video.
Components: what to use and how
Apple's guidance for components is consistent: use the system version unless you have a strong reason not to, because it comes with accessibility, localization, Dynamic Type and appearance support for free.
| Component | Key guidance |
|---|---|
| Buttons | Make the primary action visually prominent; one prominent button per view is a good rule |
| Lists and tables | Use inset grouped style for settings-like content; swipe actions for common row actions |
| Text fields | Set the right keyboard type, content type for autofill and a clear placeholder |
| Toggles | Use for on/off settings that apply immediately; no "Save" needed |
| Pickers and date pickers | Use for choosing from a known list; prefer menus for short lists |
| Menus | Use for secondary actions and choices; keep them short and grouped |
| Segmented controls | Switch between closely related views; up to about five segments on iPhone |
| Alerts | Only for critical information or destructive confirmation; keep the message short |
| Action sheets / confirmation dialogs | Offer choices related to an action the user started |
| Search fields | Place at the top of a list; show recent searches and suggestions |
| Progress indicators | Determinate when you know duration; spinners for short indeterminate waits |
Alerts deserve special care: keep them rare, give them a short title and use specific verbs ("Delete," "Keep Editing") instead of "Yes" and "No," with destructive buttons styled as destructive.
Icons and SF Symbols
SF Symbols is Apple's library of thousands of configurable icons designed to align with San Francisco. Each symbol comes in nine weights and three scales and supports several rendering modes (monochrome, hierarchical, palette, multicolor), so icons match the weight of adjacent text.
Use SF Symbols for standard actions so meaning is instantly familiar, follow their license terms, and match their weight and optical size in any custom icons.
App icons follow their own rules: you supply a 1024 × 1024 px master, the system applies the rounded mask, and the icon should not include transparency. Recent iOS versions also support dark and tinted icon variants. See our app icon design guide for the grid, principles and export sizes.
Gestures and input
Users expect standard gestures to behave the same everywhere:
| Gesture | Expected behavior |
|---|---|
| Tap | Activate a control or select an item |
| Swipe from the left edge | Go back in a navigation stack |
| Swipe down on a sheet | Dismiss the sheet |
| Swipe on a list row | Reveal row actions |
| Long press | Show a context menu or preview |
| Pull down on a list | Refresh content |
| Pinch | Zoom |
The rules: never repurpose a system gesture for something else, always offer a visible alternative to custom gestures, and do not interfere with the screen-edge gestures that return home or open Control Center.
Feedback, haptics and motion
- •Feedback should be immediate: highlight on touch, subtle confirmation on success, specific error messages.
- •Haptics reinforce meaningful moments such as a payment or a toggle, using system feedback types. Overused haptics become noise.
- •Motion explains spatial relationships and stays brief. Respect Reduce Motion by replacing large movements with fades.
Accessibility
Accessibility is a Foundations topic in the HIG, not an add-on. The minimum for every iPhone app:
- •VoiceOver: every interactive element has a meaningful label ("Add to cart," not "Button"), and reading order follows the visual order.
- •Dynamic Type: all text scales, including at accessibility sizes, without clipping essential content.
- •Contrast: text and essential icons meet contrast minimums in light and dark modes.
- •Hit targets: at least 44 × 44 pt, with enough spacing to avoid accidental taps.
- •Motion: respect Reduce Motion and avoid flashing content.
- •Bold Text, Increase Contrast and Smart Invert: check that your app remains usable with each turned on.
Privacy and permissions
The HIG and App Review both require you to be transparent about data:
- •Request permission only when the user starts a task that needs it, not at first launch.
- •Write purpose strings that explain the benefit in plain language: "Allow camera access to scan receipts."
- •Consider a short pre-permission screen that explains why before the system prompt, but never mimic the system alert.
- •Let people use as much of the app as possible without granting access.
- •If you offer third-party social sign-in, check the current rules on also offering Sign in with Apple.
HIG vs Material Design at a glance
If you design for both platforms, these differences matter most:
| Topic | iOS (HIG) | Android (Material 3) |
|---|---|---|
| Unit | Points (pt) | Density-independent pixels (dp), sp for text |
| Minimum target | 44 × 44 pt | 48 × 48 dp |
| System font | SF Pro | Roboto or the device's system font |
| Default body size | 17 pt | 16 sp (Body Large) |
| Primary navigation | Tab bar at the bottom | Navigation bar at the bottom, rail or drawer on large screens |
| Back | Back button top-left, edge swipe | System back gesture or button |
| Primary action | Prominent button in content or toolbar | Often a floating action button |
| Dialogs | Alerts, centered, short | Dialogs, with optional full-screen variant |
Common HIG mistakes that make apps feel non-native
- •Android-style floating action buttons and top tab strips copied directly onto iOS.
- •Hamburger menus hiding primary navigation instead of a tab bar.
- •Fixed font sizes that ignore Dynamic Type.
- •Custom back buttons that break the edge swipe.
- •Hard-coded colors that turn unreadable in dark mode.
- •Tap targets smaller than 44 pt, especially icon buttons in toolbars and list rows.
iOS HIG pre-ship checklist
- • Content stays inside safe areas on SE, standard and Pro Max sizes
- • All tap targets are at least 44 × 44 pt
- • Text uses Dynamic Type styles and reflows at accessibility sizes
- • Semantic colors used; light, dark and Increase Contrast tested
- • Contrast checked for text, icons and disabled states
- • Tab bar holds top-level sections only, five or fewer
- • Navigation bars show titles; large titles on top-level screens
- • Sheets have clear dismiss controls and confirm before losing data
- • Standard gestures work everywhere, including edge-swipe back
- • SF Symbols or matching custom icons with labels where meaning is unclear
- • VoiceOver labels on every control, logical reading order
- • Reduce Motion respected
- • Permissions requested in context with clear purpose strings
- • Alerts reserved for critical or destructive situations
If you want to see these rules applied before you design manually, you can generate a first draft of HIG-compliant iPhone screens in floow and check them against this list.
FAQ
Are the Apple Human Interface Guidelines mandatory?
Not directly. App Review enforces the App Review Guidelines, which cover things like safety, privacy, payments and minimum functionality. However, some HIG-adjacent rules are enforced, such as using Apple's official Apple Pay and Sign in with Apple buttons correctly, and apps that feel broken or confusing are more likely to be rejected or poorly reviewed.
What is the minimum tap target size on iOS?
Apple recommends a minimum hit target of 44 × 44 pt for all controls. The visible icon can be smaller, but the tappable area should reach that size.
What font does Apple recommend for iOS apps?
SF Pro is the system font and adapts automatically between text and display sizes. You can use custom fonts, but they should support Dynamic Type so they scale with the user's text size setting.
How often do the Human Interface Guidelines change?
Apple updates the HIG throughout the year and makes the biggest changes alongside major OS releases announced at WWDC each June. The iOS 26 release introduced the Liquid Glass design language, for example. The HIG site lists recent changes on its "What's new" page.
Should my iOS and Android apps look the same?
Keep brand, content and core flows the same, but follow each platform's conventions for navigation, controls and system behaviors.
Design it with floow
Want iPhone screens that follow these guidelines from the first draft? Describe your app in floow, choose a Mobile project and refine the screens in chat. Try:
Design an iOS notes app following Apple's Human Interface Guidelines: a tab bar with Notes, Folders and Search, a large-title notes list with swipe actions, a note editor with a toolbar, and a medium-height sheet for sharing options. Use SF-style type, semantic colors and support dark mode.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Insights18 November 2026Mobile App Usability Testing: A Lightweight MethodA practical mobile app usability testing method for small teams: recruit 5 users, write tasks, run sessions on real phones, and turn findings into fixes in a.By floow.design
Roundups18 November 20268 Uizard Alternatives for AI App Design (2026)Compare 8 Uizard alternatives for AI app design: who each tool suits, mobile screen quality, Figma and code export, and how to pick the right one for your.By floow.design
Insights17 November 2026Recipe App Design: Search, Cook Mode and ListsRecipe app design guide: the core screens, ingredient scaling, hands-free cook mode, smart shopping lists and search filters, with specs and copyable prompts.By floow.design