Contact Us
Mike Krasnovskyi Head of Automation
  • Last updated:
  • 10 min read

How to Test Websites and Apps on iPhone Duo

iPhone Duo has two displays — a 5.4-inch outer screen and a 7.6-inch inner one — and works folded, partially folded and fully open. Testing on it means checking layout on both screens, state continuity when the user unfolds, side-by-side multitasking, and how apps built with older iOS SDKs render.

Apple announced the device on 9 September 2026 and put it on sale on 23 October. It ships with iOS 27. Every device specification and viewport figure below comes from Apple or from WebKit, and we say which each time. The test recommendations are ours.

What Changes for QA on iPhone Duo

Device featureWhat can breakWhat to check
Two displays, different proportions
Breakpoints tuned for one phone shape
Layout on the outer screen, the inner screen, and both orientations
Fold and unfold mid-session
Lost scroll position, closed modals, cleared forms, paused video
State survives the transition in both directions
Partially folded posture
Content hidden behind the folding region
Nothing important sits across the crease
Split View multitasking
Layouts that assume a full-width window
The app at roughly half the inner display's width
Apps built on older SDKs
Window sits centred with empty space around it
Which SDK your build uses, and what that does to your layout
120 Hz ProMotion
Animations tuned for 60 Hz
Transitions during fold and unfold

One number is worth getting right before you start. Apple publishes resolutions — 1398 × 2034 at 460 ppi outer, 1878 × 2670 at 430 ppi inner — but it does not publish aspect ratios.

Work them out from those pixels and you get roughly 1.45:1 outer and 1.42:1 inner. Close, but not identical, so don’t assume one set of proportions covers both screens.

Both displays run ProMotion up to 120 Hz. The inner display has an under-display FaceTime camera; the outer one has a conventional 12MP Center Stage camera.

For mobile app testing, this is a compatibility testing problem with a new variable: one device is now several form factors, and your test matrix has to say so.

iPhone Duo Screen Size for Web Developers

This one has a precise answer. WebKit published the CSS viewport sizes on launch day:

PoseWidthSmall viewport heightLarge viewport height
Outer display, portrait
382
580
618
Outer display, landscape
594
368
406
Inner display, portrait (with one tab)
669
867
902
Inner display, landscape (with one tab)
951
585
620
Inner display, each window with two side by side
385
571
609

All figures in CSS pixels. Width ranges from 382 to 951 across every combination. The inner-display rows assume a single Safari tab — browser chrome changes the height.

Two things stand out. The inner display in landscape is 951px wide, just under the 1024px breakpoint where many design systems switch to their desktop layout. A 7.6-inch screen then gets served the narrow version.

And a side-by-side window at 385px is almost exactly the outer display’s width, so if your narrow layout works, multitasking mostly works too.

Treat these as a starting point. Measure window.innerWidth, screen.width and devicePixelRatio on the device or simulator before building breakpoints around any published number, ours included. Apple doesn’t state a device pixel ratio for either display.

How to Test a Website on the iPhone Duo

The good news first. WebKit’s position is that “your websites and web apps work on iPhone Duo just like they do everywhere else” — the same engine as every other iPhone, not a special build.

What to check

Breakpoints at the new widths. Load the site at each width above, especially 669px and 951px — they fall between the breakpoints most design systems define. Container queries handle this better, because a component sized by its container doesn’t care which screen it’s on.

State across the fold. Fill in half a form and unfold. Scroll a long page and fold. The transition resizes the window mid-session, and anything tied to a resize handler gets a chance to misbehave.

Safe areas. Keep using viewport-fit=cover and the env(safe-area-inset-*) variables. WebKit notes that on the outer display, web content “does not currently extend to fill the space behind these controls” and that it’s investigating a better approach — so re-check as Safari updates.

Split View at 385px. Run the site in one half of the inner display while another app holds the other half.

A caution on the foldable CSS APIs

Safari 27.1 ships the Device Posture API and the Viewport Segments API as a developer preview behind feature flags, under Settings → Apps → Safari → Advanced → Feature Flags. They’re not on by default.

You’ll find tutorials recommending @media (device-posture: folded) and env(viewport-segment-width 0 0) for foldable layouts. On iOS today, that CSS won’t fire for your users. Build with widths and container queries, and keep posture detection as progressive enhancement.

For the wider picture, our guide on testing web apps covers the checks that apply on any screen.

Optimize Your Testing Today

Ready to level up your quality? From test automation services to full-scale software testing outsourcing, we help you build a product that is extraordinary.

Will My App Work on a Foldable iPhone?

It’ll run. Whether it looks right depends on which SDK you built it with.

The three SDK tiers

Apple is specific:

  1. iOS 26 SDK or earlier. Apps “run on iPhone Duo, but won’t adapt to all layouts.” Open, your app “will appear in the center of the display, with empty space surrounding the window.” Closed, the outer display shows your content to the left of the status bar and camera.
  2. iOS 27 SDK. Apps “resize to fill most of the inner display on iPhone Duo, but still avoid the status bar on the right edge.”
  3. iOS 27.1 SDK or later. Apps are “optimized for iPhone Duo” and extend to the full display — “with toolbars and tab bars appearing vertically below the status bar.”

That third point is the one teams miss. Rebuilding with the 27.1 SDK turns your horizontal bars vertical, and Apple says it outright: check your content adapts to vertical bars before you ship a 27.1 build. An upgrade meant to fix your layout can break it a new way.

Beyond the rebuild

  • Size classes. Apple’s guidance is a compact width layout for the outer display, regular width for the inner one. An app “can have any combination of size classes,” so stop assuming iPhone means compact.
  • Resize handling. Your app’s size “changes whenever the device folds or unfolds, and it doesn’t always match the size of the screen.” Re-read it on change rather than caching it, and use viewWillTransition(to:with:) for work that must run then.
  • Reserved regions. The new ReservedRegion API covers the outer camera (always present), the inner camera (present only when active) and the folding region (conditional). Combine it with safeAreaInsets.
  • Hard-coded dimensions. Search for UIScreen.main and height checks like bounds.height == 844. Apple names these as the things to remove.
  • Animation. The HIG asks you to “avoid extreme layout changes as people fold the device.” The fold isn’t an opportunity for a dramatic transition.

Testing Without the Device

Most teams won’t have hardware on day one. Three options, with honest limits:

Xcode 27.1 simulator. Apple calls it “the best way to test the full native experience,” and Device Hub lets you preview poses. It’s also what WebKit tells web developers to use. The limit is the usual one — no real touch, no real performance, no under-display camera behaviour.

Browser emulation. Chrome DevTools or a custom Playwright viewport shows you layout at 382, 669, 951 and 385px. That catches most breakpoint problems for free. It won’t show posture, and it isn’t WebKit on iOS, so it misses Safari-specific rendering.

Real-device clouds. At least one major provider added iPhone Duo soon after launch. Check availability before planning around it — inventory for a new flagship is thin, and queues are long.

Real hardware. For the camera, the hinge, fold-and-unfold under load, or 120 Hz performance, there’s no substitute. Our article about 11 tools for iOS mobile QA  covers the rest of the toolchain.

iPhone Duo Test Checklist

Layout

  1. Outer display, portrait and landscape — no clipping, no horizontal scroll.
  2. Inner display, portrait and landscape — no stranded whitespace, no stretched components.
  3. Nothing critical sits under the folding region when partially open.
  4. Controls meet Apple’s default size of 44×44 pt on both screens. Apple’s stated floor is 28×28 pt, but 44 is what the HIG recommends you design to.
  5. Typography and imagery hold up at both pixel densities — a job for pixel perfect testing.

Continuity

  1. Scroll position survives fold and unfold, both directions.
  2. Form input isn’t lost on the transition.
  3. Video keeps playing and keeps its position.
  4. Open modals, sheets, and menus stay open and correctly placed.
  5. Authentication state and in-progress flows survive.

Multitasking and input

  1. The app works in Split View at roughly half the inner display.
  2. The keyboard doesn’t cover the focused field in the partially folded posture.
  3. Dialogs and pickers stay inside the app’s window, not the full screen.

Performance

  1. Fold and unfold transitions stay smooth at 120 Hz.
  2. No crash or memory growth across repeated fold/unfold cycles — we run at least 20 in a row.

How to Test Apps on Foldable Phones

If you already test on the Galaxy Z Fold or the Pixel Fold, most of this will be familiar. The failure modes are the same: layout at two sizes, state loss during transitions, multitasking at narrow widths, and components that assume a fixed screen.

What differs is the plumbing. Android exposes folding state through Jetpack WindowManager, whose FoldingFeature reports where the hinge sits and how far the device is open. iOS has no direct equivalent — Apple’s model is reserved regions and size classes, not a posture API.

On the web, the split is the same. Chrome for Android has shipped the Device Posture API since version 157; Safari keeps it behind a flag. So one checklist covers both platforms, and only the APIs and the exact breakpoints change.

Get Your App Ready for the Fold

A new form factor means a new set of screen states to cover, and most teams find out what breaks from their users. We’d rather you found out first.

Our mobile application testing services cover foldables, along with the rest of the device matrix. Real hardware, ISTQB-certified QA engineers, and the checks above run against your build — the same mobile QA process we use on every other device.

Contact us, and we’ll tell you what your app does on iPhone Duo.

FAQs

Probably not urgently. WebKit’s position is that existing sites work as they do on any other iPhone. The real risk is a layout only ever tested at phone and desktop widths now being used at 669px and 951px. Test first — most sites need breakpoint tweaks, not a rebuild.

Yes, for layout. The Xcode 27.1 simulator covers both displays and the poses, and browser emulation at the widths above catches most responsive problems. What you can’t emulate is the physical fold under real use, the under-display camera, and true 120 Hz performance.

Ready to Speed Up the Testing Process?

We'll get back to you within 24 hours
Which services are you interested in? (Select multiple if needed or leave blank)
QA Madness
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.