Skip to content
AppDues
Log in
Contact salesSign up

Paywall builder updates: faster design handoff, quicker editing and clearer promo proof

This release roundup covers six changes to the paywall builder, all aimed at shortening the distance between a finished design and a live, tested paywall. Below is what each change does, when it helps most, and how to sequence adoption so the team gets value without reworking its whole workflow.

Figma designs become editable paywall components

The headline change is a direct path from a Figma mockup into the paywall editor. Imported layouts arrive as native paywall components rather than a flat picture, which means the structure stays editable after import. From there the team can rewrite copy without disturbing layout, swap products and packages, translate text, attach experiments, and target specific audiences.

The practical effect is on handoff. Instead of a designer finishing a mock and an engineer rebuilding it by hand, the layout crosses over and the work shifts to content, offers and testing. Treat the import as a starting point rather than a finished paywall: confirm that packages map to the intended products and that localized strings read correctly before publishing a variant.

Keyboard shortcuts keep editing in flow

The editor now responds to keyboard shortcuts for the actions used most often: adding components, duplicating sections, undoing and redoing, and deleting blocks. The benefit is cumulative — small pointer trips add up during a rapid iteration cycle, and removing them makes a fast editing session feel fast rather than merely busy.

If your team builds paywalls in short bursts between other work, learn the shortcut set once and share it in the team's onboarding notes. The gain is largest for people who duplicate a section and then adjust copy repeatedly.

Preview across more phones and tablets before publishing

Paywalls can look right on one screen and wrong on another, and previously that mismatch often surfaced only after release. The canvas now previews a wider set of iOS and Android phones and tablets at real screen sizes, so a designer can step through devices in seconds.

Use the preview pass to check four things in order: spacing, font sizes, image crops and media positioning, then scroll behavior and where the call to action lands. Running this sequence before publishing catches the layout defects that otherwise turn into last-minute fixes.

Template gallery filters narrow the starting point

The template gallery can now be filtered by purchase method, tier or package. This matters when the team already knows the pattern it wants — a trial-first layout, a pricing grid, or a design prepared for a promotion — and would otherwise spend time scrolling to find it.

A useful habit is to pick the pattern before opening the gallery, then filter to match. That keeps template selection a decision about offer structure rather than a visual browse.

A countdown component for time-boxed offers

Any paywall can now include a countdown timer. Set the end date once and the timer updates on its own, with no extra code and no manual refresh. It suits campaigns where a deadline genuinely helps someone decide: seasonal sales, launch offers, limited-time discounts.

Because the timer is driven by a single end date, the main control to get right is that date, including the time zone your audience will read it in. Pair the timer with an offer that actually ends when the timer ends; a deadline that does not correspond to a real change in the offer undermines the trust the rest of the paywall is building.

Share verified performance metrics with a visibility choice

Verified performance metrics from a project can now be shared publicly. The publisher of the profile chooses what is visible: the profile can be published with project details, or anonymized entirely. The numbers come from the project itself rather than from a separate spreadsheet.

That makes the feature useful when results need to be shown to partners, investors or a community. Before publishing, decide deliberately between the identified and anonymized options — the choice is the control that determines how much context travels with the numbers.

A practical order for adopting the changes

Teams that iterate heavily on paywall design will get the most immediate return from the Figma import and the wider device previews, because those two remove the largest chunks of rework. Add the keyboard shortcuts next; they cost little to learn and speed up every later session. Reach for the countdown component when a time-boxed promotion is already planned, and use template filters whenever a new paywall starts from a known pattern. Metric sharing is a separate decision from building — treat it as a publishing choice rather than an editing one.

A short checklist before each launch: imported layout verified against real products, copy and translations checked, device preview pass completed, template pattern confirmed, countdown end date and time zone set, and metric visibility chosen if a profile will be shared.

Frequently asked questions

Does an imported Figma design stay editable after it reaches the paywall editor?

Yes. The layout arrives as native paywall components, so copy can be edited without changing the structure, and products, packages, localization, experiments and audience targeting can be applied afterward.

Does the countdown timer need manual updates during a campaign?

No. You set the end date once and the timer updates automatically, with no additional code required.

Can shared performance metrics hide the project identity?

Yes. When publishing a metrics profile you choose between showing project details and anonymizing the profile entirely.