Is Your App Compatible With iPhone Duo? What Works, What Breaks and What to do

Yes, your app will work on iPhone Duo. If it runs on a current iPhone today, it will install, open and do its job on Apple's foldable from the day it ships on 23 October. Nothing goes dark, nothing is pulled from the App Store, and your users will not be locked out.

That is the good news, and it deserves to come first because it is the question most people arrive with. The less comfortable news is that working and fitting are two different things. On iPhone Duo, most existing apps will manage the first and not the second.

Working is not the same as fitting

Open an unmodified app on the Duo's large inner screen and this is what users are likely to see:

• The app sitting in a phone-sized box in the middle of a much bigger display, with empty space around it.

• Navigation bars, tab bars and buttons where they have always been, while Apple's own apps have moved theirs.

• Screens that look stretched, squashed or oddly spaced once they are finally allowed to grow.

None of that stops anyone finishing a task. All of it tells a user, within a second or two, that the app was not built with their new phone in mind. To understand why, it helps to look at what makes this device so different from every iPhone before it.

Two screens, and neither is the one your app was designed for

Every iPhone until now has had one screen with one familiar shape: tall and narrow. An app could be designed once for that shape, and the only real change it ever had to handle was rotation. iPhone Duo replaces that single shape with two.

The sizes alone would be manageable. What makes this harder is that people move between them constantly:

• They start a task on the outer screen and unfold the phone halfway through.

• They use it half folded, propped on a table like a small laptop.

• They run two apps side by side on the inner screen, which means your app may get half of it.

A classic app only ever had to be right for one shape. A Duo-ready app has to be right for all of them, and hold together in the moment it switches between them.

What iOS does with apps that were never built for this

Apple knew almost no app would be ready on day one, so iOS makes a decision on each app's behalf. It checks which version of Apple's developer tools, known as the SDK, the app was last built with, and decides how much screen to give it.

• Built before iOS 27: the app gets a phone-shaped area. This is the boxed-in look described above.

• Built with iOS 27: the app gets more room, but still stops short of the edges.

• Built with iOS 27.1: the app gets the whole screen.

This is why nothing changed on a server, and no over-the-air update, will improve the experience. The only way up is a new build, submitted to the App Store.

iOS 27.1: the key to the full screen

iOS 27.1 is the release that treats the Duo as a first-class device, and building with its tools is what gives your app access to it. Xcode 27.1, Apple's development environment, arrived in beta on 18 September with the iOS 27.1 SDK and a Duo simulator that can open, close, fold and rotate a virtual device.

Building with 27.1 gives you three things:

• The full display. Your app reaches the edges of both screens instead of sitting inside a frame.

• System bars that adapt. Standard navigation bars, toolbars and tab bars move into a vertical strip at the side of the screen where that suits the layout.

• The tools to design new screens. Layouts that respond to the space available, split views that show two panes when open and collapse to one when closed, and sidebars on the inner display.

That last point is where the real work, and the real opportunity, sits. Getting the full screen is only worth it if what fills the screen was designed for it.

Why existing screens will not simply stretch to fit

Once an app is given the full screen, every layout decision made for a single tall, narrow display is suddenly on show. These are the problems we expect to find most often.

Bars and bottom navigation

• Custom tab bars and bottom navigation, common in modern apps and almost universal in cross-platform ones, are not moved by the system. Only the standard bars adapt, so a hand-built bottom nav stays stretched along the bottom of a 7.6-inch screen.

• Custom headers and toolbars behave the same way, staying across the top while the rest of the system has moved to the side.

• Floating action buttons anchored to a bottom corner can end up a long way from the content they act on.

Layout and spacing

• Screens designed around a fixed width stretch awkwardly or leave wide empty gutters.

• Apps locked to portrait lose that lock on the inner screen, which ignores it.

• The safe margins around the edges are often uneven on the Duo, so anything that assumed the left and right margins match ends up off-centre or clipped.

• Code that asks how big the screen is gets a misleading answer on a device that has two.

Other screen features

• The inner display has its camera under the screen, which changes what can sit comfortably near the top edge.

• The Duo uses Touch ID in the power button rather than Face ID. Any screen that mentions Face ID by name is now wrong on this device.

• Pop-ups, sheets and modals sized for a phone can look lost on the larger display.

None of these are exotic bugs. They are ordinary decisions that made perfect sense when there was only one kind of iPhone, which is exactly why they are easy to miss.

Every screen needs a review, not just the home screen

It is tempting to open the home screen, see that it looks acceptable, and call it done. The trouble is that each screen in an app carries its own assumptions about size and shape, so each one can fail in its own way. The screens most likely to cause problems are often the ones checked last:

• Onboarding and carousels built around fixed-size images.

• Forms, sign-up and checkout flows, where layout and the keyboard interact.

• Lists and tables with fixed column widths.

• Detail pages with images, video or maps.

• Pop-ups, bottom sheets, alerts and date pickers.

• Camera, scanning and photo capture screens.

• Web views used for payments, terms or help content.

• Empty states, error screens and loading screens.

• Login and biometric prompts.

Each of those should be checked in every way the device can be held:

• Closed, on the outer screen, in portrait and landscape.

• Open, on the inner screen, in portrait and landscape.

• Half folded.

• In Split View beside another app, at half width.

• Mid-change, such as unfolding while filling in a form. The screen should resize without losing what the user typed or where they were.

That produces a simple grid: every screen down one side, every position across the top. It is the most reliable way we know to find out how much work an app actually needs, and it turns a vague worry into a specific, costed list.

If your app is built with React Native, Flutter or web views

Cross-platform apps are more exposed, because more of their layout decisions are made in the app's own code rather than handled by the system.

React Native

• Screen dimensions read once when the app starts do not update when the phone unfolds, so layouts built from them stay the wrong size.

• React Native has no built-in way to detect the fold. Behaviour that depends on it needs a native module.

• A JavaScript update pushed over the air will not change how much screen the app gets. It needs a full native build and a store release.

// Read once, never updates
const { width } = Dimensions.get('window');

// Updates when the phone folds or unfolds
const { width } = useWindowDimensions();

Flutter

• Flutter's fold detection only works on Android and reports nothing on the Duo.

• Resizing and uneven margins can be handled in standard Flutter code. Only the fold itself needs platform-specific work.

Web views

• A web view inside a resizable app has to resize too, and mobile breakpoints set around 480 pixels land awkwardly on the wider outer screen.

Making use of the space

So far this has been about avoiding problems. The more interesting half is what the Duo makes possible, because a 7.6-inch screen is not just a bigger phone. It is room to show more than one thing at once.

• List and detail together. Orders, bookings, messages or products on one side, the selected item on the other, with no back button in between.

• Map and results. A map beside the list of places, jobs or deliveries it shows.

• Watch and act. A video, live stream or call in one pane, with notes, chat or controls in the other.

• Dashboards that fit. Several panels of information visible at once instead of spread across tabs.

• Side-by-side comparison. Two plans, products or quotes next to each other.

• Half folded. Content on the upper half and controls on the lower half, well suited to video, cameras, recipes or anything used hands free.

• Next to other apps. In Split View, a well-built app becomes the one someone keeps open beside their email or spreadsheet.

• Apple Pencil (released later). Signatures, markup and annotation become practical in a phone app.

When the phone closes, these layouts fold back into a familiar single column. Done well, the user gets the right version of the app for whichever screen they are holding, without ever noticing the switch.

For the first few months, being one of them is a visible difference in reviews, in App Store screenshots and in front of customers.

 

Costs worth knowing about up front

• Liquid Glass. Building with the iOS 27 tools removes the option to keep the older iOS look. If that update was postponed last year, it now comes bundled with this one.

• No opting out. There is no setting that exempts an app from being resized when the phone opens and closes.

These two are the usual reason a quick rebuild grows into a larger project, and the reason a review should always come before a quote.

How we approach it

• Review. Build the app with iOS 27.1, run it in the Duo simulator, and work through the screen-by-position grid above. The result is a list of what breaks and an honest estimate.

• Compatibility release. Fix what is broken: bars, navigation, spacing, margins, sizing and outdated screen references. The goal is that nothing looks wrong.

• Optimisation release. Redesign the screens that gain most from the extra space, such as list and detail, dashboards and maps. The goal is an app that feels made for the device.

Splitting the work this way gets users a version that fits quickly, while the more ambitious changes are planned properly rather than rushed.

FAQ

Is my app compatible with iPhone Duo?

Yes. Any app that runs on a current iPhone will run on the Duo. Whether it fits the screens properly depends on when it was last built and how its screens were designed.

Will my app look right without an update?

Probably not. Older builds appear in a phone-sized area on the inner screen, and custom navigation and fixed layouts tend to look out of place.

What does iOS 27.1 change?

Apps built with it can use the full screen on both displays, and standard bars adapt to the Duo automatically. It also provides the tools and simulator needed to design and test new screens.

Do we need to rebuild every screen?

Not rebuild, but every screen should be reviewed. Many will need small fixes, and a few will be worth redesigning.

Is this the same as building for iPad?

Supporting iPad doesn’t require a separate app either. Designing for duo is basically the same as supporting ipads with split view.

Can we test without the device?

Yes. The simulator in Xcode 27.1 covers every position of the device, plus Split View. Testing on real hardware is still worthwhile once it is available.

 

---

In short: your app will work on iPhone Duo from day one. Making it look and feel right on both screens takes a review of every screen, a new build with iOS 27.1, and the chance to design something your competitors may not have.