A progressive web app, or PWA, is a website that can behave like an app: users can add it to their home screen, open it full screen, use parts of it without a connection and receive notifications. For many businesses that is enough, and it saves building and maintaining separate Android and iOS apps.
For others it is the wrong choice, because the web still cannot do some things native apps can, especially on iPhones. This guide sets out where PWAs fit, where they do not, a checklist to help you decide, and what to plan before you build one.
Quick answer: A PWA makes sense when your users return often, you need one product across Android, iPhone and desktop, connectivity is patchy, and the features you need work in browsers: forms, camera, location while the app is open, payments and notifications. Choose a native or cross-platform app if you need App Store presence, continuous background tracking or Bluetooth hardware on iPhones.
What a PWA can and cannot do today
A PWA is built from standard web technology plus three ingredients: HTTPS, a web app manifest that describes its name, icons and display mode, and a service worker, which is a script that caches files and data so screens load quickly and keep working offline.
- Can: install to the home screen, open without browser bars, cache screens and data for offline use, use the camera and file uploads, read location while open, send push notifications, take payments through a gateway checkout, and update instantly without a store review.
- Limited: on iPhones, push notifications work only after the user adds the app to the home screen, and there is no automatic install prompt; users install from the Share menu with Add to Home Screen. In India, every browser on an iPhone runs on Apple's WebKit engine, so Chrome on an iPhone has the same limits as Safari.
- Cannot, or not reliably: long-running background tasks, continuous background location tracking, Bluetooth and NFC hardware on iPhones, home-screen widgets, and listing in Apple's App Store.
Situations where a PWA usually fits
These are the patterns our PWA development team looks for before recommending one. If most of your use case sits here, a PWA is worth serious consideration.
- Repeat-use tools for known users: dealer order booking, field-staff visit reports, technician job cards, or a housing society's maintenance and complaints app. Users come back daily, and you can show them how to install it once.
- Patchy connectivity: field teams in rural or industrial areas can fill forms offline, and the app sends them when a connection returns.
- One budget for all devices: a single codebase serves Android, iPhone, tablets and desktops, and every user gets updates at the same time.
- Occasional customers who will not download an app: restaurant ordering, event registration or a service booking link shared on WhatsApp opens instantly in the browser.
- Phones with little storage: a PWA usually takes far less space than a native app, which matters for users on entry-level phones.
- An existing web app that users want on their home screen: adding a manifest, service worker and offline handling is often a contained project.
When a native or cross-platform app is the better call
- You need to be found in the App Store and Play Store, because your customers search there.
- Your workflow depends on tracking location in the background, as a delivery fleet does.
- You need Bluetooth printers, scanners, NFC or other hardware on iPhones.
- Push notifications are critical, many users are on iPhones, and they are unlikely to add the app to the home screen.
- The app does heavy processing on the device, such as video editing, augmented reality or games.
In these cases, look at cross-platform app development, which still shares most code between Android and iOS. Our guide to native vs Flutter explains that next choice in more detail.
A decision checklist
Go through each requirement and note which column it falls in. If anything critical lands only in the right-hand column, a PWA alone will not be enough.
| Requirement | PWA | Native or cross-platform app |
|---|---|---|
| Forms that work offline and sync later | Yes, with careful design | Yes |
| Push notifications on Android | Yes | Yes |
| Push notifications on iPhone | Only after Add to Home Screen | Yes |
| Camera, photo upload, location while open | Yes | Yes |
| Background location tracking | Not reliable | Yes |
| Bluetooth or NFC hardware on iPhone | No | Yes |
| Listing on Google Play | Possible through a Trusted Web Activity package | Yes |
| Listing on Apple App Store | Simple web wrappers are generally not accepted | Yes |
| Updates without store review | Yes, instantly | Usually needs a store release |
| Found through Google search | Yes, pages can be indexed | Only through a separate website |
Plan these before you build
- Offline scope: decide which screens and data must work offline, and whether users only read data offline or also create it.
- Sync and conflicts: define what happens when two people change the same record offline, and how users can see that a record is still waiting to sync.
- Storage limits: browsers can clear stored data under storage pressure or after long inactivity, so never keep the only copy of important data on the device; sync early and often.
- Updates: a service worker can keep serving an old version until the app reloads, so build a clear “new version available” message.
- Installation help: Android browsers can show an install prompt; iPhone users need a short guide to Share and Add to Home Screen.
- Notification permission: ask after a user action that explains the benefit, not the moment someone first visits.
- Real-device testing: test on an inexpensive Android phone and an iPhone over a slow connection, not only on a developer laptop.
Write the answers into your brief. They decide much of the effort in a PWA project, and they are far cheaper to settle on paper than after the first release.
How EthicsComputer can help
Our PWA development team builds installable, offline-capable web apps and converts existing sites into PWAs, and we will tell you plainly when a native or cross-platform app would serve you better. If app store presence matters, our mobile app development team can plan both together. Source code and documentation are handed over to you at the end of the project.
Wondering whether your idea needs an app or a PWA?
Describe your users, where they work and what they need to do, and we will tell you which route fits.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.