Many businesses conclude they "need an app" when what they actually need is for their website to behave better on mobile: load fast even on a poor connection, be addable to the home screen, send the occasional notification. All of that, and quite a bit more, can be achieved with a PWA (Progressive Web App) without going through the development, approval and maintenance of a native app in the Apple and Google stores.
What a PWA actually is
A PWA is, in essence, a website built with some extra technical capabilities that let it behave somewhat like an app: it can be installed on the phone's home screen with its own icon, it can work (at least partially) offline because it saves certain resources on the device, and it can send push notifications on some operating systems. Underneath all of that, it remains a normal website, accessible from any browser without needing to install anything if the user does not want to.
Why avoiding a native app is usually the right call for a small business
Building a native app means, at minimum, building and maintaining separate versions for iOS and Android, going through each store's review process, which can delay every update, and convincing someone to take the step of downloading it, a much bigger commitment than simply visiting a website. A PWA, on the other hand, is built once, updates instantly for every user without going through any store, and the user can "install" it with a single tap, with no download friction or significant storage footprint.
Offline functionality: the advantage that surprises people most
One of the most valuable capabilities of a PWA is being able to save certain content on the user's device (the product catalogue, the last pages visited, basic business information) so it stays accessible even without a connection, or to show an appropriate message instead of a generic error screen when the connection fails. For businesses whose customers move through areas with patchy coverage, or simply to reduce the frustration of a slow mobile connection, this capability makes a real difference to the experience.
Notifications: use them with judgement, not as another spam channel
PWAs can send push notifications on several browsers and systems, a capability traditionally reserved for native apps. The temptation to use them for everything (daily offers, constant reminders) usually backfires: users switch off notification permissions the moment they feel they are receiving noise instead of value. Reserving them for what is genuinely useful (an upcoming appointment, a shipped order, a reply to an enquiry) keeps that channel alive far longer.
How to know if your business genuinely needs a PWA
Not every business benefits equally. It clearly makes sense for anyone with recurring mobile visits (a customer who frequently checks the catalogue or their order status), for anyone serving customers with unstable connections, or for anyone wanting a snappier experience without the cost of a native app. It makes less sense for a purely informational website visited once and sporadically, where the extra investment does not translate into a proportional benefit.
The real cost of turning a website into a PWA
Turning an existing website into a PWA does not mean rebuilding it from scratch: it involves adding a few configuration files (a manifest that defines the icon and name of the installed app) and a file called a service worker, which manages what gets saved for offline use. It is a technical layer added on top of what already exists, with a much lower implementation cost than a full native app, though it does require some technical knowledge to do well.
An important caveat on iOS: not everything works the same across systems
Although PWAs have worked reasonably well on Android for years, support on iOS has historically been more limited (fewer offline capabilities, more restricted push notifications). Before investing in a PWA assuming it will behave exactly the same on every device, it is worth checking which specific capabilities your business needs and whether they are reliably available on the operating system most of your customers use.
The icon and the loading screen: small details that define the first impression of the installed app
Once installed, the PWA lives on the phone's home screen alongside native apps from major brands, and that context demands the same visual care: a crisp, recognisable icon, and a splash screen consistent with the brand identity, instead of a blank screen that can feel like something failed during the first few seconds after opening the app.
Measuring real PWA adoption versus the traditional website
Before investing in expanding a PWA's capabilities, it is worth measuring how many users actually install it and, even more importantly, how many of them come back to use it compared with those who simply visit the website without installing anything. This data, available in most web analytics tools, allows a judgement call on whether it is worth continuing to invest in this layer or whether the target audience simply prefers the traditional browser.
Silent updates: the advantage nobody sees but everybody enjoys
Unlike a native app, where the user must actively accept every update from the store, a PWA updates transparently every time the user opens it with an internet connection. This eliminates the common problem of native app users stuck on old versions because they never updated manually, a support problem that simply disappears with this model.
When a PWA is not enough and a native app is genuinely needed
There are specific cases where a PWA cannot compete with a native app: applications needing deep access to device sensors (constant high-precision GPS, advanced Bluetooth), demanding graphics performance (complex games) or very tight integration with the operating system. For the vast majority of small businesses these cases do not apply, but it is worth knowing about them so as not to rule out a native app by default without checking whether your specific case is one of those genuine exceptions.
Long-term maintenance cost: another underrated PWA advantage
Beyond the initial development cost, a native app needs ongoing maintenance to stay compatible with every new iOS and Android version, a recurring cost many businesses do not factor in properly when deciding. A PWA, built on open web standards, has a noticeably lower long-term maintenance cost, a factor that weighs more and more as the years pass since the initial launch.
Intermittent connectivity in rural areas: a very real use case in Spain
Outside major cities, mobile connectivity in Spain can be considerably patchier, and for businesses serving this customer base (rural tourism, small-town shops), a PWA's offline capability stops being a marginal convenience and becomes a direct competitive advantage over traditional websites that simply do not load without good signal.
Frequently asked questions
Does a PWA completely replace a native app?
For most small businesses, yes, it covers the real needs. It only makes sense to stick with a native app when very specific device capabilities are needed (deep sensor access, demanding graphics performance) that a PWA cannot offer at the same quality.
How much does it cost to convert an existing website into a PWA?
It is noticeably cheaper than building a native app, since it builds on the website already in place. The specific cost depends on how many capabilities (offline, notifications, installability) are needed and the technical complexity of the current site.
Does the user have to download something from an app store?
No. The PWA installs directly from the browser with an "add to home screen" button, without going through Google Play or the App Store, although some PWAs can also be distributed through those stores if desired.
Do PWAs work well on every phone?
They work on the vast majority of modern browsers and systems, although the level of support for some capabilities (especially push notifications and offline storage) varies between Android and iOS, so it is worth checking what your specific case needs.
Do I need to redesign my website to turn it into a PWA?
Not necessarily. The technical conversion is independent of the visual design, although it is often a good moment to review performance and mobile experience aspects that are worth improving anyway.
How do I measure whether the PWA is adding real value to my business?
Specific analytics on how many users install it, how often they return to it compared to entering through the regular browser, and whether offline use reduces complaints or abandonment, are the most direct metrics for assessing whether it is worth maintaining.
What icon size do I need for my PWA to look good once installed?
It is recommended to provide several sizes (typically from 192x192 up to 512x512 pixels) so the operating system automatically picks the right resolution for the device, avoiding a pixelated icon on high-density screens.
How do I know if my users genuinely prefer the installed PWA over the browser?
By comparing return frequency and session length in your analytics tool between users arriving from the installed PWA and those browsing from the regular browser; a clear difference indicates a genuine preference, not just initial curiosity.
What type of business genuinely needs a native app instead of a PWA?
Businesses needing deep access to device sensors, demanding graphics performance (like complex games), or very tight integration with specific operating system features a PWA cannot replicate at the same quality.
Is long-term maintenance cost lower with a PWA than with a native app?
Yes, noticeably. A native app requires ongoing updates to stay compatible with every new operating system version, while a PWA, based on open web standards, needs far less recurring maintenance.
Does a PWA's offline capability make sense for businesses outside major cities?
Yes, especially in areas with patchy mobile connectivity, where this capability stops being a minor convenience and becomes a real competitive advantage over traditional websites that depend on a stable connection to work.