Do you need an app, or is a mobile website enough?
A mobile website is enough unless people use you weekly or need push, offline use, camera or location. A five-question test and what each option costs.
By Sohail Hussain11 November 20265 min read
A mobile website is enough for most businesses. You need an app when the same people will use it every week or more, and it must do something a website does poorly: push notifications they want, use without a signal, the camera or background location, Bluetooth hardware, or a fast logged-in routine like reordering or checking in. If people visit you once a month to read, compare or fill in a form, a fast mobile website serves them better and costs a fraction of an app to build and run.
We build apps through our mobile app development service, and we still recommend starting with the website more often than not. The test below takes five minutes; the rest of the post shows what each option can do and what it costs.
What can an app do that a mobile website cannot?
Less than people expect. Mobile browsers handle maps, payments, the camera for a photo upload, location while the page is open, and sign-in with a fingerprint or face through passkeys. The gaps are in a few specific capabilities and in habit.
| Capability | Mobile website | Progressive web app | Store app |
|---|---|---|---|
| Found through Google search | Yes | Yes | No; found in the stores |
| Needs an install | No | Optional | Yes |
| Push notifications | No | Android yes; iPhone only after adding to the home screen | Yes |
| Works without a connection | No | Yes, with work | Yes |
| Background location tracking | No | No | Yes, with permission |
| Bluetooth and NFC hardware | Android Chrome only | Android Chrome only | Yes |
| Home-screen icon | No | Yes | Yes |
| Updates | Instant | Instant | Through store review, except small over-the-air fixes |
| Ongoing store fees and rules | None | None | Yes |
Capabilities are as of October 2026 and change with each browser and OS release. The middle column is a real option: a progressive web app is a website that installs and works offline, and it covers more cases than people assume.
How often will people actually use it?
Frequency decides this more than features. An app asks people to find it in a store, install it, sign in and keep it. People do that for things they use often. They do not do it for a business they deal with twice a year.
Think about the apps on your own phone. Banking, messaging, food delivery, the airline you fly most, the gym you go to. Now think of the last plumber, accountant or furniture shop you used. You used their website, and you would not have installed their app.
If your customers come back daily or weekly, an app removes friction: they stay signed in, open it from the home screen and get notifications they asked for. If they come back monthly or less, every one of them meets the install step first, and most will not take it. The apps we build nearly always serve the first group: staff, drivers, members, patients with ongoing treatment, regular customers.
What does each option cost to build and run?
As of October 2026, from a small studio, a simple app with login and content costs US$20,000 to 60,000, and an app with accounts, payments, push and an admin panel US$50,000 to 150,000. Keeping it running adds 15 to 25 percent of the build cost each year for OS and store updates, plus backend hosting and the Apple developer fee. How much a mobile app costs breaks that down by feature.
A well-built mobile website is a fraction of that, and it is something you probably need anyway: it is how people find you in search. How much a website costs has the ranges. If you already have a decent site, making it faster and better on phones is the cheapest improvement available.
The running costs differ in kind as well as size. A website changes when you change it. An app changes when Apple and Google change their rules, every year, whether you want new features or not. An app with no maintenance budget usually stops working properly within a couple of OS releases.
The five-question test
Answer each honestly. Two or more "yes" answers make a real case for an app; one or none means start with the website.
- Will the same people use it at least weekly? Staff, members, regular customers.
- Do they need notifications they would be annoyed to miss? Order status, appointment reminders, shift changes, messages. Promotions do not count.
- Will they use it where the signal is poor? Warehouses, basements, rural sites, aircraft.
- Does it need device features beyond a photo upload? Background location, Bluetooth printers or scanners, NFC, continuous camera scanning.
- Is a quick signed-in routine the main use? Reorder, check in, log a job, scan a ticket.
If your only reasons are "competitors have one" or "it looks more established", do not build it. Spend the money on the website and on whatever brings customers to it.
When is the answer both?
Most businesses that need an app also need a website. The website does discovery: search, ads, links, first-time visitors. The app serves people who already chose you and come back often.
Three things make the pair work:
- One backend. The website and the app should read and write the same data through the same API. Two systems for the same customers drift apart within months.
- Links that open the app. Universal links on iOS and App Links on Android open the right screen in the app when it is installed, and the web page when it is not.
- A gentle prompt. A banner on your mobile site that offers the app to returning, signed-in visitors. Apple supports this natively with Smart App Banners. Do not block the website behind an "install our app" screen; Google treats intrusive interstitials as a poor mobile experience, and visitors leave.
What should you build first if you are not sure?
The website, with the app in mind. Build or fix a fast mobile-first site on a backend that exposes an API. Measure how many visitors return weekly and what they do. If a large, frequent group emerges, that group is your app's audience and their most common task is your first version's scope.
If the test above gave you two or more yeses, write a mobile app brief and run the features through the app cost calculator. The mobile app development guide covers the decisions that follow, from native or cross-platform to how the app reaches the stores.
Was this guide useful?