Art, design & a little curiosity
Product design ↗

Design a foldable interface around changing poses

Apple published new iPhone Duo design guidance on 9 September 2026. Use a paper prototype to explore how content, controls, and hierarchy can remain understandable as a foldable interface changes size and pose.

Original abstract visual study for product design.
Original visual study / Product design

A changing pose is a layout question

On 9 September 2026, Apple added “Designing for iPhone Duo” to its Human Interface Guidelines. The new page describes a foldable phone with inner and outer displays, a center fold, and several ways to hold or position the device. Apple recommends adapting to available space and reserved regions, keeping functions consistent across poses, and avoiding unnecessary rearrangement. This is design guidance for Apple platforms, not evidence that any particular layout has been tested successfully with users.

The useful design question is broader than “How do I make a second screen?” A foldable object changes the size and shape of the surface while a person is in the middle of a task. A reading view may gain room for a list beside an article; an editing tool may need to keep its primary action near the content; a folded hinge may divide a diagram.

Begin with the task and its content roles

Choose a small task before drawing device frames. For a field guide, the person might select a location, inspect a route, and save a note. Name the primary content, secondary content, essential controls, and any state that must persist while the layout changes. This inventory gives you something stable to protect.

Sketch the same task in a narrow view and a wider view. In the narrow version, a location list and route detail might appear one at a time. With more width, they could sit beside each other so the selected route remains visible while the person compares options. Make the selection, scroll position, and return path explicit in both sketches.

Let the fold interrupt space, not the task

A hinge or camera region can make part of the canvas unavailable or visually awkward. Place a paper strip over the area where the fold would fall and redraw the interface around it. Keep labels, thin lines, and small targets away from the interruption. If a diagram must cross the fold, test whether a deliberate gap, paired panels, or a shifted crop preserves its meaning.

Apple’s preparation material advises layouts that respond to their container and recommends checking open, closed, partially folded, and rotated states. A compact prototype can turn that guidance into an inspection routine: resize the frame gradually, pause at an awkward intermediate width, and look for sudden jumps. If the interface reorders content, write down what remains fixed and why. Small changes are easier to track than a redesign triggered by every pose.

Keep controls findable as the frame turns

A familiar horizontal toolbar may become vertical along an edge. Group controls by task, identify the actions people need most often, and check whether their labels remain clear if an icon is shown alone. Avoid using position as the only clue to function: if a control moves, preserve its label, grouping, or other recognizable relationship to its content. Also check what moves into overflow. A rarely used option can be tucked away; a needed save or back action should not disappear simply because the layout became narrow.

The larger surface should reveal more useful context, not silently remove core capabilities from the smaller one. You might show a list and detail together when space allows, while retaining a clear way to reach each on the outer display. These are criteria for a design review; actual implementation still needs device and accessibility testing.

Review a sequence, not a hero mockup

A single image of an open device can hide the transition that causes confusion. Make a short sequence: closed, opening, partially folded, open, and rotated. In each frame, mark the content that stays, the content that reflows, and the control that receives the next action. Compare the sequence at ordinary and enlarged text sizes.

The aim is continuity of meaning, not identical pixels. Keep a note for every change that affects a person’s next step. If you cannot explain the change in terms of task, space, or visibility, simplify it and test the transition again.

Put it into practice

Try it yourself

  1. Write one task and list the content, controls, and state that must remain available.
  2. Sketch a narrow layout, a wide layout, and a partially folded layout using the same task.
  3. Mark the fold and camera regions, then move essential text, targets, and controls away from occluded areas.
  4. Create a five-frame pose sequence and note what stays, reflows, or moves to overflow.
  5. Repeat the sequence with enlarged text and record unresolved questions for implementation testing.
A worked example

Worked example: a fictional pocket field guide

Imagine an invented field guide with a trail list, a selected route, a short description, and a save control. In the closed sketch, show the route detail after someone selects it, with a clear way back to the list. In the open sketch, place the list beside the detail so a second route can be compared without losing the first selection. In the partially folded sketch, keep the selected route title and save action outside the hinge area; let a map use a deliberate central break if its line would otherwise cross the fold. Now step through the five states and enlarge the text. If the list vanishes during resizing or the save control changes location without a visible cue, mark that transition for revision. The guide and the behavior are fictional; this is a paper-design exercise, not a report of an Apple device test.

References & further reading

Examples and exercises in this guide are original teaching scenarios.

Keep following the thread.

More product design ↗