Building a native app for both the App Store and Google Play is a big commitment, and for many businesses it’s more than they need. A progressive web app (PWA) offers a middle path: a website that behaves like an app, installs on a phone’s home screen, loads quickly and can even work with patchy connections. For New Zealand businesses weighing up mobile options, PWAs are worth understanding before you commit budget to two separate native apps.
This guide explains what a PWA is, what it can and can’t do, how it compares with native and cross-platform apps, and when it’s the smart choice.
What is a progressive web app?
A progressive web app is a web application built with modern browser technologies so it feels and behaves like an installed app. Users open it from a link or search result, and the browser offers to add it to their home screen. From then on it launches full screen with its own icon, without the browser address bar, much like a native app.
The word “progressive” refers to progressive enhancement: the app works for everyone in any modern browser, and adds richer features where the device and browser support them.
The technology behind a PWA
- Service worker: a background script that caches files and data, enabling fast loading and offline or low-connectivity use.
- Web app manifest: a small file describing the app’s name, icons, colours and how it should launch once installed.
- HTTPS: PWAs must be served securely, which protects users and is required for service workers.
- Responsive design: the interface adapts to phones, tablets and desktops.
Key benefits of progressive web apps
One codebase for every device
A single PWA runs on Android, iPhone, tablets and desktop browsers. That can reduce build and maintenance effort compared with maintaining separate native apps, which is attractive for SMEs and startups with limited budgets.
No app store friction
Users don’t need to search an app store, download a large file or wait for approval of every update. You publish changes to your server and everyone gets them on their next visit. You also avoid app store commission on many types of digital transactions, although you should check each store’s current rules if you plan to list there as well.
Fast and resilient
Caching through the service worker means repeat visits load quickly, and key screens can work offline. That’s useful for field staff in rural areas, on construction sites or anywhere mobile coverage drops out.
Discoverable through search
Because a PWA is built on the web, its public pages can be indexed by search engines. A native app’s content generally can’t be found through Google in the same way.
Lower barrier to engagement
People can use a PWA immediately from a link in an email, text or QR code, then install it later if they find it valuable. That’s often easier than persuading someone to download an app before they’ve seen any value.
Limitations to be aware of
PWAs have improved a lot, but they aren’t the right fit for every project. Common limitations include:
- iPhone support varies. Apple’s Safari supports installation and web push notifications on recent iOS versions, but some features arrive later or behave differently than on Android.
- Limited access to some hardware. Advanced Bluetooth, background processing, certain sensors and deep operating system integration are often restricted or unavailable.
- Less app store visibility. If customers expect to find you in the App Store, a PWA alone may not meet that expectation, though PWAs can sometimes be packaged for stores.
- Performance ceilings. Graphics-heavy games, complex video editing or augmented reality usually still perform better as native apps.
- Storage limits. Browsers can limit or clear cached data, so offline features need careful design.
PWA vs native app vs cross-platform app
The right choice depends on your users, features and budget. Here’s how the options typically compare:
| Factor | Progressive web app | Native app | Cross-platform app |
|---|---|---|---|
| Codebase | One, web technologies | Separate for iOS and Android | One shared, e.g. Flutter or React Native |
| Distribution | Web link, install from browser | App stores | App stores |
| Device features | Good and growing, some limits | Full access | Broad access |
| Offline use | Yes, with careful design | Yes | Yes |
| Updates | Instant, no store review | Via store review | Via store review |
| Typical relative cost | Usually lowest | Usually highest | Usually in between |
If you need full device access and an app store presence, our mobile app development or cross-platform app development services may suit better. If reach, speed and cost efficiency matter most, a PWA is often a strong starting point.
When a PWA makes sense for NZ businesses
PWAs work particularly well for:
- Online ordering and eCommerce: fast, app-like shopping for repeat customers, such as grocery, hospitality or trade supply orders.
- Field service and operations: job sheets, checklists and photo uploads for staff who move between sites with variable coverage.
- Customer portals: bookings, account management and order tracking without forcing an app download.
- Internal tools: staff dashboards, rostering and approvals that need to work on any device.
- Startup MVPs: testing a product idea with real users before investing in native apps.
- Events and memberships: schedules, tickets and updates that people use for a short period.
A PWA is a sensible option if most of your users are on modern smartphones, your features rely mainly on data and forms rather than specialised hardware, and you want to update quickly without app store delays.
What goes into building a good PWA
Start with a strong web application
A PWA is only as good as the web app underneath it. Clear user flows, fast pages and a responsive interface come first. Our web development team treats performance and usability as foundations, not extras.
Design the offline experience deliberately
Decide which screens and data must work offline, how changes made offline will sync later, and what users see when they’re disconnected. Getting this right avoids lost data and confusion.
Plan notifications carefully
Push notifications can bring people back, but too many will annoy them. Ask for permission at a sensible moment and send only messages people genuinely value.
Secure it properly
PWAs that handle personal information must meet your obligations under the Privacy Act 2020. That means HTTPS, secure authentication, sensible data storage on the device and a clear privacy policy.
Test on real devices
Test on a range of iPhones and Android phones, older models included, and in the browsers your customers use. Behaviour can differ more than you’d expect.
What does a PWA cost?
Costs depend on the features, integrations and offline requirements, so a scoped estimate is the only reliable figure. As a general rule, building one PWA typically costs less than building and maintaining two separate native apps with the same features, and turning an existing modern web app into a PWA can be a relatively modest project. Ongoing hosting and maintenance should be budgeted as with any software.
Getting started: a practical first step
If you already have a modern, responsive website or web app, a sensible first step is a short technical review. A developer can check whether your site is ready for a manifest and service worker, which pages would benefit most from caching, and whether any features your users rely on need native capabilities. From there, many businesses launch a focused PWA release covering the most-used tasks, measure how customers respond, and decide later whether a native or cross-platform app adds enough extra value to justify the investment. This staged approach keeps risk and cost under control while giving users a better experience quickly.
Frequently asked questions
Can a PWA work on iPhones?
Yes. iPhone users can add a PWA to their home screen from Safari, and recent iOS versions support features such as web push notifications. Some capabilities still differ from Android, so test early.
Can I put a PWA in the App Store or Google Play?
Google Play accepts PWAs packaged with tools such as Trusted Web Activities. Apple’s App Store is stricter, so listing usually requires a wrapper app with genuine native value.
Do PWAs work offline?
They can. Service workers cache key screens and data so the app keeps working without a connection, then syncs when it’s back online. The offline behaviour has to be designed and tested.
Is a PWA good for SEO?
Yes, public pages in a PWA can be indexed like any website, provided they’re built with search in mind, including fast loading and content that search engines can render.
Can my existing website become a PWA?
Often, yes. If your site already runs on HTTPS and is responsive, adding a manifest and service worker can deliver installability and faster repeat visits. More app-like features may need extra development.
Should I choose a PWA or a native app?
Choose a PWA when reach, cost and fast updates matter most and your features don’t need deep hardware access. Choose native or cross-platform when you need full device capabilities or an app store presence.
Explore whether a PWA fits your business
A progressive web app can give your customers and staff an app-like experience without the cost and friction of separate native apps. Wisdom Software is an Auckland-based team that builds web applications, PWAs and mobile apps for New Zealand businesses, and we’ll give you an honest view of which approach suits your goals.
Book a free 60-minute consultation to talk through your users, features and budget, and we’ll map out the most practical way forward.