Apple’s Foldable iPhone Has a Left-Handed Problem

Apple’s new iPhone Duo moves some familiar controls from the top and bottom of the screen into a vertical bar along the side when its larger inner display is used in landscape.

Apple says one reason for the change is to put those controls within easier reach — which raises a wonderfully simple UX question: easier for whom?

It matters far beyond Apple’s new phone. Designers have spent years making interfaces responsive to different screen sizes, but responsive design is still largely about adapting an interface to the device. The Duo is a useful reminder that genuinely adaptive design also needs to consider the person interacting with it.

Apple Changed More Than the Screen

The most interesting thing about the new iPhone Duo from a design perspective isn’t really that it folds. Foldable phones have existed for years. What’s more interesting is what Apple has done to the interface because it folds.

On the larger inner display, Apple can move navigation, toolbars and other controls into a vertical region along the side. In landscape, this takes advantage of the extra horizontal space while freeing more vertical room for content.

Apple explains the reasoning directly in its developer guidance for vertical bars on iPhone Duo. Controls that would normally occupy the top or bottom can move to the side, preserving vertical space and, according to Apple, putting them within easier reach.

Spatially, that makes perfect sense. But the Duo interface shown so far puts the Home Screen Dock vertically along the right-hand side, and The Verge’s analysis of the Duo interface questioned whether that right-hand UI rail could prove awkward for left-handed users unless Apple provides a way to flip it.

The concern also surfaced during hands-on use. MobileSyrup reviewer Dean Daley noted that he is right-handed and found the Duo comfortable, but wondered whether left-handed users would have the same experience.

None of that proves there’s a usability problem. The Duo hasn’t reached customers yet, but the design does expose a much broader question that applies to almost every interface we create.

“Easy to Reach” Is an Assumption

Designers make hundreds of invisible assumptions every time they build an interface. We assume where someone’s thumb will be, which direction they’ll swipe, where they expect the Back button to appear, and that a menu feels natural in a particular location because we’ve seen similar menus thousands of times.

Most of those assumptions are useful. Without conventions, every interface would force visitors to relearn basic interactions. Problems begin when we mistake a convention for universal human behavior.

A control positioned conveniently beneath a right thumb isn’t necessarily as convenient beneath a left one. A navigation system that feels effortless while holding a device with two hands can feel completely different when you’re standing on a train using one. Hand size, grip, dexterity and context all change the experience.

The Duo makes those normally invisible variables unusually visible because Apple has changed something users have taken for granted for years: where the controls live. Apple has made a rational spatial decision — the screen is wide, so move controls sideways and give content more vertical space — but one rational design decision can create another usability question.

Responsive Design Is About More Than Pixels

There’s an especially useful parallel here for web designers. Responsive design is still frequently discussed in terms of viewport sizes: desktop, tablet and mobile. Add some breakpoints, rearrange the columns, collapse the navigation and resize the typography.

Except users don’t experience websites as viewport widths. They experience them while holding phones, rotating devices, increasing text size, navigating with keyboards, using screen readers, zooming pages and splitting windows.

Apple’s advice to Duo developers sounds remarkably similar to where responsive web design has been heading. In its guidance for preparing apps for the iPhone Duo, Apple tells developers to avoid assumptions about display size and capability and instead design across a continuum of sizes.

Apple also warns that safe areas and layout margins can be asymmetrical, so developers shouldn’t simply assume that whatever happens on one edge of the display is mirrored on the other. That’s guidance for native iOS apps rather than websites, but the principle translates remarkably well.

Don’t design around the screen you imagine. Design around the space and conditions that actually exist. Foldables simply make the weaknesses of rigid assumptions much easier to see.

The Best Position Isn’t Always One Position

Web and interface designers constantly look for the correct position for something. Should navigation be at the top? Should filters appear on the left? Where should the CTA go? Should a floating action button sit in the bottom-right corner?

The Duo demonstrates why the better answer is increasingly: it depends. Apple isn’t actually forcing the same vertical arrangement in every situation; its developer guidance says the vertical controls remain in place on the inner display in landscape but return to a more familiar horizontal arrangement in portrait.

In other words, Apple isn’t designing one perfect layout and simply stretching or shrinking it. It’s creating rules that allow the interface to reorganize itself as the available space changes.

That’s exactly the kind of thinking modern web design needs. Instead of asking what width a card should be, define how that card behaves as its available space changes. Instead of assuming navigation permanently belongs in one location, think about where it works best under different conditions.

The distinction is important. You stop designing a page and start designing a system.

Don’t Make Users Adapt More Than Necessary

There’s a tempting defense of almost every unusual interface: people will get used to it. They probably will. Humans are remarkably good at adapting to inconvenient interfaces, from hamburger menus and mystery icons to hidden gestures that weren’t remotely obvious the first time we encountered them.

But users being capable of adapting doesn’t automatically make something good usability. A better question is how much adaptation the interface could be doing for them.

Apple clearly understands that principle. Its iPhone Duo design guidance tells designers to use adaptive layouts, respect safe areas and maintain hierarchy as the available space changes. Navigation can collapse, expand or become a sidebar, while controls can change orientation and content can move to accommodate the device.

That makes the left-handed question interesting even if it ultimately turns out to be a nonissue. It doesn’t mean every website suddenly needs a “left-handed mode”; it means we should be suspicious whenever our designs depend too heavily on the assumption that everyone interacts with them exactly as we do.

Test the Assumption, Not Just the Layout

Web testing often asks whether an interface technically works. Does the menu open? Is the button visible? Does the layout break at 768 pixels? Can someone complete checkout?

Those tests matter, but they don’t necessarily tell you whether an interface is comfortable to use. Try your mobile site with your other hand. Increase the browser’s text size, navigate without a mouse, rotate the screen halfway through a task, zoom to 200 percent, or hold a large phone one-handed and try to reach the primary navigation.

Some of the most useful usability problems appear only when designers stop interacting with their work exactly as they intended it to be used. Apple is effectively forcing that sort of thinking on developers working with the Duo, but web designers don’t need a folding iPhone to apply the same principle.

The Duo Might Not Have a Left-Handed Problem at All

It’s important not to overstate what we know. Apple says iPhone Duo preorders begin October 16 and general availability starts October 23, so until ordinary left-handed users spend meaningful time with the final product, we don’t actually know whether its control placement will cause a significant usability problem.

The concern could turn out to be minor. Apple could change aspects of the software, or people might naturally hold the Duo in ways that make the right-side controls less significant than they appear in demonstrations.

So the lesson isn’t that Apple has failed some basic UX test. What’s interesting is how easily a potential usability problem can emerge from an otherwise perfectly logical design decision: put the controls here because they’re easier to reach.

It sounds entirely sensible until you ask the next question: easier for whom? That’s worth remembering the next time you’re deciding where to put navigation, a menu, a button or a CTA. Responsive design shouldn’t only respond to screens; the best interfaces also need to respond to the people using them.

Noah Davis

Noah Davis is an accomplished UX strategist with a knack for blending innovative design with business strategy. With over a decade of experience, he excels at crafting user-centered solutions that drive engagement and achieve measurable results.