Announced 9 September 2026
Your iOS app on iPhone Duo: what breaks, and how to fix it
The inner display is 626 × 890 points at an aspect ratio of 1.42 — against 2.17 on iPhone 18 Pro. Layout code that was correct on every previous iPhone is not correct here.
Sourced from Apple’s six iPhone Duo Tech Talks. No sign-up. Progress saves in your browser.
First, the good news
Your app will not crash. Apple defined three tiers of behaviour, and the one you get depends entirely on the SDK you build against.
| Built against | Inner display behaviour |
|---|---|
| Not the iOS 27 SDK | Familiar size and aspect ratio. Works, but does not use the display. |
| iOS 27 SDK | Extends left of the status bar area on the inner display. |
| iOS 27.1 SDK | Reaches the screen edge. Bar buttons lay out vertically under the status bar. |
So this is a competitive problem, not a support ticket. The risk is looking dated beside an app that fills a 7.6-inch display — and the trap is that rebuilding against 27.1 without doing the layout work behind it can look worse than not rebuilding at all.
The four assumptions that break
8 of the 25 checks are blockers. Four of them account for most of what users actually see.
1.“The screen is about 400 points wide”
The inner display is 626. Fixed frame widths are off by more than 200 points.
How to fix it →2.“Portrait lock means portrait”
The inner display does not honor supported interface orientations. Your lock is ignored.
How to fix it →3.“Left and right insets match”
Safe areas are asymmetric now. Doubling one side puts your content off-centre.
How to fix it →4.“Phone idiom means small screen”
iPhone Duo reports the phone idiom with a regular-width display. Your iPad layout never appears.
How to fix it →
Pick your stack
Apple ships adaptive APIs for SwiftUI and UIKit. Every cross-platform framework is, so far, on its own.
Apple ships the adaptive APIs directly. Most SwiftUI apps need configuration and layout review rather than rewriting.
Every SwiftUI capability has a UIKit counterpart. Apps built on standard containers adapt with little work.
No first-party support. Flexbox layout adapts, but cached dimensions, orientation locking and safe-area assumptions all need attention.
The abstraction already exists from Android foldables. Whether the iOS embedder populates it for iPhone Duo is unconfirmed.
No first-party support. Screen.safeArea works, but mid-session resolution changes and fold-driven lifecycle events need explicit handling.
No framework-specific support needed for most cases. CSS handles the adaptation; asymmetric safe-area insets are the main trap.
Deep dives
- Capacitor, Cordova and web views on iPhone Duo
Hybrid iOS apps adapt best to the foldable iPhone, because CSS was built for variable viewports. An analysis of the few things that still break.
- Flutter on iPhone Duo: the right abstraction, possibly unwired
Flutter already has a foldable API from Android — MediaQuery.displayFeatures. An analysis of whether it reaches iPhone Duo, and what to do either way.
- React Native on iPhone Duo: what breaks and what works
Meta has shipped no iPhone Duo support. Which React Native patterns break on the foldable display, which survive, and where a native module becomes unavoidable.
- SwiftUI on iPhone Duo: adaptive layout and transitions
A walkthrough of the SwiftUI APIs for iPhone Duo — ArrangementView, ReservedRegion, size classes and vertical toolbars — in the order that actually works.
Need it done rather than explained?
We add iPhone Duo and adaptive-layout support to existing iOS apps — native and cross-platform. Run the checklist, copy the audit report it generates, and send it to us.