This is the most important question in this entire guide series, because the wrong answer costs tens of thousands with no return.
The uncomfortable truth: most companies that ask for an app don't need one. What they usually need is a fast responsive website — at a third of the cost and with no download barrier.
This guide helps you tell the difference honestly, even if the conclusion is not to buy an app.
What is a PWA?
A progressive web app (PWA) is a website with capabilities approaching an app's: it runs in the browser, but can be installed to the home screen with an icon, works partially offline, and sends notifications (with limits on iOS).
In short: most of an app's benefits, without a store, a download, or a review process.
The reference table
| Criterion | Native app | PWA / responsive site |
|---|---|---|
| Cost | $8,000 – $120,000 | $3,000 – $25,000 |
| Timeline | 6 weeks – 18 months | 2 – 12 weeks |
| Barrier to reach | Store download | A link only |
| Appears in search results | No | Yes — a major advantage |
| Push notifications | Excellent | Good on Android, limited on iOS |
| Offline operation | Complete | Partial |
| Camera and GPS access | Complete | Good but limited |
| Store fees | $99 + $25 · plus subscription commission | None |
| Update deployment time | Days (store review) | Instant |
Indicative estimates based on Apex project experience in this market as of 2026. Actual cost depends on scope, integrations, and the level of customisation your project requires.
The download barrier — the biggest overlooked factor
This decides the fate of most apps, and is rarely discussed before building.
Every step between a customer's interest and their usage loses you part of the audience: they see the link → open the store → wait for the download → grant permissions → create an account. Every step loses a percentage of people.
The decisive question: is your app's value worth downloading for someone who hasn't tried you yet?
- A restaurant a customer orders from twice a month → they won't download. They'll order from a website or a delivery platform.
- A bank they use daily → they'll download without hesitation.
And most importantly: apps don't appear in Google search results, websites do. If acquiring customers through search is part of your plan, an app alone cuts off that source entirely.
Five reasons — and only these — that justify building an app
If none apply, a responsive website will serve you:
1. Repeat usage by the same customer. Daily, or weekly at minimum. Banking, fitness, productivity, communication. Repeat usage justifies the one-time download effort.
2. A genuine need for offline operation. A field app for technicians in areas without coverage, or a travel app. "The connection might drop sometimes" is not sufficient reason.
3. Reliable push notifications essential to the service. Alerting a driver to a new order, a security alert. Note: web notifications on iOS are limited, so if your audience is on iPhone and you depend on notifications, that is a genuine reason for an app.
4. Deep device hardware access. Camera with real-time processing, Bluetooth, biometric sensors, continuous background GPS tracking.
5. The app itself is your product. If you sell the app or monetise from within it, being in the stores is part of your business model.
When a website clearly suffices
- Presenting services and collecting enquiries — service companies, clinics, professional offices.
- An online store — most stores sell successfully over the web. See our e-commerce cost guide.
- Content and blogs — appearing in search matters far more than an icon on a screen.
- Simple appointment booking — a web booking system costs $3,000–$10,000 and does the job. See our clinic app guide.
- A brochure site — no debate here.
The smarter path: start with web
This is what we recommend to most clients:
1. Build an excellent responsive website first ($3,000–$15,000). Launch within weeks, appear in search, gather real users.
2. Measure behaviour. How many users return weekly? How many want notifications? What share of visitors are on mobile?
3. Build the app when the numbers demand it — with clear requirements grounded in actual behaviour rather than assumptions.
Why is this smarter? Because you test demand at a third of the cost, and build the app later knowing what people actually use — rather than building features nobody turns out to want.
Related reading
- Website design cost — the cost of the first option.
- Native or hybrid? — if you decide to build an app.
- MVP or full product? — start small and test demand.
Frequently asked questions
Does a PWA work on iPhone?
Yes, and it can be installed to the home screen. But push notification support on iOS is narrower than on Android, and some hardware capabilities are limited. If your audience is on iPhone and you depend fundamentally on notifications, that is a genuine reason to build an app.
How much do I save choosing web over an app?
Typically 50–70%. A good responsive website costs $3,000–$15,000 versus $8,000–$60,000 for an app with comparable functionality. Add the savings on store fees and in-app subscription commission (up to 30%), plus faster update deployment.
Do apps appear in Google search results?
No, not the way web pages do. This is among the most important and most overlooked differences: a website brings visitors from search continuously, while an app needs paid marketing or direct referral. If search-based customer acquisition is part of your plan, a website isn't optional but necessary.
Do I need both?
Many companies do — a website for discovery and search acquisition, an app for repeat customers. But start with web: the website serves the whole audience, while the app serves a loyal segment that doesn't exist yet if you're just starting.
What is the biggest mistake in this decision?
Building an app before verifying repeat demand exists. The loss isn't only build cost, but the wasted months and the paid marketing spent getting people to download something they hadn't been shown to want.
When should I move from web to an app?
When your numbers show repeat behaviour: a high weekly return rate, repeated user requests for a feature that needs an app, or a clear operational need (push notifications, offline operation). The decision follows data, not ambition.
Conclusion
Most companies don't need an app — they need a fast responsive website at a third of the cost, with no download barrier, that appears in search results.
An app earns its cost in five cases only: repeat usage, offline operation, critical notifications, advanced hardware, or the app being your product itself.
And the smarter path: start with web, measure behaviour, then build the app when your numbers demand it.
Want an honest opinion? Get in touch for a free assessment — and we'll tell you plainly if a website is enough, even when that means a smaller project for us. See our web development services.