"Should we build an app?" is one of the most expensive questions a small business can get wrong. An app nobody opens costs tens of thousands of dollars up front and keeps costing money every year afterwards. But a mobile website that should have been an app quietly loses the repeat customers you worked hardest to win.
Here is the way we work through the decision with clients, including the parts of the standard app sales pitch that do not survive close reading.
Start with the honest baseline: most businesses do not need an app
Roughly 92% of small businesses worldwide still have no dedicated mobile app in 2026. That figure normally shows up in marketing material as a warning about how far behind you are. Read it the other way and it is the market telling you something useful: a fast, well-built mobile website is enough for the overwhelming majority of businesses.
The reason comes down to what each channel is good at. A website is how people find you. It is indexable by Google, shareable as a link, and one tap away from a search result, a social post or an ad. An app is something a person has to decide to install, which means it can only ever serve an audience you already have.
Websites acquire. Apps retain. Getting those two round the wrong way is the single most common and most expensive mistake in this decision.
There are three routes, not two
1. A responsive mobile website
One site that adapts to every screen size. It is the cheapest route, the only one search engines can index, and the only one with no installation barrier between a stranger and your business. For a service business, a local trade, a professional firm or a content-led brand, this is very often the whole answer. It is what our web design and development service builds by default.
2. A progressive web app
A website built to behave more like an app: installable to the home screen, able to cache content for offline use, and capable of sending push notifications on Android and on recent versions of iOS. You get one codebase, no app store review queue, and no store commission. It is a real middle path rather than a compromise, and it suits catalogues, booking tools, portals and internal staff tools particularly well.
3. A native or cross-platform app
A true app, distributed through the App Store and Google Play. Native means separate iOS and Android builds; cross-platform frameworks such as React Native and Flutter share one codebase across both. This is the right route when you need deep hardware access, sustained background activity, or the kind of performance a browser cannot reach. It is the work our mobile app development team takes on, and it is also by some distance the most expensive of the three.
What each route actually costs
The figures below are published industry benchmarks from third-party surveys, not Zenesa quotes. They are useful for sanity-checking a proposal, not for budgeting a specific project.
- Progressive web app: commonly quoted between $5,000 and $35,000, with more involved builds running higher.
- Cross-platform app (one codebase, both stores): typically cited at 30% to 60% below the cost of two separate native builds.
- Native iOS and Android: agency benchmarks cluster around $40,000 to $90,000 and upwards, with genuinely complex products going far beyond that.
Our own guide to mobile app costs goes into what moves a quote up or down, and the pricing page shows what our published packages include.
The running costs most quotes leave out
- Apple Developer Program: $99 a year, charged whether the app is free or paid, for as long as it stays on the App Store.
- Google Play: a one-time $25 registration, with no annual renewal.
- Maintenance: industry rules of thumb put native app upkeep at roughly 15% to 20% of the build cost per year, against about 10% for a progressive web app. Two codebases means two sets of operating system updates to keep pace with.
- Store commission — but only on digital goods. Apple takes 30%, or 15% under its Small Business Program and after the first year of a subscription. Google's rates changed in mid-2026 and now sit at 10% plus a 5% billing fee within the first $1m of annual earnings for users in the US, UK and EEA. Crucially, this applies to digital purchases only. Physical products, deliveries, bookings and real-world services fall outside it entirely, so plenty of small business apps pay no commission at all.
A short test: does your idea pass?
Make the case for an app if you can honestly say yes to at least two of these:
- Customers deal with you repeatedly — weekly, or close to it. Once-a-year purchases almost never justify an installed app.
- You need to reach people after they have left your site, and email is not doing the job.
- Your customers use the service somewhere with poor or no signal.
- You need real device hardware: sustained background location, Bluetooth accessories, NFC, or continuous camera scanning.
- You have a genuine account, loyalty or booking relationship that customers return to rather than a catalogue they browse once.
Stay on the mobile web if your honest answer is that customers buy from you occasionally, that your real problem is being found in the first place, or that an app would swallow the entire budget you also need for marketing. An unfound app is worth nothing; a found website compounds.
The iPhone caveat that rarely makes the pitch
If someone proposes a progressive web app, ask specifically about iOS. Installed web apps on iPhone still have no Background Sync API, no access to Bluetooth or NFC, and storage that Safari can clear after a period of inactivity. For a menu, a catalogue or a content app that is irrelevant. For a booking system that has to hold state offline, or anything that talks to hardware, it is disqualifying. Better to know before the build, not after.
Where these statistics come from, and how far to trust them
You will see confident claims that apps convert three times better than mobile websites. Treat them carefully: nearly every source publishing them sells app development or app-building platforms. The more credible number we have seen is a study of 21 retailers by Poq, which found apps converting about 1.8 times better than the same brand's mobile site, with 20 of the 21 showing a higher app conversion rate.
Even that is not the free win it appears to be. App users are a self-selected group — they already liked you enough to install something. A share of that conversion gap is the loyalty you had before the app existed, not value the app created. Which brings the argument back to the same place: an app is a retention tool, and it only pays for itself once you have people worth retaining.
What we usually recommend
For most businesses coming to us without an existing mobile audience, the sequence that wastes the least money is this:
- Build a genuinely fast, genuinely mobile-first website, and make sure it can be found. If you sell online, that means proper ecommerce web design and a checkout that works on a phone.
- Let it run long enough to produce real data. Look at how often the same people come back, on what device, and to do what.
- If the return visits are frequent enough to be worth protecting, build the app for that specific behaviour — not as a copy of the website with a launcher icon.
Sometimes step three never arrives, and that is a good outcome, not a failure. The businesses that regret building an app are almost always the ones that built it at step one.
Talk it through
If you are weighing this up right now, we are happy to give you a straight answer, including when the answer is that you do not need an app. Have a look at our mobile app development and web design services, or get in touch for a free, no-obligation conversation.
