iOS Hig Design

iOS Human Interface Guidelines Design Skill

Framework for designing native iOS interfaces that feel intuitive, consistent, and aligned with Apple's design philosophy. Based on Apple's Human Interface Guidelines, the definitive resource for apps that integrate seamlessly with iPhone, iPad, and the Apple ecosystem.

Core Principle

Apple's iOS design philosophy rests on three pillars: clarity (every element legible and purposeful), deference (the interface never overshadows the content it presents), and depth (layering, transitions, and realistic motion convey hierarchy and spatial relationships).

The foundation: The best iOS apps internalize this philosophy rather than following HIG rules mechanically. Native components, system conventions, and platform consistency aren't constraints---they're the reason iOS users trust and enjoy apps that feel like they belong.

Scoring

Goal: 10/10. Score 1 point per satisfied row of the Quick Diagnostic (6 rows), plus up to 4 points for native idiom: +1 semantic colors/text styles throughout (no hardcoded values), +1 system controls over custom reimplementations, +1 standard gestures and meaningful haptics, +1 SF Symbols and correct app-icon shape. Bands: 9-10 = native, accessible, adapts to Dark Mode and Dynamic Type, zero foreign patterns; 5-6 = works but leaks Android idioms or hardcodes color/size; <=3 = fails safe areas, touch targets, or VoiceOver. Always state the score and the specific improvements needed to reach 10/10.

iOS Design Framework

1. Layout & Safe Areas

Core concept: iOS devices have specific screen dimensions, safe area insets, and hardware intrusions (notch, Dynamic Island, home indicator) that every layout must respect.

Key insights:

• Design for the smallest screen first (375pt width, iPhone SE)
• Safe areas protect content from the notch, Dynamic Island, and home indicator---never place interactive elements under them
• Standard content margins: 16-20pt from screen edges; spacing increments: 8 / 16 / 24pt
• Minimum touch target and list row height: 44pt

Product applications:

Copy patterns:

• Use VStack { }, which respects safe areas by default
• Use .ignoresSafeArea() only for backgrounds and decoration, never interactive content
• Test on multiple sizes, including iPhone SE and Pro Max

See references/navigation.md when laying out chrome---exact nav bar and tab bar dimensions, large-title behavior, and split-view rules.

2. Typography & Dynamic Type

Core concept: iOS uses the San Francisco (SF Pro) typeface with semantic text styles that automatically scale for accessibility via Dynamic Type. Semantic styles give consistent platform hierarchy; Dynamic Type lets users read at their preferred size without breaking layouts.

Key insights:

• Large Title: 34pt Bold; Title: 17pt Medium; Body: 17pt Regular; Caption: 12-13pt; secondary text: 15pt at 60% opacity
• Minimum text size 11pt (captions/secondary only)
• Line height at least 1.3x font size; optimal line length 35-50 characters on mobile
• Always left-aligned, non-justified text

Product applications:

Copy patterns:

• Use .font(.title), .font(.body), .font(.caption) instead of hardcoded sizes; @ScaledMetric for custom spacing that scales
• Prefer weight and color variation over extreme size differences for hierarchy
• Test all layouts at the largest Dynamic Type size

See references/typography.md when matching a design to exact specs---per-style hex values and the Dark Mode text-color mapping.

3. Color & Dark Mode

Core concept: iOS provides semantic system colors that automatically adapt between light and dark appearances while preserving contrast and hierarchy.

Key insights:

• Use Color(.label), Color(.secondaryLabel), Color(.systemBackground) instead of hardcoded colors
• Color(.systemBlue) is the default tint; .systemRed for destructive actions; .systemGreen for success
• Dark Mode inverts text colors and shifts backgrounds darker while keeping relative hierarchy; accent colors need lower brightness and higher saturation to pop
• Maintain 4.5:1 contrast in both modes; preview both during development

Product applications:

Copy patterns:

• Use .preferredColorScheme(.light) and .dark in previews to test both modes side by side
• Define custom colors in the Asset Catalog with light/dark variants, not in code
• Never assume a background is white or black; test with Increase Contrast enabled

See references/colors-depth.md when checking contrast---the full WCAG ratio table (normal text, large text, UI components) and the tertiary/grouped-background tokens.

4. Navigation Patterns

Core concept: iOS uses a layered navigation model: tab bars for primary destinations, navigation stacks for hierarchical drilling, and modals for focused tasks. Users rely on these patterns to know where they are and how to get back; reinventing them makes the app feel foreign.

Key insights:

• Tab bar: 2-5 primary destinations, always visible, remembers state per tab
• Navigation bar: back button (top-left), title (center or large), actions (top-right); large title collapses on scroll
• Modals for focused tasks; dismiss via swipe-down or explicit close button
• Never use hamburger menus---iOS users expect tab bars
• Search bar can sit below the nav bar, hidden until pulled down

Product applications:

Copy patterns:

• Back button text should be the previous screen's title, not "Back"
• Tab labels are single words ("Home", "Search"); modal titles describe the task ("New Message", "Edit Profile")
• Use NavigationStack (not deprecated NavigationView) in SwiftUI

5. Controls & Inputs

Core concept: iOS provides a rich library of native controls (buttons, lists, toggles, pickers, menus, text fields) that users already understand and expect.

Why it works: Native controls ship with built-in accessibility, haptics, and learned interaction patterns; custom controls create friction and miss edge cases Apple already solved.

Key insights:

• Page-level actions go in the nav bar (top) or action bar (bottom)
• Primary buttons are filled with the theme color; secondary are outlined or text-only
• Destructive actions use red and require confirmation when irreversible
• Lists (table views) are the fundamental iOS content pattern
• Match keyboard type to input (.emailAddress, .phonePad, .URL); use .textContentType for autofill

Product applications:

Copy patterns:

• Pair .keyboardType(.emailAddress) with .textContentType(.emailAddress)
• Prefer system confirmations: .alert() or .confirmationDialog(); use .swipeActions on list rows
• Place primary action buttons at the bottom of the screen within thumb reach

Ethical boundary: Never disguise ads as native controls or make destructive actions easy to trigger accidentally.

See references/components.md when building a specific control---button styles, list/section variants, picker vs segmented-control choice, and confirmation-dialog wiring. See references/keyboard-input.md when building forms---keyboard-type table, input accessory views, and hardware-keyboard shortcuts.

6. Accessibility

Core concept: iOS has world-class accessibility features (VoiceOver, Dynamic Type, Switch Control, Voice Control), and every app must support them as a first-class concern. App Store review can reject apps that are unusable with assistive technologies.

Key insights:

• Every interactive element needs an .accessibilityLabel; use .accessibilityValue for state and .accessibilityHint for effect
• Group related elements with .accessibilityElement(children: .combine)
• Support Dynamic Type at all sizes; test at the largest setting
• Honor the 44 x 44pt touch target (section 1) and 4.5:1 contrast minimum (section 3) as accessibility requirements, not just visual defaults
• Never convey meaning through color alone

Product applications:

Copy patterns:

• Write labels as nouns ("Favorite", "Settings"); write hints as actions ("Shares this item with others")
• Test the complete app flow using only VoiceOver
• Use Xcode's Accessibility Inspector to audit contrast and labels

See references/accessibility.md before sign-off---the full VoiceOver-implementation patterns and a pre-ship accessibility checklist to run the app against.