“Should we build a mobile app?” comes up in nearly every first meeting we have, and it’s usually the most expensive sentence in the room. Most of the time our answer lands as a small letdown: not yet. Here’s the thinking behind it.
So let’s walk it the way we’d walk it with you across a table: a quick decision tree to reach a sensible default, a gut-check against your actual situation, then an honest look at what each road costs in time.
Start with one question
Strip away the noise and it nearly always comes down to one core question, with two smaller ones sitting behind it.
The tree leans toward web for one plain reason: a website is always cheaper to find, to share and to change. An app only earns the extra cost when people have a genuine reason to keep opening it.
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 costliest answer of all is “let’s do both at once.” You triple what you have to build and look after, all before you know whether a single customer actually wants it.
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
Forget matching feature for feature. What really separates the two is how long it takes to go live. A small-business web app is around two months of focused work. A proper iOS-and-Android launch is closer to five, because now you’re building three things — a backend, an iPhone app and an Android app — where the web route only needed a site and a backend.
Pick the cheaper bet first
If you remember one line from all this, make it this one: the question was never “web or mobile.” It’s “what’s the cheapest way to prove people actually want this?” For nine small businesses out of ten, the answer is a clean, fast website, with a native app kept in your back pocket for the day the demand makes it obvious.
That’s really the job we do at Zekora — helping you build the right version in the right order, so you’re not paying for an app-store launch before you’ve earned the audience for it.