iPhone Duo tutorials
Watch with a design question
A designer’s route through Apple’s iPhone Duo session, with seven chapter links, control and sheet review prompts, and an exercise for your own layout.
On this page
Use the session to turn a broad “does this adapt?” question into a few design decisions. Watch the selected chapters at Apple, then use the exercise below to compare your own layout. This page is a companion guide, not a hosted copy of the video.
Design for iPhone Duo
Apple’s chapter list and selected transcript text rechecked October 4, 2026. The existing YouTube association is retained; playback and subtitle availability were not tested. Viewing exercises are by Plurigent.
- Publisher
- Apple
- Source checked
- Verification
- Source page checked
Selected chapters
Times follow the publisher’s chapter index. The prompts below are Plurigent’s suggested exercises.
- Begin with the design goals
Write down the user task that should stay recognizable.
- Plan how the layout changes
Sketch the same task in a compact and a wider composition.
- Map where the controls belong
Annotate navigation, frequent actions and secondary actions before making a wider composition.
- Review the smaller composition
Mark which visual elements and actions need the most attention.
- Use the extra room deliberately
Ask what added space contributes besides larger elements.
- Review a sheet as its own composition
Choose a sheet in your flow. Mark the action to complete it and the route back to the previous task.
- Inspect interactions near the fold
List questions to verify later in the native implementation.
What this session helps you notice
Apple discusses adapting composition, the placement of controls, and interactions near the fold. Its advice favors resizable layouts and a consistent functional hierarchy rather than a different product for every pose.
Before watching: choose a screen with a real task
Our suggested exercise is to pick a screen you can explain in one sentence: choosing a note, reading an item, or reviewing a result. Put a box around its primary action and identify what the user must remember when the view changes.
Do not redesign while watching. Record questions first, so a visually impressive example does not distract you from your own task.
At 5:07: separate control placement from content alignment
The session describes side-positioned controls, with horizontal bars retained for the inner display in portrait. It also distinguishes content aligned within safe-area insets from immersive backgrounds that span the display. A single centered rectangle is not a complete layout specification.
At 8:36: review the sheet, not only the screen beneath it
Apple shows sheet controls adapting differently on the outer and inner displays. Its fold-avoidance discussion covers system components such as sheets and alerts. This is a native-system description; a browser device model does not add those behaviors to an arbitrary prototype.
Build a small decision board
Use the following prompts to turn the viewing session into design work. These are Plurigent exercises, not extra platform requirements. Keep the same task and realistic content in each sketch; compare the decisions, not just the dimensions.
| Review question | What to put on your board | What to decide next |
|---|---|---|
| Where does the task begin? | The entry screen and the action that moves it forward. | Can a new reviewer identify the next action without coaching? |
| What uses the wider space? | A compact composition and a wider composition with identical content. | Does the extra space add useful context or only stretch it? |
| How does the sheet end? | The open sheet, its completion action and its dismissal route. | Does the reviewer know what will be kept and what will be discarded? |
| What is still an assumption? | Annotations beside uncertain control positions or fold interactions. | Which questions belong in a native implementation review? |
After watching: make a comparison, not a certification
Draw two compositions with the same content and intent. Highlight what remains stable and what rearranges. Ask another person to point to the primary action in each drawing without an explanation.
Try a browser preview to discuss scale and presentation. Keep a separate list of questions about system behavior for implementation testing. The exercise is Plurigent’s suggested workflow, not a requirement stated by Apple.
When the video is unavailable
Read the viewing notes here, use the embedded YouTube preview, or open Apple’s session page for its chapters and transcript. Previews may load as you browse; playback begins through the player controls. Reading without playing is not the same as preventing third-party requests.
If the embed or a chapter jump is unavailable, use the original-source link and Apple’s published chapter list. The fallback does not imply that a live playback check has succeeded.
Scope and review details · v1.1.1
Scope: official sources and practical guidance. Runtime measurements and hands-on observations are labeled separately and should be rechecked against the stated versions.
- Last reviewed
- Applies to
- Designers and freelancers working on iPhone Duo experiences
- Verification status
- Apple’s chapter list and selected transcript text reviewed October 4, 2026. Plurigent’s prompts are original exercises. YouTube playback, subtitles, native examples and physical-device behavior were not tested.
Sources & review scope
Official chapter index and selected design transcript passages reviewed October 4. Seven existing chapter offsets match. No YouTube playback, subtitles or native-device verification.
Apple Developer · Sources checked Oct 4, 2026