Does your company actually need a mobile app — or is a responsive site enough?

"Do I need a mobile app?" is the question I get from at least one Baku business owner per month, and the honest answer almost always disappoints them. Most companies thinking about a native iOS/Android app would be better served — for less money, with faster delivery, with simpler maintenance — by a Progressive Web App or just a properly-built responsive website. Native isn't wrong; it's specific. This is how to figure out which side you're on, before signing a six-figure contract.

The question behind the question

"We need an app" almost always means one of three things, and only one of them actually requires a native app.

"Our customers should be able to use us on their phone." They already can — through your website on a mobile browser. This doesn't require an app. It requires a good mobile site.
"We want a presence on the App Store / Play Store." Often vanity, sometimes legitimate marketing real estate. Worth a deeper conversation about why.
"We need to access phone features the browser can't reach, or work offline reliably, or deliver native-tier performance." This is the legitimate native use case.

Most "we need an app" conversations are the first or second item, dressed up as the third. The honest version of the question separates them.

What native actually gives you

A native iOS and Android app delivers things a web app fundamentally cannot:

True background processing. The app can do work when not in the foreground — location tracking, syncing, periodic checks.
Deep OS integration. Widgets, Siri/Google Assistant shortcuts, contact list integration, share sheet participation.
Reliable offline mode. Web apps can be cached; native apps can be entirely offline-first.
Full hardware access. Bluetooth Low Energy, NFC, specific camera APIs, ARKit/ARCore.
Push notifications that work consistently. Web push exists but is unreliable on iOS specifically.
Native-tier performance. 60fps animations, instant transitions, no browser overhead.
App Store presence. Discoverability through App Store search and the "you should download this" expectation customers sometimes have.

These are real benefits. The question is whether your business needs them, or just looks like it does.

What a good responsive web site can actually do

Common misconceptions about web limitations:

"You need an app for camera access." No. Web has camera access through getUserMedia, including high-quality photo capture, video recording, QR code scanning.
"You need an app for GPS." No. Web has Geolocation API.
"You need an app for payments." No. Stripe, payment gateways, Apple Pay and Google Pay all work in mobile browsers.
"You need an app for push notifications." Mostly yes for iOS (improving slowly), no for Android (web push has worked for years).
"You need an app for offline." Web apps can work offline through service workers. Not as bulletproof as native, but acceptable for many use cases.
"You need an app for performance." A competently-built web app on modern hardware is indistinguishable from native for most use cases.

The honest answer: a good responsive web site, or a Progressive Web App, covers 70–85% of what most businesses imagine an app would do.

PWA vs native — the realistic middle

A Progressive Web App (PWA) is a web app that can be "installed" on a phone home screen, runs in a standalone window without browser chrome, can work offline, and can receive push notifications (on Android cleanly, on iOS with limitations).

PWA advantages over native:

One codebase covers iOS, Android, and desktop.
No App Store submission process — instant deployment of updates.
Much cheaper to build (often 30–50% of equivalent native app cost).
No App Store revenue cut (Apple and Google take 15–30% of in-app purchases).
Users don't have to "install" — they can just visit the URL.

PWA disadvantages vs native:

iOS support is partial. Push notifications work only as of iOS 16.4+, and many iOS users don't realise PWAs are installable.
No App Store presence — you lose discoverability.
Some hardware APIs unavailable (BLE, NFC, advanced camera features).
Background processing is much weaker than native.
Apple actively suppresses PWA capabilities periodically, and the platform feels less reliable on iOS.

For many businesses, PWA is the sweet spot — most of the native experience at a fraction of the cost.

When native is actually justified

Native is the right call when at least two of these are true:

Your business is the app. The app isn't a marketing surface — it's the product. Banking apps, taxi apps, food delivery apps, fitness apps, e-readers. The app is the core experience.
You need hardware capabilities the web can't reach. BLE for medical devices, NFC for ticketing, AR for retail try-ons, specific camera APIs for document scanning.
You need real background processing. Fleet tracking, parental monitoring apps, fitness apps that record GPS while the screen is off.
You're serving high-frequency users. A user opens the app daily, sometimes multiple times per day. The friction of "open the browser, type the URL" matters at that frequency.
You're competing in a category where customers expect an app. Banking is the clearest example. A bank without an app is at a measurable disadvantage.
App Store discoverability is a meaningful acquisition channel. True for some consumer categories, not most B2B ones.

If none of those are true, you're paying for native to satisfy an internal narrative, not a customer need.

The cost comparison, honestly

For an equivalent product:

Responsive website (well-built): 5,000–25,000 AZN. Covers desktop, tablet, and mobile browsers.
PWA (responsive site with offline + install + push): 8,000–32,000 AZN. Adds 20–30% over base responsive site.
Native app (iOS + Android, both platforms): 35,000–180,000 AZN. Sometimes much more. Two separate codebases unless using a cross-platform framework.
Cross-platform native (React Native, Flutter): 22,000–95,000 AZN. One codebase, but with some platform-specific work needed.

And maintenance:

Responsive site: 200–600 AZN/month.
PWA: 300–800 AZN/month.
Native app: 1,200–4,500 AZN/month minimum, because each OS update can break things, the platforms have separate App Store / Play Store review processes, and bugs have to be fixed twice.

A native app isn't just more expensive to build — it's more expensive forever after.

The decision framework, in one paragraph

Build a responsive website first, always. If your customers ask for an app frequently, and the friction of "open the browser" is genuinely hurting engagement, build a PWA. If the PWA hits a wall — needs hardware you can't reach, performance you can't match, or App Store presence you can't substitute for — then build native, on the strength of evidence rather than expectation.

The companies that get this wrong almost always go straight to native, spend 80,000 AZN, build an app that does 90% of what their existing website does, and discover six months later that most of their users are still using the website anyway.

At Qaynaq we build PWAs and responsive sites; for genuine native app projects we partner with mobile-focused teams rather than pretending it's an in-house specialty. If you want an honest conversation about whether your business actually needs an app, write to salam@qaynaq.com with what you're trying to solve.