One app.
Two shapes.
Layouts, readability, and continuity as the device moves between closed and open.
Get your iOS app checked on a real iPhone Duo. I’ll test the flows that matter, then send clear notes you can actually fix.
Requests are open now. Testing starts after I receive the device.
New screen shapes change familiar interactions. I’ll put your app through its important moments on physical hardware, looking for the details that are easy to miss before launch.
Choose the flows that matter most. The test is shaped around your app, not a generic checklist.
Layouts, readability, and continuity as the device moves between closed and open.
Tap targets, swipes, awkward reaches, and interactions that don’t feel right in hand.
Transitions, orientation changes, and the unexpected ways people use a larger screen.
Crashes, freezes, rough performance, and anything that interrupts a key task.
Preparing your build before the device arrives?
Read the iPhone Duo testing checklistFeedback is only useful when you can reproduce the problem. Expect a concise report focused on what happened, where it happened, and what it looked like on device.
In this illustrative example, the tab bar moves below the visible area when the app expands from the outer to inner display.
Open the app on the outer display → go to the library → unfold the device.
Safe area and layout update during the transition.
Start with your TestFlight build and the moments you most want checked.
Share your app, TestFlight link, and the flows or edge cases you want tested.
Once I have the iPhone Duo, I’ll run through the agreed scope on real hardware.
Receive practical notes and visual evidence where it helps. Ask about a retest after fixes.
Tell me about your app and what you want checked. I’ll follow up to confirm the scope and timing.