iPhone Duo has launched: What now for your app?

Ahead of the event, we argued that a folding iPhone would be irrelevant to most apps, a genuine opportunity for a few, and a good reason for everyone to fix their adaptive layout debt. Much of that still holds, but it looks like relevance will come quicker than we thought. Apple has promised continuity across the fold, meaning an app that merely survives being opened may still feel broken – more on that below.

Here are the announcements that should shape your mobile roadmap, with insight from our Design, Engineering and Product experts on what they mean for your experience, your customers and your brand.

iPhone Duo: built for continuity

The headline numbers first. The Duo opens to a 7.6-inch inner display and closes to a 5.4-inch outer display, runs the A20 Pro, uses Touch ID in the side button rather than Face ID, and starts at $1,999 for 256GB. Pre-orders open on 16 October 2026, with availability from 23 October across more than 70 countries. It ships with iOS 27.1.

Now the part that matters. Apple has given both displays the same aspect ratio, and the outer screen offers around 90% of the screen area of an iPhone 18 Pro.

Together, those choices tell you a lot about Apple’s approach to folding. On most Android foldables, unfolding transforms the screen shape and forces layouts to reflow. On the Duo, it’s closer to an orientation change: controls stay in familiar positions while content scales and transitions between displays as the device opens.

That continuity is central to the experience. Early hands-on reports have focused on how seamless the opening animation feels, with Engadget describing the transition between panels as “practically seamless”. At $1,999, that polish matters: it helps justify the price in the first few seconds of using the device and sets the standard users will expect from the apps running on it.

For developers, that’s a meaningfully easier problem than many Android foldables present — but also a higher bar. Apple has made continuity the expectation, so users will notice when your app is the one that flickers, reloads or loses its place.

Designing for the Duo

The biggest visual change is controls moving to the sides. Apple’s guidance is explicit: the wider aspect ratio means toolbars, tab bars and controls should sit along the edge of the device, preserving vertical space and keeping actions within thumb’s reach. Even the Home Screen dock is vertical, with the status bar pushed into the corner.

If your design system assumes a bottom tab bar and top navigation, there’s now an exception, and its one Apple is actively encouraging teams to embrace.

But don’t over-engineer it. Apple’s guidance is to think in two size classes, compact and regular, rather than designing bespoke layouts for every pose. Functionality and hierarchy should remain consistent, and users shouldn’t need to fold or unfold the device to access a feature. Tabletop layouts (media above, controls below) are an opportunity, not somewhere to hide functionality.

Apple published a six-video “Get ready for iPhone Duo” series on launch day, which tells you something about how hard it intends to push this. The practical takeaways:

• The aspect ratio. Stretch a portrait-first layout across its width and it will appear warped. Flowing, adaptive layouts are no longer a ‘mature option’, instead they have to become the default.
  
• Safe areas are now critical in both axes. The guidelines that tell you where to put your content to avoid it being obscured. We’re used to reasoning about them vertically. On the Duo they really matter horizontally.
  
• The promos lean heavily on landscape, and they showcased apps adapting to the device being partially folded and held like a book, with content moving away from the crease.
  
• A new vertical toolbar down the right-hand side. iOS 27 moves the controls to the side and re-adjusts them as the fold position changes. Anything that’s been placed near that edge — FABs, primary CTAs, swipe affordances — is a collision candidate.
  
• You can’t test this today. Tooling will be available with Xcode 27.1, expected to be released late September ahead of the iPhone Duo going on presale.

Does your app need to adapt?

Before the event, our advice was simple: most brands should at least test how their app performs on a foldable, even if a $1,999, low-volume device doesn’t justify major investment in year one.

Two things now raise the stakes. First, Apple’s focus on continuity means “doesn’t look broken” isn’t enough. An app that survives the fold but loses scroll position will still feel broken.

Second, side-mounted controls aren’t just a foldable consideration. They’re a signal of where Apple sees phone UI heading as screens get wider.

The strongest first-mover cases remain retail and commerce, premium brands, media and comparison-heavy journeys, and complex enterprise tools. For those brands, Apple’s appetite to champion the device could make editorial placement a realistic prize for relatively modest investment.

For everyone else, the job is simpler: audit your app and fix the adaptive layout debt.

There’s a five-week window until 23 October, and the first move costs almost nothing: run your app in the Duo simulator and record what breaks. Most teams will find issues in three areas: layouts tied to orientation, state that doesn’t survive the fold, and controls that clash with the fold or inner camera.

The decision that follows is a three-way split, not a yes/no. Do nothing beyond fixing what’s broken if your app is a short-burst utility. Adopt the baseline (size classes, safe areas, reserved regions, resizable layouts), if you have any large-screen ambition at all, because this work pays back on iPad and landscape immediately.

That turns “should we do something about folding?” into a scoped decision with a cost attached, which is a much more useful conversation to have with a board.

From there, there are three options. Fix what’s broken if your app is a short-burst utility. Adopt the baseline — size classes, safe areas, reserved regions and resizable layouts — if you have any large-screen ambition, because that work also pays back on iPad and landscape.

Long-awaited Siri AI improvements arrive with iOS 27, using personal and onscreen context to find information and take actions across apps. It launches in beta, initially in English, with French, Japanese, Korean, Portuguese and Spanish following in October, and not initially available in the EU.

The strategic consequence matters more than the feature itself. As Rebecca Stephenson, puts it: “Customers will increasingly interact with our products without opening the app, while still expecting the experience to feel consistent with the product and brand they know.“

That’s an uncomfortable proposition for anyone measuring success through sessions and time-in-app. An assistant completing a task on your behalf sits between you and your customer — controlled and styled by Apple, without your visual identity, tone or merchandising.

Rebecca sees this as a reframing rather than a threat: “The app does not always need to be the first place customers experience a brand.” But that raises a bigger question for product roadmaps: “If the app must be installed to enable these interactions, product teams must also answer: how do we demonstrate enough value for customers to install, and keep, the app in the first place?”

That’s the crux. App Intents require the app to be installed, so the app increasingly becomes infrastructure for interactions happening outside it. It still has to earn its place on the device, even as customers may open it less. Retention arguments based purely on frequency of use become less meaningful, and value needs to be measured beyond session count.

For most brands, the case for Siri AI will depend on the maturity of their customer data strategy. It means handing some control and insight to Apple’s ecosystem. For brands earlier in their journey, that could offer a faster route to market. For those with mature data infrastructure, retaining that control and insight may outweigh the benefits beyond the simplest use cases.

One practical caveat on implementation…

Apple has confirmed that heavier, server-backed Apple Intelligence features will carry daily usage limits, with expanded access available for a fee. That includes developer apps using Apple Foundation Models in Private Cloud Compute. If you’re building on Apple’s models rather than your own backend, you’re introducing a dependency you don’t control — including edge cases like what happens when a user hits their limit.

What brands need to act on

Audit which of your core actions are exposed as App Intents. That’s now a discovery surface, not a nice-to-have. Then answer the harder question: why should a customer keep your app installed if Siri can do the top three things they use it for?

If that’s difficult to answer, you’ve found a roadmap problem — and it’s better to find it now than in a retention review eighteen months from now.

Easy to miss in the hardware noise: Apple confirmed iOS 27 releases on Monday 14 September.

As we covered recently, that’s when new App Store creative assets go live, bringing image and video formats to product page headers and search results alongside screenshots. Until now, listing visuals had to show the product in use. From Monday, the App Store becomes a brand surface as well as a conversion surface.

The timing alongside the Duo is telling. Apple has launched a device built around visual expansiveness while giving brands more room to tell their story in the store. Both point in the same direction: brand quality is becoming increasingly visible in the App Store.

The immediate priority is execution. Assets need approval, restrictions are tighter than typical marketing creative, and product page optimisation means you can test variants against real traffic. Supply nothing and Apple falls back to existing In-App Events, previews and screenshots — a default rather than an active choice.

Want to prepare? Read our guide to what’s changing and what to action now.

Worth a brief mention because it makes the wider pattern clear. Alongside the new Watches, Apple announced a redesigned Health app that uses Apple Intelligence to interpret personal metrics, with insights, personalised guidance, a readiness score and Health Age.

The significance is the standard it sets beyond health. As Rebecca notes, it “helps customers understand what their data means, making products that simply present information increasingly less valuable.”

Think banking apps showing balances, energy apps showing usage or retail apps showing order status. Presenting the data is no longer enough. The opportunity is to help customers understand what matters, why it matters and what they should do next.

This week, before iOS 27 lands on Monday
Get creative assets into review, or accept Apple’s fallback knowingly rather than by omission. Audit existing screenshots and metadata for pricing, URLs and badges that were already non-compliant. Assign an owner for the App Store listing.

This month.
Run the app in the Duo simulator and produce a written list of what breaks. Decide which of the three tiers you’re in — fix-only, baseline, or design-for-device. Audit App Intents coverage.

This quarter.
Do the adaptive-layout work, because it’s the same work whether or not the Duo matters to you. Then take the harder questions to your roadmap. Rebecca’s three are a good place to start: “What becomes possible because the device can adapt? Which outcomes should customers access without navigating the app? Where must we turn information into meaningful action?”

Different announcements, one consistent message: “start with the customer outcome, then decide where and how the experience should happen.”

The device is a niche product for another year, but the expectations it sets are not.