Foldables are not new. Samsung and others have been selling them for years, and a fair question has followed the iPhone Duo launch: what is Apple actually adding?

Not a new form factor. What Apple adds is weight. When Apple publishes design guidance for a device, it becomes the default expectation across the platform. The Duo is the first iPhone that asks apps to work at two very different shapes, and it brings Split View to the iPhone for the first time. That is why it matters to designers who never plan to buy one.

The grey area between phone and tablet

A phone is easy to carry but runs out of room the moment the work gets serious. A tablet gives you the room, but it is not always in your pocket. For years we have designed for those two as separate worlds and called the space between them an edge case.

The Duo sits in that space. A user can answer something quickly on the move, then open the device and sit down to build something properly, without switching tools or starting over. For the user, the promise is that they do not have to make a hard switch between modes. For us, that promise is a requirement: the product has to keep up when the user changes their mind mid-task.

What Apple actually shipped

Apple's foldable has a 5.4-inch outer display for use when folded and a 7.6-inch internal display. It also brings Split View, the first time two apps can sit side by side on an iPhone.

The more interesting decision is in the guidance. The Duo can be held open, closed, half-folded or propped at an angle, and Apple's position is that designers should not create a separate layout for each of these scenarios. Apple asks you to design around size classes, not poses. When the device is folded, some controls move off the top and bottom edges into a vertical strip on the right, because the folded display is wider and shorter than a normal iPhone. Apple calls this pattern displacement.

Existing apps will still run on iPhone Duo without being rebuilt. Whether they look good is a separate question.

Why this is a systems problem, not a screen problem

If you design screens, the Duo looks like a new canvas to fill. If you design systems, it looks like a test of whether your decisions were ever portable.

A layout built from fixed frames breaks at the fold. A layout built from components that know what space they have, what to show first and what to hide does not. The Duo can't tell the difference between a screen you drew and a system you built, and that is exactly why it is a useful test.

Apple's guidance leans the same way. It prefers system containers over custom reimplementations, and the new fold-aware behaviours, such as moving bars into a vertical strip, apply only to bars owned by system containers. Custom navigation you built yourself gets none of this for free.

Keep the scale in view, though. Foldables are a small slice of the market. You are not designing for the Duo. You are designing for every window, split screen and tablet your product already meets, and the Duo is the first one with Apple's attention on it.

Four checks before October 23

Your layout is built on size classes, not device frames. If any screen is specified at "iPhone width," it is already wrong on the Duo and on every split-screen window. Replace device names in your specs with the behaviour you want at compact and regular widths.

Your content has a priority order. When space shrinks or a hinge occupies it, something has to give. If your team has never agreed on what that something is, the platform will decide for you. Write the order down for your top five screens.

Your state survives a fold. This is the grey area in practice. A user who opens the phone mid-task expects the same task on a larger canvas, not a reset. Apple asks designers to preserve the logic of the app regardless of the Duo's position. This is the check most teams fail, and no layout fix repairs it.

Your custom components have an escape hatch. Where you built your own navigation or toolbar, decide whether to move to the system version or to document how yours displaces around the fold. Doing neither means the Duo is where you find out.

What this asks of us

We are not exempt. We design adaptive systems for clients, so the honest question is whether our own work passes. Could we open our top flows in a half-width window tomorrow without a redesign? If not, the Duo is a useful deadline to fix that.

The Duo is one device, but the larger shift is towards experiences that move with us instead of making us adapt to them. The question is not only whether your app will work on the next device. It is whether the way you design apps today will still make sense as the boundaries between mobile, tablet and desktop keep blurring. Teams that treat the Duo as a one-off will redo this work for the next device. Teams that fix the underlying system will not.

Want your app ready for the iPhone Duo? If you'd like to make your app work well on the fold, or talk through what it means for your product, get in touch with us at design@rmgx.in.