Native app vs PWA for business: which one to ship (and which one gets expensive)
September 20, 2026 · 3 min read · genbia
“Build me an app” usually means three different things: mobile access to an admin, an icon on the customer’s phone, or a product in the App Store and Play with notifications and camera. Picking wrong is not a technical footnote. It is this year’s budget and every user’s friction.
What each one is, in operations
A PWA is a site that installs as an icon, works half-offline, and lives in the browser. Useful for catalogs, internal panels, and flows that are already web.
A native app (in our case, Expo / React Native) ships in the stores, uses system push, camera, background GPS, and the permission model users already understand.
It is not “modern vs old.” It is what the phone must do when the network drops or the rider is on the street.
Direct comparison
| Criterion | PWA | iOS/Android app |
|---|---|---|
| Install | URL + “add to home screen” | Store, review, developer accounts |
| Push | Limited (especially iOS) | Stable, expected by the user |
| GPS / camera / background | Fragile or incomplete | Built for fleet, evidence, appointments |
| Real offline | Page cache | Action queue, sync, photos |
| Customer trust | “It’s the website” | Brand icon on the phone |
| Upfront cost | Lower | Higher (stores + QA on two platforms) |
| Maintenance | One web deploy | Stores + versions + devices |
When a PWA is enough
- Users already come from the browser and do not miss a store icon.
- You do not depend on reliable push or continuous tracking.
- The flow is lookup + form, not capturing evidence in the field.
- You want to validate demand in weeks, not launch a mobile product.
If your “app” is really a Next.js site with login, start there. Publishing in stores for vanity delays learning.
When you do need a native app
- A rider, technician, or salesperson uses the phone as a work tool.
- The customer expects “the brand’s app,” not a Safari bookmark.
- Orders, appointments, or deliveries with real-time status.
- Photos, QR, location, or payments that iOS will not give you equally in the browser.
That is iOS and Android app development and the delivery platform: customer, rider, and admin are not the same surface.
The expensive mistake: two products that do not talk
A PWA for the customer and Excel for the rider is not “phase 1.” It is two truths. If you go mobile, the data model (order, assignment, evidence) lives in the backend. Screens hook into it. That is why mobile at Genbia does not start with the icon: it starts from custom software.
How we decide on a call
- Who opens the app every day (customer, staff, both).
- What happens if there is no signal for 10 minutes.
- Whether push is nice-to-have or the operations channel.
- Whether you must be in the stores for brand or partner policy.
With that we pick PWA, app, or white label. Not a stack because it is trendy.
GENBIA ships production apps with Expo/React Native and Next.js sites. A PWA is a valid option; it is not a shortcut when the work happens on the street.