Choosing iOS as a target platform means accepting a particular design philosophy along with a particular set of rules. Apple publishes the Human Interface Guidelines (HIG), maintains a consistent system of controls, typography, materials, and navigation patterns, and reviews every app before it reaches the App Store. For an HCI designer, that combination is both a gift and a constraint: much of the interaction vocabulary is already decided for you, users arrive with strong expectations about how things should behave, and deviating from convention tends to cost you more than it gains.
In this topic we look at three things: what the iOS platform actually is (devices, system design language, and the audience that uses it), the design conventions that make an app feel "native" on iOS, and the constraints that come with Apple's more controlled ecosystem — review policies, hardware and device-size assumptions, accessibility expectations, and limited freedom to invent your own UI patterns. These factors feed directly into whether iOS is the right platform for your team's project.
The videos below come from Apple Developer's WWDC sessions, which is as close to a primary source as you can get for iOS design. While watching, note the recurring vocabulary — hierarchy, consistency, materials, controls, navigation — and ask yourself two questions: what does this guidance require of a designer, and what would it prevent you from doing? Those answers become constraints you can cite in your scoping document.
An Apple WWDC25 session that walks through how an app idea becomes an actual interface, covering the design foundations Apple expects developers to apply. Based on its description, it focuses on how thoughtful design elevates functionality and makes apps feel clear, intuitive, and effortless. Expect discussion of structuring content, establishing hierarchy, and choosing appropriate system components.
It is an official Apple source and maps directly to the iOS Design Conventions subtopic, showing the reasoning behind the conventions rather than just listing them — useful when you need to justify design decisions.
A WWDC26 session on the principles of great design, linked directly to Apple's Human Interface Guidelines design principles documentation. It is likely to present the high-level values Apple wants apps on its platforms to embody, such as clarity, consistency, and deference to content. The session serves as an entry point into the HIG itself.
It gives you the conceptual frame behind the HIG, which is the single most important reference for anyone designing for iOS, and supports both the platform overview and design conventions subtopics.
A WWDC25 session introducing Apple's updated design system, with references to the Human Interface Guidelines sections on materials and related documentation. It is likely to cover the system's visual language — layers, materials, controls, and how they behave across Apple devices. This is the kind of material that shows how much of your interface iOS already defines for you.
Seeing the breadth of a prescribed system makes the ecosystem's constraints concrete, which is exactly the point of the iOS Constraints and Considerations subtopic; it also comes straight from the platform owner, so the details are accurate and current.
These sessions give you an authoritative picture of what designing for iOS actually demands, which is the raw material for MO1: you cannot meaningfully compare mobile, web, and desktop constraints until you know how tightly a platform like iOS specifies its interaction and visual conventions. The emphasis on system components, materials, and design principles gives you concrete, citable reasons for or against choosing iOS for your project, supporting the platform justification in MO2. Finally, the constraints surfaced here — prescribed patterns, device and ecosystem assumptions, and expectations your users bring with them — translate directly into the constraints and success criteria sections of the project scope document required by MO3.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.