The iPhone Duo Is Coming. Does Your Business App Need an Update?

Apple’s first foldable iPhone arrives on 23 October 2026. If your business has an iPhone app, that creates an obvious question: will it still work when somebody opens it on an iPhone Duo?

The reassuring answer is yes. Apple says existing apps will run on the new device even if they have not been rebuilt with the latest software development kit. The more useful question is whether the app will still feel deliberate as it moves between a compact outer display, a much larger inner display, a partially folded position and side-by-side multitasking.

Those are different levels of readiness. An app can launch successfully while still wasting space, hiding controls, breaking a form or making an important customer journey awkward.

Here is what Apple has announced, what should happen automatically and what businesses should test before the iPhone Duo reaches customers.

What Apple has announced

Apple unveiled the iPhone Duo on 9 September 2026. The device can be used closed, opened into a wider inner display, rotated or placed on a surface while partially folded. Its software can move content between displays and resize an app as the physical position changes.

The official Apple announcement also introduces Split View on iPhone. Two apps can run beside each other, and two windows of the same app can be opened together. Apple demonstrates this with use cases such as comparing information in two Safari windows, keeping a conversation visible beside another task and showing shared content alongside meeting participants.

On 16 September, Apple confirmed that the device will ship with iOS 27.1 on 23 October. The company says Xcode 27.1 will add an iPhone Duo simulator with controls for its new poses and orientations, with a beta due later in September. That simulator gives development teams a way to test before buying the hardware. Apple’s developer release notice records the current timetable.

This is a meaningful interface change, but it is not a new operating system or an entirely separate app platform. The iPhone Duo still runs iPhone apps. Apple has extended the layout and navigation tools developers already use so those apps can respond to a wider range of available space.

Will an existing app still work?

Apple’s compatibility approach is deliberately gradual. An app built with an older iOS software development kit should continue to run. When the phone is open, that app uses a familiar iPhone-sized area rather than automatically stretching an interface that was never designed for the larger canvas.

An app built with the iOS 27 SDK can use more of the inner display. Building with the iOS 27.1 SDK enables the full-screen experience, including standard navigation and toolbar controls that can move into the new vertical control area.

Apple explains these stages in its Prepare your app for iPhone Duo developer session. The distinction matters: compatibility does not require every business to commission an emergency rebuild, but taking full advantage of the hardware requires the app to be compiled, reviewed and tested with the new tools.

The launch test is not simply “does the app open?” It is “can a customer still complete the task they came to do in every useful display size?”

An app that uses standard interface components and flexible layouts may adapt with relatively little work. One built around fixed screen measurements, custom navigation or assumptions about portrait orientation deserves closer inspection.

Why a folding screen changes the layout

Most phone interfaces have historically moved between a short list of predictable portrait and landscape sizes. A foldable phone adds continuous change. The app may be narrow on the outer display, wide when fully open, half-width in Split View or shallow while another window or picture-in-picture video occupies part of the screen.

Apple advises developers to respond to the space the app actually receives rather than identify the device and choose a hard-coded layout. On the outer display, an app generally has a compact horizontal size. On the inner display, it has enough room for patterns such as sidebars and multi-column navigation.

The fold itself also affects interaction. Apple moves standard controls away from the curved centre region when necessary and can position navigation controls vertically along an outer edge. Safe-area information tells an app where content and controls can sit without colliding with system elements, rounded corners or the fold.

Apple’s design guidance for iPhone Duo says developers do not need a custom layout for every physical pose. The recommended approach is a freely resizable interface using compact and regular size classes, layout margins, safe areas and standard components.

What a business app should test

The highest-value checks follow the customer’s journey rather than the app’s menu. A business does not need every screen to make spectacular use of the inner display on day one. It does need the important work to remain clear and reliable.

A practical compatibility review should cover:

• Opening, closing and rotating: content should resize without disappearing, overlapping or returning the user to the beginning of a task.
• Navigation: tabs, toolbars, back buttons and custom menus should remain reachable when the available width changes or controls move to an edge.
• Forms and keyboards: sign-in, registration, checkout and data-entry screens should remain usable when the keyboard reduces the visible area.
• Fold and safe areas: important buttons should not sit across the centre curve, under a status element or too close to a rounded corner.
• Split View: the app should continue working at half width and should preserve its state when another app appears beside it.
• Multiple windows: where an app supports more than one scene, records and edits should stay consistent across both windows.
• Media and camera: previews, players, capture controls and picture-in-picture should cope with changing proportions and partially folded positions.
• Accessibility: larger text, screen-reader order, focus, contrast and touch targets should be checked at compact and expanded sizes.
• Performance: a larger canvas can reveal oversized images, expensive lists or layouts that perform too much work whenever their dimensions change.

The test should end with the real outcome. A successful checkout means the payment is recorded. A submitted enquiry must reach the intended system. A saved job, inspection or customer record must still be present after the phone changes display. A screenshot that looks acceptable is useful evidence, but it is not an end-to-end test.

What about React Native and other cross-platform apps?

A cross-platform framework does not remove the need to test platform changes. React Native, Flutter and similar tools translate shared application code into native behaviour, but each app still depends on a particular framework version, native modules and operating-system integrations.

For a React Native app, the first job is to confirm that its current toolchain can build against the supported iOS SDK and run in the new simulator. The team should then exercise responsive components, navigation, modals, keyboard handling, camera or media packages and any native code that reads screen dimensions or orientation.

Code that calculates one global screen width is particularly worth reviewing on a device with two displays and resizable windows. Apple now recommends using the size of the current scene and layout environment rather than assuming there is one unambiguous main screen.

That does not mean a React Native app needs to be replaced with a fully native one. It means the normal maintenance chain matters: supported framework versions, compatible dependencies, a repeatable build and tests focused on business-critical journeys. If the framework or an important package has not yet adopted the new SDK, the team can document the limitation and plan the update rather than guessing.

Does a business website need an iPhone Duo update?

A website is not installed against an iOS SDK, so the native-app upgrade path does not apply. Safari will still load ordinary websites. A responsive site built around flexible widths and established web standards should adapt to the available browser window.

The iPhone Duo nevertheless creates useful test cases. Apple says Safari can show two windows side by side, so the same website may be viewed on the outer display, across the inner display or in a narrower split window. Navigation, cookie controls, forms, comparison tables, embedded booking widgets and fixed-position buttons should remain usable across those widths.

Sites most likely to struggle are those that equate “mobile” with one fixed portrait width. Typical warning signs include rigid pixel dimensions, full-screen overlays that cannot scroll, controls pinned to the viewport without safe spacing, or layouts selected from the device name rather than the space available.

For most organisations, this is a focused responsive-design check rather than a new website project. The same fixes usually improve the experience on tablets, desktop windows, landscape phones and accessibility zoom as well.

What should happen before 23 October?

Start by establishing ownership. Confirm who can build the app, who controls its App Store account, where the source code lives and whether the current project still produces a release. Discovering that an old signing certificate, abandoned dependency or unavailable developer blocks the build is more serious than a layout issue.

When Xcode 27.1 becomes available, run the current app in the iPhone Duo simulator before changing anything. Record the important customer journeys in the closed, open, rotated and partially folded positions, then repeat them in Split View. This establishes what already works and stops the project growing into an unnecessary redesign.

Classify each finding:

• Release blocker: the app crashes, hides an essential action, corrupts state or prevents a customer completing a critical task.
• Compatibility improvement: the app works, but a layout, control or flow becomes confusing at a particular size.
• Enhancement: the larger display creates an opportunity for a sidebar, richer dashboard, comparison view or better multitasking experience.

Fix blockers first, then the improvements that affect frequent journeys. Enhancements should earn their place through customer value. A larger display can support a genuinely better workflow, but novelty alone is not a product requirement.

Allow time for internal review, accessibility checks, beta testing and App Store submission. If the app is business-critical, monitor crashes and customer support after the update rather than treating approval as the end of the work.

Do not rebuild an app just because the phone folds

The most important decision may be deciding how little needs to change. Apple has designed the compatibility path so older apps continue to run, and its recommended layout techniques are extensions of long-standing iPhone and iPad practice.

A healthy app with adaptive layouts may need only a new build, a small number of fixes and proper testing. An older app may expose deeper problems because its dependencies, build process and interface assumptions have gone untouched for years. In that case, the iPhone Duo is the event that revealed the maintenance gap; it did not create the whole problem.

Businesses should ask for evidence before approving a large project. Which journey fails? In which pose or window size? Does the issue affect the October launch, or is it an optional improvement? Can the change be made safely in the existing architecture? A short compatibility audit should answer those questions before anybody proposes a rewrite.

The useful takeaway

The iPhone Duo expands the range of shapes an iPhone app must handle, but it does not invalidate every app built before October. Existing software should continue to run. The immediate job is to test the journeys customers depend on, remove brittle screen assumptions and adopt the iOS 27.1 tools where the full display adds value.

For websites, the lesson is even broader: flexible layouts should respond to the window they receive, whether that window belongs to a foldable phone, a tablet, a split desktop screen or a user who needs larger text.

Apple documentation and release status checked on 17 September 2026. Xcode 27.1 availability may change after publication.

If your organisation needs an app compatibility review, a focused update or help taking ownership of an ageing codebase, explore Pixolite’s app development service and maintenance and support, or book a direct call with Damian.