iPhone Duo, Week One: What the Launch Actually Exposed

Six weeks ago I wrote that the iPhone Duo wouldn't break your app — it would expose it. The device shipped last Thursday. Five days in, exposure is the right word.

I've been watching three things in the days since launch: what developers are quietly posting on Hacker News and Mastodon, what reviewers are saying beyond the obvious "the hinge feels sturdy" takes, and what my own iOS clients are hitting as they open their apps on real hardware for the first time. The patterns are clearer than I expected to see this soon.

Here's what the first week has shown.

From the developer's seat: the debt bill came in on time

The six-step audit I wrote in September was theoretical. By Friday afternoon it was a very concrete Friday-afternoon problem. Teams that had followed Apple's standard components for the last five years opened their apps on the inner display and most of it worked. Teams that had reached for a custom bottom bar, a bespoke orientation handler, or a layout tuned to 2.17:1 found the opposite — a slightly broken experience that no test suite caught because the test suite was built for one phone.

The surprises in the first week have gone in both directions.

Good surprises: NavigationSplitView, where you'd adopted it earlier, delivered the "second level of hierarchy" essentially for free. Teams that split primary and detail years ago look prescient; teams that deferred it are now doing the refactor and the Duo port in the same sprint — which is painful but produces a better app at the end of it.

Bad surprises: UIScreen.main is more deeply embedded than most teams realised. Not in app code — in third-party SDKs. Analytics libraries, ad networks, payment UIs, map providers. Every call that fetches "the screen" to decide a text size or a modal position needs the vendor to ship an update, which means your Duo polish is now gated on someone else's release train. Expect a wave of SDK bump PRs over the next month.

Adopting Apple's defaults never looked cheaper. Ignoring them never looked more expensive.

From the user's seat: the open-closed habit is forming faster than I expected

What's surprised me most is how quickly people have fallen into a rhythm with it.

Closed is the default. Users spend most of their time there — browsing, scrolling, replying. The outer display is the phone. Open is the committed action: compose a long email, triage a backlog, watch something, do real work. The gesture of opening is becoming the gesture of "I'm actually doing this now." It's an answer to a question I don't think anyone had articulated: how do you build a phone that respects the difference between consuming and producing without making the user pick one up and the other down?

The second behaviour I didn't predict is how often people set it down. Propped, half-folded, on a desk, on the kitchen counter. The Duo spends as much time off the hand as on it. Live tracking, dashboards, timers, now-playing — anything with a "glance" use case is suddenly first-class because the hardware wants to be looked at from across a room.

The one that will shape product decisions for the next two years is Split View on a phone. Not because people are using it heavily yet — they aren't — but because they're already discovering what it feels like to run two apps at once on a device they carry. The expectations from the iPad side of the house are now going to arrive on the phone side, and apps that can't share a screen gracefully will feel smaller than they are.

From the industry's seat: foldables just stopped being Samsung's story

For six years, the foldable conversation belonged to one brand. Apple's entry changes the centre of gravity overnight — not because Samsung built the hardware badly (the Fold line is remarkable) but because Apple has an app ecosystem that's finally going to take folding seriously as a layout problem rather than an edge case. Expect every major design system to ship a "foldable" track within the next year.

The more interesting shift is what this will do to the web. Mobile Safari on the inner display is already an open question — a 7.6" screen with a hinge down the middle isn't phone, isn't tablet, and the responsive breakpoints we've used for a decade don't naturally cover it. CSS already has the viewport-segments media feature. Nobody's shipped a serious site that honours it. That changes in the next six months, because the sites that look right on a Duo will have a real advantage over the sites that look right on an iPhone 17.

What I hope we see next

Three things, in order of boringness-to-importance.

One screen-size vocabulary across mobile and web. Flexbox, grid, container queries, viewport segments — the web is almost there. iOS size classes, SwiftUI Layout, GeometryReader — iOS is almost there. The teams who stop maintaining two mental models and ship one will move materially faster.

App surfaces that aren't apps. Widgets, Live Activities, StandBy, now the outer display when the device is closed. The Duo makes it obvious that the "app" is one of several surfaces a product lives on. The product that only exists inside an app icon is going to feel small on this hardware. The product that shows up on the outer display, in a Live Activity, on a Watch, in Siri, in a widget — all without a marketing site paragraph explaining it — is going to feel modern.

A world where the hinge is boring. Right now folding is the headline. In two years the hinge should be invisible — the thing that fades into the background while the software adapts. We're not there yet. The apps I most want to build in the next twelve months are the ones that treat the hinge the way we treat safe-area insets: a layout detail the user never notices because every part of the product knows what to do about it.

If you own an app

I'll say the same thing I said in September, with a shorter timeline. The window to look like you were ready for this is open now and will close by Q1. The teams that ship a thoughtful Duo update between now and Christmas are going to look like they get it. The teams that ship one in March will look like they got around to it.

If you own an iOS app and the first week on real hardware has shown you more work than you thought — reach out. We've been doing this for the clients I named in September; I'd rather have the honest conversation about which of the six steps you actually need than see the generic "we support iPhone Duo!" release note that nobody buys.

The phone shipped last Thursday. The apps people actually enjoy on it will ship between now and the end of the year.