Getting Your App Ready for iPhone Duo: What Apple's Engineers Told Developers

iPhone Duo goes on sale October 23 on iOS 27.1. On September 16, Apple's UI frameworks engineers, designers, and the TV, Maps and Find My teams answered developer questions in the iPhone Duo Group Lab. Here are the practical answers.

Short version: if your app already resizes well on iPad, you're most of the way there. If not, users will see black bars on day one.

Timeline

• Now: Xcode 27.2 betas are out (but Duo ships on 27.1). Figma and Sketch design kits are on the Apple Developer site.
• Later in September: Xcode 27.1 adds the iPhone Duo SDK and DeviceHub with every pose and orientation. Its "modernize your app" coding skill now supports SwiftUI and knows about Duo. Maps used it to migrate off UIScreen.main.
• October 23: iPhone Duo in stores.

What Your App Looks Like, by SDK

Built with	Outer (cover) display	Inner display
Xcode 26	iPhone mini ratio, letterboxed	Centered iPhone-shaped window with black bars, no pose support
Xcode 27 + resizability	Adapts	Nearly full screen, black bar under the status bar
Xcode 27.1	Adapts	Full screen

• No opt-out. Link against iOS 27 and resizability is on. If the full job takes months, ship basic resizability first.
• Letterboxing stands out. Early buyers gravitate to ready apps, and black bars on a new, expensive phone are classic 1-star review material.

One Resizable Window, Not "Phone + iPad"

Unfolding should feel like dragging your window wider. Tasks often start closed and finish open, so state and navigation must carry over.

• Lay out by size class and width, not orientation. The inner display is regular/regular.
• Supported orientations are ignored on the inner display. Portrait-only apps still rotate and resize there (they're honored on the outer display).
• Need portrait vs landscape layouts anyway? Orientation is available as a trait or SwiftUI environment value, but Apple's own apps (App Store, Health) mostly decide by width.
• Ergonomics: closed is one-handed; open landscape keeps controls where they were when closed; open portrait is two-handed.

Use System Components for the Vertical Bar

The panel's main message. On Duo, bars move into a vertical bar on the camera side.

• UITabBarController and SwiftUI TabView move there automatically.
• A custom UITabBar added as a subview doesn't. Fully custom bars need low-level APIs and you'll rebuild a lot of system behavior.
• The bar can be left or right, so safe areas and content insets are asymmetric. Never assume left equals right.
• For columns, use NavigationSplitView / UISplitViewController. Three-column iPad layouts show two columns plus an overlay; in "book" pose they split 50/50 automatically.

Maps and Find My spent most of their Duo effort replacing hand-built toolbars and sheets with system controllers. After that, the Duo layout came almost for free.

Poses: Support the Basics

Closed, flat, laptop, book, face-down, folio case: you don't need a layout for each. Apple made that mistake internally. Add a pose-specific experience only when it's truly useful (e.g. player controls moving to the bottom half on a table), and animate the transition, not just the end state.

Use the highest-level API that fits:

1. System components adapt on their own
2. Arrangement views — like HStack/ZStack, but adapt around the fold
3. Reserved region — a rect for the fold area past a certain angle
4. Hinge angle — raw value, only if you really need it

A new AVPlayer-related API moves playback controls to the bottom when folded.

Two screens at once? Only camera apps with the system entitlement and an active camera session.

Accessibility

• Largest Dynamic Type — use the readable content guide so text doesn't stretch edge to edge.
• VoiceOver now works across two displays. Test it.
• Reduce Transparency adds an opaque backing behind the vertical bar. Check your layout with it on.

Testing Before the Simulator Ships

Resize your app with iPhone Mirroring and resizable iPhone in DeviceHub. The TV team said most bugs found on real Duo hardware reproduced this way.

Catchable now: broken layouts at odd aspect ratios, clipping at window corners, leftover UIScreen.main, screens ignoring size classes.

Mostly Duo-only: asymmetric safe areas and insets (portrait-locked apps usually only handled top/bottom), pose behavior and transitions.

Quick Answers from the Lab

• Full-screen apps (e.g. AR)? Supported — hide the status bar, skip the vertical bar.
• Multiple windows? Like iPad. Instances share state such as @AppStorage.
• Safari fold detection? Use existing JavaScript foldable standards; WebKit details come with the SDK.
• Biggest design mistake? Designing something special for every pose.

Launch Checklist

• Resizes cleanly on iPad and via iPhone Mirroring
• Layout driven by size class and width, not orientation
• No UIScreen.main
• Tabs use UITabBarController / TabView
• Custom bars and sheets replaced with system components where possible
• Multi-column UI uses split view controllers
• No left/right safe area assumptions
• Dynamic Type, VoiceOver, Reduce Transparency tested
• Pose-specific UI only where it adds value, with smooth transitions
• Built with Xcode 27.1 and submitted early enough to be live by October 23

Don't leave the last one late — review times have been unpredictable this year (see review queue delays in 2026). Before submitting, run through what to check before App Store review.

Watch What iPhone Duo Users Say

Early adopters are vocal. Black bars, broken unfolded layouts or controls stuck behind the vertical bar will show up in reviews, often in countries you don't check. AppStoreReview monitors your reviews across 175+ countries and alerts you instantly about 1- and 2-star reviews, so launch-week bugs get caught before they hurt your rating.

Start monitoring for free →