iOS Mobile Design
Master iOS Human Interface Guidelines (HIG) and SwiftUI patterns to build polished, native iOS applications that feel at home on Apple platforms.
When to Use This Skill
- Designing iOS app interfaces following Apple HIG
- Building SwiftUI views and layouts
- Implementing iOS navigation patterns (NavigationStack, TabView, sheets)
- Creating adaptive layouts for iPhone and iPad
- Using SF Symbols and system typography
- Building accessible iOS interfaces
- Implementing iOS-specific gestures and interactions
- Designing for Dynamic Type and Dark Mode
Core Concepts
1. Human Interface Guidelines Principles
Clarity: Content is legible, icons are precise, adornments are subtle Deference: UI helps users understand content without competing with it Depth: Visual layers and motion convey hierarchy and enable navigation
Platform Considerations:
- iOS: Touch-first, compact displays, portrait orientation
- iPadOS: Larger canvas, multitasking, pointer support
- visionOS: Spatial computing, eye/hand input
2. SwiftUI Layout System
Stack-Based Layouts:
Grid Layouts:
3. Navigation Patterns
NavigationStack (iOS 16+):
TabView (iOS 18+):
4. System Integration
SF Symbols:
Dynamic Type:
5. Visual Design
Colors and Materials:
Shadows and Depth:
Quick Start Component
Best Practices
- Use Semantic Colors: Always use
.primary,.secondary,.backgroundfor automatic light/dark mode support - Embrace SF Symbols: Use system symbols for consistency and automatic accessibility
- Support Dynamic Type: Use semantic fonts (
.body,.headline) instead of fixed sizes - Add Accessibility: Include
.accessibilityLabel()and.accessibilityHint()modifiers - Use Safe Areas: Respect
safeAreaInsetand avoid hardcoded padding at screen edges - Implement State Restoration: Use
@SceneStoragefor preserving user state - Support iPad Multitasking: Design for split view and slide over
- Test on Device: Simulator doesn't capture full haptic and performance experience
Common Issues
- Layout Breaking: Use
.fixedSize()sparingly; prefer flexible layouts - Performance Issues: Use
LazyVStack/LazyHStackfor long scrolling lists - Navigation Bugs: Ensure
NavigationLinkvalues areHashable - Dark Mode Problems: Avoid hardcoded colors; use semantic or asset catalog colors
- Accessibility Failures: Test with VoiceOver enabled
- Memory Leaks: Watch for strong reference cycles in closures

