This guide is for product owners, digital leads and CTOs who are about to fund one or two store apps and want to know whether a web app would do the job. It belongs to Netbase's web application development work, where the route is chosen before design starts, and it sits next to the store-app view of the mobile app development service.
In this guide
- When can a PWA replace a mobile app?
- Which features does each platform allow a web app?
- How do the routes compare?
- How do you run the blocking-feature test?
- What breaks most often in a PWA rollout?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives and how to choose between them
- Limits of this guide
- Frequently asked questions
- Next step
When can a PWA replace a mobile app?
A progressive web app (PWA) is a website with a web app manifest, a service worker that caches content and serves it offline, and HTTPS. Once installed, it opens from the home screen in its own window, without browser bars, and it updates whenever the site is deployed.
It replaces a store app when three things are true. The app is used while it is open on screen, not in the background. Every device feature on the must-have list works in the browsers your users run. And users reach you through links, search, email or QR codes rather than by browsing an app store.
Customer portals, booking and order tracking, field forms, catalogues, dashboards and internal tools usually pass. Apps built around Bluetooth devices, NFC tags, background location, wearables or home-screen widgets usually fail, and no amount of web engineering changes that, because the browser does not expose the feature.
Which features does each platform allow a web app?
The table below is the matrix Netbase uses in a route review. It reflects browser compatibility data published by MDN and the WebKit and Chrome teams, checked on 2026-11-20; browsers change, so the matrix is re-checked at the start of each project.
-
Automatic install prompt
- iPhone and iPad (Safari engine)
- No; users add it from the Share menu
- Android (Chrome)
- Yes, through the beforeinstallprompt event
- Desktop (Chrome, Edge)
- Yes
-
Web push notifications
- iPhone and iPad (Safari engine)
- Yes since iOS 16.4, only after the app is added to the Home Screen
- Android (Chrome)
- Yes
- Desktop (Chrome, Edge)
- Yes
-
App icon badge
- iPhone and iPad (Safari engine)
- Yes for Home Screen web apps since iOS 16.4
- Android (Chrome)
- No (Badging API not supported)
- Desktop (Chrome, Edge)
- Yes on Windows and macOS
-
Background sync after the app closes
- iPhone and iPad (Safari engine)
- No
- Android (Chrome)
- Yes (Background Sync API)
- Desktop (Chrome, Edge)
- Yes
-
Bluetooth devices
- iPhone and iPad (Safari engine)
- No
- Android (Chrome)
- Yes (Web Bluetooth)
- Desktop (Chrome, Edge)
- Yes
-
NFC tags
- iPhone and iPad (Safari engine)
- No
- Android (Chrome)
- Yes (Web NFC, Chrome on Android only)
- Desktop (Chrome, Edge)
- No
-
Long-lived offline data
- iPhone and iPad (Safari engine)
- Kept for Home Screen apps; Safari tabs can lose script storage after seven days without use
- Android (Chrome)
- Yes, within the storage quota
- Desktop (Chrome, Edge)
- Yes
-
Store listing
- iPhone and iPad (Safari engine)
- App Store review expects more than a repackaged website
- Android (Chrome)
- Google Play through a Trusted Web Activity
- Desktop (Chrome, Edge)
- Microsoft Store accepts PWAs
Three rows carry most decisions. Install on iPhone is manual, so the product must teach it with an in-app hint, and WebKit's own announcement of web push for Home Screen web apps makes clear that notifications only reach users who have installed the app. Background work stops when the app closes on iPhone. And device hardware beyond camera, microphone and location stays out of reach on Apple devices; MDN marks Web Bluetooth as unsupported in Safari.
The storage row matters for offline-first products. WebKit states that web apps added to the Home Screen have their own counter of days of use, separate from Safari, so a field app that users install keeps its offline data; the same app used only in a Safari tab can lose it.
How do the routes compare?
| Option | Strength | Risk | Choose it when |
|---|---|---|---|
| PWA only | One codebase with the website, instant updates, no store review | iPhone limits in the matrix; users must install by hand | Every must-have feature is green on the main platform |
| PWA plus store wrapper | Store presence on Android at low effort | Apple can reject a wrapper that adds nothing native | Android store discovery matters and iPhone users can use the web app |
| Cross-platform store app | One codebase, full device and background access | Two store reviews, release cycles and a separate backend contract | A blocking feature exists, or store discovery drives growth |
| Native app per platform | Deepest platform features, widgets and wearables | Two codebases to build and maintain | The product lives on platform-specific features |
The comparison is about capability and operating effort, not quality: a well-built PWA and a well-built store app can both feel fast. The native vs cross-platform guide compares the store-app routes in more depth.
How do you run the blocking-feature test?
-
List the must-have features
Write each feature the first release cannot ship without, separate from the nice-to-have list, and tie each to a user task.
-
Find the main platform
Use analytics from the current site or app to see which share of users runs iPhone, Android and desktop, by user group if field staff and customers differ.
-
Mark each feature against the matrix
Green when every browser in scope supports it, amber when it needs a workaround (manual install, sync on open), red when the browser does not expose it.
-
Apply the rule
One red must-have on the main platform decides for a store app or a wrapper. Ambers are design work, not blockers, if the product team accepts them.
-
Prototype the riskiest amber
Build the install hint, the offline queue or the push opt-in on real devices before the full build, and decide with that evidence.
-
Set a switch trigger
Write down which future feature would move the product to a store app, so the PWA is a deliberate stage, not a dead end.
The test looks at the worst cell, not the average. Ten green features do not compensate for one red feature that the main user group needs every day.
What breaks most often in a PWA rollout?
Install friction on iPhone is the first: if the product never shows people how to add the app to the Home Screen, push and badges never reach them. The second is an offline design that assumes background sync, which works on Android and fails silently on iPhone, so queued actions must also replay when the app reopens.
The third is caching the wrong things. Prices, stock and permissions must always come fresh from the server; catalogues and static assets can be cached. The mobile app backend and offline sync guide covers conflict rules that apply to web and store apps alike.
For online stores, the decision often sits inside the commerce platform. Cmsmart, a Netbase brand, offers PWA ecommerce development for WooCommerce and Magento stores, the platforms Netbase also delivers custom commerce on.
Where AI fits
AI features reach PWA users the same way as on any web app: an assistant, smarter search or a camera feature served through an API. Netbase works with the major commercial and open-source AI tools and models, chosen per project; AI features show a fallback when the device is offline, and engineers review AI-assisted code and tests before release.
- In delivered work
Product recommendation engine
Built for 4over4's online store from browsing history and previous purchases; it runs on the web, not in a store app.
- Available capability
Assistants and camera features in web apps
Offered on request; not yet tied to a published case on a PWA.
What delivery record exists, and what does not
- Dey Page. Netbase built a mobile-first business directory for Nigeria whose field verification capture (GPS, geotagged photos, ID capture and offline sync) runs in the mobile web app, next to a React Native app for iOS and Android with push notifications for consumers and business owners. That split follows the logic of this guide: field capture in the web app, push and store presence in the store app. Read the Dey Page record.
- Commerce platforms. Netbase has delivered stores on WooCommerce, Magento 2, Laravel and headless commerce, the platforms where storefront PWAs are most often added.
- People. Netbase has hired PHP, Laravel, Magento, WordPress and React Native developers, so web and store-app routes are staffed from one practice.
What does not exist: the Dey Page record does not call its mobile web app a PWA, so this guide claims no PWA build by name, no install count, no engagement figure and no result. Most Netbase projects are delivered on fixed-price contracts; this page names no price.
Alternatives and how to choose between them
If the blocking-feature test fails, the choice is between a cross-platform store app and a native app; pick cross-platform when one team must ship both stores and native when the product depends on widgets, wearables or platform-specific features. If the test passes but store presence matters, add a Trusted Web Activity for Google Play and keep iPhone users on the web app.
A third option is to keep a responsive website and skip installation altogether. It fits when users visit rarely and only need to read or buy, because install prompts and push add little for a once-a-year customer.
The PWA layer also depends on the site underneath. A content-heavy site needs its CMS and content model settled first; see headless CMS options compared and content modelling before choosing a CMS.
Limits of this guide
- Browser support changes with each release; the matrix reflects documentation checked on 2026-11-20 and must be re-checked per project.
- Regional rules for app stores and browser engines differ and are not covered here.
- The guide does not compare frameworks or vendors and gives no cost or timeline figures.
Plan the next step with a Netbase consultant
Frequently asked questions
Yes, since iOS and iPadOS 16.4, but only after the user adds the web app to the Home Screen and grants permission from a tap. Users who keep the app in a Safari tab receive no notifications.
Not by default, because a PWA installs from the browser. A store listing needs a wrapper app, and Apple's review guidelines expect an app to offer more than a repackaged website, so plan native features if the App Store matters.
Yes, the service worker can cache screens and queue forms and photos on the device. On iPhone the queue is sent when the app is opened again, not in the background, so the design must show staff what is still waiting.
That works when the backend exposes a clean API, because a later store app can reuse it. Write down the feature that would trigger the switch before you start.
Next step
If you are weighing a PWA against store apps, send us your must-have feature list and we will reply with a route review against the platform matrix.
Related services and solutions
Web application development with AI built in where it converts Netbase provides web application development for product and commerce teams that need fast, maintainable web apps and storefront front ends, with AI search, assistants and automation added where they measurably help. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to its published case studies, PrintLeo's page load improved 35% and 4over4's conversion rose 48%.
Learn More
Mobile app development with AI features for commerce and product teams Netbase provides mobile app development for retailers, startups and product teams to reach customers on the phone they already use: cross-platform React Native apps and mobile-optimized commerce that loads fast, converts and uses AI where the phone makes it useful. We scope each app in discovery, reuse your existing backend and APIs, and plan the store release with you.
Learn More
Mobile product accelerator for AI-ready apps: reusable foundations for auth, push, offline and payments A mobile app accelerator is a set of reusable app foundations, covering sign-in, push notifications, offline data and payments, that Netbase configures for each new product, so the build starts on what makes your app different, such as AI search, personalisation or on-device AI. It is a growth capability, delivered as custom development with cross-platform React Native skills.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.