"We need an app" is one of the most expensive sentences a business can say without thinking it through. Sometimes it's true. Often what's really needed is a fast, installable mobile experience — and that can cost a fraction of a native build. Before you commit to the Play Store and App Store route, it's worth understanding what you actually gain by going native, and what you give up by not.
There are really three choices on the table: a progressive web app (PWA), true native apps (separate codebases for Android and iOS), and cross-platform frameworks like Flutter that produce native apps from one codebase. Each fits a different situation. Here's the honest breakdown.
What a PWA actually is
A progressive web app is a website built to behave like an app. It runs in the browser but can be installed to the home screen, work offline, and send push notifications. No app store, no download, no install friction — a user taps a link and they're in.
PWAs have come a long way. On Android they're genuinely capable: installable, push notifications, offline caching, camera and location access all work. On iOS, support has historically lagged and remains more limited, though it has improved — push notifications, for instance, now work for installed web apps, with some constraints. That iOS gap is the single biggest thing to weigh when you choose.
Where a PWA shines:
- Cost and speed. One codebase serves web and mobile. You're not building and maintaining two or three separate apps, so it's typically the cheapest and fastest route to a working mobile product.
- No app-store friction. No review queues, no store fees, no waiting days for an update to go live. You ship a fix and every user has it instantly.
- Reach. Anyone with a link can use it immediately. For a first version testing demand, that low barrier is a real advantage.
- Discoverability. It's a website, so it's indexable by search engines — something a native app simply isn't.
If your app is mostly content, dashboards, bookings, ordering, or account management, a PWA often does everything you need at a fraction of the cost.
Where native earns its keep
Native apps — and capable cross-platform frameworks that compile to native — are the right call when the experience depends on things the web can't reliably reach:
- Deep hardware access. Bluetooth peripherals, advanced camera control, NFC, background location, fingerprint/face authentication, sensors. The web touches some of these but not all, and not consistently across devices.
- Heavy performance demands. Smooth high-frame-rate animation, real-time graphics, on-device processing, or anything graphics-intensive runs better native.
- Reliable offline-first behaviour. A PWA caches well, but apps built to work entirely offline with large local data — field tools, logistics, point-of-sale — are more dependable as native.
- Store presence as a channel. For consumer products, "search the App Store and find us" is a real distribution and credibility signal. Some users won't trust a product that isn't in the store.
- Rock-solid push and background work. Native push and background processing are more capable and consistent, especially on iOS where the PWA story is weaker.
The cost is exactly what makes PWAs attractive in reverse: you're now maintaining store listings, review cycles, and code that has to keep working across OS updates. That's an ongoing commitment, not a one-time build.
Where Flutter fits
If you've decided you need native but don't want to build and maintain two separate apps, cross-platform frameworks are the practical middle ground. Flutter, in particular, lets you build genuinely native Android and iOS apps from a single codebase, often reaching near-native performance, with the web as a possible additional target.
The trade-off is honest: you write once and ship to both stores, which saves real money over two separate native teams, but you're committing to the framework's ecosystem and occasionally writing platform-specific code for the trickiest device features. For most product apps that need store presence and good performance without bleeding-edge platform tricks, that trade is well worth it. We cover this in more detail on our Flutter app development page.
A simple way to decide
Run your idea through these questions in order:
- Does the experience need deep hardware, heavy performance, or true offline-first behaviour? If yes, you're looking at native or Flutter. If no, keep going.
- Is App Store / Play Store presence a real distribution or trust requirement for your audience? If yes, lean native or Flutter. If your users will happily use a link, a PWA is in play.
- How important is shipping fast and cheap right now? If you're validating demand or budget is tight, a PWA gets you to market quickly and you can go native later if the numbers justify it.
- Do you need it on web and mobile? A PWA covers both from one codebase; Flutter can target both too; pure native covers neither for free.
A pattern we often recommend: start with a PWA to prove the idea, then invest in native or Flutter once you know it works and you've hit a concrete wall. That sequencing keeps your spend tied to evidence rather than ambition. The mistake is building three native codebases for an idea you haven't validated — or forcing a hardware-heavy, store-dependent product into a PWA it will keep fighting.
The honest summary
Many businesses can and should start with a PWA: it's cheaper, faster, reaches everyone with a link, and updates instantly. Move to native or Flutter when you genuinely need the device's capabilities, the store as a channel, or performance the web can't deliver — and choose Flutter over separate native builds when you want store-grade apps without maintaining two codebases.
When we scope a mobile app development project, we start by pinning down which of these you actually need, so you don't pay for native when a PWA would do — or ship a PWA that can't do the job.
Trying to figure out which one fits your product? Tell us what you're building and we'll give you a straight recommendation, including the cheapest route that actually works.