What a PWA is
A Progressive Web App is a web app that behaves like a mobile app: it can be added to the phone's home screen, opens full-screen, can work offline and – on newer systems – send notifications. It doesn't have to be downloaded from a store: just go to the website address.
One codebase serves Android and iOS phones, tablets and computers.
Comparison
| PWA | Mobile app (store) | |
|---|---|---|
| Installation | from the browser, no store | from the App Store and Google Play |
| Platforms | all – one codebase | iOS and Android |
| Updates | instant, no review | through the stores, with review |
| Visibility in Google | yes, content can be indexed | the app no, the product page yes |
| Visibility in app stores | no | yes |
| Hardware access | basic (camera, GPS, notifications) | full |
| Cost | usually lower | usually higher |
When a PWA is enough
- tools for employees – orders, reports, checklists, a panel for field technicians,
- customer portal – checking orders, bookings, invoices, tickets,
- a SaaS product used both on a computer and on a phone,
- a quick test of an idea before you invest in a full mobile app,
- when you want the user not to have to install anything – e.g. a one-off order after scanning a QR code.
When a mobile app is the better choice
- users are meant to find you in the App Store and Google Play – e.g. consumer apps, loyalty apps, shops,
- the app needs full hardware access: Bluetooth, NFC, advanced background work, widgets,
- reliable push notifications on iPhones matter – in a PWA they only work after the app has been added to the home screen, and many people won't do that,
- the app has to handle subscription payments purchased in the store,
- you're building a brand for which being in the stores matters for its image.
On the iPhone a PWA has more limitations than on Android. If most of your customers use iOS and notifications are key, test this before deciding.
A middle way
Often the best route is to start with a web app (PWA) and, once the idea has proven itself, add a mobile app that uses the same backend and API. Nothing from the first stage goes to waste: the server, database, admin panel and logic all stay.
We also describe this strategy in the article about planning an MVP.
How to choose – three questions
- Where will users come to the app from? From Google, a link or a QR code – PWA. From an app store – mobile app.
- How often will they use it? Every day – the icon and notifications matter a lot. Occasionally – installation can be a barrier.
- Do you need hardware features? If so, check whether the browser supports them on both systems.
We build both web apps and PWAs and mobile apps, so we'll help you choose the solution that fits your situation, not whatever we happen to be selling.
Related services: web apps, mobile apps.