top of page
Search

Your Line-of-Business iOS Apps Are Not Ready for the iPhone Duo

Writer: MacSmithAI
MacSmithAI
3 days ago
6 min read

Apple's foldable reaches stores on Friday 23 October. Your fleet will see a handful of them — I argued last time that the Duo is a pilot device and not a fleet standard, and nothing since has changed my mind. But "a handful" is not "none," and the people who get one first are usually the people whose complaints travel fastest.


Here is the part that has nothing to do with the hinge: every iPhone-only app your company runs has an assumption baked into it that the iPhone Duo breaks. Apple published its guidance on this the day of the announcement — a developer Tech Talk called Prepare your app for iPhone Duo — and it is unusually specific about what goes wrong and why.


You do not need to write Swift to act on it. You need to know what to ask, and you have about six weeks in which the answer is still cheap.


The assumption that breaks

Every iPhone ever shipped has been compact width. That is the size class iOS reports to an app, and it is the signal a decade of iPhone code has used to decide "show me the phone layout." iPads report regular width, which is why they get sidebars and split views and phones do not.


The Duo's inner display reports regular in both dimensions. Apple's wording is that it is "regular in both dimensions, leaving room for sidebars." It is, as far as your app's layout logic is concerned, an iPad that happens to be a phone.


That is the whole problem in one sentence. Everything downstream follows from it.


Apple's guidance is blunt about the three habits that break. Use size classes rather than interface orientation. Do not assume display size or capability from the user interface idiom — the check that reads userInterfaceIdiom == .phone and concludes "small screen, portrait, one column" is now wrong on a shipping iPhone. And stop reaching for the main screen, because there are two of them:


// Apple's guidance: don't reference the main screen on a two-display device.
// Get it from the window scene instead.
let screen = window?.windowScene?.screen

There is one more that catches line-of-business software specifically: the inner display does not honor supported interface orientations. Plenty of internal apps are pinned to portrait, often deliberately, sometimes because rotating them looks broken. On the Duo's inner display that pin does not hold.


The good news, and it is real: NavigationSplitView, UISplitViewController, TabView and UITabBarController are, in Apple's description, "fully adaptive across every pose" — columns collapse when the device is closed and tile or overlay when it is open. An app built on standard navigation components largely lands on its feet without anyone touching it. An app with hand-rolled layout is where the trouble lives.


That distinction — standard components versus hand-rolled — is the single most useful thing you can learn about each of your apps, and most vendors can answer it in one email.


Three tiers, depending on what it was last built with

Built with

On the inner display

Pre-iOS 27 SDK

Runs at a familiar iPhone size and aspect ratio, using only the space left of the status bar

iOS 27 SDK

Extends left of the status bar area on the inner display

iOS 27.1 SDK

Reaches the screen edge, and lays standard navigation and toolbar buttons out vertically


The first row is the one to internalise. Apple's exact words: "Your app runs on iPhone Duo even without recompiling, but screen usage improves with each SDK."


Nothing crashes. Nothing is unavailable. This is not an outage and you should not sell it upstairs as one. It is a quality problem — the executive holding a $1,999 phone opens your expense-report app and finds it sitting in a letterbox in the middle of a 7.6-inch display, looking exactly as neglected as it is. That is the expectation to set with leadership now, in September, rather than defending it in late October.


The five questions to send your app owners

For every iOS app your organisation depends on — in-house or vendor — this is the whole list:


  1. Does its layout branch on UIScreen.main, userInterfaceIdiom, or interface orientation? Those are the three Apple named specifically. Any "yes" is a flag.

  2. Is it locked to portrait? The inner display will not honor that.

  3. Is it built on standard navigation components, or is the layout hand-rolled? Standard means it probably adapts for free.

  4. What SDK is the current shipping build compiled against, and what is the plan for the iOS 27.1 SDK? This determines which row of the table above you land in.

  5. Has anyone opened it in the Duo simulator and folded it?


Question five is the one that turns this from a conversation into a fact, and it is free.


You can test this without buying one

Xcode 27.1 includes an iPhone Duo simulator in Device Hub, with on-screen controls to — again Apple's words — "open, close, rotate, and fold the device to check your layout in every pose." Nobody needs a $1,999 folding phone to find out whether an app embarrasses you on it. An afternoon and a Mac is the entire cost.


Apple also renamed its modernization tooling: the app modernization skill is now App Resizability in Xcode 27.1, with SwiftUI and iPhone Duo support.


One honest caveat on timing. Writing on 10 September 2026, developer Blake Crosley reported that the Xcode 27.1 beta and Apple's written Preparing your app for iPhone Duo guide were still marked "coming later this month" or "coming soon" — a roughly six-week gap before devices ship. I have not independently confirmed what is downloadable as you read this. If a vendor tells you the tooling is not available yet, that may simply be true. Treat it as a reason to get a committed date out of them, not a reason to let the thread drop.


What nobody can tell you yet

Being straight about the gaps is more useful than filling them, so, as of 10 September 2026:


  • There is no Duo-specific MDM or Apple Business Manager guidance. Not from Apple, not from any MDM vendor. Nothing on supervision, enrollment, restrictions or declarative management that is specific to a folding device. Anyone telling you otherwise this week is extrapolating.

  • Apple's own eSIM deployment guide has not been updated to list the Duo. Its supported-device list still stops at iPhone 17 and iPhone Air. The Duo is eSIM-only worldwide — Apple's product page says so plainly — but the deployment documentation has not caught up.

  • The inner display's exact geometry is not an Apple figure. The widely repeated 1.42 aspect ratio and 626×890 points come from a single developer write-up, not from Apple. The direction is right and it matters — a 1.42 ratio letterboxes 16:9 video badly — but do not put that number in a requirements document.


What Apple has confirmed is worth planning around: "Split View allows users to open two apps side by side on iPhone for the first time," including two windows of the same app. Your app may find itself in half the width of an unfamiliar display, beside something else, in a state it has never occupied on a phone in its life.


The practical takeaway

Do not open an app remediation project. The Duo is a pilot device, the failure mode is cosmetic, and a funded workstream aimed at a device you will own six of is the wrong use of a quarter.


Do triage instead, this week, and keep it to an afternoon. Rank your iOS apps on two axes: will a Duo-carrying executive actually open it, and is its layout hand-rolled. Anything scoring high on both goes on a short list. Send the five questions to the owners of that short list, and ask specifically for question five — someone folding it in the simulator and sending you a screenshot. Three apps checked before 23 October is a good outcome. Everything else can wait for a complaint that may never arrive.


The reason to do it now is not that the Duo is important. It is that in October this costs you an email, and in November it costs you a meeting with someone holding a two-thousand-dollar phone and a bad first impression of software you own.



Comments

bottom of page