PWA on iPhone in 2026: what works, what is missing and when it is enough for a business

A company wants to give employees or customers a phone app, and the question comes up straight away: build a native app and go through the stores, or is a PWA enough? The most common worry is: "will it work on iPhone?" This guide collects the facts current as of October 2026, with sources from Apple and WebKit, and our own experience with PWAs in a client deployment and in our own tools. If you are looking for a contractor, see our custom PWA applications.

What is a PWA and how is it different from a website and a native app?

A PWA is a web application that you install from the browser onto the home screen. It differs from an ordinary website in that it has an icon, opens in a separate window without an address bar, can work partly offline and can send notifications. It differs from a native app in that it does not go through a store and has a single codebase for iPhone, Android and desktop.

Technically a PWA is a website with two additions: an app manifest (name, icons, display mode) and a service worker, a script that keeps the app's files in the phone's memory and receives notifications.

PWA on iPhone in 2026: what works and what is missing?

On iPhone a PWA has push notifications, badges with a number on the icon and a full-screen window, and since iOS 26 it installs as an app by default. What is missing is an automatic install prompt, Bluetooth, NFC, USB and background work. Details with sources below.

Push only after adding to the home screen (iOS 16.4+)

Since iOS 16.4 a web app added to the home screen can ask for permission for push notifications, provided the request is made in response to a user action, e.g. tapping a button. The same version added badges with a number on the icon (the Badging API), and other browsers on iOS can add websites to the home screen from the Share menu. Since iOS 18.4 WebKit also supports Declarative Web Push, a simpler and more battery-friendly way of sending notifications.

iOS 26: every website from the home screen opens as an app

In iOS 26 Apple changed the rule: every website added to the home screen opens as a web app by default. The user can switch off the "Open as Web App" toggle and keep an ordinary bookmark. Previously, when a site had no manifest or suitable meta tags, iOS opened it in the browser (heise). A good manifest is still needed: it decides the name, icon, colours and start address.

Safari 27 from September 2026 does not change these rules, but adds improvements for service workers (WebKit).

The EU and the DMA: the iOS 17.4 episode

In February 2024, in the iOS 17.4 beta versions in the European Union, home screen apps opened like ordinary tabs, and Apple explained this by the requirements of the Digital Markets Act (DMA). In early March 2024 the company reversed that decision: web apps from the home screen continue to work in the EU, based on WebKit. The conclusion for a business: a PWA on iPhone in Poland works just as in other countries. It is still worth having a plan B, that is, a shared codebase from which a store version can be built if needed.

What is still missing on iPhone

• An install prompt. Safari does not support the beforeinstallprompt event, so it will not show an "Install" button like Chrome on Android. You have to guide the user with instructions.
• Bluetooth, NFC and USB from the browser. Safari does not support Web Bluetooth, Web NFC or WebUSB. A Bluetooth barcode scanner that works as a keyboard will work, but direct communication with a device will not.
• Background work. There is no Background Sync or Background Fetch, so data entered offline will be sent by the app only when the user opens it again.

How do you make employees actually install the PWA?

Give them a link or a QR code, show instructions tailored to the phone in the app and hide them after installation. On iPhone installation is a few taps in Safari, but without instructions most people will not find it.

Instructions for iPhone (iOS 26, Safari):

1. Open the link to the app in Safari.
2. Tap Share (in Safari's compact layout, first ⋯).
3. Scroll the list and choose Add to Home Screen (if you cannot see it, tap More).
4. Leave "Open as Web App" switched on and tap Add.

Deployment checklist:

• a QR code on a poster in the office or warehouse and a link in the welcome email,
• an "Install" card in the app: an install button on Android, step-by-step instructions on iPhone,
• detection of the app mode and hiding the card after installation,
• notifications switched on with a button only after installation,
• a "New version available" message instead of reloading in the middle of work,
• a 180×180 px icon for iPhone (apple-touch-icon) and a maskable icon for Android.

Where does a PWA work well in a business? Examples

Best where an employee has to do a short task on a phone: clock in at work, approve a document, check a status. Below are processes from Business Panel, deployed in a wholesale company (a separate time-tracking PWA and a mobile view of the panel), and from our tools.

Time tracking with notifications and manager approval

A separate time-tracking PWA: an employee starts and ends work with one button. A push notification reminds them to start the shift, and after it ends to close the working time. Manual entries and leave requests go to the manager, who sees who is working right now and approves or rejects an entry with a reason. Installation is guided by a card with instructions for iPhone and Android.

Document approvals in the field

This is not a separate PWA, but the same panel in the phone's browser (a mobile view: cards instead of tables, a bottom bar). A KSeF (Poland's National e-Invoicing System) invoice goes to the person responsible for the cost centre (MPK). Approval takes a few taps, and the decision stays in the document's history. We write more about this process in the guide on KSeF cost invoice workflow by MPK (available in Polish). Document workflows with stages set up for the company work similarly, e.g. draft → verification → manager approval → accounting.

Dashboards and panels for the team

A sales dashboard and panels with live data, also in a phone's browser, with no installation. 40–50 people use the web panel at the same time, and views load in about 0.5 s.* On a phone tables turn into cards, and navigation moves to a bottom bar. Such a mobile view is easy to turn into a PWA later.

* Data from our deployments, not a guarantee. Performance depends on scope and infrastructure.

Administration tools on a phone

Our server panel is a PWA in which we check the machine's status, containers, services, logs, domains and certificates. Sign-in requires a password and a mandatory TOTP code, optionally a passkey, and actions are saved in an audit log. A separate watchdog sends email alerts.

When, after all, the App Store and Google Play?

When customers look for an app in the store, when you need Bluetooth, NFC or background work, or when the company wants certainty that it works regardless of Apple's decisions about browsers. Then we build a native layer on the same codebase instead of writing the app from scratch.

Apple guideline 4.2: a merely wrapped website will not pass

The App Store guidelines require that an app offers features, content and an interface that go beyond a repackaged website. An app that only displays a site in a window will usually be rejected. Google Play lets you publish a PWA as a Trusted Web Activity, but quality rules apply there too.

A shared codebase + a native layer

Capacitor runs a web app inside a native app and gives it access to phone features through plugins: native notifications, the camera, files, offline work. The same codebase serves the PWA and the App Store and Google Play versions. It is worth agreeing the scope of native features and the time needed for store review at the start.

PWA security in a business

A PWA is as secure as its sign-in and its server: two-factor sign-in, roles and short sessions are the basics. A phone is easy to lose, and in a warehouse or on a building site it is sometimes shared.

• 2FA: a password plus a TOTP code from an authenticator app, or a passkey with Face ID or Touch ID.
• Roles and permissions: an employee sees their own working time, a manager the team, accounting the invoices.
• Audit log: who approved what and when.
• Minimum data on the phone: the service worker caches the app's files, while business data (invoices, amounts) is fetched from the server and not stored; only the sign-in session stays in memory, and signing out removes it.
• Shared phones: a short idle time before sign-out and a visible "Sign out" button.
• Notification content: no sensitive data on the lock screen, e.g. "New request awaiting approval" instead of amounts and names.

How to start: an MVP as a PWA first, the stores later

Start with one process that hurts the most today and build it as a PWA. The first version (MVP) typically takes 2–3 months from the start of the project.

1. Choose a process and users, e.g. invoice approvals for managers.
2. Write down what the app needs from the phone. If it is Bluetooth, NFC or background work, plan a native layer right away.
3. Build a PWA with 2FA sign-in, notifications and installation instructions.
4. Run a pilot with a few people with iPhones and Androids.
5. When a store presence becomes necessary, add a native layer on the same code.

We describe the details of the offer, including App Store and Google Play versions on shared code (e.g. Capacitor), on the page about custom applications. If you are considering a portal for wholesale customers, also read a B2B portal for wholesalers: a ready-made platform or a custom one?