Designing Paywalls for Both iPhone Duo Displays
The iPhone Duo gives a paywall two very different canvases. Folded, vertical room is scarce. Unfolded, a layout built for a narrow phone can stretch text and purchase buttons far wider than they should go. This guide walks through four adjustments you can make to an existing paywall in the dashboard, plus the version checks that determine whether those adjustments actually take effect on a device.
Why the same paywall behaves differently on each display
A paywall designed for a standard phone width assumes a single column of predictable proportions. On the Duo's outer screen that column has less height to work with, so fixed footers and long benefit lists compete for space. On the inner screen the opposite problem appears: components set to fill the available width keep growing, and a purchase button that looked right on a narrow phone can dominate an open display.
The fixes are not device-specific hacks. Min/max sizing controls, compact footers, multi-step flows, and native navigation each address one of those two pressures, and each applies wherever the paywall is shown.
Step 1: Cap content and button widths
Components whose width or height is set to Fill expand until they hit a limit you define. That is the lever for the open display: content fills a narrow space and stops growing once it reaches the cap.
The starting values below are a reasonable first pass, not a rule. A short headline, a long benefit list, and an image-heavy layout will each want different numbers.
Starting width values
The table below lists the elements to adjust and the settings to try first. Treat every figure as a starting point to tune against your own design.
Step 2: Reclaim space on the closed screen
The fixed footer is usually where the closed display runs out of room. Plan choices, a purchase button, supporting copy, and generous spacing can crowd out the content above them.
Read the whole screen as one unit and ask whether a customer can understand the offer, see the price, and reach the controls without strain. Tighten spacing that serves no purpose and cut copy that repeats itself, while keeping pricing, subscription details, and purchase controls legible. If the screen still feels overloaded, the next step is to change how much the paywall asks a single screen to say.
Step 3: Move benefits onto their own screen
A multi-step paywall helps when one screen is carrying several benefits at once. Introduce the benefits on an early screen, then present the subscription offer on a later one. The paywall editor lets you design each screen separately and add buttons that move customers between them; the plan selection and purchase happen on the final screen.
The Paywall AI Editor can do the split for you. Add a blank screen ahead of your existing paywall and ask the editor to move the benefits onto it. It matches your branding, writes a headline for the new screen, and relocates the benefit copy, which frees space for the offer on the last screen.
Because adding steps changes the experience, review the generated copy, the navigation, and the final purchase screen, then test the flow with your audience before publishing.
Step 4: Let the AI Editor apply the layout changes
You can also hand the whole adjustment to the Paywall AI Editor. Ask it to optimize the existing paywall for the iPhone Duo so it works on both the open and closed displays. It can make the layout edits for you, fitting content to the outer screen and using the extra room on the inner one.
A simple prompt is enough to start: "Optimize this paywall for iPhone Duo so it looks good on both the open and closed displays." Review what changed, preview both configurations, and refine with follow-up prompts if you want a tighter footer, narrower content, or more room for benefits.
Step 5: Keep the close button where iOS expects it
If your paywall lets customers dismiss it without subscribing, check where the close button lands on the Duo. Depending on the display, the orientation, and how your app presents the paywall, iOS may move navigation controls to the side. A close button drawn inside your paywall will not follow them automatically.
To hand placement to iOS, select the button in the Paywall Editor and turn on Use system navigation in its properties. That swaps your close button for a native iOS close control. On a multi-step paywall, review the close and back buttons on every screen and enable the setting where it makes sense, then test the flow on both displays.
Verify the whole experience
Test the paywall closed, open, and rotated, using the same presentation your app uses. Check for readable content with clean wrapping and no clipping, balanced widths on the open display, footers that leave room for the rest of the screen, accessible close/back/continue/purchase controls, and complete navigation through every step to the final offer.
Also confirm which SDK version your app ships. Multi-step paywalls need iOS SDK 5.83.0 or later; older versions show only the final screen. Min/max sizing needs 5.93.0 or later; builds on older SDKs drop the limits. Requirements for other frameworks are covered in the SDK documentation.
A worked example
Take a single-screen paywall with a full-width background, a content stack holding a headline and five benefits, and a fixed footer with three plan options and a purchase button.
First, set the content stack to Fill with a maximum width near 600pt, centered in its parent, and the purchase button to Fill with a maximum near 400pt. On the open display the text and button now sit in a comfortable column instead of spanning the full width. Second, trim the footer: shorten the supporting copy and reduce spacing so the plan options and purchase button still fit on the closed screen. Third, if five benefits still crowd the closed view, add a blank screen before the paywall and ask the AI Editor to move the benefits there, leaving the offer and purchase controls on the final screen. Fourth, enable Use system navigation on the close button so iOS can place it correctly when the display changes.
Finally, preview folded, open, and rotated, and confirm the SDK version supports both multi-step flows and min/max sizing.
Adjustment-to-setting map
Use this map to connect each reader-facing adjustment to the exact control or threshold that governs it.
| Element | Setting to try |
|---|---|
| Background container | Keep it full width |
| Main content stack | Fill, maximum width around 600pt, centered within its parent |
| Purchase button | Fill, maximum width around 400pt, centered within its parent |
Starting values to adjust for your design; short headlines, detailed benefit lists, and image-heavy paywalls may need different widths.
| Adjustment | Exact control or threshold |
|---|---|
| Cap component width | Min/max sizing, which works with Fill rather than Fit or Fixed |
| Min/max sizing on iOS | SDK 5.93.0 or later; older SDKs ignore the limits |
| Multi-step paywall on iOS | iOS SDK 5.83.0 or later; older versions display only the final screen |
| Close button placement | Use system navigation in the button's properties |
Version thresholds are exact requirements; confirm the SDK version shipped in your app before relying on these behaviors.
Frequently asked questions
Does min/max sizing target the iPhone Duo specifically?
No. The limits apply wherever the paywall appears. Content fills a narrower space and stops growing in a wider one, so you do not need a Duo-specific configuration.
Which sizing mode does min/max sizing work with?
Only components sized with Fill respond to the limits; Fit and Fixed do not. On iOS the feature also requires SDK 5.93.0 or newer, and builds on older SDKs drop the limits entirely rather than approximating them.
Why does my multi-step paywall show only the final screen?
Seeing only the last screen usually means the bundled SDK predates multi-step support. The flow requires iOS SDK 5.83.0 or newer; on anything older, the app shows just the final screen and skips the earlier steps. Check the version in your build before debugging the design.
How do I stop a close button from being misplaced when the display changes?
Select the button in the Paywall Editor and enable Use system navigation in its properties. That replaces the in-paywall close button with a native iOS close control that iOS can place correctly. On multi-step paywalls, review close and back buttons on each screen.