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 and a genuine opportunity for a specific few, and that the sensible move for everyone was to fix their adaptive layout debt regardless. Whilst some of this holds true, it looks like relevance for all mobile apps will come quicker than we first thought. Apple has promised continuity across the fold, so an app that merely survives being opened will still feel broken – more on that shortly.

Here are the announcements that should shape mobile roadmaps, and why, with input from our Design, Engineering and Product experts on what they mean for your mobile 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 with availability from 23 October, around five weeks behind the iPhone 18 Pro, across more than 70 countries. It ships with iOS 27.1 rather than 27.0.

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

Read those two facts together and you get Apple’s entire philosophical position on folding. On most Android foldables, the cover screen is narrow and the inner screen is squarish, so unfolding is a transformation, your layout has to reflow into a different shape. On the Duo, unfolding is closer to an orientation change; Apple’s own design guidance describes controls holding a consistent position while content scales, with the software transitioning between displays as the device opens.

The device feels premium. Almost every hands-on account has fixated on the animation as the device opens, with Engadget calling the transition between the two panels “practically seamless”. The outer screen appears to become a window onto the larger display beneath it, and on a phone at this price point, that polish is doing real commercial work: it’s what makes the device feel worth the money in the first ten seconds of holding it. It also sets a tone users will expect the rest of the experience to match.

This is a meaningfully easier problem than Android developers have had to solve. It’s also a higher bar, because Apple has set the expectation that opening the device feels continuous rather than jarring, and 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 that controls move to the sides. Apple’s guidance is explicit: the wider aspect ratio means toolbars, tab bars and controls should sit along the side of the device, preserving vertical space for content and keeping actions within thumb’s reach. The Home Screen dock is vertical, and the status bar has been redesigned into the corner.

If your design system assumes a bottom tab bar and a top navigation bar, that assumption now has an exception, and it’s one Apple is actively encouraging teams to adopt rather than opt out of.

Apple’s other instruction is one we’d underline for anyone tempted to over-invest: don’t design a bespoke layout for every pose. The guidance is to think in two size classes, compact and regular, and to preserve functionality and hierarchy across all of them. A feature should never require the user to open or fold the phone to reach it. Tabletop layouts (media above, controls below) are a legitimate flourish, not a place 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?

We said before the event that most brands should, at the minimum, get testing how their app might hold up on a foldable in preparation for this, even though the device costs $1,999, and is a low-volume, high-visibility product in year one.
But two things could shift the calculus. First, the continuity expectation means “doesn’t look broken” is now a lower bar than users will actually apply; an app that survives the fold but loses scroll position will feel broken even if nothing crashed. 

“If we do nothing, apps will letterbox,” explains Apadmi’s Technical Director, Tom Thackstone. “They’ll run in the centre of the unfolded screen, the same way an iPhone-only app does on an iPad, where that already reads as cheap and non-premium. It’s easier to justify that iPad users can always just use their iPhones. This will be a user’s primary device that they’ve paid £1,999 for; it will read like you don’t care.”

Second, the side-mounted control pattern isn’t a foldable-only concern; it’s an indication about where Apple thinks phone UI is heading as screens get wider.

The teams with the clearest first-mover case remain the same: retail and commerce, premium brands whose customers populate the price point demographic, media and comparison-heavy journeys, and complex enterprise tools. For those, Apple’s appetite to champion the device makes editorial placement a realistic prize for a modest investment. For everyone else, the audit is still the job.

What to do next

There’s a five-week window between now and 23 October, and the first move costs almost nothing: run your existing app in the Duo simulator and record what breaks. Most teams will find three categories of issue — layout logic tied to orientation, state that doesn’t survive the fold transition, and controls that land under the fold or the inner camera. Those findings are what turn “should we do something about folding?” into a scoped decision with a number attached, which is the conversation you want to have with a board rather than an abstract one about form factors.

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.

Design for the device only if you can pass the test Apadmi’s Product Director, Rebecca Stephenson, sets for it: “Existing apps will continue to work, but they will not automatically take advantage of the new form factor, giving product teams an opportunity to create additional customer value. We need to ask: what customer problem becomes easier, or disappears, when the device unfolds?“

That question is a useful filter precisely because most apps fail it. “The user sees more rows” is not a problem disappearing. “The user no longer has to hold two tabs in their head to compare two things” is. If you can’t articulate the second kind of answer, stop at the baseline and spend the money elsewhere.

A new era for App Store creative

Easy to miss in the hardware noise: Apple confirmed iOS 27 releases on Monday 14 September. That’s four days away.

As we covered recently, that release is when App Store creative assets go live; the new image and video formats that appear in your product page header and in search results, alongside your existing screenshots. Until now everything visual on your listing had to show the product in use. From Monday, the store becomes a brand surface as well as a conversion surface.

The connection to the Duo is not incidental. Apple has just launched a device whose entire pitch is visual expansiveness, on the same platform release that gives brands their first proper storytelling canvas in the store. Both point the same direction: the App Store is becoming a place where brand quality is legible.

The practical implication is a deadline rather than a strategy. Assets need review approval before they appear, the constraints are stricter than standard marketing instincts allow (no pricing, no discounts, 4+ rating on everything, video that works muted), and product page optimisation lets you test variants against live traffic rather than argue internally. Teams that supply nothing will get Apple’s fallback; In-App Events, previews and screenshots, which is a default, rather than an active decision.

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

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

The strategic consequence is the part worth sitting with. 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 is a genuinely uncomfortable proposition for anyone whose success metrics are built on sessions and time-in-app. An assistant that can complete a task on your behalf is, from a brand perspective, an intermediary standing between you and your customer, one you don’t control, styled entirely by Apple, with none of your visual identity, tone or merchandising.

Rebecca’s reading is that this is a reframing rather than a threat: “the app does not always need to be the first place customers experience a brand.” Which is right, and also raises the question that should be on product roadmaps this quarter: “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?”

This is the crux, and it’s a harder problem than it first appears. App Intents only work if the app is installed, so the app becomes infrastructure for interactions that happen outside it, earning its place on the home screen while being used less and less directly. Retention arguments built on frequency of opening stop working, and the value has to be legible somewhere other than the session count.

For most brands, incorporating Siri AI likely hinges where you are in your customer data journey. It will require you to hand over control and insight to Apple’s black box. For those just starting out it will mean faster time to market, but for those with a mature infrastructure and estate, the value of retaining this data will be enough reason to avoid it for all but the simplest of features.

One practical caveat on implementation…

Apple has confirmed that the heavier weight server-backed Apple Intelligence features carry daily usage limits, with expanded access coming for a fee and the metered list explicitly includes developer apps using Apple Foundation Models in Private Cloud Compute. If you’re building on Apple’s models rather than your own backend, that’s a rationed dependency out of your control Introducing edge cases like “what happens when a user hits that cap?”.

What brands need to act on

Audit which of your core actions are exposed as App Intents, because that’s now a discovery surface, not a nice-to-have. Then do the harder piece: write down, in a sentence, why a customer keeps your app installed if the assistant can do the top three things they use it for. If that sentence is difficult to write, that’s the roadmap finding, and it’s better surfaced now than in a retention review in eighteen months.

A bonus announcement: Health

Worth a brief mention because it makes the pattern obvious. Alongside the new Watches, Apple announced a redesigned Health app that uses Apple Intelligence to adapt to a user’s own metrics; an Insights tab, personalised guidance, a readiness score and a calculated Health Age.

The significance in this is the standard being set, and it isn’t confined to health. As Rebecca notes, it “helps customers understand what their data means, making products that simply present information increasingly less valuable.”

Read that against your own sector. Banking apps that show a balance, energy apps that show a usage graph, telco apps that show data consumed, or retail apps that show an order status. Every one of those presents information and leaves the interpretation to the customer, and every one of them now sits on a phone where the system apps have moved on. Her wider point applies across every journey: teams need to help customers understand “what matters, what is useful and what trusted action they should take 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.