Nobody Panicked About Foldables Until Apple Made One

The iPhone Duo is here, my feed is having a breakdown about breakpoints, and I think we're all panicking about the wrong thing.

Apple announced the Duo days ago, and within about four hours my entire feed turned into a support group for designers grieving their grid systems.

The problem, apparently, is this: the Duo is a squat little passport-shaped phone when it's closed, and roughly an iPad mini when it's open. Two completely different screens, one device, switching between them whenever the user feels like it. What happens to our layouts? What happens to our components? What happens to the media queries we spent three sprints arguing about?

Genuine question, asked with love: where has everyone been since 2018?

Because foldable phones are not new. Royole's FlexPai was the first one you could actually buy, back in October 2018. Samsung announced the original Galaxy Fold in February 2019 and shipped it that September, after a slightly humiliating delay to stop the screens from dying. Huawei's Mate X landed the same year. That's seven or eight years of real foldable phones, in real hands, loading our websites, running our apps, folding and unfolding in the middle of our checkout flows.

And we collectively decided to care about it on Tuesday.

That's an accessibility problem long before it's a technical one. Every time “supported devices” quietly means “the iPhone frames already in our Figma file,” someone is being sorted into the group that gets a good experience and someone else is being sorted into the group that gets a tolerable one. We rarely make that decision on purpose. We just make it, and it always seems to work out nicely for us.

Okay. Now the phone.

Everyone is yelling about breakpoints. Breakpoints are the easy part.

Width is solved. We have had flexible grids, fluid type and container queries for years. If your layout falls apart going from a small screen to a big one, that is a known problem with a well-documented fix, and it was known in 2019.

The genuinely hard part is the thing almost nobody is posting about, and I've started calling it the fold event.

A foldable doesn't just have two sizes. It changes size while your app is running. Which means the interesting questions aren't about measurements at all. They're about what happens to everything that was already in progress:

• Someone is scrolling an article and opens the phone. Do they land at the same pixel position, or on the same paragraph? (Only one of those is correct.)
• A modal is open. A dropdown is anchored to a button that has now physically moved several centimetres to the left. What is that dropdown attached to now?
• Someone is halfway through a form, keyboard up, typing. Does the field stay in view, or does the reflow bury it under the keyboard?
• A video is playing. An upload is running. A draft is unsaved. Does any of it survive?
• Your progress indicator showed one step at a time. Now there's room for three. Is that a different component, or the same one breathing?

the fold event: the state change nobody specced

And it gets slightly worse, in a way I find genuinely interesting. Craig Federighi, Apple's software boss, said in a post-keynote interview that the Duo doesn't just serve up iPad layouts when you open it. Some apps do look iPad-ish — Settings has that two-column thing, Photos is basically the same — but the home screen and the camera were built specifically for this device, and developers are expected to give it its own treatment.

Translation for anyone doing sprint planning: this isn't a new screen size on an existing platform. It's a third thing. iPhone, iPad, and now Duo, with its own reachability rules and its own opinion about what should happen when it opens.

That's not a media query. That's a ticket. Possibly several.

Credit where it's due: Apple still wins the boring stuff

Let me get the obvious out of the way, because “Apple is late but shiny” is a lazy sentence and I refuse to publish it.

Apple is late, and on paper the hardware is behind. No telephoto lens. No silicon-carbon battery. No ultra-fast charging. The main camera is almost certainly smaller than the one in the Pro. Anyone calling this the most advanced folding phone ever made has not opened a spec sheet in a while.

But Apple doesn't really compete on specs. It competes on decisions per square centimetre, and the Duo is a masterclass in that. It's a bit like what good F1 teams do with a new set of regulations: let everyone else spend three seasons crashing into the concept, then show up with the version that's been in the wind tunnel the whole time.

• The open/close animation. A soft progressive fade from the screen you were on into the screen you're going to, with no perceptible lag when you snap it shut. I've used foldables where there's a beat of black before the cover screen catches up, and that beat is the entire difference between “one device” and “two devices sharing a hinge.” Apple deleted the beat. It's the interface equivalent of a K-drama holding a look two seconds longer than it needs to. Technically unnecessary. Completely the reason you're still watching.
• The matte nano-texture coating on the inner screen. My favourite decision on the entire phone, because it's one material choice quietly solving three problems. It kills reflections. It feels smooth under your thumb. And because it scatters light instead of bouncing it, it visually hides the crease, which reviewers are putting roughly level with the Oppo Find N6 — the best anyone has managed. One layer, three wins, zero marketing bullets.
• Speaker placement. Top speaker on the front, bottom speaker on the back, so when you open the thing you still have one on each half and stereo survives the fold. Someone had to think of that, and then someone had to defend it in a meeting where it definitely sounded insane.
• Half-open tent mode with a soft glow clock. Fold it partway, lock it, and it becomes a bedside display that wakes you gently. Nobody put that as a feature request. Someone just watched what people do with a hinge.

Not one of these will ever appear in a comparison table. All of them are why the thing feels like it costs two thousand dollars. Attention to detail isn't a coat of polish applied at the end. It is the product, and Apple keeps proving that while everyone else optimises for the table.

They hid a sensor under a screen twice. Only one of them worked.

The headline detail is that the Duo's inner screen has no notch, no island, no hole punch. Nothing. The selfie camera lives underneath the display. Corner to corner, uninterrupted.

I'm on an iPhone 13, where the island sits at the top of everything I do like an uninvited flatmate, so my first reaction was: that's genuinely insane. They buried a camera under a surface that changes colour and brightness sixty times a second, and you cannot see it.

Then I saw the video it produces. It's rough. Visibly soft, in perfectly decent lighting.

Here's the part that makes me itch: we already ran this experiment. Samsung shipped under-display cameras on several generations of Fold, and then stopped, because users worked out they'd rather have a small visible hole punch and a camera that actually works. We got the answer. We're doing it again anyway.

What saves this from being a simple “Apple messed up” take is that Apple hid something under a display twice this cycle, and only one of them was a mistake.

On the iPhone 18 Pro, they moved the Face ID infrared camera under the panel. The Dynamic Island shrank by 25%, which buys enough room for three Live Activities instead of two. There's a slightly different pixel arrangement in the top-left corner and you will never, ever notice it. Clean win.

So why does one work and the other doesn't? Because of what the sensor is for.

Face ID is a sensor. Its only job is to recognise a shape. It can do that through a slightly murky window and literally nobody will ever inspect its work. The selfie camera is a camera. Its output is the entire point. Every photon the display stack steals is a photon that was supposed to be your face.

That's the transferable lesson, and it goes way beyond phones: you can bury the parts of a system whose output nobody looks at, and you cannot bury the parts whose output is the deliverable. Worth asking before you hide anything, in hardware or in an interface.

Go and hold your passport, I'll wait

Seriously. Go get it. Hold it in one hand. Try to curl your fingers around it and reach your thumb across the front.

Unless you have unusually large hands, you can't — not comfortably. That is the closed shape of the iPhone Duo: short, wide, and about as thumb-friendly as a paperback. Open it up and you're using both hands, no negotiation, no discussion.

Samsung's Galaxy Z Fold 8, out in July 2026, moved to a wider, passport-style 5.5-inch cover screen and a 7.6-inch inner display, making it their widest book-style foldable ever and a deliberate break from the tall shape they used for years. The narrow-and-tall option now lives on the Fold 8 Ultra instead. And Google's Pixel Fold has been the short, wide one since 2023.

Genuine question for whoever knows: why are we doing this? Why are we making phones that are harder to hold, on purpose?

I'll let that sit and carry on.

The industry converged on this, and Apple turned up last to a decision that had already been taken. Which honestly makes the criticism bigger, not smaller. The whole category has decided that a foldable is fundamentally “a small tablet that folds,” and that its phone mode is the compromise you accept in exchange. That's a perfectly defensible bet for watching things, reading things, splitting the screen and typing properly. It's a strange bet for the thing people mostly do with phones, which is operate them one-handed while walking, carrying a coffee, and not really looking.

Physical ergonomics is UX. It decides reach, grip, thumb travel, fatigue and how often the thing hits the pavement. We don't get to file it under “industrial design” and consider our part finished, because every single consequence lands in the interface.

The accessibility bill

Here's where I stop being charmed.

• The dock is stuck on the right. With the Duo open, the software deliberately pulls the UI toward the right-hand side for reachability. Good instinct! But there's no setting to move it to the left. On a two-thousand-dollar device, which hand you use is not a preference. It's a spec.
• Face ID is gone entirely. The Duo authenticates with a fingerprint reader built into the power button, on the right rail.

Most people are saying, “fine, Touch ID is nice, I missed it.”

I'm saying it's a regression, because those two things are not equivalent for everyone. Face ID is passive: you look at it, it works, and it keeps working if your hands are wet, gloved, full, shaking or just not that precise today. Touch ID is an active, accurate press on a specific spot. For anyone with a tremor, arthritis, limited dexterity, worn or missing fingerprints, or anyone using the phone mounted in a car or propped on a desk, that's a real loss of access. Not a vibe. Access.

Then stack the two. The hardware assumes your right hand, because that's where the fingerprint reader is. The software assumes your right hand, because that's where the dock is, permanently. Two separate teams, two separate layers, same assumption, arrived at independently. Which tells you either nobody in that room was left-handed, or somebody was and got outvoted.

And one small thing that says a lot: the dock holds four items and refuses a fifth. You can take things out. You cannot put things in. The comfortable reach zone genuinely is a finite budget, which is a real constraint worth designing around — but rather than expose that trade-off to the person holding the phone, they picked a number and locked the door.

My twelve-year grudge, still going strong

The camera has stuck out of the back of the iPhone since the iPhone 6 in 2014. I've been complaining about it since roughly 2014. Nobody has ever cared, which has not slowed me down.

The standard defence is thinness versus physics, and fine, that's real. But look at what the trade-off actually produces. The phone doesn't sit flat. It rocks on the table like a wobbly restaurant table you keep trying to fix with a napkin. The most fragile and most expensive component on the device is the bit that touches every surface you put it down on. And the company that sells the phone as remarkably durable ships it in a shape that basically requires a case — which means the industrial design almost nobody experiences is the industrial design that got approved.

Optional detour · Portugal Let's talk about the price, and let's do it from where I'm standing This is the section where I'll admittedly vent about my country's economic state, and how the price of a simple Apple phone shapes its future. Skip it if it doesn't concern you in the slightest — honestly. Open it if you're curious.

In Portugal, the iPhone Duo starts at €2,399 and the top configuration is €3,899. For context inside Apple's own lineup here: the iPhone 18 Pro starts at €1,499, the iPhone Air at €1,349, the iPhone 17 at €1,139. So the Duo lands roughly €900 above the next most expensive iPhone and becomes, comfortably, the most expensive iPhone ever sold in this country. I'm not even going to go over the 23% VAT issue, because we would never leave this page.

Now, the part that international coverage never includes, because international coverage is written in dollars.

According to Eurostat, the average annual salary for a full-time worker in Portugal was €24,818 in 2024, against an EU average of €39,800. That's 38% below the European average, and the tenth lowest in the Union.

So the cheapest possible iPhone Duo costs a Portuguese worker on the average net salary something like one and a half to two months of their entire pay. On minimum wage, closer to two and a half months of gross income. Before rent.

And Lisbon rent does not leave you two and a half months of anything except a slight sense of panic. I can buy a car in this country for less than this phone. Not a super nice car, true, but one that starts, passes inspection and gets me to the airport.

I don't want this to turn into an economics essay. I'm a designer, not an economist, and there is a version of this article that disappears into tax policy and never comes back. So I'll keep it to why it bothers me personally.

I love this country. Embarrassingly, defend-it-at-dinner-parties love it. And I've watched people here work full weeks, every week, and still do maths in the supermarket aisle. Meanwhile, the international image of Portugal is sunshine, cheap wine, pretty tiles and the happiest little corner of Europe. The distance between that postcard and the actual group chat is enormous, and it keeps getting wider while everyone tells us how lucky we are with the weather.

And yes, obviously, nobody has to buy this phone. Most people won't. It'll be bought by whoever wants it and can afford it, which is how literally every product on the planet works, and I'm not out here demanding price controls on luxury electronics.

But launching a €2,399 device into a country where that's roughly two months of the average salary, at exactly the same price as Luxembourg, with a financing plan helpfully attached, and treating it as unremarkable? Come on. Somebody in that room ran the numbers. Nothing about it changed.

Which, if I bring it back to my actual job: pricing is part of the experience. It's the first interaction anyone has with a product, and for most people here it will be the only one. You can design the most beautifully considered fold animation in the industry, and if the number in front of it means “not for you,” that's the interaction. That's the whole thing they'll ever feel about it.

So who is it for? Honestly, I don't think it's for anyone yet.

The reviewers say this is for people who've been curious about foldables for years and don't want to leave the Apple ecosystem.

Reader, that is me. Almost to the letter.

I've had an iPhone since I was eleven years old, starting with a 3GS. That's not brand loyalty at this point. It's more like a personality trait I inherited. And I've spent the last two years seriously curious about foldables. I have genuinely, more than once, considered walking away from the entire Apple ecosystem to go and try one — which for someone with my history is roughly the emotional equivalent of changing religion.

I am the target market. And I'm not buying it. I don't think you should either.

Not because foldables are silly. They aren't, and I'll come back to that. But because you're paying a premium for a first-generation hinge with no long-term track record, a selfie camera that shoots visibly worse video than the one on a phone half the price, no telephoto lens, no fast charging, and an interface that has quietly decided which hand you use. Samsung is on its eighth generation of this and launched the Fold 8 at $1,800.

Being late is fine. Being late, more expensive, and less complete is a harder sell.

If what you want is a foldable, buy one from a company that's already made seven of them and learned something each time. If what you want is an iPhone, buy an iPhone; they're extremely good. If what you want is specifically this object, wait for the second generation, which is where Apple has historically fixed the things it got wrong in public.

None of which means the category is a gimmick. China bought more foldables last year than the rest of the world combined. That market has existed for ages; it just wasn't waiting for a Western permission slip. Foldables are real, the demand is real, and everything I said earlier about designing for them still applies whether or not any of us buys this particular phone. The device is just a bad deal from where I'm standing.

What I'd actually do in October

The Duo is not an emergency. But it's an excellent excuse to fix a handful of things that have been quietly broken since 2019.

• Stop testing sizes. Start testing transitions. Resize the viewport while something is happening: modal open, form half-filled, video playing, keyboard up. That's where it actually breaks.
• Put fold behaviour in the spec. For every screen: what's preserved, what reflows, what's anchored to content versus anchored to a position.
• Audit your reachability for handedness. If every primary action sits bottom-right forever, that's a decision. Make it consciously, and give people an exit.
• Never let one biometric be the only door. If face, fingerprint or a precise tap is the only way in, you've locked somebody out.
• Treat physical ergonomics as your job too. Grip, weight, reach and one-handed use shape your interface whether or not you were in the room when the enclosure was signed off.

Apple didn't create the foldable problem. It just made it impossible for the rest of us to keep pretending it wasn't there, which is a service, in the most irritating way possible.

The devices were always here. The users were always here. We just weren't looking until the logo got familiar.

written on a phone that does not fold