Apple's iPhone Duo brings foldable screens to iOS and an AI-built hinge

Apple has taken the wraps off the iPhone Duo, its first foldable iPhone, announced at the company's "Surprise and Shine" event on Wednesday, September 9. According to a developer write-up on dev.to, the device carries a 5.4-inch display on the outside and a 7.6-inch panel on the inside, and ships running iOS 27.x.

A hinge matched by algorithms

Foldable phones have historically degraded faster than conventional handsets, since the folding mechanism endures roughly twice the wear, as TechCrunch notes. Apple's answer, per TechCrunch's reporting, is a critical hinge designed and manufactured with the help of AI and 3D printing.

Apple's chief hardware officer Johny Srouji described the process at the event. During manufacturing, AI algorithms pair each individual hinge with the housing that best matches it, ensuring alignment; a confocal laser progressively scans the surface topology of every unit; and a 3D printer then lays down up to 25 micro layers of a custom photopolymer to eliminate what Srouji described as residual waviness. He also cited a custom nano-texture finish that reduces glare and reflections, plus a multi-layer lamination strategy intended to boost durability. Whether those protections are enough to keep the Duo in peak condition over years of folding remains to be seen, TechCrunch adds.

Doing nothing still works, mostly

The dev.to write-up walks through what happens if developers ship no update at all: the app runs, does not crash, and is not removed from the store. What changes is how much screen the app gets, and that depends on which SDK it was last built against. Apps built with an older SDK are letterboxed on the inner display, keeping their old aspect ratio with black bars on either side. Apps rebuilt with the iOS 27 SDK extend left of the status bar while avoiding the camera area. Apps built with the iOS 27.1 SDK get full edge-to-edge layout, with standard navigation and toolbar buttons stacking vertically. The cheapest meaningful fix is simply rebuilding with Xcode 27.1.

Four poses, not two orientations

The deeper shift is conceptual. The dev.to guide identifies four poses apps must now handle: closed in portrait, which behaves like an ordinary iPhone; closed in landscape; open in a tall, near-square vertical stance; and open horizontally. Add intermediate states — partially folded like a book, or propped in a tent on a table — and layouts have to survive live transitions between all of them.

Critically, the inner display ignores an app's declared supported orientations. Code that branches on UIDevice.orientation or supportedInterfaceOrientations becomes unreliable, so the recommendation is to branch on size classes instead. The outer screen reports the same size classes as any current iPhone, while the inner screen reports regular width and regular height — effectively handing apps iPad-class space for sidebars and two-column layouts.

The specific code changes

Several long-standing assumptions break at once, according to the dev.to post:

• UIScreen.main is ambiguous on a two-display device, and Apple has signalled it is heading for deprecation. Developers should read displayScale from the trait collection or fetch the screen from the window scene, and prefer scene bounds or the SwiftUI environment for layout sizes.
• Safe areas are no longer symmetric. With the camera on one side and Split View giving an app half the display, left and right insets can differ, so each edge must be handled independently. Interactive foreground content belongs inside the safe area; background artwork can bleed past it.
• The Duo introduces reserved regions: physical features that carve into the display. A division region is the fold itself — active only while the device is folded, zero width when flat — while an occlusion region covers the under-display FaceTime camera. Developers can query these, including inactive ones, to make structural choices that stay stable as the device opens and closes, such as keeping grid columns off the fold. Standard containers like NavigationStack, TabView, List and ScrollView already adapt automatically, and the system repositions alerts, menus and popovers around reserved regions. Continuously scrolling content such as articles should not jump to dodge the fold; displacement is meant for discrete elements like buttons and control clusters.
• iOS 27.1 adds ArrangementView, a container that sits between navigation and content, takes a primary and a secondary view, and decides placement based on size classes, aspect ratio and any active divisions. Its split style divides the available bounds horizontally when the device is wider than tall and vertically otherwise.

Why it matters

The iPhone's single rectangular screen has been a safe assumption since 2007, and a large amount of iOS code quietly depends on it. The Duo makes that dependency visible: apps that hardcode screen sizes, assume mirrored safe-area insets or branch on orientation will look or behave wrong on the inner display, while apps already doing adaptive iPad-style layout need mostly minor adjustments. There is also a manufacturing angle — Apple deploying AI for per-unit precision matching and 3D-printed micro layers is a concrete example of machine learning moving into physical production rather than just software features. For most teams the practical path is short: rebuild with the newest SDK, audit uses of UIScreen.main and orientation checks, and treat the inner screen as the iPad the app never officially supported.