Skip to content
AppDues
Log in
Contact salesSign up

Selling one-time packs on web without building a second payments stack

A daily music puzzle built for the browser faced a familiar split: mobile players could buy through app stores, while roughly a third of its audience stayed on desktop and would not install an app.

Adding a web checkout for one-time packs — with entitlements synced across platforms — turned that desktop-only group into paying players, without a solo developer having to build and maintain separate mobile and web payment infrastructure.

The approach: one codebase, one catalogue, web checkout added

For a one-person team, running separate payment systems for mobile and web was not sustainable. The solution used a ready-made Web Billing SDK instead of custom infrastructure: a secure, customisable checkout on the web for one-time packs, with purchases automatically synced across iOS, Android and web. The SDK was plugged into the existing React Native codebase, keeping one unified catalogue and entitlement system. Mobile players kept using familiar app-store flows; desktop players got a checkout designed for the web. One-time purchases across app stores and Stripe were handled with entitlement syncing, and global management — from syncing to refunds — did not require custom infrastructure.

Reported results

Reported results from this example: 30% more players unlocked by enabling desktop purchases; 60-65% checkout completion on web, described as well above industry averages; and one unified codebase for web and mobile, saving hours of engineering time. The web channel was described as incremental — a route to revenue that would otherwise have been missed entirely, rather than a replacement for mobile.

What came next

With billing and entitlements handled by a single partner, the developer could spend time on gameplay instead of infrastructure. Planned next steps included multi-pack bundles to simplify repeat purchases and social features such as playlists and score-sharing. As the game expands globally, the same cross-device purchasing is intended to let players buy packs seamlessly wherever they play.

Decision checklist: should you add web checkout?

Use this as a checklist when deciding whether web checkout fits your game:

  • Is a meaningful share of your audience on desktop or browser-only devices who will not install your app?
  • Do you sell one-time items (packs, unlocks) as well as, or instead of, subscriptions?
  • Can you keep one catalogue and entitlement system across app stores, web and Stripe?
  • Will a purchase on one platform be recognised on the others without manual support work?
  • Does your team size make building and maintaining a separate web payments stack unrealistic?
  • Have you planned how refunds and entitlement changes will be handled centrally?

If most answers are yes, a web billing channel is likely to be incremental revenue, not duplicated effort.

ConfigureTargetTest
Mobile vs web purchasing in this example
Mobile app storesWeb checkout
Where the player paysIn-app purchase flowBrowser checkout for one-time packs
EntitlementsSynced across platformsSynced across platforms
CodebaseShared React Native codebaseSame shared codebase and catalogue

Illustrative comparison based on the example workflow; confirm current store and processor terms before implementation.

Frequently asked questions

Why not require desktop players to use the mobile app?

No. The desktop audience was already playing in a browser and did not want to install the mobile app, so a web checkout was needed to convert them.

How was the work kept manageable for a solo developer?

A single React Native codebase and one catalog/entitlement system were used, with app-store flows on mobile and a web-optimised checkout on desktop, both powered through the same billing partner.

What happens if someone buys on web and then plays on mobile?

Purchases were synced across iOS, Android and web so a player who bought on one platform had the same access on the others.