What Is a PWA, and When Should Your Business Skip the Native App?

A PWA, or progressive web app, is a website built to behave like an installed app. Users open a link, tap Add to Home Screen, and get an icon that opens full screen and works offline, with no App Store or Google Play involved. For most internal tools and first versions, it does a native app's job for far less.

What a progressive web app actually is

A progressive web app is a normal web application with extra pieces that let a phone treat it as an app. A manifest file gives the phone the app's name and icon. A service worker, a script running in the background, saves the app's screens on the device so it still opens when the signal drops. The browser only allows this over a secure HTTPS connection.

Your user sees something simpler: a link by WhatsApp or email, saved to the home screen, that then opens full screen like any other app. Updates reach everyone the next time they open it, with no store review.

A PWA still runs inside the phone's browser engine, though, so it does not get everything a native app gets. The gap is widest on iPhone.

PWA vs native app: what you actually give up

Choosing a PWA over a native app means giving up store discovery and background access to the phone. In return you build one codebase instead of two, which costs less and updates without a store review. If your users have to find you by searching the App Store, a PWA is the wrong choice.

On iPhone, Apple only added web push for home screen apps in iOS 16.4, and it still works only once the user has added the app to the home screen. A PWA also cannot reliably track location while closed, which matters for tracking a vehicle all day. In South Africa that gap touches fewer people than US guides suggest: Statcounter Global Stats put Android at 81.42% of the country's mobile market in September 2026 and iOS at 18.57%.

The common mistake is paying for native because it feels more serious. Earlier this year we scoped a route planning and safe parking platform for a South African logistics business. Driver safety is the point of it: SAPS figures reported by Freight News counted 349 truck hijackings from October to December 2025. The value sat in the manager's route builder and a portal where truck stop attendants update free parking bays. The driver's job in phase one was to open the route, see the safe stops, and tap through to Waze, Google Maps or Apple Maps. We recommended a PWA for the driver app. With that choice, our estimate for the whole first version, not just the driver app, came out at 8 weeks instead of 14 and under half the cost of the native option. Estimated design time fell from 200 hours to 30, because the driver app would reuse the dashboard's interface components instead of following Apple's and Google's design rules. Both options were designed on the same backend, so a native app in phase two would need no rewrite.

How to decide between a PWA and a native app

Write down what your user does on the screen in the first version, and for how long. If it is a short, specific job, like checking a route or confirming a delivery, a PWA covers it. Most staff tools and B2B portals fall here, and so do most MVPs. This is the kind of first version we scope in our MVP development work, where the budget belongs in the part that creates the value. Whether one codebase can serve web and stores at once is a separate question, covered in web app vs mobile app.

Pay for native when strangers must find you in a store, or when the app has to run in the background all day. iPhone notifications are the other case, since a PWA only gets them after the user adds it to the home screen. Store distribution also brings Apple's and Google's fees and rules, which we cover in how to avoid app store fees. Ask any developer one thing: if we start as a PWA, how much of the backend carries over to native later? If the answer is "not much", the plan is wrong. Our guide to choosing a mobile app developer in South Africa has more questions.

A PWA is the right first version for most business apps that are handed to their users rather than found by them. Launch with it, and let real usage tell you whether native is worth paying for. Keep the backend separate from the screens, so that a native app later means a new front end, not a rebuild.

Questions about PWAs

What is the difference between a PWA and a native app?

A native app is built for iOS or Android and installed from a store. A PWA is built with web technology and installed from a link. Native gets deeper device access, such as background location. A PWA ships faster: our first-version estimate for a logistics platform was 8 weeks with a PWA driver app, against 14 with a native one.

Do PWAs work on iPhone?

Yes. PWAs work on iPhone, but the user has to add the app through the browser's Share menu, because iOS does not show an install prompt. Once added, it opens full screen like any app. Some features remain more limited than on Android, especially notifications and anything that needs to run in the background.

Can a PWA send push notifications on iPhone?

Yes, since iOS 16.4, which Apple announced on the WebKit blog in February 2023. The catch is that notifications only work after the user has added the app to the home screen and granted permission. If your users will not take that step, iPhone push from a PWA will not reach them.

Does a PWA work offline?

Yes. A PWA uses a service worker to save its screens and recent data on the device, so it opens and shows cached information without signal. Anything that needs fresh data, such as live parking availability, still needs a connection. In South Africa that matters during load shedding, when cell towers can drop out.

Do I need the App Store or Google Play for a PWA?

No. A PWA is shared as a link, and users save it to the home screen themselves. There is no store review to wait for. You also skip the developer account fees and the store's cut of payments. For a closed business tool, missing store discovery costs you nothing, because you already know who your users are.

Is a PWA cheaper to build than a native app in South Africa?

Yes. One web codebase serves every phone and there are no store reviews to design around. When we scoped a South African logistics platform, choosing a PWA for the driver app brought the whole first-version estimate to under half the native option, with design hours down from 200 to 30. The saving shrinks when heavy device features are needed.