When a business needs an application, the usual question is "iOS or Android?". The right question is different: what functionality do I need and who is going to use the app?
What is a PWA
A Progressive Web App is an application that lives in the browser but behaves like a native app: it installs on the mobile home screen directly from the browser, works offline, receives push notifications, and loads quickly. It does not require publication on the App Store or Google Play.
Key differences from a native app
Native app: code specific to each platform (iOS and Android are separate developments), mandatory publication in app stores with their approval processes, updates that go through the store.
PWA: a single development that works on any device and operating system, direct distribution via URL without stores or approvals, instant updates that reach all users without anyone having to update anything. There are no review processes that can block or delay a feature, and no 30% store commission on every transaction.
When to choose a PWA
A PWA makes sense when:
- You need the app to work on iOS and Android without paying for two separate developments
- Content changes frequently and you need to update without going through the stores
- Distribution is direct: employees, specific clients, closed communities
- You do not need deep access to the device hardware
- You want development speed and lower cost without sacrificing user experience
Two real projects built as PWAs
AI Employee is a voice-based order management application for the distribution and hospitality sector. Employees install it on their mobile from the browser in seconds, without the App Store. Orders are processed by voice, without a keyboard. It works in environments with limited connectivity.
Palvetagem is a complete liturgical application for the Catholic community in Estonia, with 1,239 sections and more than 8,800 verses. It works completely offline — the user downloads the content once and accesses it offline permanently. Distributed throughout the entire community without going through any store.
The real cost of each option
Budget is one of the factors that most influences the decision, but the common mistake is comparing only the initial development cost without considering the total lifecycle cost.
Native app: developing for iOS and Android are two separate projects. That means two teams or one team working twice as hard, two publication processes, two update cycles, and two sets of bugs to fix when the operating system version changes. The annual maintenance cost of a native app typically represents between 15% and 20% of the initial development cost.
PWA: a single development that works on all devices. Updates are deployed in seconds without going through any store. Maintenance cost is significantly lower because there is only one codebase to maintain.
For most projects aimed at internal use or specific communities — employee tools, client platforms, offline catalogues, management applications — the PWA reduces the initial budget by between 40% and 60% compared to an equivalent native development.
PWA and SEO: an advantage native apps do not have
Native applications are not indexable by search engines. A user searching on Google will not find the content of a native app — they can only reach it through the app store or a direct link. That severely limits organic user acquisition and forces reliance on advertising or visibility within the store's own ecosystem.
A PWA, being a website, is indexable. Every section, every page, every piece of content can appear in search results. For businesses that want their tool or catalogue to have organic visibility, this is a structural advantage.
Additionally, PWAs can be shared like any link. No download friction, no forcing the user to go to the App Store — you simply send the URL and the user installs it on their home screen directly from the browser in under three seconds. Each page has its own URL, meaning you can link directly to any section from an email, a message, or a campaign.
Real limitations of PWAs you should know
PWAs are not the right solution for everything. There are cases where the native app is still the appropriate choice:
- Access to specialised hardware: if the app needs to use Bluetooth in the background, control specific peripherals, or continuously process sensor signals, the native app has access to APIs that PWAs cannot reach.
- Stores as a distribution channel: if the goal is for unknown users to discover the app by searching in the App Store or Google Play, the native app is the way to go.
- Very specific iOS features: Apple has deliberately limited some PWA capabilities in Safari. Push notifications on iOS were blocked for years (enabled in iOS 16.4), and certain hardware APIs still have restrictions.
- In-app payment apps: the business model of charging per download or store-managed subscription (In-App Purchase) is exclusive to native apps.
Frequently asked questions about PWA vs native app
Can a PWA be installed on an iPhone?
Yes. From Safari on iOS, the user can add the PWA to their home screen with a couple of taps. It installs like any app and appears with its own icon. From iOS 16.4, PWAs can also send push notifications on iPhone, although the user must give explicit permission.
Do PWAs work without an internet connection?
It depends on how they are built. Well-developed PWAs use Service Workers to cache content and work offline. The Palvetagem project mentioned in this article is an example: users download the content once and access it completely offline indefinitely.
How long does it take to develop a PWA?
A medium-complexity PWA — with authentication, database, offline functionality, and adapted design — can be ready in four to eight weeks. An equivalent native development for iOS and Android doubles or triples that timeline.
Can you migrate from a native app to a PWA?
Yes, although it is not a direct migration — it is a redesign. The business logic can be largely reused, but the interface and state management need to be rebuilt. In projects where the existing native app has an established user base, migration is usually done in parallel to avoid interrupting the service.
Do PWAs appear on Google?
Yes, and that is one of their greatest advantages over native apps. Being web technology, all PWA content is crawlable and indexable by Google. If the PWA has pages with useful content, those pages can rank in organic searches. A native app published in the App Store does not have this capability.
What happens if the user removes the PWA from their home screen?
They do not lose their data. Unlike a native app where deleting the app deletes local data, in a PWA data is usually synchronised on a server. The user can reinstall the PWA at any time by opening the URL in the browser, and finds everything as they left it.
When a native app makes more sense
The native app is the right choice when the functionality depends on deep hardware access (real-time image processing, specialised sensors, intensive GPS in the background), or when the app stores are themselves a distribution channel.
The right question
It is not iOS or Android. It is: what does the app need to do and who is going to use it? With that answer, the choice between PWA and native app becomes obvious. In most projects we receive, the PWA is the most sensible option — technically and economically.
If you need deep hardware access, the stores are your main distribution channel, or your monetisation model depends on Apple or Google's ecosystem, the native app makes sense. In all other cases — which are the vast majority — the PWA delivers the same user experience at a fraction of the cost, without publication friction, with instant updates, and with search engine visibility that a native app can never have.
The question is not which technology is better in the abstract. It is which one best solves your specific problem with the budget and timeline you have. That assessment is the first thing we do on every project before writing a single line of code.