PWA vs native app for a party game — what 6 months of data say about retention

We launched Party Challenges as a PWA six months ago. A browser-based 18+ party card game — 1,000+ cards, multiple game modes, no app store listing.

The question we keep getting: why not just ship a native app?

After half a year of real usage data, here's the honest comparison from inside a consumer micro-game. No theory — just what we measured.

The setup

Party Challenges runs on Lovable + Supabase. Pure web stack, installable as a PWA. No React Native wrapper, no Flutter bridge, no App Store or Play Store listing. Players open a URL, pick a deck, and play.

We also run two sister games on the same stack — Scary Challenges and Here We Ask — so the patterns repeat across three products.

Distribution: PWA wins clearly

Party games spread through group chats. Someone texts a link, everyone opens it.

With a native app, that flow breaks: tap link → app store → install → open → find the game → wait for everyone else to do the same. For a spontaneous party game, that chain kills conversion.

With a PWA, it's: tap link → playing. The URL is the distribution. Share it in WhatsApp, iMessage, Discord — everyone's in within seconds.

For our category, this difference is massive. Most sessions start because someone shares a link mid-conversation. A store listing adds friction at the worst possible moment.

Install conversion: native wins on signal, PWA wins on speed

Native apps have a clear "install" action. Users commit. That commitment creates a psychological anchor — the app sits on their home screen, they feel ownership.

PWAs have "Add to Home Screen," but almost nobody uses it unprompted. The install rate for our PWA prompt sits in low single digits. Most users just bookmark or re-open from their chat history.

The trade-off: native gets a stronger install signal but loses all the users who won't install anything for a 20-minute party game. PWA captures the casual majority but loses the retention anchor.

Re-engagement: native wins on mechanics

This is where native pulls ahead. Push notifications, badge counts, home screen presence — native has built-in re-engagement loops that PWAs can only approximate.

Our PWA re-engagement relies on: someone sharing the link again, organic search (SEO brings people back for "party card games"), or the rare Add-to-Home-Screen user opening the icon.

Native apps can send a "Your friends played last weekend — new deck dropped" push and pull users back. We can't. For a party game that's inherently episodic (play once every few weeks), this gap matters.

Performance: tie

This surprised us. We expected native to feel faster — especially for card animations and deck loading.

In practice, a well-built PWA on modern phones is indistinguishable from native for our use case. Card transitions run smooth, deck loading is near-instant (Supabase edge functions), and offline support works via service worker.

The performance gap that existed five years ago has largely closed for content-display apps. If you're building a 3D game or heavy computation app, native still wins. For card games? No difference users can feel.

Monetization: PWA wins on margin

Party Challenges runs a Premium tier that unlocks After Dark content. One-time purchase, no subscription.

As a PWA, we process payments through Stripe. Zero platform cut beyond standard card processing fees.

A native app on iOS would cost 15–30% of every transaction through Apple's in-app purchase system. On our price point, that's the difference between a sustainable margin and a rounding error.

For micro-transactions in a consumer game, the store cut is disproportionately painful. PWA lets us price aggressively and keep the economics simple.

The verdict for party games

| Dimension | PWA | Native | Winner |
|-----------|-----|--------|--------|
| Distribution | Share URL → instant play | App store funnel | PWA |
| Install signal | Weak (Add to Home Screen) | Strong (app icon) | Native |
| Re-engagement | Relies on re-share / SEO | Push, badges, home screen | Native |
| Performance | Smooth (modern browsers) | Smooth | Tie |
| Monetization | Stripe, no platform cut | 15–30% store tax | PWA |
| Time to market | Ship today | App review + deploy cycle | PWA |

Net assessment: PWA wins on acquisition and monetization. Native wins on retention mechanics. For a party game where most sessions are spontaneous (someone shares a link at a gathering), acquisition speed matters more than retention mechanics.

The honest number: our repeat-visit rate would likely be higher with native push notifications. But we'd never have reached those users in the first place — the app store install funnel would have filtered them out.

What we'd do differently

If we were starting today with unlimited resources, we'd ship PWA first (capture the viral loop), then add a native wrapper later purely for push notifications and home screen presence. The web version stays the canonical product; the native app is a retention layer on top.

But with limited resources? PWA-only is a net positive. The distribution advantage outweighs the retention gap for games that spread through group chats.

Building Party Challenges — a free 18+ browser party card game. Also shipping Scary Challenges, Here We Ask, and 13 other products at Inithouse.