What is a PWA?
A PWA (Progressive Web App) is a web application that runs in the browser but that users can add to their phone's home screen and open like an app. It has its own icon, opens full screen, and the browser bar disappears. It can work to a certain extent without an internet connection, and it can send notifications.
Users don't go to an app store; they tap a link, choose "Add to Home Screen" and start using it. When you release an update, everyone sees the new version the next time they open it — no waiting for store approval.
Side-by-side comparison
| Topic | PWA | App store app |
|---|---|---|
| Installation | From a link, added to the home screen | Downloaded from the App Store / Google Play |
| Updates | Instant, no approval | After store review |
| Store visibility | None (limited routes on Android) | Yes |
| Notifications | Full on Android; on iOS if added to the home screen | Full |
| Offline use | Possible, with limits | Full |
| Device features | Camera and location available; Bluetooth and some sensors limited | Full |
| Development and maintenance | One codebase, by a web team | Mobile development plus store management |
PWA support on iOS has improved in recent years, but it is still not as broad as on Android. We clarify these limits before the project starts.
When a PWA is the right choice
- Your users are a defined group: employees, dealers, existing customers
- Being discovered in the stores isn't a goal
- The features are mostly forms, lists, reports, orders and photos
- Launching quickly and updating often is important
- You already have a web panel and want a simple mobile face for it
Example: a building materials distributor might choose a PWA instead of an app store app so its dealers can place orders and check their account balance. The dealer gets the link by SMS and adds it to the home screen; when a promotion changes, the update reaches everyone instantly.
When you need an app store app
- You are building a consumer app for a wide audience, and being found in the stores matters
- There is heavy use of Bluetooth, NFC or special hardware
- Reliable notifications on iOS are critical
- The app will work offline for long periods with large amounts of data
Decision checklist
- Who are the users, and how do we reach them?
- Which device features are absolutely required?
- Are notifications essential for iOS users?
- How often will you update?
- Is there a chance you will go to the app stores later?
For that last question, there's good news: you can start with a PWA and, if demand grows, move to an app store app using the same server side. The investment isn't wasted. If you choose the store route, we describe the process on the app store publishing process page.
Frequently asked questions
Is a PWA different from a website?
Yes. A regular website opens in the browser and doesn't work offline; a PWA is installed on the home screen, opens like an app and can keep data in its cache.
Can we turn our existing website into a PWA?
Technically, PWA features can be added to most websites. But a company website usually doesn't need them; a PWA really makes sense for panels and portals that people use again and again.
Is a PWA secure?
It only runs over HTTPS; its security level depends on the security of the web application behind it.
To talk about which one suits you, take a look at our mobile app service or write to us through the contact page. The web side is built by our custom software team.