PWA instead of an iOS/Android app: when it works and when you lose users

“We want an app.” Typical first sentence when a client arrives with a mobile use case. Often the right answer — but not always. For Fotopast.cloud, a SaaS for managing camera trap photos, we built one PWA instead of two native apps. Shipped in 2 months instead of 5-6, with full push notification support and an offline fallback.

It works. But not every mobile app would survive that transition. Five factors we weigh.

1. Hardware / sensor access — where PWA hits the wall

PWAs have limited hardware access. They can take camera input, but only through the file picker — not a live capture with a custom overlay. Bluetooth Low Energy? In Chrome yes, Safari still no. NFC? Android Chrome only. Background geolocation? Not reliably anywhere.

For Fotopast it was fine — photos upload in bulk from the trap camera over a different path (the camera's 4G module), and the PWA only displays and manages them. If the app had to let users scan custom QR codes right in-camera with AR preview, PWA would be out. It's a split: what the app does with the phone vs. what it does with the data.

2. Push notifications — Apple is the barrier

Web push notifications have worked in browsers since 2015. On iOS Safari they worked starting iOS 16.4 (April 2023), and even then only if the PWA is installed via “Add to Home Screen.” Without the install prompt, no push — Apple intentionally made it harder to protect its App Store ecosystem.

Fotopast's audience (hunters, gamekeepers) doesn't need push heavily — the trap camera emails them, that's enough. If your use case falls apart without instant push (chat, transaction alerts, security alerts), PWA leaves 30-40% of your iOS users uncovered.

3. App Store presence — the marketing factor

Don't underestimate the “we're in the App Store” credibility signal. For a consumer product that signal often matters (“we're a real brand”). For a B2B tool for a specific professional community — Fotopast is exactly that — irrelevant. Hunters find the app via QR codes in ads, word of mouth, Google search. “I discovered it on the App Store” contributes nothing.

Ask: where do your users actually find the app? If via App Store search, PWA is a handicap. If via web, QR, direct link — PWA is as good as native.

4. UX expectations of the audience

30+, professionals, B2B — 90% don't care whether the app is native or a PWA as long as it works. Gen Z, younger millennials, gaming, entertainment — they expect the install-from-App-Store flow; otherwise the app “doesn't feel right.”

Fotopast's audience is 40+, hunters, gamekeepers, farmers. For them, seeing a web app with the same home-screen icon as WhatsApp is a bonus, not a problem. For a 25-year-old's quick-service app, the same choice would feel wrong.

5. Offline scenarios and reliability

PWAs can do offline via Service Workers, but it's more work than in native (where SQLite or Core Data are first-class). If your app has to run 100% without signal — field tools, logistics — native is more reliable.

Fotopast's offline is nice-to-have, not must-have. A hunter in the forest has no signal, but also doesn't need it — the photos were downloaded earlier, they're just browsing. On reconnect it syncs.

A decision framework

PWA makes sense when:

• Hardware access fits within browser APIs (camera via picker, GPS when active, notifications with limits)
• B2B or 30+ professional audience
• Distribution via web/QR/direct link, not the App Store
• Offline is acceptable in a reduced form
• Fast iteration — one codebase instead of two

Native is a better fit when:

• Hardware use case requires custom capture / sensors / BLE
• Consumer audience expects App Store presence
• Push notifications are load-bearing (iOS barrier is a blocker)
• 100% offline is core to the use case
• Budget covers 2 codebases and 2 deployment pipelines (App Store review delays every ship by 1-3 days)

Fotopast outcome

2 months from kickoff to production. One codebase, three deployment targets (web, iOS home screen, Android home screen). User feedback 6 months in: no one said “I miss a native app.” That tells us the decision fit.

With a different audience the decision would be different. PWA isn't better or worse than native — it's a different trade-off. Those five factors are the map where you find your position on it.