Mobile App or PWA: Which One Does Your Business Actually Need?

The Decision in 30 Seconds

You need a native mobile app if:

Users need to perform a task more than 2x per week
You require push notifications that work reliably
You need camera, Bluetooth, ARKit, HealthKit, or other device APIs
Being on the App Store is a credibility signal for your audience
You charge in-app purchases or subscriptions

You're better off with a Progressive Web App if:

Users come to you 1–2x per month (or less)
The task is short and infrequent
You have a small budget and you're testing the market
SEO is your main acquisition channel
You can't justify the time cost of two App Store reviews

Everything below is just unpacking those bullets.

What a PWA Actually Is in 2026

A Progressive Web App is a regular website with three add-ons: a service worker (offline caching), a web app manifest (so it can be installed to the home screen), and modern web APIs (push notifications, geolocation, camera).

On Android in 2026, PWAs are near-equivalent to native apps in capability. On iOS, Apple still throttles them deliberately: limited push notification support, sketchy background sync, and Safari resets the cache every 7 days of inactivity.

That iOS gap is the entire crux of the decision.

The iOS Reality

If even 30% of your users are on iPhone and they care about push notifications, you need a native app. PWAs on iOS still suffer from:

Notifications require the user to first open the PWA, then approve a separate prompt
Background fetch is unreliable
Storage limits kick in faster
No App Store presence = no organic discovery

If your audience is overwhelmingly Android (think parts of Southeast Asia, Latin America, India), PWAs are a far better cost-benefit. In Canada, the US, and Western Europe, iOS share is high enough that the PWA-only route hurts.

When PWA Wins Cleanly

Internal tools. Your sales team using a Salesforce dashboard on the road. They don't need an App Store presence. They need fast load and reliable forms. A PWA is the right answer - easier to deploy, easier to update, no review delays.

Content-heavy, SEO-driven products. A recipe site, a blog, a documentation product. The PWA gets you indexable content AND a save-to-home-screen option for power users. Building a native app for this would be over-engineering.

MVP validation. You don't know if users want this thing yet. A PWA you can deploy on Vercel in an afternoon beats a 6-week App Store submission cycle.

When Native Wins Cleanly

Daily-use consumer products. Workout tracker, meditation, journaling, social. Users open these 5+ times a week. They need to live on the home screen, work offline, and use push notifications that actually arrive.

Service business client apps. CCXITMT's video review app, Founder Feast's event app. Users open them when there's something to do, but it has to feel reliable. App Store presence matters.

Anything with payments. Apple's 30% in-app purchase tax sucks, but the trust signal from a real App Store listing is worth real money for a paid product.

Anything needing native device APIs. Camera with computer vision, Bluetooth peripherals, ARKit, HealthKit. PWAs can't access most of these reliably.

The Hybrid Trap

Sometimes founders ask: "Can I have a PWA AND a native app?" Yes, but it's almost never the right answer for a small team. You now maintain two products. The PWA exists to skip an install. The native app exists for power users. Each platform's bugs are now your problem twice.

A better pattern: ship the native app, and have a marketing site that deep-links into it. If a user lands on a product page without the app, show "Open in App" with a fallback to "Install".

Cost Comparison

PWA from scratch: CAD 8k–18k for an MVP. No App Store review. No native build pipeline.

Native cross-platform app (React Native): CAD 18k–35k for the same scope. Plus 5–10 business days for first App Store review.

For a one-off, that's a real difference. For a product you'll maintain for 2+ years, the gap closes - native apps need fewer "Apple just changed something" emergency fixes.

What "Push Notifications" Really Means in 2026

This is the biggest single PWA gotcha.

On Android, PWA push works fine. Almost identical to native.

On iOS, Apple finally added PWA push notifications in iOS 16.4, but with caveats:

The PWA must be installed to the home screen first
The user must explicitly approve a push permission separately
Delivery is less reliable than native (Apple deprioritizes them in low-power mode)
No rich content support (images, action buttons) at parity with native

If push notifications are critical to your engagement loop and you have iOS users, build native.

App Store Review: The Hidden Cost

The first App Store submission for a native app will be rejected. It's almost a law. You'll forget a required URL in the metadata, you won't have the right "Sign in with Apple" implementation, or your privacy policy will reference a data point you don't actually collect.

Budget 2 weeks total: 5 days for first submission and rejection, 3 days to fix and resubmit, another 5 days for the second review. After the first app, you'll know what to check. The first time is rough.

PWAs ship the moment you push to production. That's a legitimate advantage.

The Decision Tree

Do you need camera, Bluetooth, HealthKit, ARKit, or similar? → Native.
Are users opening this 3+ times per week and need push notifications? → Native.
Are payments / subscriptions a core revenue driver? → Native.
Is App Store presence a credibility signal? (legal, healthcare, finance) → Native.
Otherwise, are most users on Android? → PWA.
Otherwise → PWA, with a plan to add native if engagement justifies it.

My Default Answer

For service businesses asking "should we build a mobile app?", I usually push back first. A well-designed mobile-optimized website plus a PWA install banner covers 80% of the use case at 30% of the cost.

For SaaS founders building a product that lives on someone's home screen and competes for daily attention, the answer is almost always native. If that's you, see my React Native + Expo MVP guide and what it actually costs in Canada.

Want Help Deciding?

I'll spend 30 minutes on your specific situation and give you a clear recommendation, not a sales pitch. Book a call.