iPhone Duo paywall guide: fold-ready layout, close button and shipping checks
iPhone Duo changes the shape of the screen your paywall appears on. Closed, it is a compact phone; open, it is closer to a small tablet; half-folded, the hinge can cut through the middle of your layout. This guide turns those posture changes into a concrete paywall checklist: what to preview, which controls to switch to system navigation, how to present the paywall in a sheet, how to stop content stretching on the inner display, and what to verify before submitting.
What iPhone Duo changes for a paywall
iPhone Duo is Apple's first foldable iPhone. It has a passport-like shape when closed and opens like a book to roughly iPad Mini size. The practical consequence for a paywall is that one screen must serve two very different widths: a 5.4-inch outer display and a 7.6-inch inner display, plus portrait, landscape, partially folded and Split View states.
Apple's Human Interface Guidelines frame this as designing for compact width outside and regular width inside. A paywall presented in a sheet inherits much of that adaptation from iOS, but only if the paywall is built and presented in a way that lets the system do its job. The main risks are a close button that ends up in the wrong place, content that stretches too wide on the inner screen, and prices or call-to-action controls that sit on the fold when the device is partially open.
Postures, risks and the right response
The hinge API reports three main states: .closed, .partiallyOpen and .fullyOpen. On top of those come portrait and landscape orientation, plus ways of setting the phone down. Treat each combination as a layout test rather than a single device size.
The table below is a reader checklist, not a substitute for testing in the simulator. Use it to decide what to inspect first in each posture.
Apple's guidance applied to a paywall
Apple published a Human Interface Guidelines page for iPhone Duo and accompanying tech talks. None of it is written specifically for paywalls or StoreKit, but several general rules map directly onto paywall behavior.
First, avoid extreme layout changes as the device folds and keep the same functionality across postures. For a paywall, that means the same packages, prices, trial terms and call to action whether the phone is open or closed. Second, put navigation controls where people expect them: on Duo, the vertical strip on the side, with Back and Close at the top of that axis. Third, keep tappable elements off the fold. When the device is partially folded, iOS slides sheets out of the fold for you, so a paywall presented in a sheet is covered. If you present full screen, the fold runs through the middle of the layout; Apple suggests an even number of columns so nothing straddles the fold, which means two package cards side by side work better than three.
Sheet placement is the last piece. On the inner display, iOS centers a sheet unless you redirect it: presentationPlacement(_:) lets you anchor it to the leading or trailing edge instead. On the outer display, a sheet that carries only one button can skip the vertical bar and settle just before the camera cutout.
Adapting an existing paywall: five steps
The setup below uses features that are live in the paywall system. It does not require waiting for a new foldable-specific release.
- Preview in the paywall editor. The editor includes an iPhone Duo preview. Switch between open and closed, portrait and landscape. The preview matches the Duo's screen shape, safe areas and camera, and shows the paywall as it appears in an app built with Xcode 27.1. Use it to catch obvious problems before opening Xcode.
- Build with Xcode 27.1 and open the Duo simulator. Choose iPhone Duo in Device Hub and use the simulator controls to open, close, rotate and fold the device. Walk the paywall through every posture before changing anything, so you know what is actually broken. Make sure the simulator runs iOS 27.1, not iOS 27. If you present PaywallView in SwiftUI, Xcode Previews can help too: the canvas overrides picker has a Display group for previewing content on the device's other display.
- Present the paywall in a sheet. Presenting in a sheet lets iOS handle several Duo behaviors: the inner display centers the sheet by default, and a partially folded device slides the sheet clear of the hinge. The simplest option is the presentPaywallIfNeeded modifier, which checks the entitlement, presents the paywall in a sheet and dismisses it once the entitlement is active. On iPad it shows the paywall in a modal that is roughly iPhone-sized. For more control, present PaywallView yourself in a .sheet and check the close button placement as described above.
- Give content a maximum width. On the open inner display, a paywall built for a phone can stretch edge to edge. Set the main content stack to Fill, then give it a Max width so it stops growing on wide screens. Min/max sizing needs purchases-ios 5.93.0 or later; older SDKs ignore the limits. The Paywall AI Editor can also be asked to make a paywall look good on iPhone Duo.
- Run the checklist before shipping. Test every posture and confirm the items in the checklist below.
Shipping checklist
Before you submit, walk the paywall through every posture and confirm each item:
- Close is reachable and does not collide with the camera or the side bar.
- Close and Back appear as system controls, in the side bar on the closed display.
- The call to action is visible without scrolling on the closed, landscape screen, or you have deliberately accepted the scroll.
- Nothing tappable, and no price or trial term, sits on the fold when the device is partially folded.
- The inner display in landscape does not look stretched.
- Selecting a package, folding and unfolding preserves the selection.
- The paywall still looks right on a regular iPhone and iPad.
For App Store submission, iPhone Duo-optimized apps can be submitted now. Starting April 2027, any app submitted will need to include iPhone Duo screenshots, so capture the app on both displays. App Store Connect also has a preview tool that shows how screenshots and the product page look on iPhone Duo before submission.
Why native rendering helps on a foldable
The paywall system renders natively on iOS, and PaywallView is a regular SwiftUI view. That is why the steps above work with Apple's own tools: the paywall is presented in a system sheet, its close button can be swapped for the system control, and iOS can move the sheet out of the fold. A paywall that was not built for the device is noticeable to someone who has just unfolded a new phone; the checklist is designed to catch that before release.
| Posture | What can go wrong | Response |
|---|---|---|
| Closed, portrait | Close button may collide with camera or side bar; call to action may require scrolling | Use system navigation; check the closed landscape screen for CTA visibility |
| Closed, landscape | CTA may fall below the fold | Confirm CTA is visible without scrolling or accept the scroll deliberately |
| Fully open, portrait | Content may stretch edge to edge | Set main content stack to Fill with a Max width |
| Fully open, landscape | Layout may look stretched | Verify max width and inspect in the Duo preview and simulator |
| Partially open | Tappable elements or price terms may sit on the fold | Present in a sheet so iOS slides it away from the fold; keep prices and controls off the fold |
| Split View | Paywall may be compressed beside another app | Check the paywall in Split View and confirm the CTA and close control remain reachable |
This table is a reader checklist derived from the guide's posture and layout guidance. It is not a substitute for testing on the simulator or a physical device.
Frequently asked questions
How do I make the paywall close button work on iPhone Duo?
Select the close button in the paywall editor and turn on Use system navigation. This requires purchases-ios 5.98.0 or later. iOS then places the system Close control in the vertical side bar on iPhone Duo and in the navigation bar on iPhone and iPad. If you use presentPaywallIfNeeded, the SDK provides the navigation bar. If you present PaywallView yourself in a sheet, the SDK adds Close to your existing navigation bar; if there is no navigation bar, wrap PaywallView in a NavigationStack. In UIKit, PaywallViewController adds its controls to the presenting navigation controller.
Can I keep my own designed close button instead of the system control?
Yes. If you are on an older SDK or a hybrid SDK, or you leave Use system navigation off, your designed close button stays inside the paywall. You can opt the sheet out of the vertical bar with toolbarVerticalBehavior(.disabled). Apple describes the vertical bar as the default and says opting out works well for sheets with only a single toolbar button, so treat it as a stable choice rather than toggling it on and off. A custom close button positioned in your own code stays exactly where you put it, which on the outer display can put it next to the camera or the side bar; check the Duo preview and the simulator and move it if it collides.
Should I present the paywall in a sheet or full screen on iPhone Duo?
A sheet does a lot of the adaptation for you. On the inner display the system centers it by default, and when the device is partially folded the sheet slides away from the fold. If you present full screen, the fold runs through the middle of the layout; Apple suggests an even number of columns so nothing straddles the fold, which means two package cards side by side work better than three.
When do I need iPhone Duo screenshots for App Store submission?
You can submit iPhone Duo-optimized apps now. Starting April 2027, any app you submit will need to include iPhone Duo screenshots, so capture the app on both displays. App Store Connect also has a preview tool that shows how screenshots and the product page look on iPhone Duo before submission.