Ingenious Techlab TeamTwo things happened to iOS apps in September 2026, and most coverage treats them as one.
The first is iPhone Duo, Apple’s first folding iPhone. It goes on sale on 23 October. Your app will run on it without any work. Whether it looks like it belongs there is a separate question.
The second affects every iOS app, whether or not a single customer ever buys a foldable. From April 2027, every app uploaded to the App Store must be built with the iOS 27 SDK. An app built with that SDK won’t launch at all unless it uses a structure called the scene-based life cycle, which many existing apps don’t.
This guide covers both in plain language, for the people who have to decide what to do and budget for it. Every date and technical requirement links to Apple. Where a sentence is our estimate or opinion, it says so.
What Apple actually shipped, and what it hasn’t yet
iPhone Duo has two screens. When closed it’s a phone with a 5.4-inch display. Unfolded like a book, it reveals a 7.6-inch inner display. Apple publishes the pixel dimensions: 1398 × 2034 for the outer display and 1878 × 2670 for the inner one.
What matters for apps is the shape. Most iPhones are tall and narrow. iPhone Duo’s screens are close to square.
An app designed around a tall, narrow phone meets a screen roughly 1.4 times as tall as it is wide. That single change explains most of what goes wrong on the device.
Here is what exists today, and what doesn’t:
- Published: six Tech Talk videos for developers, Apple’s design guidelines for iPhone Duo, the iOS 27 and Xcode 27 releases, and — since 18 September — Xcode 27.1 beta, which carries the iOS 27.1 SDK and the iPhone Duo simulator. Your team can now see your app on the device without owning one. We covered what the Xcode 27.1 beta contains and what its simulator cannot do separately.
- Still not published: Apple’s written guide, Preparing your app for iPhone Duo. And the simulator is not a substitute for hardware for everything — it cannot run StandBy or most app extensions, so widgets and share extensions still need a real device.
That second point matters when you read advice elsewhere. Until 18 September nobody outside Apple had seen a third-party app on iPhone Duo, apart from the few Apple says are already taking advantage of the folding design (it names Netflix, Zoom and Slack) — so treat any article older than that, and any specific measurement in one, with suspicion.
The dates that matter
Two of these dates matter most. 23 October is when real customers start opening your app on a foldable. April 2027 is the deadline to change how the app is built — and it applies to every iOS app, not just ones people use on iPhone Duo.
The rebuild trap: iOS 27 and the scene life cycle
Start here, because it affects every iOS app and it’s the one that can stop an app from launching.
Apple’s iOS 27 release notes put it bluntly:
Apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch.
In practice:
- Your app on the App Store today keeps working. An existing binary isn’t affected. The failure only happens when an app is rebuilt with the iOS 27 SDK.
- You can’t avoid rebuilding. From April 2027, Apple only accepts uploads built with the iOS 27 SDK or later. Your next bug fix, price change or feature release after that date needs the new SDK.
- The fix is structural, not cosmetic. An app built the older way sets up its screens from a single app-wide controller. The scene-based way splits that into the app itself and each window of it. The change touches your app’s start-up code, and it’s where deep links, push notifications and third-party SDKs often hook in.
Whether this is a small or a large job depends heavily on what your app is built with. From version 3.41, Flutter migrates apps automatically as long as their app delegate hasn’t been customised. React Native adds support in version 0.88, which is still a release candidate, and Expo’s fix has not been released at the time of writing. Native apps need the migration done by hand. We cover each in detail in iOS 27 for developers: the changes that break builds.
The practical advice: don’t let your first iOS 27 build be the one you need to ship urgently. Do the migration on a quiet week, well before April.
How your app will look on iPhone Duo
Apple describes three possible experiences, depending on the SDK your app was last built with.
- Not rebuilt. Your app runs, but on the big inner display it appears at “a familiar size and aspect ratio” — essentially a phone-shaped window with unused space around it. Closed, it uses the space beside the status bar and camera.
- Rebuilt with the iOS 27 SDK. The app extends to the left of the status bar area on the inner display. It uses more of the screen, but not all of it.
- Rebuilt with the iOS 27.1 SDK. The app reaches the edge of the screen, and standard navigation and toolbar buttons move to run vertically down the side. This is the full iPhone Duo experience. It requires Xcode 27.1, which isn’t out yet.
The trap in tier three: reaching the screen edge exposes every layout assumption your app makes. An app that looked fine in a phone-shaped window can look worse once it fills a near-square display, if it was never designed to resize.
Why your app has to resize while it runs
On a normal iPhone, your app’s screen size is effectively fixed. On iPhone Duo it changes while someone is using it: they open the device, close it, rotate it, or fold it partway and stand it on a table.
Apple’s guidance is not to design a separate layout for each pose. The system reports a “compact” size when the device is closed and a “regular” size when it’s open, and a well-built app adapts to those two. An app built with fixed sizes, or one that locks itself to portrait, is where the work is. Apple states that the inner display doesn’t honor the orientations your app says it supports.
Why toolbars move to the side
On the outer display, and on the inner display in landscape, iPhone Duo moves toolbars and tab bars from the top and bottom of the screen to the side.
If your app uses Apple’s standard navigation and tab bar controllers, this happens automatically. If your team placed its own toolbar, tab bar or navigation bar on screen instead — common in branded apps — Apple’s Tech Talk sample code notes that content from those bars “won’t be considered.” Those screens need rework.
What breaks, by kind of app
This is our assessment, based on Apple’s published guidance. Since 18 September a developer can check it against the iPhone Duo simulator in the Xcode 27.1 beta, which is the fastest way to confirm which row your app is in.
| Your app is… | Likely outcome on iPhone Duo | Where the work is |
|---|---|---|
| Built mostly from Apple’s standard components, already works on iPad | Adapts well once rebuilt | The scene life cycle, then testing each pose |
| iPhone-only, designed for one screen size | Runs, but looks like a phone app in a box | Removing fixed sizes and orientation locks |
| Heavily branded, with custom tab bars and toolbars | Custom bars won’t move to the side | Rebuilding navigation around standard components, or adapting custom ones |
| A game, video or camera app | Aspect ratio and camera behaviour change | Filling a near-square screen; handling two front cameras |
| React Native or Flutter | Resizes correctly, can’t see the fold | Framework upgrade for iOS 27, then layout checks |
What to do: a decision in three questions
Decision flow: what to do about iPhone Duo and iOS 27
Question 1
Will you ship an update to your iOS app after April 2027?
Almost every business will. From April 2027 every App Store upload must be built with the iOS 27 SDK — and an app built with that SDK does not launch unless it uses the scene-based life cycle.
→ Minimum for everyone: rebuild with the iOS 27 SDK and adopt the scene life cycle.
Question 2
Do iPhone Duo owners matter to your business?
In our view, people buying a phone that starts at $1,999 (U.S.) are often the customers apps most want to keep. An un-adapted app still works, but looks like a phone app in a box on the inner display.
→ If not yet: stop at the minimum. Your app appears at a familiar size on the inner display.
Question 3
Is your app built mostly from standard system components?
Standard navigation, tab bars, split views, sheets and toolbars adapt to every pose on their own once you build with the iOS 27.1 SDK.
→ Yes: build with the iOS 27.1 SDK, remove fixed sizes and orientation checks, test every pose. No: budget for custom bars, fold-aware layouts and reserved regions.
What it takes, roughly
These are our planning estimates, not quotes. They assume a single, typical iOS app and exclude new features.
- Scene life cycle only, no layout work: typically a few days for a native or React Native app, and often little or nothing for a Flutter app with an unmodified app delegate. More if your start-up code is heavily customised with deep links and third-party SDKs.
- Adapting layout for iPhone Duo, for an app already built with standard components and resizing in mind: typically one to two weeks including testing each pose.
- Custom navigation, fixed layouts, or games and camera apps: substantially more, and worth scoping properly before committing to a date.
The cheapest order is almost always: the scene life cycle first, then layout. The first is required regardless. The second is only worth paying for once the first works.
How to brief your developer
If you have an in-house team or an agency, these questions get a useful answer quickly:
- Has the app adopted the scene-based life cycle? If not, what’s involved and what does it touch — deep links, notifications, analytics SDKs?
- Which framework and version is the app on, and does that version support iOS 27?
- Does the app lock orientation or use fixed widths anywhere?
- Are the tab bar and toolbars Apple’s standard components or custom?
- What’s the plan to test every pose in the iPhone Duo simulator, which shipped in the Xcode 27.1 beta on 18 September?
If you want someone to answer these for you, that’s exactly what our free evaluation is for. If you’d rather work through it yourself, iphoneduosupport.com has a step-by-step iPhone Duo checklist.
Framework-specific guides: React Native and Expo · Expo SDK 58 beta · Flutter.