The folding iPhone ships October 23. Here's what breaks in your app, and how to fix it.

Apple opened App Store submissions for the iPhone Duo on October 5, and the device goes on sale October 23. It is Apple's first folding iPhone: a smaller outer display you use with it closed, and a larger inner display when you open it. The catch for developers is that your app's size changes the moment someone folds or unfolds the device, and that size does not always match the physical screen. To handle it, Apple shipped the Xcode 27.1 release candidate on October 5 with the folding simulator, a Device Hub for checking every pose, and a set of layout APIs built around the fold.

Here is the part that sets the deadline. Apps built with the iOS 27 SDK already resize to fill most of the inner display. Build against the iOS 27.1 SDK and your app gets the "optimized for iPhone Duo" badge, with toolbars and tab bars moving into a vertical bar below the status area. Older builds still run, just with black borders. From April 2027 every App Store submission has to include iPhone Duo screenshots, so even if you skip the hardware for now, you cannot skip the layout work for long.

What actually breaks

Two things, mostly. The first is hardcoded screen sizes. Apple's own guidance is blunt about it: search your project for UIScreen.main and get rid of it. Read size from the view or window instead (view.bounds, window.bounds, or GeometryReader in SwiftUI), and re-read it whenever it changes, because a fold can resize your app in the middle of a session. The second is orientation logic. On iPhone Duo the device's orientation no longer tells you the shape of your app, so anything keyed off UIDevice.current.orientation or interfaceOrientation needs to go. Compare the width and height of the space you actually have.

For layouts that need to respond to the fold itself, there are two new tools. Reserved regions let you ask the geometry proxy where the hinge and cameras are: a .division region marks the fold, an .occlusion region marks a camera, and each one reports its frame and whether it is active right now. The fold's region is only active when the device is partially open, which is a useful detail, because you can read it while the device is flat and lay out an even number of columns so nothing ever lands on the crease. The second tool, ArrangementView in SwiftUI (or UIArrangementViewController in UIKit), is a two-pane container that splits or overlays your primary and secondary views and moves the divider onto the fold for you.

We have watched this movie before

In our native iOS and Android projects, the apps that sailed through the iPad multitasking and Split View era were always the ones that sized views against their container rather than the screen. The ones that hardcoded dimensions needed real surgery, and it was never a quick afternoon. We have seen the same split in healthcare and IoT work, where a phone build and a tablet build shared one codebase: the team that trusted size classes shipped, the team that special-cased screen bounds spent a sprint undoing it. iPhone Duo is the same lesson with a new shape. If your layout already adapts to iPad and to iPhone Mirroring on the Mac, you are most of the way there.

One word of caution on the shortcut. Xcode 27.1 lets you ask the coding assistant to "get my app ready for iPhone Duo," and it will scan for these patterns and propose fixes. That is genuinely useful for finding every UIScreen.main in a large codebase. It is not a reason to merge the diff unread. Layout changes touch exactly the screens your users spend the most time on, and an automated rewrite that moves a control off the fold can just as easily push a tap target under a camera. Review it like any other pull request.

The move for this week

Point one CI lane at Xcode 27.1, build against the iOS 27.1 SDK, and run your three or four highest-traffic screens through every pose in the simulator: closed, open, book, and rotated. Before any of that, grep the codebase for UIScreen.main, UIDevice.current.orientation, and fixed frame constants. That search alone tells you how big this job really is, long before you write a line of new layout code. For most apps it is smaller than it looks. For a few it is a rewrite, and better to know now than in March 2027.

This is also a good moment to think past iOS. The discipline iPhone Duo forces, sizing against a container and never trusting a fixed viewport, is the same one that keeps a web app readable from a phone to an ultrawide monitor. When we build cloud-native apps for enterprise clients, that responsiveness is just assumed. Native mobile is finally being pushed the same way, and the teams who treat it as an architecture habit rather than a one-off patch will spend a lot less time chasing the next form factor. You can see how we have approached cross-platform work in our portfolio, and the development page covers how we build for web and mobile together.

If getting an app ready for a new form factor without rewriting your layout from scratch sounds familiar, let's talk.