If you have been hearing about the iPhone Fold rumours, you already know what the hardware is going to look like. A 5.5-inch outer cover display for one-handed use, and a 7.8-inch inner display that opens horizontally into a near-square, tablet-style canvas.
The hardware picture has been circulating all around for months. What nobody knew was how Apple planned to handle the apps on that big inner screen.
What Apple Actually Announced
Apple didn’t mention a foldable iPhone once at WWDC 2026. Not a single word. But inside its Platforms State of the Union developer session, it mentioned a change that makes absolutely no sense unless a foldable phone is coming.
Apple told developers to move away from designing apps for specific devices and fixed orientations, and to instead target what it described as “a dynamic range of sizes and aspect ratios.”
The practical result is that apps rebuilt against the iOS 27 SDK are automatically opted in to resizability, and Xcode now includes a resizable iOS simulator for testing layouts at arbitrary sizes.
In Lyman’s terms, iPhone apps will now fluidly resize to fit whatever screen they land on. No more fixed layouts locked to one specific aspect ratio. No more black borders when you open an app on a screen that’s slightly the wrong shape.
And for developers already building with SwiftUI, in Apple’s words, “well on your way to supporting full resizability.”
What Does This Have to Do With Android?
Basically, Everything. Multi-window support was first introduced in Android 7, released in 2016, which means Android has required apps to handle flexible, resizable layouts for nearly a decade.
The core principle is that an app should reflow gracefully across different screen sizes, rather than being built for one specific shape.
Web designers had the same idea even earlier. Responsive design, where a website adapts its layout based on the screen width, became standard practice around 2010-2012. The idea that software should fit the screen rather than the screen fitting the software is not new. It’s just new to the iPhone.
To be fair to Apple, Android’s foldable story has not been seamless either. Android foldable owners have spent seven years discovering which of their apps work and which ones don’t. Having the policy and actually enforcing it are two different things.
But the point stands that Apple is arriving late to a concept its rival Android has been fighting with since 2016.
Why Apple Has to Do This Now
The iPhone Fold creates a problem that no existing iPhone app was built to handle. A foldable phone is not just about a bigger screen, but it’s about a screen that changes shape during use.
When you unfold the device, the inner display measures roughly around 7.76 inches at a 2,713 x 1,920 resolution.
The inner screen is closer to a 4:3 aspect ratio, which is better suited for side-by-side app multitasking and video consumption without black bars.
That’s a completely different shape from the tall, narrow screen of the ordinary iPhone app, which has been designed since 2007.
The iOS 27 Code That Gives It All Away
Developers digging through the first iOS 27 beta have uncovered framework strings including “foldState,” “angleDegrees,” and “mechanicalAngleDegrees.”
The code also includes a function designed to identify the number of built-in displays connected to a device.
The OS is being built to know whether the device is folded, how far it has been opened, and whether it is running two integrated screens at once. These references were not present in earlier versions of iOS.
In macOS 27, iPhone Mirroring can now be resized beyond the iPhone’s fixed aspect ratio for the first time and depending on the chosen aspect ratio, it renders either an adjusted version of the app’s iPhone layout or its iPad layout, when one is available.
That’s a live preview of exactly how the Fold’s two screens will behave.
Although resizability is not the same as optimisation. An app that scales fluidly to fill a 7.8-inch screen is not necessarily the one that takes advantage of a 7.8-inch screen. There’s a difference between an app that doesn’t break and an app that’s genuinely better on a larger display.
The ideal scenario would have been proper iPad apps running natively on the inner display, with a richer layout with more content, more sidebar navigation, and more information on screen all at once. That’s what a large display is actually for. Resizability gets you there technically, but it doesn’t force developers to rethink their layouts for a bigger canvas.
Also Read: iOS 27 Brings Major CarPlay Upgrades: Here’s Everything New
