On 23 October 2026 iPhone Duo went on sale: a foldable iPhone with two displays, an outer one when it is closed and an inner one that opens "like a book". For users it is a new form factor. For teams that maintain iOS apps it is a new deadline: from April 2027, every app and game submitted in App Store Connect must include iPhone Duo screenshots.

The good news is that you do not have to rewrite the app. But a few common code patterns break on this device, and it is better to find them now than a month before the deadline. Below we cover what Apple said, how an app behaves depending on the SDK, what to check in code, and what to prepare for your App Store page.

What Apple announced

According to Apple's announcement of 5 October 2026 and its iPhone Duo preparation guide:

  • iPhone Duo is available to customers from 23 October 2026;
  • you need to recompile the app with Xcode 27.1, which adds support for the new device; behavior in all poses and orientations can be checked in Device Hub;
  • iPhone Duo screenshots can be submitted now: your product page then shows a badge saying the app is optimized for iPhone Duo;
  • from April 2027 such screenshots become mandatory for every new submission.

Apple also suggests stating in the "Helpful Details" section of a featuring nomination that the app is optimized for iPhone Duo in all device poses.

How an app behaves depending on the SDK

How your app looks on the new device depends on the SDK it was built with. Apple describes three scenarios:

SDKOpen (inner display)Closed (outer display)
iOS 26 or earlierWindow centered at a familiar size with empty space around itContent sits to the left of the status bar and camera
iOS 27Fills most of the inner display, but still avoids the status bar on the rightApple does not specify
iOS 27.1 or laterEdge to edge; toolbars and tab bars move vertically below the status barEdge to edge, with a consistent experience across both displays

The practical takeaway: if you build with the new SDK, check how your UI handles vertical bars. This is where teams most often notice shifted elements and content that overlaps.

Step 1. Automated check

Apple suggests starting with a skill for a coding assistant: in Xcode you simply ask it to "get my app ready for iPhone Duo". For other agents the skill can be exported with xcrun agent skills export. Apple warns that it finds most issues but not all, so a manual review against the checklist below is still needed.

Step 2. Three patterns to find in your code

1. Screen size is taken from the main screen

If your code contains UIScreen.main, it is a candidate for a fix, because the window size no longer equals the device size and changes mid-session when the device is folded or unfolded:

  • replace UIScreen.main.bounds with view.bounds or window.bounds; in SwiftUI use GeometryReader or onGeometryChange;
  • move size-dependent calculations to layoutSubviews or viewDidLayoutSubviews; reading the size once at launch or in viewIsAppearing is not enough;
  • take scale from traitCollection.displayScale (UIKit) or @Environment(\.displayScale) (SwiftUI);
  • replace UIWindow(frame: UIScreen.main.bounds) with UIWindow(windowScene:), and do not store a screen: get it when needed through view.window?.windowScene?.screen.

2. Layout depends on orientation

Remove logic based on UIDevice.current.orientation, statusBarOrientation or interfaceOrientation. Compare the available width and height instead, through view.bounds, superview.bounds or the GeometryReader size.

3. Device type is guessed from idiom or size class

  • replace userInterfaceIdiom == .phone or .pad checks with size-class and available-space logic;
  • do not equate horizontalSizeClass == .regular with iPad: an iPhone can now have regular width too;
  • remove hardcoded checks such as bounds.height == 844;
  • for full-bleed media using .scaleAspectFill or .aspectRatio(contentMode: .fill), choose fill or fit based on the current size classes or aspect ratio, or set a focal point.

As a reference for the inner display, Apple suggests treating it as a natural extension of your iPad layout: the app should look as if it were designed for the larger screen.

Step 3. Test resizing

One run on a device is not enough. Apple suggests three ways to check:

  • The iOS resizable simulator in Device Hub for quick checks at arbitrary sizes;
  • iPhone Mirroring on macOS 27: resize the window to extreme sizes in both directions;
  • The iPhone Duo simulator in Xcode 27.1: the most accurate way to see the full native experience.

Also test scenarios where the size changes mid-task: filling in a form, video playback, an open keyboard, checkout. This is where state gets lost and layouts jump.

What to prepare for the App Store

From April 2027 a new version cannot be submitted without iPhone Duo screenshots. So it is worth preparing ahead:

  • capture screenshots in different orientations following Apple's specification;
  • check how your page looks in the App Store Connect preview tool, including the new creative assets;
  • mention in your featuring nomination that the app is optimized for iPhone Duo in all poses.

A checklist for the coming weeks

StepWhat to doOutcome
1Build with Xcode 27.1 and run in the iPhone Duo simulatorA list of screens with broken layout
2Find UIScreen.main, orientation checks and device idiom checksA list of places in code that depend on device size
3Fix the critical screens: onboarding, payment, the main flowAn app that does not break when folded or unfolded
4Test resizing during a sessionState is preserved and layout does not jump
5Prepare iPhone Duo screenshotsA ready set well before April 2027

This table reflects our practice, not Apple's official position. The order may differ per team depending on architecture: a SwiftUI project usually has fewer screen-size dependencies than a long-lived UIKit codebase.

Conclusion

iPhone Duo does not require a separate app, but it does require the app window to be genuinely flexible. A team that already supports iPad and multitasking will get through this quickly. A team that still relies on the main screen size and orientation should start with an audit now, while a few months remain before the screenshots become mandatory.

If you need help auditing an iOS app for adaptive layout or preparing for the new App Store requirements, get in touch: we will estimate the scope and propose a plan.