Most web store advice is written for publishers with a live-ops team. This page is for the studio of one to five people wondering whether the whole thing is worth a weekend. The honest answer has a number in it.
The arithmetic
Three inputs: your monthly in-app revenue, the share you think would move to the web, and the fee gap.
| Monthly in-app revenue | 10% moves to the web | Saving per month at a 25–30% vs 3.9% gap | Verdict |
|---|---|---|---|
| $1,000 | $100 | $20–26 | Not yet; spend the weekend on the game |
| $5,000 | $500 | $105–130 | Marginal; worth it if you already have a backend |
| $20,000 | $2,000 | $420–520 | Yes |
| $50,000 | $5,000 | $1,050–1,300 | Yes, and start live ops |
The fee gap is the app store's rate (15–30% depending on tier and platform, tables) minus the web fee (3.9% on Appside). The share that moves is the unknown; 10% is a conservative first guess for a game with a community, and the first-purchase offer is what moves it (why). Tax and payment costs come off the saving too (the full cost).
The smallest version that works
Not a store with every pack. Three things:
- One payment link. Your best-value pack, opened from the game with
purchase(sku, playerToken)(payment links). No store page to design. - One reason. A first web purchase bonus on that pack.
- One channel. Wherever your players already are: Discord, a subreddit, your newsletter, the in-game shop where the rules allow it.
If that earns in month one, add the store page, more packs, a weekly offer. If it doesn't, you've spent a weekend and learned that your players don't follow links yet.
The weekend
| Time | What | With |
|---|---|---|
| Hour 1 | Paste your app link, confirm the packs, add terms and privacy | Studio |
| Hours 2–3 | Token endpoint on your backend (behind your login), signed with a key you register once | player tokens |
| Hour 4 | The purchase call in the game, the return link |
quickstart, deep links |
| Hours 5–6 | Webhook handler: verify, grant once per order ID, 200 | webhooks |
| Hour 7 | Buy a pack from your own build with the test card; see the balance move | Test purchase |
| Hour 8 | The first-purchase offer, one code for the Discord, publish | Studio |
A solo developer did roughly this for our demo game; its backend is one Node file with SQLite.
What doesn't scale down
Be honest about these before the weekend:
- A backend. Something must sign tokens and receive webhooks. If your game has no server, that's the real project.
- Tax. On the web, tax is yours; the app store handled it. For a small game in one or two countries it's a registration and a filing calendar, or you limit the store to where you're registered (tax guide).
- Refunds and support. A policy you can quote in two sentences (refunds).
- Change. A store that never changes stops earning. Even one weekly offer, set on Monday, counts.
When to wait
- In-app revenue under a few thousand a month, or no community to send.
- No backend and no plan for one.
- Your players are mostly in regions where you can't link from the game and you have no outside channel yet.
In those cases the better weekend is spent on the game. Come back when the table above says yes.
Create your store free. No card needed, nothing until a pack sells; 3.9% per successful payment when one does.