Paywall Builder Changelog: What Changed and When to Use It
A component-based paywall builder lets a team assemble, localize and test an in-app paywall without shipping a new app build. The capabilities below are described as they appear in the upstream product's own release notes; treat them as a parity description rather than a claim about any specific deployment. The goal here is a decision aid: which capability solves which problem, and what to check before you rely on it. Product naming and release timing are owner-confirmed inputs, not asserted here.
Editor layout and editing workflow
The editor moved from a dual-panel arrangement to a sidebar layout. Components, layers, branding, media and localization sit in labeled tabs, while the canvas stays central. The practical benefit is that the workspace has room to grow without crowding the design area.
Editing speed improved in two ways. Figma-style keyboard shortcuts cover moving, duplicating, selecting and deleting components, and an in-editor help icon lists the supported commands. Separately, components can now be copied between paywalls, not only within one. Structure, styling and bindings travel with the paste, which helps when several campaigns share a hero section, benefit list or pricing block.
Draft protection runs quietly in the background. Every change is written continuously, so closing the tab or reloading the page is far less likely to wipe out an unfinished layout. Because saves happen so often, validation problems also show up sooner rather than at the end. What does not change is the release gate: a draft stays a draft until you deliberately publish it. Background saving protects work in progress; it is not a release switch.
Branding, media and localization controls
A dedicated Branding tab centralizes saved colors, gradients and custom fonts so they can be reused across every paywall in a project. Branding assets appear directly in color and typography pickers during editing, which reduces one-off values and lets a team standardize styles once.
The Media gallery shows all uploaded assets in one place, supports drag-and-drop upload, and lets you preview and clean up files. Existing assets can be reused instead of re-uploaded, which matters when many paywalls share campaign artwork.
Localization gained a safety net. Edit a string in the default language and the editor works out which translations have fallen behind, then shows a warning badge in the sidebar with the specific locales and fields involved. From that list you can bring the translations up to date in one click, or dismiss the warning when the difference is intentional. The point is to keep translated copy from lagging behind the source text without anyone noticing.
Exit offers, countdowns and plan sheets
An exit offer gives a dismissing user a second chance. When someone closes a paywall without buying, you can send them to a second paywall with a different offer rather than ending the flow on the spot. Typical uses are a different billing option, a lower price, or a final reminder before the user leaves. Exit offers cover iOS, Android and hybrid SDKs, and they slot into existing paywalls and experiments.
A countdown component adds a timer to any paywall. You set an end date once and the timer updates automatically, with no extra code or manual updates. It suits campaigns such as Black Friday, launch promos or limited-time discounts where timing helps a decision.
Sheets give a button a destination for additional content. Choose a sheet as the button's target and a Sheet component shows up nested inside that button in the Components panel. Select the sheet, or anything within it, and the paywall preview displays it. You fill the sheet with components exactly as you would any stack, and since a sheet can carry its own packages and purchase buttons, a customer can buy straight from the options it shows.
Design handoff, previews and templates
Figma mockups can be exported directly into the editor, arriving as native components. Once imported, the layout is editable in the ways that matter for shipping: rewrite copy while the structure stays put, point it at different products and packages, translate the text, attach experiments, and scope it to chosen audiences. The gain is speed. Designers keep working in Figma, and the team running paywall tests can take a finished mock to a live variant without rebuilding the layout by hand.
Previewing now covers a wider set of iOS and Android phones and tablets, with the canvas updating to real screen sizes. Walk the layout on each target device and check the things that break first: whether the call to action lands where you want it, how the page scrolls, where images are cropped and media placed, whether type sizes hold up, and any spacing that looks off.
Template filtering by purchase method, tier or package helps when you already know the pattern you want, such as a trial-first layout, a pricing grid or a promo-ready design.
Real prices, AI drafts and video
The editor previously showed placeholder product prices. It now displays real prices, which gives a more realistic view while you work. One condition applies: the product must have been seen in at least one test purchase before its price will display. A worked example: if you add a new annual plan to a paywall and the editor still shows a placeholder, that plan has not yet been through a test purchase — run one, then reopen the paywall to see the actual price.
AI can generate a paywall from an app store page, useful as inspiration or a starting point to adjust and test. Videos can be added as their own component, like images, and can also be set as backgrounds on the root paywall, the footer, or any parent component such as stacks and packages.
On native iOS and Android SDKs, a method now intercepts purchase intent when the purchase call to action is tapped, so a custom UI can appear before the purchase flow continues. Documented uses include an age gate or parental consent screen, and disclosures such as country-specific terms or legal language that a customer must confirm.
A checklist for choosing what to adopt
Use this to match a capability to a concrete need before changing a live paywall.
- Reusing layouts across campaigns? Copy components between paywalls so structure, styling and bindings carry over.
- Managing many locales? Rely on the out-of-date translation badge, and dismiss it only when a default-language change is deliberate.
- Losing work mid-edit? Confirm drafts are auto-saving, but remember publishing is still a separate, deliberate action.
- Running a time-limited promo? Set the countdown end date once and let the timer update itself.
- Offering an alternative at dismissal? Configure an exit offer as a second paywall rather than ending the flow.
- Showing accurate prices in the editor? Make sure each product has at least one test purchase recorded first.
- Presenting extra terms or an age gate? Use purchase-intent interception on native iOS and Android SDKs.
- Letting users compare plans? Route a button to a sheet with its own packages and purchase buttons.
Frequently asked questions
Does auto-save publish my paywall?
No. Drafts are saved continuously in the background, but publishing behavior is unchanged: nothing goes live until you choose to publish. Auto-save protects work in progress and surfaces validation issues earlier.
Why does a product price still show as a placeholder in the editor?
Real prices display only after the product has been seen in at least one test purchase. Until then, the editor cannot show the actual price for that product.
Can a sheet complete a purchase on its own?
Yes. A sheet can hold its own packages and purchase buttons, so customers can buy directly from the options displayed inside it.
Where can videos appear on a paywall?
Videos can be added as a standalone component, like an image, and can also serve as backgrounds on the root paywall, the footer, or any parent component such as stacks and packages.