Apple's first foldable iPhone arrives soon. According to Apple's developer news, iPhone Duo becomes available on October 23 running iOS 27.1, and Xcode 27.1 adds development support with updated SDKs and a simulator for the device's poses and orientations. The device has an outer display, a larger inner display, and partially folded states, which means your app can be resized, rotated, and reshaped while someone is using it. For consumer apps this is a design opportunity. For B2B apps, such as field service, inspections, sales tools, and logistics, it is a reliability question. One developer quoted by InfoQ described it as “a whole new platform dropping with a month's lead time.” The teams that will be fine are the ones that followed Apple's layout guidance all along.
Build with Xcode 27.1 to use the whole screen
InfoQ reports that apps built with earlier Xcode versions do not extend beneath the status bar and camera areas on iPhone Duo. In other words, an old build will run, but letterboxed and less polished than competitors who rebuilt. Plan a release built with Xcode 27.1 once it is available, and budget time for the testing below. Enterprise customers who buy devices for field teams will notice which vendors look native on day one.
Stop branching on idiom and orientation
Apple's guidance, as summarized by InfoQ, is direct: avoid fixed iPhone screen dimensions such as UIScreen.main.bounds , size views relative to their containers, and do not base layout decisions on userInterfaceIdiom or UIInterfaceOrientation . Use size classes instead, observing horizontalSizeClass and verticalSizeClass changes. B2B codebases often contain years of “if iPad, show the split view” logic. On iPhone Duo, that logic picks the wrong layout when the device unfolds.
Use standard navigation and toolbars
In some poses, toolbars and navigation bars can appear vertically along the side of the display. Apps that build custom navigation or toolbars with UIToolbar , UINavigationBar , or UITabBar may not adapt. Apple recommends the standard APIs: the toolbar(content:) modifier on a NavigationStack or NavigationSplitView in SwiftUI, and toolbar items on view controllers inside a navigation controller in UIKit. If your design system wraps a custom bottom bar everywhere, this is the moment to revisit it.
// Adapt to space, not to device type
struct JobsRootView: View {
@Environment(\.horizontalSizeClass) private var hSize
var body: some View {
if hSize == .regular {
NavigationSplitView { JobListView() } detail: { JobDetailView() }
} else {
NavigationStack { JobListView() }
}
}
}Respect the fold and the cameras
iPhone Duo introduces reserved regions: the fold that divides the display into areas, and places where hardware such as the camera occludes content. Framework-provided views adjust automatically, but custom views need to query reserved regions, using reservedRegions(kind:options:layoutDirectionBehavior:) in SwiftUI or reservedRegions(kind:options:) in UIKit. Signature pads, barcode scanning overlays, dense data tables, and custom canvases are the B2B components most likely to land a critical control on the fold or behind a camera.
Revisit camera-heavy workflows
iPhone Duo can capture from the outer display camera, the inner display camera, and the rear camera, and opening, closing, or rotating the device can change which camera is active. Inspection, proof-of-delivery, and document-capture flows should select cameras by the direction they face rather than assuming a fixed device layout, and handle camera changes mid-capture without losing the photo or the form state.
Cross-platform teams are not exempt
If your app uses React Native or Flutter, the same principles apply: layouts must respond to available space rather than device type, and native modules for cameras, scanning, or custom navigation need checking. Track your framework's releases for iPhone Duo support and test on the simulator once your toolchain supports Xcode 27.1. Do not assume a cross-platform layer has handled reserved regions for custom components.
If your customers manage devices through MDM, check with their IT teams whether they plan to buy iPhone Duo for field staff. Their purchasing timeline tells you how urgent this work really is for your accounts, and it gives your success team a reason to start a useful conversation.
Preserve state through every fold
Folding and unfolding changes the available space while a user is mid-task. A technician halfway through a checklist, a driver capturing a signature, or a sales rep editing an order should not lose input when the device changes pose. Keep form and workflow state in models that survive view rebuilds, avoid tying important state to specific view instances, and test interruptions deliberately: unfold during a form, fold during an upload, rotate during a scan.
Make the larger display worth opening
Beyond not breaking, think about what the inner display enables for your users. A list-detail layout for jobs or orders, a map beside a stop list, or a document beside its approval form can save field workers real time. Pick one high-value workflow and design a regular-width layout for it, rather than stretching the phone layout across the whole screen. That is the version customers will show their peers.
Plan the release
Write a short readiness plan: audit screens for fixed sizes and idiom checks, migrate custom bars, fix reserved-region conflicts in custom controls, test camera flows, then ship a build made with Xcode 27.1. Tell customers which app version supports iPhone Duo properly so IT teams buying the device know what to deploy.
Founder takeaway
iPhone Duo rewards apps that already follow Apple's adaptive layout guidance and exposes those that do not. Rebuild with Xcode 27.1, replace idiom and orientation checks with size classes, move to standard navigation and toolbars, keep custom controls out of reserved regions, harden camera flows, and test each pose. For B2B apps, looking native on a new device is part of being the reliable vendor.