Skip to content
AppDues
Log in
Contact salesSign up

Paywalls builder: native, remotely deployable paywalls

A paywall is the screen where a download becomes a subscriber, so small design and copy changes can matter. The Paywalls builder is built around a component library, more variables, and a draft-to-publish workflow. This guide explains what the builder offers, what stays the same, and how to move from template or blank canvas to a live, testable paywall.

What the Paywalls builder offers

The builder centers on layout freedom and configuration depth.

  • Fully customizable layouts. A library of UI components — text, images, buttons, stacks, and more — lets you compose a layout that matches your branding instead of only editing a fixed template.
  • More flexibility. More variables, every string localizable, and the ability to set unique values based on a customer's introductory offer eligibility.

For inspiration, Paywalls.com lets you filter real paywall screens by UI element, app category, and trending or top-growth paywalls.

What stays the same

The builder keeps the properties that make Paywalls useful:

  • Native on-device rendering. Paywalls are built with 100% native code, so the screen feels and performs like the rest of your app.
  • Remote control. You can deploy changes without shipping an app update for each one.
  • Templates. The template list is larger than before and is described as continuing to grow. Use a template as a starting point or publish it as-is.
  • Experiments and Targeting. Paywalls still work with Experiments and Targeting, so you can deploy or test with a subset of your audience to measure impact.

In short: the design surface is flexible; the delivery and measurement model stays the same.

From idea to live paywall: the three-stage workflow

The builder follows a simple sequence. Treat each stage as a checkpoint before moving on.

  1. Choose your approach. Start from a template in the library or create a paywall from scratch. Template-first is faster when a layout already fits; blank-canvas is better when branding or structure is unusual.
  2. Add and configure components. Customize existing components or add new ones, then set size, spacing, color, and other properties. Because every string is localizable and variables can respond to introductory offer eligibility, this is also where you tailor copy per audience.
  3. Save and publish. Save drafts at any time to return later or share with your team. When ready, click Publish Changes to make the paywall available in supported SDK versions.

A useful distinction: saving a draft does not put anything in front of users; publishing does. And publishing a paywall change is a remote deployment, not an app-store release — but it still only reaches supported SDK versions.

Pre-publish checklist

  • Confirm the paywall is built on a supported SDK version before expecting it to appear.
  • Decide whether this paywall will run as a full rollout or a targeted/experiment subset.
  • Check that every string that needs translation has a localized value.
  • Verify any introductory-offer-eligibility variants render correctly for eligible and ineligible customers.
  • Save a draft, share it with the team, then publish deliberately rather than as a side effect of editing.

Worked example: a reading-app paywall

Imagine a reading app that wants a paywall matching its serif-heavy brand. The team starts from a template with a headline, feature list, and subscribe button. They replace the default text component with branded copy, add a stack to group the feature list, and set a variant of the headline for customers eligible for an introductory offer. They save a draft, share it with a marketer for review, then publish. Because the paywall renders natively and is remotely controlled, the change reaches supported SDK versions without an app update. They then run it through Experiments with a subset of the audience before a wider rollout.

Frequently asked questions

Do published paywall changes require an app update?

No. Paywalls are remotely controllable, so you can deploy changes without an app update for each one. Published changes are available in supported SDK versions, so confirm your SDK version before expecting a change to appear.

What is the difference between saving a draft and publishing?

Saving keeps your work in a draft state so you can return later or share it with your team. Publishing — via Publish Changes — makes the paywall available in supported SDK versions.

Can a paywall show different values to customers eligible for an introductory offer?

Yes. The builder supports setting unique values based on a customer's introductory offer eligibility, alongside more variables and localizable strings.

Can I test a paywall with only part of my audience?

Yes. Paywalls support Experiments and Targeting, so they can be deployed or tested with a subset of your audience to measure impact.