PWA vs. Native App: Does Your Business Actually Need an App, or Will a Website Do?

The App Question Every Business Faces

At some point, someone on your team (or a client, or your cousin who works in tech) will say: "We should build an app."

It sounds exciting. An app icon on people's phones. Push notifications. A dedicated experience. It feels like legitimacy.

But here's the uncomfortable truth: most business apps fail. The average smartphone user downloads zero new apps per month. The apps people do use are dominated by a handful of giants — social media, messaging, banking, and streaming. Your local service business or B2B company is not competing for that home screen space.

That doesn't mean mobile doesn't matter — it absolutely does. But the solution for most businesses isn't a native app. It's either a Progressive Web App (PWA) or simply a fast, well-designed mobile website.

What's a Progressive Web App?

A PWA is a website that behaves like an app. It's built with standard web technologies (HTML, CSS, JavaScript) but offers capabilities that used to be exclusive to native apps:

Installable: Users can add it to their home screen without an app store
Offline capable: Works without an internet connection (for cached content)
Push notifications: Send alerts even when the browser is closed
Fast: Caches assets for near-instant loading after first visit
Responsive: Adapts to any screen size
Updatable: Changes deploy instantly (no app store review process)

Examples of PWAs you may have used:

Twitter/X (twitter.com as a PWA)
Starbucks (ordering PWA)
Pinterest
Uber
Spotify (web player)

The Comparison

Cost

| | PWA | Native App | |---|-----|------------| | Development | $5,000-$30,000 | $25,000-$200,000+ | | Timeline | 4-12 weeks | 12-40 weeks | | Maintenance | Low (one codebase) | High (iOS + Android + backend) | | Updates | Instant (deploy to web) | App store review (1-7 days) | | App store fees | None | $99/year (Apple) + $25 one-time (Google) |

A native app requires separate development for iOS (Swift) and Android (Kotlin) — or a cross-platform framework like React Native or Flutter, which is cheaper but still significantly more expensive than a PWA.

Capabilities

| Feature | PWA | Native App | |---------|-----|------------| | Offline access | Yes (cached content) | Yes (full) | | Push notifications | Yes (Android + desktop; limited on iOS) | Yes (full) | | Camera access | Yes | Yes | | GPS / Location | Yes | Yes | | Bluetooth | Limited | Yes | | NFC | Limited | Yes | | Contacts access | No | Yes | | App store presence | No | Yes | | Home screen install | Yes (prompted) | Yes (via store) | | Biometric auth | Limited | Yes | | Background processing | Limited | Yes | | Performance (graphics-heavy) | Good | Excellent |

The gap has narrowed significantly. In 2026, PWAs can do about 85-90% of what native apps can. The remaining 10-15% matters for specific use cases but is irrelevant for most business applications.

User Experience

PWA advantages:

No download friction (no app store, no install, no storage worries)
Instant access via URL (shareable, searchable)
Always up to date (no version fragmentation)
Discoverable via search engines (SEO benefit)

Native app advantages:

Smoother animations and transitions
Better integration with device features
More reliable push notifications (especially on iOS)
App store discovery (for consumer apps with broad appeal)
Perceived legitimacy for certain industries

The iOS Problem

Apple has historically limited PWA capabilities on iOS/Safari. While things have improved in 2026, there are still restrictions:

Push notifications work on iOS 16.4+ but with limitations
No background sync
PWAs get evicted from storage if not used regularly
Installation prompts are less obvious than on Android

If your audience is heavily iOS (which in New Zealand and Australia, it often is), this matters. A PWA will work, but the experience won't be quite as seamless as on Android.

When You Need a Native App

Legitimate Reasons

Hardware-intensive features: Bluetooth connectivity, NFC, advanced sensors
Graphics-heavy applications: Games, AR experiences, complex animations
Background processing: Fitness tracking, location monitoring, music playback
Offline-first critical use: Apps that must work reliably without any connectivity
App store presence is essential: Your audience discovers apps through stores, or your industry expects it
Enterprise deployment: MDM (Mobile Device Management) integration for corporate devices

Poor Reasons (That Sound Good)

"Our competitors have an app" — do their users actually use it? Check the app store reviews and download counts.
"We need push notifications" — PWAs handle push notifications on most platforms now.
"It'll look more professional" — a well-designed mobile website is indistinguishable from an app for most users.
"We want an icon on their home screen" — PWAs can be installed to the home screen.
"We need offline access" — PWAs support offline functionality for cached content.

When a PWA Is the Right Choice

Strong PWA Use Cases

Service businesses: Booking systems, client portals, service tracking. Users access occasionally, don't want to download an app for something they use monthly.

E-commerce: Product browsing, cart management, checkout. PWAs convert at 2-3x the rate of mobile web because they're faster and can send abandoned cart notifications.

Content platforms: News, blogs, reference material. Offline reading, fast loading, push notification for new content.

Internal tools: Employee dashboards, project management, reporting. No app store distribution needed.

Event/venue: Menus, schedules, maps. QR code → instant access, no download required.

The Conversion Advantage

Native apps require a user to:

Find the app in the store
Click install
Wait for download
Open the app
Possibly create an account

A PWA requires:

Click a link
Use it

Every step in the native app journey loses users. Studies show that requiring an app download reduces engagement by 20% compared to instant web access.

When a Good Mobile Website Is Enough

Here's the option nobody wants to hear: for most businesses, you don't need a PWA or a native app. You need a fast, well-designed mobile website.

A mobile website is enough if:

Your users visit occasionally (not daily)
You don't need push notifications
Offline access isn't important
Your primary goal is information and lead generation
Your budget is limited

The vast majority of local businesses, service companies, and B2B firms fall into this category. A responsive website that loads in under 3 seconds on mobile will serve you better than a mediocre app that 200 people download and 15 actually use.

Building a PWA: What's Involved

If you've decided a PWA makes sense, here's what's required:

Technical Requirements

HTTPS: Your site must be served over a secure connection (this should already be the case)
Service Worker: A JavaScript file that manages caching, offline functionality, and push notifications
Web App Manifest: A JSON file that tells browsers how to display your app (icon, name, theme colour, display mode)
Responsive design: Must work across all screen sizes
Fast loading: Under 3 seconds on 3G networks

Development Approach

Upgrade existing website: If your site is already well-built, adding PWA capabilities can take as little as 1-2 weeks of development time.

Build from scratch: A new PWA built with frameworks like Next.js, Nuxt, or SvelteKit: 4-12 weeks depending on complexity.

Use a PWA builder: Tools like PWABuilder (by Microsoft) can add basic PWA capabilities to existing sites with minimal code.

Framework Options

| Framework | PWA Support | Best For | |-----------|------------|----------| | Next.js (React) | Excellent (next-pwa plugin) | Complex apps, SEO-heavy sites | | Nuxt (Vue) | Excellent (built-in PWA module) | Vue-based projects | | SvelteKit | Good (manual setup) | Performance-focused apps | | Gatsby | Good (gatsby-plugin-offline) | Content-heavy sites | | Angular | Excellent (built-in) | Enterprise applications |

The Decision Framework

Ask These Questions

1. How often will users interact with it?

Daily → Native app or PWA
Weekly → PWA
Monthly or less → Mobile website

2. Do you need device hardware access beyond camera and GPS?

Yes (Bluetooth, NFC, sensors) → Native app
No → PWA or mobile website

3. What's your budget?

Under $10K → Mobile website
$10K-$30K → PWA
$30K+ → Native app is an option

4. How important are push notifications?

Critical to the business model → PWA or native app
Nice to have → PWA
Not needed → Mobile website

5. Is your audience primarily iOS?

Yes, and you need full native features → Native app
Yes, but basic PWA features are fine → PWA
Mixed or Android-heavy → PWA works great

6. Do you need app store presence?

Yes, for discovery and credibility → Native app
No → PWA

The Hybrid Path

You don't have to choose once and forever.

Start with a mobile website. Get it fast, responsive, and well-designed. This serves 80% of your needs.

Upgrade to a PWA when you need offline access, push notifications, or installability. This can often be done on top of your existing site.

Build a native app only when you've validated demand through your PWA usage data and your business genuinely requires native capabilities.

This progressive approach saves money, validates assumptions, and ensures you're building what your users actually need — not what sounds impressive in a meeting.

The Bottom Line

Most businesses asking "should we build an app?" should actually be asking "is our mobile website good enough?" For the majority, the answer is to invest in a fast, well-designed responsive site — and save the app budget for marketing that drives people to it.

If you genuinely need app-like features, a PWA delivers 90% of the native experience at 20% of the cost. And if your use case truly demands a native app, at least you'll know you chose it for the right reasons, not just because it sounded cool.