Your Rectangle Is About to Grow a Hinge

For years you designed for a flat rectangle. Small one in a pocket, big one on a desk, maybe a tablet in between. That world is ending. This fall and into next year, the screen your users hold is going to fold, roll, and in some cases disappear onto their faces. Let me catch you up on what shipped, what's coming, and what it means for your team.

The pocket tablet is real now

Apple's foldable iPhone, reported as the iPhone Ultra, is heading into mass production. The Elec reports that Apple finalized the key specs and the hinge problems, larger tolerances, defect rates, and odd noises after durability tests, are mostly fixed. A September launch is back on.

When it opens, this thing is not a bigger phone. The inner display is a 7.8-inch, 4:3 OLED, right up against the 8.3-inch iPad mini. Mashable put it plainly: the iPhone Ultra looks more like part of the iPad family than any iPhone. Price is reported at $2,300 to $2,500, roughly double an iPhone 17 Pro Max.

So one device carries two layouts. A narrow phone screen closed, a near-tablet open. Your app has to handle both, and the switch between them, without breaking.

Samsung is turning form factors into a menu

At its July Unpacked event, Samsung is expected to show three foldables at once: the Z Flip 8, the Z Fold 8, and the Z Fold 8 Ultra. The confusing part, Alex Perry noted, is that the Z Fold 8 is a new wider phone, while the true successor to last year's Fold gets the Ultra name. The Z Fold 8's 7.8-inch inner screen lines up almost exactly with the reported iPhone Ultra, which tells you Samsung wants a direct fight.

And they are not stopping at folds. Samsung is reportedly working on a rollable phone, possibly called Z Slide, with a 10-inch display planned for 2028. Stan Schroeder points out Samsung was already first to ship a tri-folding phone.

The screen size is no longer a fixed thing you can assume. It slides along a range while the user holds it.

The software is already bending

This is not just hardware. The platforms are shipping features built for the extra space. Android 17 added Bubbles, where a long-press turns an app into a floating, resizable window you can stack on top of another app. Google is also splitting foldable screens for gaming, putting the game on top and a virtual controller on the bottom half.

That matters for your roadmap. Multi-window and floating layouts move from edge case to expected behavior. If your app assumes it owns the whole screen, or breaks when resized on the fly, users on these devices will feel it fast.

The screen that has no screen

Glasses are the other shift, and they split into two camps. Samsung's Galaxy Glasses are expected to follow Meta's playbook: camera plus an AI assistant, no heads-up display. Then there's Even Realities, now valued at $1 billion after a $150M round, betting the other way. Their G2 skips the camera and beams information into your line of sight, controlled by a tap-and-swipe ring.

CEO Will Wang calls smart glasses the most personal computing device people will ever wear, and says the display is the hard part. "Smart glasses are the first product category to rely on optical displays," he told TechCrunch. His power users lean on a copilot that reads a live conversation and explains jargon in real time.

There's no rectangle here at all. Just short glances, voice, and one line of text at a time.

The deep cut

Don't build three separate designs for phone, fold, and glasses. Build one that reflows. The real work is defining your content priority, what shows first when space shrinks, what expands when it grows, and what collapses to a single glance or a voice line. Even Realities sells that last state to a paying crowd: a third of their users are company executives, and average orders run near $1,000. People will pay for the glance.

So the practical move for Monday is an audit. Pull your top three screens and ask what happens at 5 inches, at 8 inches, and at one line of text. If the answer is "it breaks" or "we never checked," that's your next sprint, not a 2028 problem.

Three questions for your team

1. What are our top three flows, and do they survive a mid-session resize from phone width to tablet width without breaking?
2. If we had to show one flow as a single glance or a voice reply, what is the one thing the user needs first? Do we even know?
3. Are we designing for a fixed screen size, and where in our codebase is that assumption hiding?