Design native iOS apps following Apple's Human Interface Guidelines...
Framework for designing native iOS app interfaces that feel intuitive, consistent, and aligned with Apple's design philosophy. Based on Apple's Human Interface Guidelines, the definitive resource for building apps that integrate seamlessly with iPhone, iPad, and the broader Apple ecosystem.
Apple's iOS design philosophy rests on three foundational pillars: clarity, deference, and depth. Every element must be legible and purposeful (clarity). The interface should never overshadow the content it presents (deference). And layering, transitions, and realistic motion must provide hierarchy and spatial relationships (depth).
The foundation: The best iOS apps don't just follow HIG rules mechanically---they internalize the philosophy that the interface exists to serve the user's content and tasks. 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.
Goal: 10/10. When reviewing or creating iOS interfaces or SwiftUI/UIKit code, rate them 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.
Core concept: iOS devices have specific screen dimensions, safe area insets, and hardware intrusions (notch, Dynamic Island, home indicator) that must be respected in every layout.
Why it works: When layouts respect safe areas and standard spacing, the app feels native and trustworthy. Users never have content hidden behind hardware features or system UI, and the visual rhythm matches the rest of the platform.
Key insights:
Product applications:
| Context | Layout Pattern | Example |
|---|---|---|
| Status bar | 59pt height, always respected | Time, signal, battery area |
| Navigation bar | 44pt standard row + 58pt large title | Back button, title, actions |
| Content area | Flexible, scrollable, respects safe area | Main app content |
| Tab bar | 49pt height, translucent with blur | 2-5 primary destinations |
| Home indicator | 34pt inset at bottom | System gesture area |
Copy patterns:
VStack { } which respects safe areas by default.ignoresSafeArea() only for backgrounds and decorative elements, never for interactive contentEthical boundary: Never hide critical content or controls behind hardware intrusions. Users with any device should have equal access to all functionality.
See: references/navigation.md for detailed navigation bar and tab bar specifications.
Core concept: iOS uses the San Francisco (SF Pro) typeface with a semantic text style system that automatically scales for accessibility via Dynamic Type.
Why it works: Semantic text styles create consistent visual hierarchy across the platform. Dynamic Type ensures every user---including those with visual impairments---can read content at their preferred size without breaking layouts.
Key insights:
Product applications:
| Context | Typography Pattern | Example |
|---|---|---|
| Screen titles | .largeTitle or .title style |
Large title collapses on scroll |
| Body content | .body style, 17pt |
List items, descriptions |
| Secondary info | .subheadline or .footnote |
Timestamps, metadata |
| Tab labels | 10pt SF text | Tab bar item labels |
| Buttons | .body weight semibold |
Primary action text |
Copy patterns:
.font(.title), .font(.body), .font(.caption) instead of hardcoded sizes@ScaledMetric for custom spacing that scales with Dynamic TypeEthical boundary: Never disable Dynamic Type or set fixed font sizes that prevent accessibility scaling. Every user deserves readable text.
See: references/typography.md for complete text styles, font sizes, and Dark Mode typography rules.
Core concept: iOS provides semantic system colors that automatically adapt between light and dark appearances, ensuring proper contrast and visual hierarchy in both modes.
Why it works: Semantic colors maintain readability and hierarchy across appearances without manual intervention. Users who prefer Dark Mode get a first-class experience, and apps that support both modes feel polished and native.
Key insights:
Color(.label), Color(.secondaryLabel), Color(.systemBackground) instead of hardcoded colorsColor(.systemBlue) is the default tint/accent; .systemRed for destructive actions; .systemGreen for successProduct applications:
| Context | Color Pattern | Example |
|---|---|---|
| Primary text | Color(.label) |
Adapts white/black per mode |
| Secondary text | Color(.secondaryLabel) |
60% opacity in both modes |
| Backgrounds | Color(.systemBackground) / .secondarySystemBackground |
Layered depth |
| Destructive actions | Color(.systemRed) |
Delete buttons, warnings |
| Interactive tint | App accent color or .systemBlue |
Links, toggle states |
Copy patterns:
.preferredColorScheme(.light) and .dark in previews to test both modes side by sideEthical boundary: Dark Mode is not optional polish---it is expected by users. Never ship an app that is unreadable or broken in Dark Mode.
See: references/colors-depth.md for semantic colors, Dark Mode palette, and contrast ratio guidelines.
Core concept: iOS uses a layered navigation model with tab bars for primary destinations, navigation stacks for hierarchical drilling, and modals for focused tasks.
Why it works: Consistent navigation patterns mean users always know where they are, how they got there, and how to go back. Violating these patterns creates confusion and makes the app feel foreign on iOS.
Key insights:
Product applications:
| Context | Navigation Pattern | Example |
|---|---|---|
| App structure | Tab bar with 3-5 tabs | Home, Search, Profile |
| Content hierarchy | Push navigation (drill-down) | List > Detail > Edit |
| Focused tasks | Modal presentation | Compose, settings, filters |
| Search | Pull-down search bar | Spotlight-style search |
| Split view | iPad sidebar + detail | Mail, Notes on iPad |
Copy patterns:
NavigationStack (not deprecated NavigationView) in SwiftUIEthical boundary: Never trap users in flows without a clear exit. Every screen must have an obvious way to go back or dismiss.
See: references/navigation.md for tab bar, navigation bar, modals, search patterns, and split views.
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 come with built-in accessibility, haptic feedback, and interaction patterns that users have already learned. Custom controls create friction and often miss edge cases that Apple has already solved.
Key insights:
.emailAddress, .phonePad, .URL).textContentType for autofill support (email, password, address)Product applications:
| Context | Control Pattern | Example |
|---|---|---|
| Forms | Native text fields with proper keyboard types | Email field with @ keyboard |
| Settings | Grouped list with toggles, disclosure | iOS Settings style |
| Selection | Picker, segmented control, or action sheet | Date picker, sort options |
| Destructive actions | Red button + confirmation alert | "Delete Account" flow |
| Context actions | Long press menu or swipe actions | Edit, share, delete on row |
Copy patterns:
.keyboardType(.emailAddress) and .textContentType(.emailAddress) together.alert() or .confirmationDialog().swipeActions on list rows for common actionsEthical boundary: Never disguise ads as native controls or make destructive actions too easy to trigger accidentally. Confirmation dialogs exist for a reason.
See: references/components.md for buttons, lists, input controls, menus, and confirmation dialogs. See also: references/keyboard-input.md for keyboard types and input patterns.
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, not an afterthought.
Why it works: Accessibility is not optional---it is required by app store guidelines and by ethical design practice. Over 1 billion people worldwide live with some form of disability. Accessible apps also benefit all users (larger text in sunlight, VoiceOver while driving).
Key insights:
.accessibilityLabel describing what it is.accessibilityValue for current state and .accessibilityHint for what it does.accessibilityElement(children: .combine)Product applications:
| Context | Accessibility Pattern | Example |
|---|---|---|
| Icons | .accessibilityLabel("Favorite") |
Heart icon with label |
| Sliders | .accessibilityValue("\(Int(volume * 100))%") |
Volume control |
| Buttons | .accessibilityHint("Shares this item") |
Share button |
| Groups | .accessibilityElement(children: .combine) |
Avatar + name row |
| Images | Decorative: .accessibilityHidden(true) |
Background patterns |
Copy patterns:
Ethical boundary: Accessibility is not a nice-to-have. Shipping an inaccessible app excludes real people. Treat VoiceOver testing as seriously as visual testing.
See: references/accessibility.md for VoiceOver implementation, Dynamic Type support, and accessibility checklist.
Core concept: iOS uses SF Symbols as the standard icon system and requires app icons in specific sizes with the signature superellipse ("squircle") mask applied automatically.
Why it works: SF Symbols are designed to align perfectly with San Francisco text, scale with Dynamic Type, and adapt to different weights and sizes. Consistent iconography makes the interface feel cohesive and native.
Key insights:
Image(systemName:)) for all standard icons---they scale with textProduct applications:
| Context | Icon Pattern | Example |
|---|---|---|
| Tab bar | SF Symbols, filled variant for selected | house.fill, magnifyingglass |
| Navigation bar | SF Symbols at regular weight | gear, plus, ellipsis |
| List accessories | SF Symbols, secondary color | chevron.right, checkmark |
| App icon | 1024px square, simple bold design | Single recognizable glyph |
| Widgets | SF Symbols matching widget style | Consistent with app branding |
Copy patterns:
Image(systemName: "heart.fill") for SF Symbols.symbolRenderingMode(.hierarchical) for multi-color depth.imageScale(.large) or .font() to size symbols relative to textEthical boundary: Never use misleading icons that suggest functionality that does not exist. Icon meaning should match the iOS convention (e.g., trash = delete, not archive).
See: references/app-icons.md for icon size tables, shape specifications, and design guidelines.
Core concept: iOS defines standard gestures (swipe back, pull to refresh, long press for context menu) and haptic feedback patterns that must be respected and never overridden.
Why it works: Gestures are muscle memory. When an app overrides the swipe-back gesture or repurposes pull-to-refresh, users feel disoriented and frustrated. Haptics provide invisible confirmation that an action registered, reducing uncertainty.
Key insights:
Product applications:
| Context | Gesture/Haptic Pattern | Example |
|---|---|---|
| Navigation | Swipe right from left edge | System back gesture |
| Modals | Swipe down to dismiss | Sheet dismissal |
| Lists | Pull to refresh, swipe for actions | Refresh content, delete row |
| Media | Pinch to zoom, double-tap | Photo viewer |
| Confirmation | .success haptic on completion |
Payment confirmed |
| Selection | Selection haptic on toggle/pick | Picker wheel scroll |
Copy patterns:
UIImpactFeedbackGenerator(style: .medium) for physical interactionsUINotificationFeedbackGenerator() with .success, .warning, .error for outcomesUISelectionFeedbackGenerator() for UI state changes.prepare() before triggering haptics to minimize latencyEthical boundary: Never use aggressive haptics to pressure users into actions. Haptic feedback should confirm, not coerce.
See: references/gestures.md for standard gesture table, haptic feedback patterns, and animation guidelines.
| Mistake | Why It Fails | Fix |
|---|---|---|
| Overriding standard gestures | Users expect swipe-back, pull-refresh globally; overriding breaks muscle memory | Use system gestures for their intended purposes; add custom gestures only for supplementary actions |
| Touch targets under 44pt | Small targets cause mis-taps and frustrate users, especially with accessibility needs | Ensure all interactive elements are at least 44 x 44pt |
| Ignoring safe areas | Content hidden behind notch, Dynamic Island, or home indicator | Always respect safe area insets; use .ignoresSafeArea() only for backgrounds |
| Using Android patterns on iOS | Hamburger menus, top tab bars, material-style FABs feel foreign | Use tab bars for primary navigation, bottom sheets, native iOS components |
| Skipping Dark Mode | Users who prefer Dark Mode see broken layouts, unreadable text | Use semantic colors; test both appearances; define light/dark color pairs |
| Hardcoding font sizes | Breaks Dynamic Type, excludes users who need larger text | Use semantic text styles (.title, .body, .caption) throughout |
| Low contrast text | Fails WCAG AA, unreadable in sunlight or for low-vision users | Maintain 4.5:1 minimum contrast ratio; test with Increase Contrast setting |
| Not testing on real devices | Simulator misses performance, haptics, safe area edge cases | Test on physical devices, especially the smallest and largest screen sizes |
Audit any iOS interface design:
| Question | If No | Action |
|---|---|---|
| Does the layout respect safe areas on all device sizes? | Content may be hidden behind hardware features | Audit all screens on iPhone SE and Pro Max; fix safe area insets |
| Are all touch targets at least 44 x 44pt? | Users will mis-tap, especially with accessibility needs | Increase tap areas; use .frame(minWidth: 44, minHeight: 44) |
| Does the app work fully in Dark Mode? | Dark Mode users see broken/unreadable UI | Replace hardcoded colors with semantic system colors |
| Does text scale properly with Dynamic Type? | Accessibility violation; excludes low-vision users | Replace fixed font sizes with semantic text styles; test at largest setting |
| Can a VoiceOver user complete every task? | App is inaccessible to blind and low-vision users | Add accessibility labels, values, hints to all interactive elements |
| Are navigation patterns native iOS? | App feels foreign; users struggle to navigate | Replace hamburger menus with tab bars; use standard push/modal navigation |
This skill is based on Apple's Human Interface Guidelines, the official design documentation for all Apple platforms. For the complete guidelines, platform-specific guidance, and latest updates:
The Apple Human Interface Guidelines are authored and maintained by Apple's Human Interface Design team, one of the most influential design organizations in technology. The HIG traces its origins to 1984, when Apple published the original Macintosh Human Interface Guidelines alongside the launch of the first Macintosh computer. That document established principles---direct manipulation, see-and-point, consistency, WYSIWYG, user control---that defined graphical user interface design for decades. Under the leadership of designers including Jef Raskin, Bruce Tognazzini, and later Jony Ive and Alan Dye, Apple's design philosophy evolved through Mac OS, iPhone (2007), iPad (2010), Apple Watch (2015), and Apple Vision Pro (2024). The HIG has been continuously updated to reflect new interaction paradigms---from mouse to multi-touch to spatial computing---while maintaining the core belief that technology should be intuitive, accessible, and delightful. Today the HIG is freely available at developer.apple.com and remains the essential reference for anyone building apps on Apple platforms.
