“Should we build a mobile app?” is one of the most common — and most expensive — questions we hear from small businesses. The right answer is rarely “yes” on the first product. It is usually “not yet, and here’s why.”
This post walks through the decision the way we walk through it with clients: a short tree to get to a default answer, a scorecard to sanity-check it, and a timeline to put real cost on the choice.
Start with one question
Almost every web-vs-mobile decision collapses to two follow-up questions on top of one core one.
The reason the tree leans toward web is simple: web is always cheaper to find, share, and update. Mobile only pays back when there is a real reason users keep opening the icon.
When the web wins
- You need to be found. Search engines crawl websites, not app stores in the same way. If discovery is part of growth, you need a web presence first.
- Your users are casual. Booking once a month, checking a price, filling a form. Asking them to install an app is asking them to opt in to a relationship they don’t want yet.
- You ship changes often. A web app deploys in minutes. A mobile app needs a store review every time you fix a typo.
- You have one team. One web codebase covers iPhone, Android, tablets, laptops, work computers. Two mobile codebases cover only iPhone and Android — and you still need a backend.
When mobile wins
- Re-engagement matters. If your business model depends on people opening the product several times a week, the home-screen icon and push notifications are worth the cost.
- You need the device. Camera-heavy flows (delivery proof, KYC scans), GPS, biometrics, NFC payments — these are native-first capabilities.
- The network is unreliable. Field agents, drivers, technicians. Offline storage and sync make mobile non-optional.
- Performance is part of the brand. If smooth, near-instant interactions are the product (think wallets, trading, gaming), native still has a real edge.
The “both” trap — and the PWA middle ground
The most expensive answer is “let’s do both at the same time.” It triples the surface area you have to maintain before you know whether the product idea even works.
A better sequence:
- Ship the web version first. Use it to validate that real users will pay, return, and recommend it.
- Add a Progressive Web App (PWA) layer for installable-from-the-browser, basic offline, and home-screen presence. It gets you ~70% of the “feels like an app” experience for ~10% of the cost.
- Build a native app only when the PWA stops being enough — usually that means push notifications you can’t live without, deep hardware integration, or store-level distribution becoming critical.
What it actually costs
The honest comparison isn’t feature-for-feature — it’s effort-to-launch. A small-business web app takes about two months of focused work; a real iOS + Android launch is closer to five months because you’re building three things (backend, iOS, Android) instead of one (web + backend).
Pick the cheaper bet first
If you take one thing away: the question isn’t “web or mobile?” — it’s “what’s the cheapest experiment that proves people want this?” For 9 out of 10 small businesses, that experiment is a clean, fast, well-structured web app — with the option to add native later, once the demand is real.
That’s the work we do at Zekora: building the right version of the product, in the right order, so you’re not paying for an app store presence before you’ve earned it.