Skip to content
tutorials

Apple's $2k Phone Hides a CSS Secret

Apple's new iPhone Duo just made foldable phones mainstream overnight. A single CSS media query is the only thing standing between a seamless user experience and a broken website on these new devices.

Marcus Lee
Apple's $2k Phone Hides a CSS Secret

Foldables Just Went Mainstream

Apple's recent announcement of the iPhone Duo, priced at $1,999, marks a pivotal moment for web development. Shipping October 23, 2026, this device, featuring a 5.4-inch outer and 7.6-inch inner display, catapults foldable phones from a niche curiosity into a mainstream reality for all web developers. Ignoring these adaptable form factors is no longer an option.

Fortunately, browser engineers anticipated this shift. We now have a powerful CSS media query, @media (device-posture: folded), designed specifically for these devices. This query detects if a device is in a folded state, like a book or miniature laptop, rather than its continuous flat posture. It empowers developers to apply targeted styles for optimal user experiences across various physical configurations.

Imagine a blog post. On a flat, continuous screen, a single-column layout works perfectly, maximizing readability. However, when the user folds their iPhone Duo into a book-like position, that single column might become awkward to read across the crease. With device-posture, you can easily switch to a two-column layout, placing content elegantly on each screen segment, instantly improving usability and interaction.

This simple adaptation demonstrates the immediate power of the device-posture media query. Developers can now craft responsive designs that fluidly adjust not just to screen size, but to the physical interaction model of the device itself. Chrome already supports these features, and Safari's iPhone Duo simulator includes them, albeit behind a flag, signaling their imminent widespread availability.

Making Your Site Fold-Aware

Beyond static CSS rules, web experiences for foldable devices truly shine with dynamic interactions. The Device Posture API for JavaScript allows your site to respond to how a user holds their iPhone Duo or other foldable, providing a richer, more intuitive experience. It moves beyond just styling for flat or folded states, enabling real-time reactions.

Your application can listen for a change event on the device's posture, triggering actions whenever the phone's state transitions between continuous (flat) and folded. This means you can automatically pause a video when a user begins to close their phone, or save form progress instantly as they switch postures. Imagine a recipe app showing ingredients on one screen and instructions on the other, dynamically splitting content as the device folds.

Detecting these fold state changes with JavaScript is straightforward. Here’s a foundational snippet:

if ('ondeviceposturechange' in window) { window.addEventListener('deviceposturechange', (event) => { const currentPosture = event.target.devicePosture.type; console.log(`Device posture changed to: ${currentPosture}`); // Implement dynamic actions here based on currentPosture ('continuous' or 'folded') });
}

This event listener provides the devicePosture.type, allowing you to build more interactive and intuitive foldable web experiences. Chrome and Samsung Internet already fully support this API, while Safari's iPhone Duo simulator includes it behind a feature flag, indicating future support for Apple's $1,999 device.

Designing for Two Screens at Once

Foldable devices introduce a fascinating concept: viewport segments. When an iPhone Duo is folded, it presents two distinct display regions, each controllable independently. This moves beyond simply reacting to a fold; you can design for genuine dual-screen experiences, treating each segment as its own canvas.

To precisely place content, developers use CSS environment variables. For example, env(viewport-segment-width) and env(viewport-segment-height) provide the dimensions of each individual segment. This allows you to create powerful, adaptive layouts, ensuring elements align perfectly around the physical hinge or gap.

Consider advanced use cases that truly shine with dual screens. A video player could occupy one segment, while its transcript, chapters, or related comments display interactively on the other. Similarly, an email client might show your inbox list on one segment and the selected message's full content simultaneously on the adjacent one, boosting productivity.

Chrome already supports these features, with the Viewport Segments API available from Chrome 138. Samsung Internet has offered this functionality for years on their foldable phones. While Safari's iPhone Duo simulator, released with Xcode 27.1, includes these APIs behind a feature flag, you can explore related CSS features, like device-posture, further on the device-posture CSS media feature - MDN Web Docs.

Enjoying this? Get one like it in your inbox each morning.

one email a day · unsubscribe in two clicks · no third-party tracking

The Browser Battlefield: Who's Ready?

We've explored the "why" of fold-aware design; now, let's look at the "where." Good news: many tools are ready today! Chrome offers stable support for the device-posture media query and JavaScript API, including the Viewport Segments API available from Chrome 138. This means a significant portion of the Android foldable market can already experience your enhanced layouts. Samsung Internet has championed these features for years, ensuring a robust experience for its vast fleet of foldable devices.

Safari's journey is just beginning. The new iPhone Duo simulator, released with Xcode 27.1, notably includes both the device-posture and viewport segments APIs. This signals Apple's clear intent to support these capabilities. However, these features are currently nestled behind a feature flag, meaning while Apple is preparing for the $1,999 iPhone Duo's October 23, 2026 release, full support might not be enabled by launch.

So, what's a developer to do? Embrace progressive enhancement! Design your baseline experience to be solid and accessible on all browsers, including those without foldable APIs like Firefox. Then, layer in the advanced device-posture and viewport segments features as enhancements. This strategy ensures a superior, tailored experience for users on capable foldable devices—like a split screen for video and notes—without compromising functionality for anyone else. It's about gracefully adapting, not breaking.

Frequently Asked Questions

What is the CSS device-posture media query?

It's a new CSS media feature that allows web pages to adapt their layout based on a device's physical state. It has two main values: continuous for a flat screen and folded for when the screen is bent or hinged.

How do I control content on both sides of a folded screen?

You can use the Viewport Segments API. CSS environment variables like viewport-segment-width and viewport-segment-height allow you to style the distinct screen areas on either side of the fold, creating dual-screen experiences.

Which browsers currently support foldable CSS features?

Chrome and Samsung Internet have full support for the device-posture media query and Viewport Segments API. Safari support is available in the iPhone Duo simulator but is currently behind a feature flag. Firefox does not yet have support.

What's the difference between the CSS media query and the JavaScript API for foldables?

The CSS device-posture media query is declarative, used for styling layouts based on the device's state. The JavaScript Device Posture API is imperative, allowing you to run code in response to fold events, such as pausing a video or saving data.

Found this useful? Share it.

For builders

Want Stork to write one of these about your product?

Send us a URL. We use the product, form a view, and publish what we actually think — in 8 languages, labeled Sponsored, with no copy approval on your side. That last part is what makes it worth quoting.

See how it works$500 · AI tools & software only

For builders

This page is doing a job for someone else’s tool.

AI agents read it. Buyers land on it. It answers in eight languages and over MCP. Your tool can have one like it — live in 24 hours.