Skip to content
AppDues
Log in
Contact salesSign up

Build a slider paywall where buyers choose the price

A flexible paywall does not need a separate feature set for every amount. Create several store products at different prices, attach all of them to one entitlement, and let a slider select which product is purchased. A buyer who chooses the lowest tier and a buyer who chooses the highest tier receive the same premium access.

How the model works

The core idea is separation of price from access. Store products represent amounts, the entitlement represents premium access, and the interface maps each slider position to one product. This keeps the implementation straightforward: fetch the current Offering, sort its packages from lowest to highest price, display the selected price, purchase the matching package, then check the single entitlement.

Create the products and entitlement

Use five lifetime tiers as a concrete example: Bronze at $1.99, Silver at $4.99, Gold at $9.99, Platinum at $14.99, and Diamond at $19.99. Give each product a clear identifier following the pro_bronze_lifetime pattern, keep names and descriptions consistent because the benefit does not change, import the products into the subscription platform, create one entitlement, attach all five products to it, and place all five in one Offering.

Agent-assisted or manual setup

The same setup can be created through an MCP-connected agent or manually in the store console and dashboard. With an agent, the prompt should specify five non-consumable lifetime purchases, one Pro entitlement, identical access for every tier, permission to buy a higher tier later, and correctly linked products and Offering. Manually, create the products in App Store Connect or Google Play Console, import them, create the entitlement, attach every product, and add them to the Offering. A test store can be used when the real store connection is not available.

Connect the app and check access

Install the React Native SDK using protected module code0003, configure it at app startup with the correct public key for iOS or Android using protected module code0004, and find those keys under Project Settings and API Keys. To gate features, fetch CustomerInfo and check the Pro entitlement with protected module code0005. Because every tier grants that same entitlement, no tier-specific access branch is needed.

Build the slider purchase flow

Fetch the current Offering, sort packages by price, and map each package to one slider step. Show the selected price above the slider, purchase the selected package when the buyer taps Unlock, verify the entitlement after purchase, and provide Restore Purchases. Protected module code0006 contains the complete slider implementation, including loading, purchase, restore, tier presentation, and shared-feature display. If the selected package is unavailable, show an unavailable message instead of attempting a purchase.

Subscriptions, clarity, and later changes

The model also works with subscriptions, including a mixed approach where the lowest price is recurring and higher prices are one-time purchases. Make the total and monthly amounts unmistakable to avoid confusing buyers or risking store rejection. It is especially suitable for independent apps, creator tools, open-source projects, and products where buyers may want to support continued development at different levels.

Launch checklist

Before launch, confirm that every product is attached to the entitlement, every product appears in the Offering, slider order matches price order, the displayed price comes from the selected package, purchase verification checks the entitlement, restore works, and a buyer can later buy a higher tier. Also confirm that product names do not imply different features when the actual access is identical.

Frequently asked questions

Do different price tiers need different access logic?

No. In this design every tier is attached to the same entitlement, so the access check is identical regardless of the amount paid. The product choice changes only the price.

Can the lowest tier be a subscription while others are one-time purchases?

Yes, if the store and platform rules allow it. Keep the total price and any recurring price obvious so the offer is not confusing.

Can tiers be changed later without rebuilding the app?

Yes. Because the tiers are delivered through an Offering, you can add or remove tiers, change the default selection, or test another pricing approach without rebuilding the purchase flow.