Do PWAs work on iPhone?

Yes. On iPhone and iPad, a web app can be added to the Home Screen from Safari and then opens in its own window without browser controls. Since iOS 16.4, a web app installed this way can also send push notifications, provided the user grants permission after interacting with it, for example by tapping a button.

Can a PWA work offline?

Yes, within limits. A PWA can cache its screens and some data, store what users enter and send it once the connection returns. That covers a few hours without signal comfortably. For days offline with large amounts of local data and conflicting edits to reconcile, a native app remains the more robust choice.

Can a web app send push notifications on mobile?

Yes, on both Android and iPhone, with one difference. On Android, web push works from the browser or from the installed app. On iPhone, it requires iOS 16.4 or later and a web app added to the Home Screen. In every case, the user has to give explicit permission before any notification is sent.

Can we start with a PWA and go native later?

Yes, and it is often the most economical path. The server, the database and the admin back office stay the same; only the mobile front end is rebuilt if a genuine native need appears. Starting on the web lets you confirm real usage before paying for two store apps to publish and maintain.

Mobile appsBusiness softwareMethodBudget

Web app, PWA or native app: which one for your business?

Published October 23, 20266 min read

For a business application used by your own teams, a web app, installable as a progressive web app (PWA), covers most needs at a lower cost than a native app: one codebase, no app store review, instant updates. A native app earns its place when the job needs deep access to the phone (background location, Bluetooth, long periods offline) or when your customers expect to find you on the App Store and Google Play.

This guide compares the three options criterion by criterion, in plain language, and is honest about where each one stops.

Three ways to ship an application

A web app runs in a browser on a desktop, tablet or phone. Nothing to install: a URL is enough. It is the natural form for an admin back office, a client portal or a management tool.

A PWA is a web app that goes further. According to Google's web.dev guide to PWAs, it "can be installed", gets an icon on the home screen, opens "in a standalone window, wholly separated from a browser's user interface", and can keep showing content when offline. The same guide points out that a web app can reach any device "with a single codebase".

A native app is written for one operating system, iOS or Android, and downloaded from the App Store or Google Play. It has full access to the device, at the cost of two apps to build, get approved and maintain. Cross-platform frameworks such as React Native and Flutter share much of the code between the two systems, but you still publish through the stores.

The comparison, criterion by criterion

Criterion	Web app	PWA	Native
Install	None	Home screen	App store
Offline	No	Partial	Full
Push	Desktop, Android	Yes (iOS 16.4+)	Yes
Updates	Instant	Instant	Store review

Three rows deserve a closer look.

Offline use. A PWA caches its screens and can queue what users enter until the connection returns. That is enough for a field engineer driving through a dead zone. For a stock count lasting several days in a warehouse with no coverage, with thousands of records and conflicting edits to reconcile, a native app gives you more headroom.

Push notifications on iPhone. This was long the main argument against PWAs. Apple added Web Push for web apps in 2023: as WebKit announced, from iOS and iPadOS 16.4, "a web app that has been added to the Home Screen can request permission to receive push notifications", after a user action such as tapping a subscribe button. A page simply open in Safari cannot: installation is still required.

Updates. A web app is up to date the moment you deploy it. A native app goes through Apple and Google review for every release, and users must install the update. For a business tool that changes every week, the difference shows quickly.

Where native is genuinely better

It would be dishonest to claim a PWA does everything. Native still wins on:

background work, such as continuous location tracking for a driver while the screen is off;
some hardware access, depending on the platform: Bluetooth, NFC, specialist sensors, professional scanners. Web support varies widely between browsers, and Safari on iPhone offers less than Chrome on Android;
long offline periods with a lot of local data;
store visibility, when customers search for your app by name;
very demanding interfaces, such as games or drawing tools.

If one of these sits at the heart of your use case, native is justified. If it is a nice-to-have, it rarely outweighs doubling the work.

What each option costs

Cost is driven less by screens than by how many things must be built and kept running.

Web app or PWA: one codebase for desktop, tablet and phone, often shared with the back office. No developer accounts, no commission on sales, no waiting for approval.
Native: two apps (or one cross-platform codebase), on top of the back office and server you need in every case. Add the Apple Developer Program at $99 a year, the one-time $25 Google Play registration, review for every release, and updates forced by new versions of iOS and Android.

One trap to know about: wrapping a website in an app shell to get onto the App Store is not enough. Apple's App Review Guidelines (guideline 4.2) ask for "features, content, and UI that elevate it beyond a repackaged website". If a store presence is essential, plan for it from day one.

For a detailed breakdown of mobile costs, see how much a mobile app costs for a business.

Four questions to decide

Who will use it? Your own staff, on devices you control, are well served by a PWA. Consumers who look for your brand in the App Store more often expect a store app.
Which phone features are essential? List them precisely. Camera, barcode scanning, one-off location and signature capture all work on the web. Background tracking and advanced Bluetooth point to native.
How long without a network? Minutes or hours: a PWA. Several days with a lot of data: native.
How often will it change? A business tool changes a lot in its first months. The web spares you an approval cycle for every fix.

If your answers lean towards the web, start there. The decision is not final: the server, data and back office carry over, and only the mobile front end would be rebuilt if a native need appears. Choosing between the two main cross-platform frameworks is covered in React Native vs Flutter.

Typical situations

Need	Sensible option
Admin, management, reporting	Web app
Field data, photos, signatures	PWA
Client portal with notifications	PWA
Continuous GPS tracking of a fleet	Native
Consumer app sold through the stores	Native

This table shows a tendency, not a rule. Many projects combine a web back office with an installable mobile front end; for a small or mid-sized business it is the most common setup.

Where LPR Studio stands

Our technical foundation is the web: React, Next.js and TypeScript, standard and well-documented tools. We build applications that work on desktop, tablet and phone, installable when the use case calls for it. We will not tell you a PWA replaces everything: when your need is genuinely native, we say so at the prototype stage, before any price is set. How long a first version takes is covered in how long it takes to build a business app, and our method is on the approach page.

Where to start

Start from how the tool will be used, not from its form: who uses it, where, with what network and which phone features. At LPR Studio, the visual prototype is free and presented in a video call within 5 working days, wherever you are. It shows the application on desktop and on mobile, which is the right moment to check that a web version is enough for your team.