"We need an app" often means "we need to be on customers' phones" — and those are different problems with different price tags. A progressive web app (PWA) puts your web experience on the home screen without app stores; a native/cross-platform app buys deeper capability at multiple times the cost. Most businesses choose backwards. Here is the honest split.
What a PWA actually is
Your website, engineered to install from the browser, work offline, load instantly, and (on Android) send push notifications. No store review, no 30% platform fees on web payments, one codebase with your site, instant updates. Cost: ₹1–4L on top of a well-built site — often less if the site is already modern (website economics).
The honest capability gap
| Capability | PWA (2026) | Native/cross-platform |
|---|---|---|
| Home screen + offline | ✅ | ✅ |
| Push notifications | ✅ Android; ⚠️ iOS limited (installed PWAs only, no badging finesse) | ✅ Full |
| Camera, location, payments (UPI intents) | ✅ Mostly | ✅ Full |
| Background sync, Bluetooth, sensors | ⚠️ Patchy | ✅ |
| Store presence/discovery | ❌ (wrappers possible) | ✅ |
| Deep OS integration (widgets, watch) | ❌ | ✅ |
iOS remains the asterisk: Apple's PWA support improved but stays deliberately behind — if iPhone push engagement is core to your model, the gap is strategic, not technical trivia.
The decision, plainly
PWA first when: your product is content, commerce, booking, or dashboards; your traffic is web-acquired (search/ads → install friction kills native funnels); your budget wants one codebase; and re-engagement runs on WhatsApp anyway — which in India it usually does, neutralizing the push-notification gap.
Native/cross-platform when: the app is used daily as a habit (push + presence matter), store discovery is a channel, you need the capability list above, or investors/partners expect store presence as legitimacy.
The common right answer for Indian SMBs: excellent fast website → PWA → cross-platform app when metrics prove mobile habit — each stage funded by the last, no ₹8L app built for an audience that never asked.
The trap to avoid
Building a native app because "everyone has one," then watching 90% of traffic stay on the site while the app rots at 200 installs. Apps are commitments — maintenance, OS updates, store policies — not trophies.
Unsure which stage you are at? Send us your traffic reality — we will answer with numbers, not a pitch. Ranges at the calculator.
Frequently asked questions
What is a PWA and how is it different from a native app?
A progressive web app is your website engineered to install from the browser, work offline, and load instantly — no app store, instant updates, one codebase. Native apps buy deeper OS integration, full push support, and store presence at several times the cost.
How much does a PWA cost compared to a native app?
₹1–4 lakh on top of a modern website versus ₹4–15 lakh for a cross-platform app build — plus the app's permanent maintenance, OS-update, and store-policy commitments. The PWA also shares its codebase with your site.
What are PWA limitations in 2026?
iOS push notifications remain limited (installed PWAs only, behind Android's support), background sync and Bluetooth are patchy, and there's no store discovery or deep OS integration like widgets. On Android, capability covers most business needs.
Should my business build a PWA or an app first?
For web-acquired traffic in commerce, content, booking, or dashboards: PWA first — install friction kills native funnels, and WhatsApp handles re-engagement in India anyway. Build the app when metrics prove daily mobile habit, funded by proven demand.