What you need to know
- Apple documents both layout adaptation and continuity of state.
- A transition review can start with unfinished work.
A larger layout is one part
Apple’s preparation guide says apps built with the iOS 27.1 SDK can use iPhone Duo’s full display, with standard toolbars and tab bars arranged vertically. It also asks developers to check content adaptation before shipping.
Our editorial focus is the session that is already underway when that layout changes. A release review can follow a person’s unfinished work instead of stopping at a screenshot of the expanded interface.
Preserve the task
Apple’s design guidance calls for keeping functionality and element state consistent between displays. It also says controls and content should remain accessible across device poses, while avoiding extreme rearrangements as the device folds.
Those principles make a transition part of the interaction to examine, in our view, rather than just a way of reaching another screen size.
Follow an unfinished edit
Imagine a fictional inventory app in which a worker selects an item and begins writing a note. Our proposed demonstration would change the available layout before the note is submitted. The evaluator would then ask the worker to identify the item, explain whether the note is still a draft and find the action that completes it.
A second pass could begin with a different item selected and an empty note. This would make it easier to discuss whether the display communicates the current task, rather than whether the evaluator remembers the first example. These are proposed interface exercises, not tests we conducted or descriptions of a shipping app.
The review could record what the person believed had been saved, what they expected to happen next and which visible detail supported that expectation. A layout can look orderly while still leaving those questions unanswered.
Review completion as well as appearance
For the fictional exercise, the useful result would be a set of reproducible moments where the worker’s explanation diverges from the intended task. The product team could revisit each moment with the same starting item and draft, then discuss whether the revised view makes the next action clearer. That gives the review a concrete outcome beyond an attractive demonstration.


