TL;DR — pick-by-scenario
- Build a web app if your product is B2B SaaS, an internal tool, or a content-driven service where users arrive via search or shared links. No installation barrier, every device, easiest iteration.
- Build a PWA if you need a web app plus home-screen presence, push notifications and offline access — without maintaining two native codebases. Best fit for e-commerce, media, B2C dashboards and marketplaces.
- Build native (iOS + Android) if your app depends on ARKit/ARCore, NFC payments, HealthKit, background location, on-device ML, or tight OS integrations like CarPlay and Android Auto. Also the default for consumer retention plays where daily active use is the core KPI from day one.
- For most B2C products in the $50k–$200k budget range, a well-executed PWA gives you 80% of the native experience at 40–60% of the cost. Don't overbuild unless you have a concrete reason.
Web app, native, PWA: what each really means in 2026
The terms are often misused. Here is a precise definition for each, because the choice between them depends on understanding what they actually are.
Web app
A web application runs in a browser tab. It may be a simple multi-page site, a React SPA, or a Next.js server-rendered app — the defining characteristic is that the user navigates to a URL and the browser hosts the experience. No installation. No app store. Every operating system and device that has a modern browser can use it. This is the default choice for B2B SaaS, internal tools, and any product where acquisition comes from organic search or direct links.
Native app
A native app is compiled for a specific platform — Swift/SwiftUI for iOS, Kotlin/Jetpack Compose for Android — or built with a cross-platform framework like React Native or Flutter that targets both. It is distributed through the App Store or Google Play, installed on the device, and has full access to hardware APIs, OS services and background execution. The price of that power is two codebases (or one cross-platform codebase with platform-specific modules), App Store review latency and a mandatory installation step that drops 20–50% of casual users before they see your product. See our comparison of React Native vs Flutter in 2026 for more on the cross-platform framework choice.
Progressive Web App (PWA)
A PWA is a web app that adds three things: a service worker (enables caching and offline), a Web App Manifest (enables installation and home-screen icon), and HTTPS (required for both). That combination unlocks installability, push notifications and offline access — capabilities that were exclusive to native until recently. The user can add a PWA to their home screen directly from Safari or Chrome, and it opens in a standalone window without browser chrome, looking and behaving much like a native app. You still deploy it as a URL; the browser handles the rest.
What PWAs can and can't do on iOS & Android now
The most common misconception we hear from US and EU clients in 2026 is still "PWAs don't work on iPhone." That was largely true before 2023. It is not true anymore. Here is the current state, platform by platform.
iOS (Safari 17+, 2026)
- Web Push: Supported since iOS 16.4 (March 2023). Users who add a PWA to their home screen can receive push notifications via the Web Push standard. Safari on iOS (not installed PWAs) still requires a permission prompt, consistent with native apps.
- Installation: Add to Home Screen works; the installed PWA opens in a standalone window with a custom icon. iOS 17+ supports the BeforeInstallPrompt API for in-app install prompts, though Safari's implementation has quirks compared to Chrome.
- Offline: Service workers work fully. Caching, background sync and IndexedDB are all available.
- Gaps on iOS: No NFC, no ARKit/RealityKit, no HealthKit or Motion & Fitness APIs, no background audio in locked-screen mode, no Bluetooth LE pairing. These remain native-only territories on iOS in 2026.
Android (Chrome, 2026)
Android has had the most complete PWA support for years and it has only improved. Web Push, installation, offline, Bluetooth LE, NFC (experimental behind a flag in Chrome), background sync and file system access are all available. The gap between a well-built PWA and a React Native app is genuinely small on Android for most use cases. The main missing piece is deep OS integrations: Android Auto, Wear OS, widget slots and notification channels with granular categories.
Cost & time-to-market compared
These numbers are based on our own delivery data for US and EU clients across 2024–2026 and our mobile app development cost benchmarks for 2026. Team configuration: 1 PM, 1 designer, 2–3 engineers, 1 QA. Scope: 8–12 screens, auth, push, payments, analytics.
| Dimension | Web App | PWA | Native (iOS + Android) |
|---|---|---|---|
| Build cost (typical range) | $30k–$80k | $40k–$100k | $80k–$250k |
| Time to first usable build | 4–6 weeks | 5–8 weeks | 8–14 weeks |
| Codebases to maintain | 1 | 1 | 1–2 (cross-platform or native) |
| App store review delays | None | None | 24–72 h per release |
| Hot-fix deployment | Instant | Instant (service worker update) | OTA for JS (RN); review for Flutter/native |
| Organic App Store discoverability | None | Limited (Google Play Trusted Web Activity) | Full App Store & Play Store SEO |
| Installation friction | Zero (URL) | Low (browser prompt) | High (App Store download) |
The cost delta between a web app and a PWA is small — often just the service worker setup and manifest configuration, which adds one to two weeks of engineering work to an existing project. The delta between a PWA and native is where the real decision lives. See also our page on our web application development service for how we scope these projects.
Offline, push & device features
Offline capability and push notifications are the two most commonly cited reasons to choose native over a web app. In 2026, both are achievable on PWA for most use cases. Here is the realistic breakdown.
Offline access
A service worker can pre-cache all assets and even API responses, making a PWA fully functional without a connection. This works equally well on iOS and Android. The design challenge is deciding what to cache and how to handle write conflicts — a user submitting an order form offline needs background sync to flush that write when connectivity returns. Libraries like Workbox (from Google) make service worker authoring manageable for React and Vue apps. If your app is a static content reader, product catalogue, or dashboard with read-only data, "offline" is a one-sprint feature on a PWA.
Push notifications
Web Push (RFC 8030) is now supported on Chrome (Android), Safari (iOS 16.4+, macOS Ventura+) and Firefox. The permission UX is nearly identical to native push — users see a system-level prompt and can manage permissions in OS settings. Delivery rates in our 2025 campaigns for EU e-commerce clients averaged 78–85% of what equivalent native push achieved, which is within acceptable range for most products. The main gap: push does not work if the PWA is opened in a browser tab without being installed to the home screen on iOS.
Device features: the honest picture
| Feature | PWA (iOS) | PWA (Android) | Native |
|---|---|---|---|
| Camera & microphone | Yes | Yes | Yes |
| Geolocation | Foreground only | Foreground only | Background + foreground |
| Push notifications | Yes (installed PWA) | Yes | Yes |
| NFC | No | Experimental | Yes |
| ARKit / ARCore | No | No | Yes |
| Bluetooth LE | No | Yes (Web Bluetooth) | Yes |
| Biometric auth | WebAuthn / Face ID | WebAuthn / fingerprint | Full platform biometrics |
| In-app purchases | No (Apple policy) | Payment Request API | Full App Store / Play billing |
Distribution, app stores & discoverability
Distribution is where native still has a structural advantage that a PWA cannot fully replicate.
App Store discoverability
The App Store and Google Play together drive a significant share of new app installs, particularly for consumer apps in the US. App Store search accounts for 65–70% of app discovery in the US according to multiple 2025 studies. A PWA does not appear in these search results unless you wrap it in a Trusted Web Activity (TWA) and submit it to Google Play — which some teams do successfully. Apple does not allow PWA submissions to the App Store.
For B2B and enterprise products, this matters much less. Users find B2B tools via Google search, sales conversations and product-led growth loops — not the App Store. A web app or PWA is actually advantageous here because zero-installation means shorter time from awareness to first value.
The EU regulatory angle
The EU Digital Markets Act (DMA) has required Apple to allow alternative app distribution in the EU since March 2024. In practice, side-loading via web pages and alternative marketplaces is now legally permitted for EU users on iOS. This shifts the discoverability calculus for EU-focused products — it no longer requires an App Store listing to reach iPhone users with an installed experience. The practical implementation is still maturing, but it is worth factoring into multi-year product strategy.
If your product targets the US and EU consumer markets with a strong organic App Store presence as a growth lever, native is the right choice. If you are building B2B SaaS, an internal tool or a product where search and direct links drive acquisition, a PWA covers your bases. Read our comparison of iOS vs Android: which platform first for the US-vs-EU platform split context.
Decision matrix
Use this table to score your situation. For each row, mark which column applies. The column with the most marks is likely your answer — but weight the rows by their importance for your specific product.
| Decision factor | Web App | PWA | Native |
|---|---|---|---|
| Primary user acquisition channel | Search, links, sales | Search + re-engagement | App Store organic |
| Budget | $30k–$80k | $40k–$100k | $80k+ |
| Audience type | B2B, internal, enterprise | B2C, e-commerce, media | Consumer, high-retention apps |
| Push notifications needed | No | Yes (standard) | Yes (maximum control) |
| Offline usage required | No | Yes (most scenarios) | Yes (complex sync) |
| Hardware APIs (NFC, AR, BLE, background GPS) | No | Partial (Android) | Full |
| Time-to-market priority | Fastest | Fast | Slower |
| Monetisation via in-app purchases | No (use Stripe) | Web payments only | Full platform billing |
| Deployment agility (hot-fix speed) | Instant | Instant | 24–72 h review |
One pattern we see repeatedly with US and EU startups: they build native too early. A PWA launched in month 3 at $60k that validates product-market fit is far more valuable than a $180k native app launched in month 9 that nobody uses. Native makes sense once retention data proves that daily active use and App Store discoverability are worth the investment — not as a starting assumption.
FAQ
Is a PWA cheaper than a native app?
Yes, in most cases. A PWA is built on shared web technologies, so you maintain one codebase instead of separate iOS and Android builds. Development cost is typically 40–60% lower than two native apps. If you need deep hardware integration or strong App Store presence, native pays back the premium.
Can a PWA work offline?
Yes. A service worker can cache assets, API responses and full pages so the app functions without a connection. Read-heavy apps (content, dashboards, catalogues) can be fully offline-capable. Write-heavy apps need background sync to queue writes and flush when connectivity returns.
Do PWAs work on iOS in 2026?
Better than ever. Apple shipped Web Push support in Safari on iOS 16.4 and has continued improving it. Installed PWAs on iOS receive push notifications, appear on the home screen and run in a standalone window. Gaps remain — NFC, ARKit and HealthKit are native-only — but iOS is no longer a blocker for most PWA use cases.
When should I build a PWA instead of a native app?
Build a PWA when your audience is broad and acquisition-driven, when budget is constrained, or when core use cases work without deep hardware access. PWAs excel for e-commerce, media, B2B dashboards and SaaS tools. Stick with native when you need ARKit/ARCore, background location, NFC payments or tight OS integrations like CarPlay.
Is a web app good enough instead of a mobile app?
For most B2B SaaS and internal tools, a responsive web app is the right first choice — it reaches every device, requires no installation and is easiest to iterate. The question shifts when retention matters: push notifications, home-screen presence and offline access improve daily active use significantly. If that KPI is critical from day one, invest in at least a PWA.
Can I turn my web app into a PWA later?
Yes, and it is often the right progression. Adding a service worker, a Web App Manifest and HTTPS to an existing web app can take one to two weeks for a senior engineer. If your app is already built on React, Vue or Angular, Workbox makes service worker authoring straightforward. The main prerequisite is HTTPS on every page.
Last updated 1 June 2026. PWA capability data reflects Chrome 124, Safari 17.4 and the W3C Web Platform baseline. Platform support changes quickly — verify against MDN for the latest per-API status.
