Installation and Distribution Models
You'll learn: How PWA distribution differs fundamentally from traditional app store models and why this matters for reach and control.
Two Different Worlds
When you build apps, you have two primary distribution paths: app stores (like Apple's App Store or Google Play) and browser-based PWA installation.
App Store Distribution
App stores act as gatekeepers. You submit your app for review, wait for approval (sometimes days or weeks), and pay fees (often 15-30% of revenue). Users must:
- Search the store
- Tap "Install"
- Wait for a multi-megabyte download
- Grant permissions upfront
Analogy: Like selling products in a mall—you get foot traffic and trust, but pay rent and follow strict rules.
PWA Browser Installation
PWAs are discovered through the web—via search engines, links, QR codes, or social media. When users trigger the install prompt (the one you captured in lesson 2356), the app adds to their home screen immediately—no store approval, no download wait. You control:
- When updates deploy (instantly)
- Who can access your app (no geographic restrictions)
- Revenue terms (no platform cut)
Analogy: Like running your own storefront—direct customer relationships, but you handle all marketing yourself.
Key Differences
| Feature | App Store | PWA |
|---|---|---|
| Approval Time | Days/weeks | Instant |
| Discovery | Curated search | Open web |
| Updates | User-initiated | Automatic |
| Fees | 15-30% | None |
PWAs offer reach (anyone with a browser), speed (instant deployment), and control (your rules). App stores offer visibility and platform trust.
Key Takeaway: PWAs distribute through the open web with zero gatekeepers, while app stores provide curated discovery at the cost of fees, delays, and restrictions—choose based on your audience and business model.