realdevicecheck. Request a test

iPhone Duo
app testing
checklist.

Start with the customer journeys that matter, then change the screen around them. Use this checklist to prepare in Xcode now and plan a physical-device pass after launch.

Request a real-device test

Test the task.
Then change the canvas.

A screen can look correct in isolation and still lose state, hide a control, or interrupt a task when its available space changes. Apple’s iPhone Duo preparation talk calls out flexible layouts, safe areas, and Split View. The practical test is to run your important flow through those changes.

Pick a real journey first: sign in, find content, create something, or complete a transaction. Repeat it while opening, closing, rotating, or sharing the screen.

Five checks
worth running.

  1. 01

    Open and closed layouts

    Launch the app in each display state. Check readable text, visible navigation, and controls that remain reachable without crowding or unused space.

    LAYOUT
  2. 02

    Change state mid-task

    Start a key flow on the outer display, open the device, then close it again. Look for lost input, a reset screen, or navigation that changes unexpectedly.

    CONTINUITY
  3. 03

    Safe areas and system controls

    Inspect buttons, forms, toolbars, and overlays near screen edges. Apple notes that iPhone Duo safe areas can be asymmetric, especially in landscape and Split View.

    REACHABILITY
  4. 04

    Rotation and Split View

    Repeat the same task after rotation and while the app shares the inner display. Check that essential content stays visible and usable as width changes.

    RESIZING
  5. 05

    Touch and reliability on hardware

    Once the phone is available, verify gestures, tap targets, smoothness, crashes, and any behavior that only becomes clear when the device is in hand.

    REAL DEVICE

Technical basis: Apple Developer’s iPhone Duo resources and Prepare your app for iPhone Duo. This is a planning checklist, not a report of tests already performed.

Prepare now.
Confirm on device.

BEFORE DEVICE ARRIVAL

Use Apple’s tools.

Build and preview flexible layouts in Xcode. Apple’s current developer resources describe SDKs and Device Hub tools for iPhone Duo preparation.

See Apple’s resources ↗
AFTER DEVICE ARRIVAL

Check real behavior.

Run the agreed flows on physical hardware, change display states during use, and capture clear evidence for anything that breaks.

Request a device test ↗

Make your test
request useful.

Tell me what a successful run looks like. The clearest requests include an app name, TestFlight link when available, the two or three flows that matter most, and any specific screen or transition you’re concerned about.

Ready for a real-device pass?

Requests are open now. Testing begins after I receive the iPhone Duo; scope and timing are confirmed before work starts.

Request a test

Common questions.

Can you test my app before the iPhone Duo is available?

I can review your request and plan the scope now. Physical-device testing begins after I receive the phone.

Do I need a TestFlight link to ask?

No. You can describe the app and the flow first, then share the build when it is ready for testing.

Will you test both display states?

Yes, if they are part of the agreed test scope. The request form lets you identify the transitions and screens that matter most.

Can I request a retest after a fix?

Yes. Mention the issue you want checked again, and I’ll confirm the scope and availability.