Human Interface Guidelines for indie iOS developers.
A craftsman's read of Apple's HIG — how to design satisfying, HIG-respecting interactions that feel native, without the bloat of a design team you don't have.
The HIG is a philosophy, not a checklist
Read the Human Interface Guidelines the way a woodworker reads the grain. Apple's document is not a list of pixel values to memorize — it's a set of principles about deference, clarity, and depth that add up to interfaces which feel like the operating system, not on top of it.
Indies who thrive on the App Store share one habit: they treat the HIG as taste calibration. Every screen answers three quiet questions — Is content the hero? Is the next action obvious? Does motion earn its place?
Design for the thumb, not the pointer
The HIG's minimum 44pt hit target isn't a suggestion — it's a physical constant. On a 6.7" iPhone held one-handed, the thumb reaches roughly the bottom two-thirds of the screen. Primary actions live there. Destructive ones don't.
A common indie mistake is porting a macOS mental model to iOS: dense toolbars, chevron menus, tiny tap targets. Redraw the layout around the arc of the thumb and 80% of your UX complaints disappear.
Motion is meaning, not decoration
Apple's system animations use spring physics for a reason: springs communicate causality. When a sheet lifts, its inertia tells you it came from your finger. When a badge pulses, its rhythm tells you something changed.
The HIG-respecting rule of thumb: animate transformations of state (position, scale, presence), not the arrival of static content. If your splash screen animates for its own sake, remove it. If a card morphs into a detail view, keep it — that's continuity.
Type is your first UI
Dynamic Type is non-negotiable. It's the single largest accessibility win you can ship, and the fastest way to earn feature placement. Design at Large (Default) and audit at XXL — if your layout breaks, your hierarchy is wrong, not the setting.
SF Pro's optical sizes exist so headers, body, and captions render with correct spacing at every scale. Use the semantic text styles (largeTitle, headline, body, caption) instead of hard-coded points; the system does the math.
Haptics are punctuation
A well-timed .success haptic on completion, a .selection tick on a segmented control, a soft .impact on a card flip — these are the difference between an app that feels alive and one that feels like a webview.
The HIG cautions restraint for a reason: haptics used everywhere feel like nothing. Reserve them for state confirmations and physical metaphors (drag, snap, unlock). Silence is a design choice.
Privacy is part of the interface
Every permission prompt is a UI moment. The HIG asks you to ask only for what you need, and to ask when the user understands why. A location prompt on launch is a red flag; a location prompt after tapping "Find nearby" is a design decision.
Ship on-device by default. When you must sync, tell the user in plain language what leaves the device. Privacy isn't a compliance checkbox — for indies, it's a positioning asset.
Sweat the empty, error, and edge states
Indies who understand the HIG obsess over the states most teams skip: the first-run empty view, the offline error, the loading skeleton, the search-with-no-results. These are 80% of a real user's session and 0% of most design mockups.
Give each state a purpose: teach, recover, or reassure. An empty state that shows a single sample item and a clear next action outperforms any onboarding carousel.
Test in the shape of the platform
The HIG describes an operating system that spans iPhone, iPad, Mac, Vision, Watch, and CarPlay. You don't have to support all of them — but the interactions you do ship should feel at home wherever they run. Test on the smallest supported device and the largest. Test with VoiceOver on. Test at Reduce Motion. Test in Low Power Mode.
A HIG-respecting app is one where the platform's defaults are your defaults, and every deviation is a deliberate, defensible choice.