A PWA (Progressive Web App) is a website that can be installed on a phone, open in its own window and receive notifications on compatible systems. For many businesses it is a leaner alternative to a native app, provided you check what works on iOS and Android.

What a PWA is and what changes for the user

A PWA is a web application that the browser can offer to install. Once installed, it gets an icon among the apps and opens without the browser interface. MDN describes the requirements and behaviour of installation.

To be installable it must be served over HTTPS and have a manifest with name, icons, start URL and display mode. These are documented technical requirements, not optional details.

One codebase for desktop and mobile

The same HTML, CSS and JavaScript can serve a desktop browser, a tablet and a smartphone. Compared with two separate native apps, it often reduces development and maintenance.

Available capabilities vary by browser and platform. Before choosing a PWA, test the features you need on your audience’s devices.

Installation, notifications and iOS limits

Since iOS and iPadOS 16.4, WebKit supports Web Push for web apps added to the Home Screen. The permission request must follow direct user interaction, such as tapping a button.

On iPhone, installation goes through the Share menu and “Add to Home Screen”; there is no automatic prompt.

Offline: it has to be designed

A PWA can keep selected data available offline, but the behaviour has to be built. Decide what to store, for how long and how to sync changes when the network returns.

It helps for catalogues used in a warehouse, technical sheets on site, checklists in the field. For a brochure site, offline rarely adds value.

Stores, fees and updates

Distributing on the web avoids store approval waits and store commissions. Payment costs and applicable contractual or legal duties remain.

Store terms vary by revenue tier, transaction type and region. If you sell digital products, read the channel’s rules before choosing the distribution model.

Web updates also depend on the cache strategy. A user may keep seeing the previous version until the service worker replaces it, and that needs handling.

When to choose a PWA

Installability, web updates and partial offline access make sense for catalogues, customer areas, internal tools and bookings.

If you need deep native features, integration with specific hardware or distribution in the stores, a native app remains the stronger choice. The decision depends on the required features and the audience’s devices.

To assess a specific case, email us. If the PWA has to connect to an admin system, the work on processes starts there.