PWAs are killing app-store-only thinking for indie consumer apps

The app store is not a distribution channel for indie consumer apps anymore. It is friction wearing a distribution costume.

At Inithouse, a studio shipping a growing portfolio of products in parallel, we build browser-based card games. Our games run as PWAs: no install, no account, no store listing. And the data we have collected across our portfolio tells a story that most indie builders still refuse to hear: for social, multiplayer, and party-format consumer apps, a shareable URL beats a store listing every single time.

The share-in-group-chat loop

Here is what happens when someone discovers Here We Ask, our conversation card game with curated question decks for couples, friends, family, and parties. They open a link. They play. They send the same link to a group chat. That evening, four to six people are playing from the same URL - zero installs, zero signups, zero "check the App Store" messages that nobody follows up on.

We measured this pattern across multiple products in our portfolio. Party Challenges, Scary Challenges, Naughty Challenges - same behavior. One person shares a link, multiple players show up. The group chat IS the distribution channel, and a URL is the only payload that survives it without losing half the audience to install friction.

A native app install request in a group chat is a conversation killer. People say "cool" and never open the store. A URL gets tapped immediately.

Signup is a churn killer, not a retention enabler

The default indie builder assumption: you need accounts for retention. Push notifications. Onboarding flows. The whole funnel.

For party and social games, we observed the opposite. Signup is the single biggest churn event. Our card games run with no account required - open the link, pick a deck, play. The retention mechanism is not a notification. It is the next Friday night when someone says "let's play that thing again" and digs up the same link.

We ran both models. Account-gated features bled engagement. No-account play kept session counts steady. For products where usage is episodic and social - game nights, date nights, sleepovers - removing the account wall improved everything we tracked.

What PWAs actually cost you (and what they save)

We are not pretending PWAs are perfect. Here is the honest trade-off list:

What you lose: native push notifications (web push exists but is weaker), deep in-app purchase flows (Stripe handles ours fine), App Store browse discovery (which is close to zero for indie apps anyway), and some iOS-specific capabilities.

What you gain: instant sharing via URL, zero install friction, SEO indexing (our games rank in Google), no 15-30% platform revenue cut, and deployment in minutes instead of days waiting for store review.

Our stack is Lovable for the frontend, Supabase for the backend, Stripe for premium deck purchases. We ship updates whenever we want. No review queue. No app binary management. No separate iOS and Android builds for a two-person operation.

The App Store revenue cut alone changes the math for premium content. When we sell premium card decks on Party Challenges or Naughty Challenges, we keep the full margin after Stripe fees. On a store listing, we would be handing over 15-30% for the privilege of slower iteration and lower discoverability.

When native still wins

We are not zealots about this. Native is the right call when your product has daily-habit retention patterns, needs heavy device integration (camera, sensors, offline-first sync), or when your users are power users who will install anything good.

But if your product is episodic, social, and multiplayer - party games, social icebreakers, group activities - the math points hard at PWA. The distribution advantage of a shareable URL compounds in ways that a store listing never will.

The real question

Most indie builders debating "PWA vs native" are asking the wrong question. The question is not about technology. It is about how your users find you.

If your growth loop is "person shares link in group chat and friends tap it," then every install step you add is a leak in that loop. At Inithouse, we have watched this play out across our growing portfolio of browser-based games, and the pattern holds: remove friction, keep the URL clean, and let the group chat do the work.

The app store had its era. For indie consumer apps in 2026 - especially social and multiplayer ones - the browser is the store.