"We want an app" is one of the most common opening lines we hear, and most of the time the honest answer is that an app is not what the business needs. Not because apps are bad, but because an app has to earn a place on somebody's home screen, and very few businesses give anyone a reason to keep one there.
The test
One question settles it most of the time:
Will the same person use this more than once a week, for months?
If yes, an app can be justified. Banking, food delivery, a tool your staff use every shift, a service with genuine daily habit behind it.
If no — and for a hotel, a jeweller, a clinic, a builder, a tour operator or a shop, it is almost always no — then an app is a very expensive way to be ignored. People will not install an application to book a room once a year. They will search, tap the first decent result, and call.
What an app costs that nobody mentions
The build is the small part. The recurring costs are:
- Two codebases, unless you use a cross-platform framework, and even then two sets of platform quirks.
- Store review, every time you fix a typo. Days, not minutes.
- Developer accounts, annually for Apple, once for Google.
- Forced upgrades. Both platforms drop support for old versions on their schedule, not yours. An app left alone for two years often simply stops being installable.
- Installation friction. This is the killer. Every step between "interested" and "using it" loses people, and an app has several: find it in the store, wait for a download, grant permissions, create an account.
A website has none of these. A link is the installation.
The middle option most people have not heard of
A progressive web app is a website that can be installed to the home screen, opens without browser chrome, works offline, and can be updated by you, instantly, without a store review. On Android — which is the phone your customers and staff are actually holding — the experience is close enough to a native app that most users cannot tell.
This is often the right answer for internal tools, where the audience is your own staff rather than the public. We built the field CRM for an agri business this way: their team installed it from a link, it caches what it needs so it keeps working when signal drops in the interior, and pushing a fix takes a deploy rather than a week of store review. A native app would have cost several times as much and been worse at the one thing that mattered — being updatable that afternoon.
PWAs are weaker on iOS, where Apple limits some capabilities, so if your audience is heavily iPhone-based, test before you commit.
When you genuinely do need native
There are real cases, and they share a pattern — you need something the browser cannot reach:
- Continuous background location, such as fleet or delivery tracking.
- Bluetooth hardware — printers, weighing scales, card machines.
- Serious offline work with large local data.
- Reliable push notifications to iPhones.
- Biometric login, or app-store distribution as a business requirement.
If your requirement is on that list, build the app. If it is not, you are probably buying a home-screen icon.
The question behind the question
When somebody asks for an app, what they usually want is one of three things: to look modern, to send notifications, or to make repeat ordering easier. Only the last genuinely needs an app, and even then only sometimes.
- Looking modern is a design problem. A fast, well-made site does more for that than an app nobody installs.
- Notifications — in India, WhatsApp reaches more of your customers, more reliably, than a push notification from an app they may have uninstalled.
- Repeat ordering — a saved cart and a one-tap reorder link work in a browser.
Our usual advice
Build the mobile website properly first. Make it fast on a mid-range Android on mobile data, make ordering or enquiring take two taps, and add WhatsApp as the contact route. Run it for six months and look at your analytics.
If a meaningful group of people is coming back weekly, you now have both a reason to build an app and the data to design it. If they are not, you have saved yourself several lakh and learned something true about your customers.
Common questions
Does my business need a mobile app?
Only if the same person will use it more than once a week for months. For a hotel, jeweller, clinic, builder or shop that is almost never true, and an app becomes an expensive icon nobody installs. A fast mobile website serves those businesses better.
What is a progressive web app?
A website that can be installed to the home screen, opens without browser chrome, works offline and updates instantly without app store review. On Android it feels close to a native app, which makes it a strong choice for internal tools and staff systems.
How much more does an app cost than a website?
The build is the small part. The recurring costs are two codebases, app store review on every fix, annual developer accounts, and forced upgrades when platforms drop support. A website has none of these, and a link is the installation.
