A progressive web app (PWA) is a web application that opens from an address like a website, but it installs on the phone's home screen, launches full screen, can work without a connection and can receive notifications. For many business apps a progressive web app is enough and costs less than a store app. On iPhone, though, it has specific limits, mainly around offline work and access to external devices, and you should know them before you choose.
What a PWA is, in practice
Technically, a PWA is an ordinary website or web application with three extra pieces:
- HTTPS, meaning the site is served securely. Without it, nothing else works.
- A manifest, a small file that tells the phone the app's name, which icons to use, which page to start from and whether to open full screen without the browser bar.
- A service worker, a script that sits between the app and the network: it stores screens and data locally, serves them when the connection drops and receives push notifications.
On Android, Chrome offers installation when the site meets a few installability criteria: HTTPS, a manifest with a name, 192 and 512 pixel icons, a start page and a display mode. The app can also show its own "Install" button, because Chrome passes it the event it needs.
On iPhone, installation goes through the Share menu, with "Add to Home Screen". Since iOS 16.4, browsers other than Safari can do this too. With iOS and iPadOS 26, Apple changed a rule that had stood for years: every site added to the Home Screen opens as a web app, even without a manifest, unless the user turns off the "Open as Web App" option. If there is a manifest, icons and service worker are used as before.
A note for anyone working in Europe: in February 2024 Apple announced that, to comply with the Digital Markets Act, it would remove Home Screen web apps for users in the European Union. On 1 March it reversed course: in the statement reported by 9to5Mac it confirmed that web apps would stay, still based on WebKit, and with iOS 17.4 the feature came back as before. Today a PWA in the EU works on iPhone the same way it does in the rest of the world.
What a progressive web app can do on iPhone and Android
This is where most guides stay vague, with phrases like "limited hardware access". The table lists the features that matter in a business app, with support as stated by WebKit and by MDN compatibility data (checked in November 2026).
| Feature | Android (Chrome) | iPhone (web app added to Home Screen) |
|---|---|---|
| Install on the home screen | Yes, also with a button inside the app | Yes, only from the Share menu |
| Push notifications | Yes | Yes, since iOS 16.4, after a user tap that requests them |
| Number on the icon (badge) | No | Yes, since iOS 16.4 |
| Camera and location | Yes | Yes |
| Background sync when the network returns | Yes | No |
| Reading NFC tags | Yes | No |
| Connecting to Bluetooth devices | Yes | No |
| Publishing on a store | Google Play, via Trusted Web Activity | App Store only if the app offers more than a repackaged website |
The two rows to look at most closely are background sync and external devices. On Android a PWA can queue a submission and let it go out by itself when the phone gets signal again, thanks to the Background Sync API. On iPhone this feature does not exist, neither in Safari nor in installed web apps. NFC and Bluetooth from the browser are not available on iPhone at all: if the app has to read a tag on a fire extinguisher or talk to a portable printer, on iOS you need an installed app.
Notifications, on the other hand, now work on both. On iPhone there are two conditions: the app must have been added to the Home Screen, and permission has to be requested after a user gesture, for example a tap on "Turn on notifications", as the WebKit team explains. In practice, anyone who only opens the PWA in the browser without installing it will never get a notification. For an internal app you fix this with ten minutes of training. For an app aimed at your customers it is a real obstacle, because many of them will not install it.
Offline: where business PWAs break
"Works offline" means different things depending on what the app has to do. Browsing a catalogue or the history of a system without a connection is easy: the service worker keeps screens and data locally, and a PWA handles this well on every platform.
The problem is writing data without a connection. Take a technician closing a job in a basement boiler room: they fill in the job report, take six photos, get the customer's signature, walk back up to the street and put the phone in their pocket. On Android the PWA can send everything as soon as there is signal, even if the app has been closed. On iPhone the upload only starts when someone opens the app again. If the technician forgets until the evening, the office gets the report in the evening.
Then there is storage. A web app's data lives in browser storage, which has a quota and which the system can clear if the phone is full. WebKit describes this in its storage policy: by default data is "best effort", and the app can ask for it to be made persistent, which Safari grants based on its own criteria, for example if the app is opened from the Home Screen. Installed web apps have at least one advantage: the deletion after seven days without visits that Safari applies to websites does not apply to them, because they have their own usage counter and WebKit treats loss of their data as a bug.
None of this makes a PWA unusable offline, but it changes how you design it:
- the app must show clearly what is still on the phone and what has already reached the server, with a counter that is easy to see;
- the upload should be retried every time the app opens, and the coordinator in the office must see which jobs are closed in the field but not yet synced;
- photos should be downsized before being saved locally, because they are the first thing to fill the quota;
- if the unsynced data are documents you cannot afford to lose, such as a signature on a delivery note, an installed app is still the safer choice.
Push notifications and publishing on the stores
Notifications on iPhone without an Apple developer account
You do not need an Apple developer account to send notifications from a PWA. The WebKit team says so explicitly: web notifications on iPhone go through Apple's service but do not require membership in the Apple Developer Program.
The PWA on Google Play
You can publish it. With a Trusted Web Activity the PWA is packaged into an Android app that opens your site full screen; a file published on the site (Digital Asset Links) proves that the app and the site have the same owner. For an internal app you usually do not need this, but it helps when your customers expect to find you in the store.
The PWA on the App Store
This is harder. Apple's guidelines (section 4.2) require an app to offer "features, content, and UI" beyond a repackaged website. A wrapper that only shows your web app risks rejection. If you really need the App Store, it makes sense to build a proper app, perhaps sharing some screens with the web version.
PWA or native app: how to choose for a business app
For a business app the budget matters, and we cover it in how much it costs to develop an app, but the choice comes down to four questions: who uses it, where, on which phone, and what happens if data gets lost.
Portal for your customers
The customer opens the portal to check an order's status, download an invoice or a report, or open a request. They use it a few times a month, nearly always with a good connection. Here a PWA is the right choice: the customer opens it from the link in their email, without downloading anything, and always sees the latest version. Notifications are a bonus for those who install it, while for everyone else email and WhatsApp are enough. We wrote about this in the article on the customer portal.
Department app or control panel
An app used in the warehouse, on the production floor or in the office, on company tablets and phones connected to the internal Wi-Fi. The Buzzi Connect case is of this kind: the interface for controlling the welding machines is a web application, installed on a server in the plant and opened from PCs, tablets or smartphones connected to the network. With company devices you also pick the operating system: if you need NFC or Bluetooth readers, giving everyone Android tablets makes the PWA sufficient.
App for the sales team
Sales reps browse the catalogue and price lists at the customer's site and send the order. Offline browsing works well in a PWA too. The doubt concerns orders written without a connection: if your reps use personal iPhones and often work in areas with no signal, consider an installed app, or design the PWA so the order stays locked as a draft until the server confirms it. For the features a digital catalogue needs, see the article on the B2B app for the sales team.
App for field technicians
Job reports, photos, signatures, work in basements, warehouses and building sites without signal. Here we usually recommend an installed app. In the Dabe Connect case the office management software is web based, while the technicians' app, Dabe Mobile Connect, is an installed app built with Expo (React Native): the technician receives work orders, fills in the report, attaches photos and gets the customer to sign on the phone. This is the setup we see working best when field work is the core of the process. We listed the features to ask for in a technician app in the guide to digital job reports for field technicians.
Often the right project mixes the two: a web app for the office and for customers, an installed app only for people on the road. That is what we offer in our business mobile app and web app development, starting from a single backend connected to your management software.
When a PWA is the wrong choice (and when you do not even need one)
A PWA is the wrong choice when the app has to win new customers inside the App Store, when it has to talk to external devices on iPhone, when data written offline is critical and users are on iPhone, or when you need phone features the browser does not expose. In these cases, saving money on the first version almost always means rebuilding it as an installed app later.
At the other end are the cases where you do not even need a PWA. If your users are five people in the office on PCs, if the app is opened twice a month, or if the management software you already use has a decent mobile version, a well built responsive web application is enough. Manifest and service worker can be added later, without rewriting the application, on the day someone asks for an icon on the Home Screen.
A practical check before you decide: take the actual phones of the people who will use the app, count how many are iPhones and ask them where they work without signal. With those two answers the choice is almost always already made.
Let's talk
If you are evaluating an app for your technicians, your sales reps or your customers and you are not sure a progressive web app is enough, book a call with Selli. We will look together at who will use it, on which phones, with what connection and which systems it has to talk to. If a PWA is enough we will tell you, and sometimes we will tell you that the management software you already have is enough. We work in two-week sprints, with a test environment where the app runs on your team's phones before release, and the code stays yours.