Skip to content
AppDues
Log in
Contact salesSign up

Pre-sell app subscriptions on the web before launch

Selling a subscription through a website before an iOS or Android app reaches the stores can keep more revenue, remove install friction from the first purchase, and turn early interest into paid validation. This guide explains when that approach fits, how store rules affect the in-app experience, and two ways to connect a web purchase to access inside the app.

Why pre-sell before launch

Pre-selling works best when demand already exists outside the stores. Brands launching for an existing fanbase, newsletters serving subscribers, creators with social audiences, and teams building for an established community can ask people to pay during development or before release. Three practical gains follow. First, web checkout usually costs little more than card processing, rather than the 15-to-30 percent store commission on in-app purchases; a $99 annual plan can net about $96 on the web versus as low as $69 in-app. Second, a landing page with one clear subscribe action removes the download, first-launch sign-up and paywall steps that lose people, so the same campaign can produce more paid conversions. Third, money arriving during beta both funds further work and proves willingness to pay, while early subscribers can become a feedback group. Web payment providers also tend to pay out faster and more frequently than app stores.

Examples that show the pattern

The Pump limited its closed beta to 5,000 founding annual subscribers at $99.99 a year; those places sold out within 72 hours for about half a million dollars before launch. Marvel Move offered a limited Founders Club weeks before release: $99 up front for two full years, plus private live-streams with the writers, compared with a $74.99 yearly in-app price. Fluent Forever raised almost half a million Kickstarter dollars for a language-learning app that did not yet exist, with backers redeeming perks after launch; the campaign acted as both seed funding and a waitlist. Fitness creators commonly bundle early app access with PDFs, gear or a founder bundle sold through a webshop. The shared pattern is a reachable audience, a simple promise, and a reason to buy before the app is generally available.

Good fit or probably skip

Consider pre-selling when you already have a fanbase, email list, community or creator following, and when the value is easy to grasp without trying the product, such as workout plans, meditation content, fiction writing or streaming video. Be cautious when the product is a casual game or impulse utility where people expect instant in-app gratification, when discovery depends purely on organic store search with no off-store funnel, or when Family Sharing is central, since that only works with in-app purchase. Use this as a first filter before building checkout.

Store compliance: what changes inside the app

Selling on the web is allowed; advertising that purchase path inside the app is where limits appear. For Apple, digital goods sold inside an app generally must use In-App Purchase under Guideline 3.1.1. A free companion build that lets people sign in to content paid for elsewhere can fit Guideline 3.1.3(f), like a login screen without on-device checkout. Reader apps in categories such as books, video and music may use an External Link Account Entitlement for one manage-or-create-account link opening Safari, but price mentions or persuasive web-savings language are prohibited and the entitlement disqualifies IAP products in the same app. Avoid steering inside the app: start with a neutral login and optionally a limited free preview, keep subscription wording on the website, in email or in paid marketing, and include baseline functionality such as read-only content or a demo so the app is not entirely blank without a paid account. Per May 2025, Apple had dropped anti-steering provisions for US-based users, allowing a web purchase button on paywalls for customers accessing the US App Store front. For Google Play, digital subscriptions sold inside an Android app must use Google Play Billing. Since 2023, User Choice Billing has let selected global partners present their own checkout alongside Google's, by invitation only, and the External Offers programme for the EEA lets developers show a clearly labelled link to a web purchase flow with a mandated disclosure screen and a reduced service fee. Elsewhere, the safest pattern is a login-only build with marketing driving people to the web and no overt calls to pay outside Play Billing. At the time of writing in April 2025, neither platform forbade pre-selling on the web before launch or honouring those subscriptions in the app. A review-ready companion build lets existing subscribers authenticate, offers some basic non-pay-walled functionality, and saves pricing and purchase calls for the browser or email. Policies evolve, so recheck the latest guidelines before each release; this is not legal advice.

Managed route: redemption links

Redemption links suit teams without a web app experience where people log in to access content, because they avoid building backend logic from scratch. Configure products in the managed service and connect Stripe, then embed the web SDK on the marketing site for inline purchases or use a hosted web paywall link; no user account is required at purchase time for either. A redemption link is emailed immediately after payment. In the app, handle the deep link with minimal code and the SDK: the link binds the purchase to the anonymous app_user_id and unlocks entitlements on first launch. That means a few lines of JavaScript on a self-hosted page, one deep-link listener in Swift or Kotlin supplied with the SDK, and minimal UI confirming premium status. Account creation can stay optional, with email-and-password prompted only after entitlement is active, or the app_user_id to email association can be saved after first open. Selling can start with only a managed-service account and a Stripe account, with no app or self-hosted website required. Remember that a recurring subscription starts at purchase, not at first app open.

Custom route and closing decision

A custom Stripe or Paddle stack needs a secure backend mapping purchases to user IDs, webhook handling for renewals, cancellations and charge failures, an entitlement API the app calls on every launch, and ongoing compliance covering VAT, dunning and pro-rates. The trade-off is zero managed-service fees and total flexibility against an estimated 2-4 weeks of engineering plus ongoing maintenance. Starting with a managed solution and revisiting build versus buy later is often the lower-overhead path. Pre-selling complements store distribution rather than replacing it: capture revenue early, validate demand, fund development, and arrive in the stores with a paying community instead of an empty funnel. Decide where those first subscription dollars land, and start before the next line of code if your future users are already waiting to pay.

Managed versus custom pre-sale checklist
Decision checkManaged redemption linksCustom Stripe or Paddle stack
Best whenNo web login experience exists and speed mattersYou need full control and can staff ongoing maintenance
Purchase flowInline web SDK or hosted web paywall link; redemption link emailed after paymentYour own checkout, backend and webhooks
In-app unlockDeep link binds purchase to anonymous app_user_id and unlocks entitlements on first launchEntitlement API called on every launch
Ongoing workManaged handling of renewals, failures and complianceYou handle VAT, dunning, pro-rates, renewals, cancellations and charge failures
Timing noteRecurring subscription starts at purchase, not first app openDepends on your backend design

Estimates and policy context are as captured in April/May 2025; recheck current store policies before release.

Frequently asked questions

How much do platform fees change when selling on the web?

Web checkout typically costs around a standard card-processing fee, described here as usually around three percent, compared with the 15-to-30 percent commission Apple and Google collect on in-app purchases. A $99 annual plan sold on the web nets about $96, whereas the same plan sold exclusively in-app can drop as low as $69 after store fees.

Is pre-selling on the web allowed before an app is live?

Selling on the web before launch has always been allowed and does not depend on newer external-payment rules for live apps. The restrictions concern how prominently an app itself can direct users to external payment pages, not whether you can pre-sell on the web and honour those subscriptions inside the app.

What does building the web pre-sale yourself require?

A custom stack needs a secure backend mapping purchases to user IDs, webhook handling for renewals, cancellations and charge failures, an entitlement API the app calls on every launch, and ongoing compliance for VAT, dunning and pro-rates. That route offers zero managed-service fees and total flexibility, but was estimated at 2-4 weeks of engineering plus ongoing maintenance.

When does a pre-sold recurring subscription start?

With redemption links, a recurring subscription starts when the user completes the purchase, rather than when they first open the app. Factor that timing into trial, start-date and customer messaging.