This content was generated with the help of AI and published without prior human review. It may contain errors and is not professional advice. Report a problem: info@delionsoft.com.
Apple has published guidance for adapting iOS apps to the iPhone Duo, a foldable device with an outer display, a larger inner display and intermediate partially folded states. According to the original report, apps that assume a single fixed screen size, or that draw their own navigation chrome, are the ones most likely to look wrong. Some developers have criticised the short lead time between the announcement and the device.
What happened
The guidance covers four areas. First, build tooling: apps compiled with Xcode 27.1 can use the full screen area, while apps built with earlier versions do not extend under the status bar and camera regions. Second, layout: Apple advises against reading fixed dimensions such as UIScreen.main.bounds, and against branching on userInterfaceIdiom or interface orientation. The recommended approach is container-relative sizing with standard SwiftUI stacks, navigation and split views, or UIKit Auto Layout, driven by horizontal and vertical size class changes.
Third, navigation and toolbars. On the Duo, toolbars and navigation bars may be placed vertically along the side of the display in certain poses. Custom bars built directly on UIToolbar, UINavigationBar or UITabBar may not follow that behaviour; standard toolbar APIs attached to a navigation stack or navigation controller will.
Fourth, reserved regions. These represent the fold that divides the display, and areas where hardware occludes content — the inner front camera when active, the outer front camera always. Framework-provided views adapt automatically; custom views need to query the reserved regions APIs and lay out around them. Camera handling also changes, since opening, closing or rotating the device can change which of the three cameras is active, so apps should select by the direction a camera faces rather than by a fixed identifier.
Reaction quoted in the original report was mixed. One developer compared it to a new platform arriving with roughly a month of notice, and another wondered how many apps will bother. The iOS Dev Weekly editor made the more uncomfortable point: this kind of homework has been announced well in advance before, and most teams still did it late — UIScreen.main.bounds was, as he put it, "a bug waiting for a device".
Why it matters
For a small team with one iOS app, this is not a rewrite, but it is a real block of work that competes with your roadmap. The cost is proportional to how much custom layout and custom chrome you accumulated. Teams that stayed close to standard containers and size classes will mostly need testing time; teams with hand-rolled tab bars, hardcoded insets and screen-size branching will need refactoring before they can even evaluate the device. Camera-heavy apps — scanning, KYC, field reporting — carry the most risk, because a pose change can silently switch the active camera.
What to do
- Audit your codebase for fixed screen dimensions, idiom checks and orientation checks. That list is your backlog, and it is useful work regardless of whether you ever ship for the Duo.
- Replace custom navigation and toolbar constructions with the standard APIs where you reasonably can; the side-mounted placement is handled for you there.
- If you depend on the camera, review how you select devices and how your session behaves when the device is opened, closed or rotated.
- Decide explicitly whether Duo support is in scope this quarter. An honest "not yet" with a date beats an unplanned scramble.