iPhone Duo tutorials
App testing checklist
A practical iPhone Duo app testing matrix for compatibility, fold/unfold, orientation, resizing, state restoration, safe areas, keyboard, navigation, WebView, camera, media, and regression evidence.
App testing checklist More context
A practical iPhone Duo app testing matrix for compatibility, fold/unfold, orientation, resizing, state restoration, safe areas, keyboard, navigation, WebView, camera, media, and regression evidence.
On this page
Test one continuous user task across open, closed, rotated, folded, and multitasking states. Record the environment, transition, expected outcome, actual outcome, and evidence; separate Simulator observations from physical-device results and from Plurigent’s online design preview.
How should I test an app on iPhone Duo?
Start from a real task, not a gallery of screenshots. Capture the environment and precondition, perform a device or window transition, then continue the same task. This exposes state loss, duplicate work, unreachable controls, and incorrect layout decisions that isolated screenshots miss.
Use Device Hub for iPhone Duo simulator behavior. Use Plurigent’s online Simulator for visual exploration and discussion. Treat physical-device evidence as its own evidence class rather than merging all three into one “tested” label.
Use TestFlight for the beta build, and check release eligibility separately
Apple’s September 18, 2026 update accepts Xcode 27.1 beta builds with the corresponding iOS/iPadOS 27.1 SDKs for internal and external TestFlight testing. Its September 28 update also accepts Xcode 27.2 beta 2 and corresponding SDK builds.
Acceptance in TestFlight is separate from selecting a Duo-capable SDK/runtime and from public App Store submission. Apple published Duo screenshot/preview specifications earlier; a specification alone is not proof that all asset-upload or release workflows are open. Check the current submission guidance for the intended distribution path.
Record the environment before recording Pass or Issue
A result without its environment becomes hard to reproduce as Xcode and iOS 27.1 evolve. Put the toolchain and app build at the top of every regression record.
| Field | Record |
|---|---|
| Mac | Model / architecture |
| macOS | Exact version |
| Xcode | Version + build |
| Runtime | iPhone Duo simulator/runtime version or physical device OS |
| App | Commit/build identifier |
| Date | Test date |
| Evidence type | Simulator / physical device / Online design preview / code inspection |
| SDK | Exact SDK version used to build the app |
| Window and system UI | Display, app window, orientation, posture, bars and layout container |
| Input and accessibility | Keyboard type/state, language, text size and relevant accessibility settings |
| Web experiments, if relevant | Safari versus app WKWebView; explicitly enabled flags and default baseline |
Regression matrix: test change, state, and recovery together
The matrix below is a starting point, not a claim that every row applies to every product. Add product-specific flows such as authentication, payments, attachments, maps, camera capture, media editing, or long-running network tasks.
| Area | Transition or stress | What to verify |
|---|---|---|
| Compatibility | Launch existing build, then build with iOS 27.1 SDK | Core task works; full-screen opt-in changes are understood |
| Fold / unfold | Open ↔ partially folded ↔ closed | Layout adapts; task and state remain coherent |
| Orientation | Portrait ↔ landscape where applicable | Size-class decisions and controls remain reachable |
| Resize / Split View | Move app between available regions | No hard-coded screen assumption; safe areas re-query |
| Foreground / background | Background during an unfinished task | Expected restoration without duplicate work |
| Safe area / bars | Change bars, Split View side, or system UI | Foreground controls stay reachable; background can remain full bleed |
| Keyboard | Resize/fold while input is focused | Focus, value, validation, and action remain usable |
| Navigation / modal | Transition with detail, sheet, menu, or alert open | Context remains understandable and dismissible |
| WKWebView | Resize while form/list/request is active | Page does not reload unintentionally; viewport and scroll remain sensible |
| Camera / media | Change pose while preview or playback is active | Surface, orientation, controls, and state follow product intent |
| Attachment picker | Change size before/after selection | Presentation and selected state survive appropriately |
| Performance | Repeat transitions and multitasking | No uncontrolled memory growth, duplicate requests, or severe frame drops |
| Vertical bars / overflow | Move a detail view between roomy and compact layouts | Important actions remain reachable and overflow items keep clear labels. |
| Physical versus design pixels | Prepare screenshots and compare layout references | Use the current App Store asset specification; do not derive deliverable pixel sizes from Figma scale. |
Simulator-specific checks and limitations
Device Hub supports opening, closing, rotating and folding the simulated device. The release-note snapshot reviewed on September 23 records slow first launch, unavailable StandBy and limits on running/debugging most app extensions for the Xcode 27.1 beta Duo runtime.
These issue notes were not re-tested in this content update. Record the exact toolchain and runtime, check later release notes and keep a tooling constraint distinct from an app failure or a pass. Physical-device work remains a separate evidence category.
Use evidence labels that say what was actually verified
Keep Not checked, Pass, Issue, and Not applicable distinct. A reviewed item is not automatically a passing item, and a visual check is not equivalent to a functional or performance check.
For every Issue, capture a reproducible transition and attach evidence. For every Not applicable result, record why it does not apply. Re-run affected rows after fixes rather than changing only the summary status.
Before treating adaptation work as release-ready
Complete the product-specific regression matrix on the environments you actually support, including physical-device work where required. Re-check third-party SDKs, system integrations, camera/media flows, accessibility, and any behavior that Simulator cannot exercise.
This guide organizes the work; it is not an automated certification and does not establish that a particular app is compatible or fully adapted.
Scope and review details · v0.13.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
- Xcode 27.1 beta · iPhone Duo Simulator / Device Hub · iOS 27.1 · SwiftUI · UIKit · WKWebView
- Verification status
- App Store Connect distribution notes reviewed October 4, 2026. Simulator limitations retain their September 23 release-note scope. The matrix is a proposed checklist, not a completed native test or release certification.
Sources & review scope
Selected preparation transcript passages reviewed October 4 for system containers and task continuity. No native SDK compilation or device/runtime measurement.
Apple Developer · Sources checked Oct 4, 2026September 18 and 28, 2026 TestFlight entries reviewed October 4. Beta-build acceptance is not Duo runtime compatibility or public App Store submission approval.
Apple Developer · Sources checked Oct 4, 2026Xcode 27.1 beta release-note snapshot reviewed September 23, 2026. Retained Simulator/Catalyst/preview details were not fully re-read or reproduced in the October 4 content update; check the exact current build.
Apple Developer · Sources checked Sep 23, 2026