Web app vs native app: how to choose, including progressive web apps
Web app vs native app is one of the first decisions in any app project, and it shapes cost, timeline and what users can do. A web app runs in the browser on every device; a native app is installed from a store and built for one platform. Progressive web apps and cross-platform frameworks sit in between. This guide compares the options, sets out decision criteria, the store rules, the cost logic and the risks, and shows when each one is the right answer.
The short version
- A web app reaches every device from one codebase and updates instantly.
- A native app gives full device access, the best feel and a place in the app stores.
- A progressive web app (PWA) is a web app that can be installed and work partly offline.
- Choose by what users need to do, how often, on which devices, and whether they will install anything.
- Store rules reject apps that are only a wrapped website.
Definitions
Web app: an application that runs in a web browser and is reached through a web address. It is built with web technologies, runs on any device with a modern browser and is updated on the server for everyone at once. Our web app development page describes typical examples.
Progressive web app (PWA): a web app that adds a web app manifest and offline support, so users can install it on the home screen, open it in its own window and use parts of it without a connection. The W3C Web Application Manifest specification (Working Draft, 11 November 2026) defines how the installed app is described.
Native app: an app built for one operating system with that platform's tools, for example Swift for iOS and Kotlin for Android, and installed from the App Store or Google Play. See native mobile app development.
Cross-platform and hybrid apps: store apps built from one shared codebase with frameworks such as Flutter or React Native, or a web app inside a native shell. Our mobile app development frameworks guide compares them, and the cross-platform app development page covers native vs cross-platform in detail.
Web app vs native app side by side
| Aspect | Web app | PWA | Native app |
|---|---|---|---|
| How users get it | Open a link | Open a link, optionally install | Download from a store |
| Devices | Any modern browser | Any modern browser | One platform per build |
| Updates | Instant, for everyone | Instant, for everyone | Through store review and user updates |
| Offline use | Limited | Partial, by design | Full, by design |
| Device features | Camera, location, files; limited background work | As web, plus push on installed apps | Full: sensors, background tasks, widgets, wearables |
| Store presence | No | Not by default | Yes, with store search and reviews |
| Codebases | One | One | One per platform, or shared with a framework |
| Payments for digital goods | Your own payment provider | Your own payment provider | Store rules on in-app purchases apply |
Decision criteria
- Who are the users? Staff on company devices will open a link; consumers often expect to find a brand in the store.
- How often will they use it? Daily use justifies an installed app; occasional use rarely does.
- Which device features are needed? Background location, Bluetooth, widgets, wearables and heavy camera work point to native.
- Offline needs. Field work without coverage points to native, or a PWA designed for offline from the start.
- Notifications. Since iOS and iPadOS 16.4 (2023), web apps added to the Home Screen can receive web push notifications on iPhone and iPad; native apps have full notification support on both platforms.
- Speed of change. A product still finding its shape benefits from instant web updates.
- Desktop users. If the same tool is used on computers, a web app serves both.
A quick scoring test
Score each statement from 1 to 5. The higher total points to the better starting point.
| Points toward a web app or PWA | Points toward a native app |
|---|---|
| Users work on computers as well as mobile devices | Users are mostly on mobile devices, daily |
| Features are forms, lists, dashboards and documents | Features need sensors, background work or wearables |
| Users reach it through links, email or a portal | Users expect to find it in the app stores |
| The product will change often in its first year | The feature set is stable and well understood |
| Coverage is good where it is used | Work happens offline or with weak coverage |
Store rules shape the decision
Wrapping a website in an app shell and submitting it to the stores rarely works. Apple's App Store Review Guideline 4.2 (Minimum Functionality) says an app "should include features, content, and UI that elevate it beyond a repackaged website", and guideline 4.2.2 says apps should not primarily be web clippings, content aggregators or a collection of links (guidelines last updated 16 October 2026). If store presence matters, plan real native value: offline work, notifications, device features or widgets.
Accessibility applies to both
The European Accessibility Act (Directive (EU) 2019/882) applies to services such as e-commerce provided to consumers after 28 June 2025, and its requirements cover websites and "mobile device-based services, including mobile applications". Public sector bodies already follow Directive (EU) 2016/2102 for websites and mobile apps. Whatever you choose, accessibility is part of the scope. See our European Accessibility Act guide.
Cost logic
We do not quote amounts here. Compare these lines:
- Build: one web codebase, or one per platform for native, or one shared codebase with a cross-platform framework.
- Release: web releases are immediate; store apps need store accounts, store listings, screenshots, review rounds and privacy declarations.
- Upkeep: native apps need yearly work for new operating system versions and store rules; web apps need browser testing and security updates.
- Distribution: a web app needs links and search visibility; a store app needs store optimisation.
Our guides to web app development cost and app development cost break down the cost drivers.
Risks
| Risk | Web app or PWA | Native app |
|---|---|---|
| Platform limits | Browser support for a feature changes or lags | Store rejects a release or changes rules |
| Reach | Users never install it and forget the link | Users do not download it at all |
| Upkeep | Testing across browsers and screen sizes | Two platforms to keep current every year |
| Lock-in | Low: open web standards | Store accounts and payment rules |
When a web app is the right answer
- Internal tools, portals, dashboards and booking flows used on computers and mobile devices.
- A first version of a product that will change often.
- Users who arrive through links and would not install an app.
When a native app is the right answer
- Daily use on mobile devices, with notifications, offline work or device features.
- Consumer products where store presence and reviews drive growth.
- Performance-heavy features: maps in motion, media, augmented reality.
Many products use both: a web app for administration and desktop users, and a native or cross-platform app for people on the move, sharing one backend.
Questions to ask before deciding
- Who uses it, on which devices, and how often?
- Which device features are must-haves rather than nice-to-haves?
- Must it work offline?
- Will users find it through the stores, through links, or through our own portal?
- How often will we change it in the first year?
Our app development service decides store app or web app first, and our web app development service builds browser-based tools and PWAs. Every guide is in the guides library.
Questions people ask
What is the difference between a web app and a native app?
A web app runs in the browser and is reached through a web address; one codebase serves every device. A native app is built for one operating system, such as iOS or Android, installed from an app store, and has full access to the device's features. Web apps are faster to release and update; native apps feel more integrated and work better offline.
Is a progressive web app as good as a native app?
For many business uses, yes: forms, dashboards, catalogues, booking and internal tools work well as progressive web apps that can be installed on the home screen and work partly offline. For heavy graphics, deep hardware access, background tasks and the best possible feel on each platform, native apps still have the edge.
Do web apps support push notifications on iPhone?
Yes, with conditions. Since iOS and iPadOS 16.4 (2023), web apps that the user has added to the Home Screen can ask for permission and receive web push notifications, after a direct user action such as tapping a subscribe button. On iPhone and iPad the feature is tied to the Home Screen web app.
Can we put a web app in the App Store?
Only if it offers more than the website. Apple's App Store Review Guideline 4.2 requires apps to include features, content and interface that elevate them beyond a repackaged website. A thin wrapper around a website is likely to be rejected; a hybrid app that adds real native features can be accepted.
Should a business start with a web app or a native app?
Many start with a web app, because it reaches every device from one codebase and is quick to change while the product is still being shaped. A native app follows when users need offline work, device features or store presence. Where staff use the app every day on company devices, a web app is often enough for good.
Sources
- Apple: App Store Review Guidelines, 4.2 Minimum Functionality (last updated 16 October 2026, read 13 November 2026)
- WebKit: Web Push for Web Apps on iOS and iPadOS (16 February 2023) (read 13 November 2026)
- W3C: Web Application Manifest, Working Draft 11 November 2026 (read 13 November 2026)
- Directive (EU) 2019/882 (European Accessibility Act), Article 2 and Annex I (read 13 November 2026)
- Directive (EU) 2016/2102 on the accessibility of public sector websites and mobile applications (read 13 November 2026)