Skip to content

Fixed-scope offer

iPhone Duo readiness review

Price
From £2,500
Time
2 weeks
Payment
50% deposit to book, balance on launch; monthly plans billed in advance.

iPhone Duo is a new device and few apps are ready for it. We've built for it. In two weeks we review your existing iPhone app against Apple's published guidance for the foldable, fix the layout problems it will hit, and give you a written test report.

We reply within one working day.

What happens after you get in touch

We reply within one working day.

  1. Step 1

    We reply within one working day

    We read what you sent and come back with questions, a rough view of cost, or a time to talk.

  2. Step 2

    A 20-minute call

    We talk through what you need and tell you honestly whether we're the right team. No charge and no obligation.

  3. Step 3

    A written, fixed-price proposal

    Scope, price and timeline in writing. Nothing starts until you've signed it off.

Who it's for

Teams with a live iPhone app, whatever it's built with, who want it to work properly when customers open it on iPhone Duo rather than find out from reviews.

What you get: An app that lays out correctly on both displays and in every pose Apple documents, the fixes made in your code, and a written test report you keep.

What's included

  • A code review for the patterns Apple says break on iPhone Duo: sizing from the main screen, layout decisions made from device orientation, and layouts chosen by device idiom or by assuming a regular width means iPad.
  • Layout by size class: a compact-width layout for the outer display and a regular-width layout for the inner display, sized to the container rather than to fixed iPhone dimensions, as Apple's guidance asks.
  • Reserved regions: content kept clear of the fold (a division) and the cameras (an occlusion) using Apple's ReservedRegion API, or the system containers that handle them for you.
  • Split View on the inner display and the asymmetric safe areas that come with it, so controls along one edge never cover content.
  • The outer display: your navigation bars, toolbars and tab bars, which the system can present vertically along the side, checked so every item has an icon and nothing important is dropped.
  • Opening, closing, folding and rotating: every view, sheet and popover checked in each pose, following Apple's testing guidance.
  • A written test report with screenshots from the iPhone Duo simulator, what we changed, and what we recommend next, for example a camera capture accessory on the outer display if your app uses the camera.

Not included

  • New features designed for the device, such as a second-screen experience or content on the outer display during capture. We scope those separately once the app is ready.
  • Claims about hardware we haven't tested. We test in Apple's iPhone Duo simulator in Xcode 27.1, and on a device when one is available; where a behaviour comes from Apple's documentation rather than our own test, the report says so.
  • iPad and Mac versions of the app.

What Apple's documentation says the device changes

  1. 1

    Two displays, many sizes

    A compact outer display and a large inner display, each with a front camera. Apple's guidance is that an iPhone app can now have any combination of size classes, so layouts must come from size classes and the space available, not from the device type or its orientation.

  2. 2

    The fold and the cameras are reserved regions

    When the device is partly open, the fold divides the inner display. The outer camera sits in a corner of its display, and the inner camera appears only while it is in use. iOS reports all of these as reserved regions, and content has to be arranged around them. System containers such as split views do this for you; custom layouts have to ask.

  3. 3

    Bars move to the side

    In some poses the system presents navigation bars, toolbars and tab bars vertically along the side of the display. Items without an icon aren't shown vertically, which is how buttons quietly disappear on apps that haven't been checked.

How it runs

  1. Days 1 to 3We build your app with Xcode 27.1, run it in the iPhone Duo simulator in every pose and orientation, and review the code for the patterns Apple lists. You get a findings list with a fix for each.
  2. Days 4 to 8The fixes: size-class layouts, reserved regions, bars and Split View, with a TestFlight build you can try.
  3. Days 9 to 10A re-test in every pose, the written report with screenshots, and a short call about what to do next.

Why trust us with it

We've built for iPhone Duo ourselves: our own app, Cuefold, puts your script on the outer screen on iPhone Duo, and was built with Xcode 27.1 and the iPhone Duo SDK, the same tools we use for this review. It's on the App Store today.

What this is based on

Every technical statement on this page comes from Apple's public developer documentation, listed here. Where our report relies on a documented behaviour rather than our own test, it says so.

  1. 1Preparing your app for iPhone Duo (Apple technology overview)
  2. 2Three steps to make your app shine on iPhone Duo (Apple Developer)
  3. 3Designing for iPhone Duo (Human Interface Guidelines)
  4. 4ReservedRegion (SwiftUI documentation)
  5. 5ArrangementView (SwiftUI documentation)
  6. 6CameraCaptureAccessory (SwiftUI documentation)

After launch

Keep it working after launch

Websites and apps need looking after once they're live. App care is the plan most people choose after this, at £450 a month.

Already have an app or site that needs looking after?

Questions we get asked

Yes. The app still runs in an iOS scene and is resized the same way, so the same rules about size classes, orientation and reserved regions apply. Some fixes sit in the framework or its plugins rather than in your code; the findings list says which, and what the framework version you're on supports.

Other ways to start

Start with a 20-minute call with our team.

Tell us where you are and what you need. We'll tell you honestly whether this offer fits, or what would. We reply within one working day.