iPhone Duo app testing: a checklist for your next release
To test an app on iPhone Duo, run a useful task on each display, then repeat it while opening, closing and changing the phone's pose. Check that entered text, navigation and required actions survive the change. Add keyboard, sheet, Split View and accessibility checks to the flows your customers depend on. Record the build and starting conditions beside every result.
Apple's foldable iPhone makes a screenshot of a tidy screen a weak release check. You also need to know what happens when that screen changes size halfway through someone's work. The scenarios below are suggested QA checks, not claims that these defects exist in your app.
Which app build should you test first?
Start with the candidate you intend to distribute. Ask engineering which iOS SDK built it, and record that separately from the iOS version running on the device.
According to Apple's preparation guide, apps built with iOS 26 or earlier use a smaller window on the inner display. The iOS 27 SDK lets apps use most of that display; iOS 27.1 or later enables fuller screen use and vertical standard bars. Unused space in an older build can therefore be expected compatibility behaviour. A newer SDK doesn't establish that every custom screen works.
Keep a result from the currently released build if you're changing SDKs. It gives you a comparison when a control moves or a layout starts using more space. Test the new candidate again rather than carrying the old build's pass forward.
What belongs in the first test pass?
Choose one task your users need to finish: completing an order, editing a document, booking an appointment or sending a message. Prepare test data so you can repeat it.
Run it from a fresh launch on the outer display and from a fresh launch on the inner display. Then introduce the changes below during the task. A screen that opens correctly can still fail when reached by unfolding from a different layout.
| Check | What to do | What counts as a useful result |
|---|---|---|
| Launch on each display | Reach the same task from a fresh launch on each display | Content fits and the task can be completed |
| Open during editing | Enter recognisable test text, then open the phone | Text, selection and the current step remain usable |
| Close during navigation | Open a detail screen, then close the phone | The selected item remains available and Back follows the intended path |
| Rotate with a sheet open | Show a picker, confirmation or menu, then rotate where supported | You can read, act on and dismiss it |
| Use a partially folded pose | Pause during the task and fold the phone partway | Essential content and controls remain usable in the intended pose |
| Show the keyboard | Focus a field near the end of a long form | You can read the field, reach validation messages and submit |
| Use Split View | Put the app on each side beside another app, where supported | Required actions work in the available space on both sides |
| Increase text size | Repeat the task with a larger accessibility text size | Labels remain understandable and required actions remain reachable |
Keep the test small enough to repeat after a fix. Use the mobile device test matrix to assign wider coverage across your team, rather than giving every tester the same unbounded list.
What should you watch for when controls move?
Apple's design guidance describes controls moving to the side in several configurations. In Split View, each app's controls sit along its outer edge, so testing only the right-hand position misses a different arrangement on the left. Safe areas can also be asymmetric.
Check custom bottom bars, floating buttons and menus near the screen edges. Try the primary action with the keyboard showing, and look in overflow menus before calling an action missing. The failure worth reporting is concrete: Save is covered, Close doesn't respond, or an error message cannot be brought into view.
For apps with two content panes, select an item before changing display. Confirm that the detail still belongs to that item when the layout changes. For example, a message list might keep its selection while the editor switches to a different draft. That's more useful to investigate than “the wide layout looks wrong”.
How do you check accessibility through a display change?
Run one complete journey with VoiceOver, including a display change while a control is focused. Check whether the next action has a useful spoken label and whether focus remains in a sensible place. Open and dismiss a sheet, then continue the task.
Repeat the keyboard check at a larger text size. A form can look acceptable until validation adds another line or the keyboard leaves too little room for the action. For the full screen-reader procedure, use the mobile accessibility testing guide.
What can you check before you have a physical Duo?
Apple's Prepare your app for iPhone Duo session shows the iPhone Duo simulator in Xcode 27.1 and Device Hub controls for opening, closing, rotating and folding. Use those controls to repeat the same task across configurations. Record the Xcode and simulator runtime versions with the result.
Keep simulator and physical-device results separate. For a camera, scanner or other flow that depends on handling the phone, assign a physical-device run as well. If nobody has run it yet, write “not tested”. A simulated layout pass doesn't establish the result of that hardware check.
How should you record coverage for the release?
Give each row one task and one transition. This short worksheet lets a reviewer see both the result and the gaps without opening every bug report:
App version / build:
Build SDK:
Installed iOS / simulator runtime:
Hardware or simulator (and Xcode version if applicable):
Tester / date:
Task and prepared test data:
Starting display / orientation / pose:
App position: full screen, or Split View side and space
Keyboard / text size / VoiceOver state:
Action or transition:
Expected task outcome:
Result: pass / fail / blocked / not tested
Observed outcome / issue link:
A pass applies to the build and case recorded. If the test is blocked by sign-in or missing test data, record the blocker instead of marking the layout as passed. Agree which failures prevent release based on the affected task, its impact and any workable recovery.
When a case fails, use the iPhone Duo bug-reporting guide for the evidence and reproduction template. Keep the starting display and folding step in the report even if the final screenshot looks self-explanatory.
If your test build uses BugScreen's iOS SDK, its collected context includes device, OS and app version/build fields. Describe the pose and transition yourself. Before the testing round, send a sample report from each display and check that the evidence reaches the person investigating it. You can create a BugScreen workspace to try that reporting route with your next candidate.
Frequently asked questions
What should an iPhone Duo app testing checklist cover?
Cover launch on each display, opening and closing during a task, supported orientations, partially folded use, keyboards, sheets, Split View and accessibility. For each case, record the app build, installed iOS version, starting conditions and result. Choose tasks that matter to your app rather than treating every possible combination as equally important.
Can I test an iPhone Duo app without the phone?
Apple provides an iPhone Duo simulator in Xcode 27.1, with Device Hub controls for opening, closing, rotating and folding. Use it to inspect layouts and repeat transitions. Label simulator results clearly and leave physical-device checks untested until someone runs them.
Does building with a newer iOS SDK prove that my app supports iPhone Duo?
No. The build SDK affects screen usage and standard control placement, but your team still needs to check custom layouts and whether people can finish tasks across display changes. Record the build SDK separately from the iOS version installed on the test device.