"Our app works on iPhone. Do we need to do anything for iPhone Duo?"

The question

Picture the product manager at a retailer with a perfectly good iPhone app, asking the question in the headline: "Our app works fine. Customers are already posting photos of their new iPhone Duo. Do we actually need to do anything, or is this a big-phone thing we can ignore?"

It's a fair question, and one plenty of teams will be asking this weekend. Apple's first foldable iPhone, iPhone Duo, went on sale at Apple Stores worldwide on Friday, October 23, 2026. The short answer is that your app will run, but it may not look right, and the fix depends mostly on which version of Apple's tools you build with.

Your app won't crash on the new phone. It'll just look like it was made for an older one.

What customers see, depending on how you built the app

Apple's developer guidance lays out three cases.

Built with the iOS 26 SDK or earlier. The app runs, but when the phone is unfolded it appears in the center of the inner display with empty space around it. Folded, the outer display shows the app to the left of the status bar and camera. It works, but it looks like a letterboxed movie on a new TV.

Built with the iOS 27 SDK. The app resizes to fill most of the inner display, still keeping clear of the status bar along the right edge. Much less empty space.

Built with the iOS 27.1 SDK or later. Apple calls this optimized for iPhone Duo. The app uses the full display, and toolbars and tab bars appear vertically below the status bar. Apple's note here matters: before you ship a 27.1 build, make sure your content still works when those bars turn vertical.

So the first thing to find out is simple. Ask your team, or your agency, which SDK your current App Store build used. That one answer tells you what your customers saw on Friday.

What tends to break when the app starts resizing

Moving to a newer SDK lets your app fill the screen. It also exposes shortcuts in the code that assumed every iPhone was a fixed rectangle. Apple names the usual suspects:

Sizing from the main screen. Code that reads UIScreen.main to decide how big things are will get the wrong answer, because on iPhone Duo the app's size changes when the phone folds or unfolds and doesn't always match the screen. Apple says to size from the view or window instead, and in SwiftUI to use GeometryReader or onGeometryChange.

Reading the size once. Checking the size at launch isn't enough, since a fold can resize the app mid-session.

Using orientation to choose layouts. On a foldable, whether the phone is held sideways doesn't tell you what shape the app is. Compare the actual width and height you have instead.

Assuming device type. Code that checks whether this is an iPhone or iPad, or that treats regular width as "must be an iPad," will behave unexpectedly. On the inner display, Apple says your app should look like a natural extension of its iPad layout.

Hard-coded screen sizes. Checks like a screen height equal to 844 points, or a list of known iPhone sizes, won't match iPhone Duo.

Full-bleed images and video. A hero image set to fill the frame can crop off important content on a wider display. Apple suggests choosing between fill and fit based on the space, or setting a focal point. For a retailer, that's your product photography.

How to find the problems quickly

Apple has made the first pass easier than usual. In Xcode, you can ask the coding assistant to "get my app ready for iPhone Duo." Apple says the skill scans the project for the patterns above, explains each problem and suggests a fix. If your team uses a different coding agent, Apple says the skill can be exported with the Terminal command xcrun agent skills export.

Apple is also clear that the skill finds most issues, not all of them. Treat its list as a starting point and review the code paths it doesn't cover, especially custom layouts, onboarding screens and checkout.

Then test resizing, using the tools Apple lists:

• the iOS resizable simulator in Device Hub
• iPhone Mirroring on macOS 27, resizing the window to extreme sizes in both directions
• the iPhone Duo simulator in Xcode 27.1, which Apple calls the best way to test the full native experience

Walk through the flows that make you money: browsing, product pages, cart, checkout, account. Fold and unfold in the middle of each one.

What we'd tell that product manager

Here's roughly the plan we'd suggest.

This week. Find out which SDK your live build uses. Open the app on the iPhone Duo simulator and see what customers see today. Run Apple's readiness skill and collect the list.

Next sprint. Move to the newest SDK your team can support, fix what the skill and the testing turn up, and check every screen where images fill the frame. If your release schedule is tight, prioritize the checkout and product pages over settings screens.

When the build is ready. Apple says that when you submit iPhone Duo screenshots in App Store Connect, your product page shows a badge saying the app is optimized for iPhone Duo. There's a new preview tool for checking how your assets look, and you can submit a featuring nomination noting your iPhone Duo support. For a retailer heading into the holidays, that badge is a small but real signal to new-phone owners browsing for apps.

What not to do. Don't build a separate "foldable mode." Apple's guidance points the other way: one layout that adapts to the space it has.

We covered the wider version of this problem, a customer opening your app on a phone you've never tested, in On Christmas morning, someone opens your app on a brand-new phone. iPhone Duo is the sharpest example of it this year.

If your team needs help updating the SDK, fixing layout code or testing across iPhone Duo's displays before the holidays, our mobile applications team does exactly this work. Talk to us.

Related work: Spin Market.