Guide · Apple newsroom, Apple Developer news and Tech Talks read 22–23 September 2026

    iPhone Duo apps: what changes for your users, and the seven updates an existing app needs

    iPhone Duo ships on October 23, 2026: the first foldable iPhone, a 5.4-inch phone closed and a 7.6-inch screen open, on iOS 27.1. Every app in the App Store runs on it. Few are built for it. This page is for the product manager, designer or founder who owns an app and has never built for a phone: what changes for the person holding it, the seven updates your app needs ranked by how much work each is, the sentence to send your developer for each, the two dates that matter — and the fact the iPhone-only guides leave out: foldables have been on Android since 2019, and one product spec covers both.

    Verified

    The short answer. An app that is not updated runs on the Duo in a phone-shaped box in the middle of the big screen. An app rebuilt with the new iOS 27.1 SDK fills the screen, and its buttons move to a column on the side. Beyond that rebuild, the work is six more changes, most of them one sentence to a developer or an AI agent if the app uses Apple’s standard parts, and a project if its navigation was built from scratch. The date for the store: to be live when people have the phone on October 23, submit to App Review by around October 16. The date for everyone: “Starting April 2027, apps and games uploaded to App Store Connect need to meet the following minimum requirements: iOS and iPadOS apps must be built with the iOS 27 & iPadOS 27 SDK or later” (Apple Developer news, 9 September 2026).

    The point the iPhone guides skip. Android has shipped foldables since 2019. Android’s developer documentation describes the same postures — flat, half-opened, and in the half-opened state “tabletop posture (horizontal fold) and book posture (vertical fold)” — and the same answer: “Adaptive layouts provide an optimized user experience when a foldable device is folded or unfolded, in portrait or landscape orientation, or in tabletop or book posture.” A product spec that says “adaptive layout: two panes on the open screen, nothing under the fold, a standing-mode feature” describes the Duo and the Galaxy Z Fold at once. In a tool that builds both platforms from one project, it is one line in the PRD, not two projects.

    What changes for the person holding it, in plain words

    Closed, it is a normal phone. Held upright, that is the screen every iPhone app was designed for. Turned sideways, it is new: a small, wide screen no iPhone has had.

    Open, it is the size of a small iPad, either way round. An iPhone app on that screen does one of two things. It stretches — same layout, bigger, empty space on the right. Or it rearranges — two things next to each other, the way Mail on an iPad shows the inbox on the left and the open message on the right. Stretched is what “not ready” looks like. Rearranged is what “ready” looks like.

    Two apps side by side. Apple’s newsroom: “Split View allows users to open two apps side by side on iPhone for the first time.” People will drag a photo or a link from another app into yours.

    Half-open on a table, it stands by itself. StandBy — the clock-and-widgets mode — works “on either the outer or inner display — even when it’s not charging.” Apple Pencil support is announced for later this year.

    For a product manager, each of those is a place a feature did not have before: a second screen, two panes instead of one, a phone that stands up. The seven changes below are how an existing app meets them.

    Three layouts, one new

    Apple’s “Prepare your app for iPhone Duo” talk names three size-class combinations. Outer display, portrait: regular height, compact width — the layout every iPhone app knows. Outer display, landscape: compact and compact — new. Inner display: regular and regular in both orientations — the iPad layout.

    The sentence that tells a product team how much work it has: if the app already works properly on iPad — two panes, rotating, side by side with another app — it is most of the way there. If the iPad version is the iPhone layout stretched, that is what everyone will see when they unfold the phone.

    The seven changes, ranked by effort

    Each one: what the user sees, how much work, and the sentence to send your developer or type into an AI agent. The question that decides the effort on almost every line is whether the app uses Apple’s standard parts for navigation (lists, tab bars, split views) or parts built from scratch to look special — ask it first.

    1. Rebuild with the iOS 27.1 SDK — effort: a rebuild, no code changes. Apple’s talk shows an older-SDK app running on the open screen at “a familiar size and aspect ratio” — a phone-shaped box — and a 27.1 app that “extends to the edge of the screen” with its bars in a vertical column. Xcode 27.1 beta has been available since September 18. Sentence: none; select Xcode 27.1 and build. This is also the change the April 2027 rule makes mandatory for every update.

    2. Two panes instead of one — effort: one sentence if the app uses Apple’s parts, a project if it doesn’t. On the open screen a list should become a list on the left and the selected item on the right. Apple’s NavigationSplitView and TabView adapt to the fold, the cameras and the side column on their own; custom navigation does not. Sentence: “On the open iPhone Duo screen, show [the list] as two panes: the list on the left, the selected item on the right; keep the current navigation on the closed screen; move the tabs into the left pane on the open screen.” If the navigation is custom, this is the moment to replace it with Apple’s rather than adapt it.

    3. The buttons move to the side — effort: an afternoon. The row of buttons at the top becomes a column on the side, shared with the status bar. Order matters: back or close at the top, the main action under it, the rest below; every button gets an icon and a name so the phone can choose which to show; counts become badges; extras fold into a “more” menu you control. Sentence: “Arrange the toolbar for iPhone Duo’s vertical bar: back at the top, [main action] pinned under it, the rest below; give every button an icon and a name; show [count] as a badge; keep [button] out of the overflow menu.”

    4. Nothing under the fold — effort: free with Apple’s parts, about a day per custom screen. Half-folded, there is a crease across the screen and two camera holes; Apple calls them reserved regions. Standard containers move content off them by themselves. A custom screen — a player, a board, a chart — needs to be told: split it across the fold, or float one part over the other. Sentence: “When iPhone Duo is half-folded, keep [part A] above the fold and [part B] below it.”

    5. The hinge — effort: an idea, then an afternoon. The app can read how far the phone is open — an angle plus whether it is closed, half-open or flat — with a few lines of code (iOS 27.1 and later). That is a new input, like the tilt sensor Maps uses. Finding the feature is a product job: a memory app that becomes a slideshow when it stands on a table; a recipe app that goes hands-free; a timer that gets big when half-folded. Sentence: “When the hinge is half-open and the phone is resting, switch to [the standing-mode feature].”

    6. Shapes and sheets — effort: an hour. The front screen has uneven corners, so rounded backgrounds the app draws itself need Apple’s shape that follows them; pop-up sheets rearrange on their own but should be checked once open and closed. Sentence: “Use the shape that follows iPhone Duo’s screen corners for the card backgrounds.”

    7. StandBy, drag and drop, Pencil — effort: an hour. Widgets that skipped StandBy should get it, because StandBy now works on either screen without charging. Two apps side by side means people will drag things into yours — decide whether that should work. Apple Pencil support is coming later this year; if the app has anything you draw or sign, put it on the roadmap.

    The same spec on Android: one PRD, two foldables

    Every change above has an Android counterpart, and the vocabulary is close enough that a product spec can name both in one line. Android’s foldable documentation describes the states as FLAT and HALF_OPENED and, when half-opened, “tabletop posture (horizontal fold) and book posture (vertical fold)”; the Duo’s half-open-on-a-table is Android’s tabletop posture. Two panes on the open screen is the same window-size-class decision on both platforms — regular width means two panes — and Android’s adaptive-layout guidance says so in one sentence: layouts “adapt” when the device is “folded or unfolded, in portrait or landscape orientation, or in tabletop or book posture.” Nothing under the fold has the same name on Android — a folding feature that occludes the display — and the same rule.

    For a product manager this means the spec line is written once: “Adaptive layout: two panes in regular width; content avoids the fold; a standing-mode feature when half-open on a surface.” In a tool that builds both platforms from one project — in Modaal, the logic of each feature is written once and the iPhone app renders it in SwiftUI while the Android app renders it in Jetpack Compose — that line produces the Duo version and the Galaxy Z Fold version from the same PRD. The iPhone-only builders can write the first; the second is a second project. How to build a cross-platform app with AI has the mechanism; the PRD prompt has the document.

    The two dates

    October 23, 2026 is when people have the phone (pre-orders October 16). Apple reviews every app before it goes in the store, and review takes days, so to be live on launch morning, submit by around October 16 with a build from Xcode 27.1. The store fees are the usual: $99 per year for the Apple Developer Program, $25 once for Google Play if the Android version ships too.

    April 2027 is when the rebuild stops being optional: from then, every app or update uploaded to App Store Connect must be built with the iOS 27 SDK or later. An app that is not rebuilt cannot be updated after that date, on any phone.

    The video version of this page, with the seven changes done live on one of our apps, is on YouTube.

    Where to start if you own an app and don’t write Swift

    Ask your developer the one question: did we build our own navigation, or use Apple’s parts? If Apple’s, the whole list above is days; if custom, change 2 is the project and the rest is days. Then send the sentences. If you build with an AI agent yourself — Modaal builds with the Xcode you select, so the 27.1 beta is a menu choice, and runs the app in the Duo simulator open, closed and half-folded — the sentences above are the prompts; the agent writes a plan you approve before it changes anything. The Free plan covers one project with unlimited prompts on one platform; Pro is €9 per user per month billed annually and adds both platforms and TestFlight distribution — /pricing. Modaal for product managers is the page for how a PRD becomes the build.

    The seven changes at a glance

    #ChangeWhat the user seesEffortAndroid counterpart
    1Rebuild with the iOS 27.1 SDKFull screen instead of a phone-shaped boxA rebuild, no code changesTarget the current SDK; window size classes
    2Two panes instead of oneList left, detail right on the open screenOne sentence (Apple’s parts) / a project (custom)Two panes in regular width — same decision
    3Buttons move to a side columnOrdered column: back, main action, restAn afternoonNavigation rail / adaptive navigation
    4Nothing under the foldContent moves off the crease and camerasFree (Apple’s parts) / a day per custom screenFoldingFeature occlusion — same rule
    5The hinge as an inputA standing-mode feature when half-openAn idea + an afternoonHALF_OPENED, tabletop / book posture
    6Shapes and sheetsCorners and pop-ups that fit each poseAn hourAdaptive sheets
    7StandBy, drag and drop, PencilWidgets on the standing phone; drops from other appsAn hourMulti-window drag and drop

    Effort labels assume an app on Apple’s standard navigation; a custom-navigation app makes change 2 the project. Apple Tech Talks and Android foldable documentation read 22–23 September 2026.

    Frequently asked questions

    It will run. Apple’s Tech Talk shows an app built with an older SDK running on the open screen at “a familiar size and aspect ratio” — a phone-shaped box in the middle of the big display. Rebuilt with the iOS 27.1 SDK, the same app “extends to the edge of the screen”. The rebuild is change 1 of seven and needs no code changes.

    Two dates. To be in the store when the phone ships on October 23, 2026, submit to App Review by around October 16. From April 2027, Apple requires every app or update uploaded to App Store Connect to be built with the iOS 27 SDK or later — the rebuild becomes mandatory for updates then.

    Seven changes: a rebuild with no code changes; two panes instead of one (one sentence if the app uses Apple’s standard navigation, a project if the navigation is custom); the side column of buttons (an afternoon); nothing under the fold (free with standard parts); the hinge feature (an idea and an afternoon); shapes and sheets (an hour); StandBy, drag and drop and Pencil (an hour). The one question that decides it: standard parts or custom navigation.

    Yes. Each change above is a sentence a product manager can send to a developer or type into an AI agent. In Modaal the agent takes the sentence, writes a plan you approve, then changes the Swift and runs the app in the Duo simulator open, closed and half-folded; you build with the Xcode 27.1 beta by selecting it.

    The same product decisions do. Android’s documentation names the same states — flat, half-opened, and tabletop or book posture when half-opened — and the same answer, adaptive layouts by window size class. A spec line “two panes in regular width, content avoids the fold, a standing-mode feature” covers the Duo and the Galaxy Z Fold; in a tool that builds both platforms from one project it is one line, not two projects.

    Two apps side by side for the first time on an iPhone; a phone that stands half-open on a table, with StandBy on either screen without charging; an app-readable hinge angle; Apple Pencil support announced for later this year. Each is a place for a feature that did not exist on an iPhone — the standing-mode feature is the one most apps can find.

    Apple published six iPhone Duo Tech Talks (Design for iPhone Duo; Prepare your app for iPhone Duo; Raise the bar with iPhone Duo; Strike a pose with adaptive layouts on iPhone Duo; Leverage multiple displays and scenes on iPhone Duo; Build a great camera experience for iPhone Duo) and a Human Interface Guidelines section, Designing for iPhone Duo. Xcode 27.1 beta includes the simulator with every pose and an App Resizability agent skill.

    The reasons that can be stated as facts: the developer tools shipped on September 18, five weeks before launch; every existing app runs in a smaller box until rebuilt; and from April 2027 the rebuild is required for updates anyway. Whether a Duo-specific feature is worth your roadmap is a product decision this page does not make for you; it gives the seven changes and their effort so that the decision is sized.

    Send the seven sentences — or type them yourself

    Modaal builds with the Xcode 27.1 beta you select and runs your app in the Duo simulator. Your own AI agent writes the plan you approve, then the Swift and the Kotlin. Free for one project.

    Keep reading