Most Businesses Don't Need an App

Somebody in your extended network has an app. A cousin's distributor, a competitor in Noida, a supplier who keeps mentioning it. So the question arrives at your desk: should we build one too?

The honest answer, for most Indian businesses under a few hundred crore, is no. Not because apps are bad, but because an app is a subscription you pay forever in money and attention, and most businesses cannot name a single thing it would do that a fast mobile site would not. This piece gives you the test.

What an app actually costs after it is built

The build quote is the smallest number in the conversation. What people underestimate is that an app is two products, not one, and both of them decay.

You are shipping to iPhone and to Android. Even with a shared codebase, that is two store listings, two review processes, two sets of device quirks, two crash reports to read. Then the platforms move underneath you. Apple charges roughly $99 a year — about eight thousand rupees at current rates — just to keep a developer account alive; let it lapse and your app disappears from the App Store. Google Play charges a one-time registration fee of $25, but it enforces something more expensive: apps must target a reasonably recent Android API level, and that bar rises every year. An app nobody has touched in eighteen months can be pulled from the store for no reason other than age.

So the real cost is: build, plus a retainer for OS updates you did not ask for, plus someone to answer one-star reviews, plus the phone bill of the person who fixes it when it crashes on a Redmi model you have never held. If you would not happily pay that every month for three years, you are not buying an app. You are buying a project that will quietly die and leave a dead listing with your company's name on it.

The install is the real wall

Here is the mechanism that kills most business apps, and it has nothing to do with code.

A mobile website costs the user one tap from a Google result or a WhatsApp link. An app costs them: tap the link, land on a store page, wait for a download over patchy 4G, find space on a phone that is already full, open it, and — usually — create an account before they see anything. Every one of those steps sheds people. And you have to win that whole sequence before they have any evidence you are worth it.

Then there is the home screen. Look at yours. Most people keep a handful of apps they open daily and a folder of things they downloaded once. For your app to survive there, a customer has to want you weekly. A wholesaler placing orders every Tuesday wants you weekly. Somebody who buys a water purifier once in five years does not, and no amount of design changes that.

This is why "we'll send push notifications" is a weak reason to build. Push only reaches people who installed and did not mute you. If you have not earned the install, push reaches nobody. Meanwhile a WhatsApp Business message reaches a number you already have.

The conditions that justify an app

An app earns its keep when it does something a browser genuinely cannot, or does something so often that install friction is paid back quickly. In practice that means one of these:

• Weekly or daily repeat use by the same people. Distributor ordering, tiffin and grocery subscriptions, gyms, clinics with recurring appointments, a school parent portal. Frequency is the single strongest signal.
• A logged-in workforce. Field staff, delivery riders, service technicians, sales teams collecting orders in the market. These users are contractually obliged to install it, so the install wall vanishes. This is the most reliably successful category of Indian business app and it is usually an internal tool, not a customer one.
• Real hardware needs. Barcode scanning all day, background location tracking for a route, working offline in a basement warehouse or a village with no signal, tight integration with a Bluetooth printer or a card reader. Browsers can do some of this now, but badly and inconsistently.
• Money moving repeatedly. Saved payment methods, wallets, loyalty balances, subscriptions where the friction of re-entering details every time actually loses you sales.

If you can tick one of these honestly, keep talking about an app. If you cannot, you are considering a mobile app because it feels like what a serious company does, and that is an expensive feeling.

What the same money buys on your mobile site

Most of what owners actually want from an app — feels fast, looks modern, customers can order without ringing us — is available on the web, for less, with no install.

Start with speed, because it is the closest thing to a free lunch. Google publishes its Core Web Vitals thresholds openly: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. A site that clears those on a mid-range Android over 4G feels, to a customer, indistinguishable from an app. A photo straight off a phone is often four megabytes; resized and served properly it can be under two hundred kilobytes. That one change does more for perceived quality than any animation.

Then the things people think are app-only and are not: Add to Home Screen gives you an icon on the phone without a store; a mobile site can hold a login, a saved cart, an order history and a payment gateway; a WhatsApp click-to-chat button beats in-app messaging for almost every Indian SMB because the customer is already in WhatsApp. Add a clean ordering flow and a proper CRM to hold the customer record, and you have most of the app without the store, the review queue or the annual fees. If the site is the problem, that is a web development job, not an app job.

What not to buy

Some things get sold hard in this category and we would not spend our own money on them.

• The webview wrapper. Agencies will offer to "convert your website into an app" cheaply. What you get is your existing site loaded inside an app shell. It is slower than the browser, it looks like a website with a stuck header, and both stores have a long history of rejecting apps that add no value beyond a repackaged site. You pay to be worse.
• The website-plus-app bundle at one price. If the app is nearly free when bundled, it is nearly free because nobody intends to maintain it. Ask what year two costs. The silence is the answer.
• An app justified by push notifications alone. See above. Reach without an install is zero.
• An app before you can see your own numbers. If you cannot currently say how many people visit your site on mobile and where they drop off, you have no basis for the spec.

The option nobody pitches you

Frequently the real problem behind "we need an app" is internal: orders arriving on three WhatsApp numbers, a dispatch register in a notebook, quotations retyped from scratch. The customer-facing app would not fix any of that. A tidy internal system would.

That may be a workflow automation job, or a CRM that field staff can open on a browser on their own phones. It is usually cheaper than an app, it does not need store approval, and you can change it on a Thursday afternoon without waiting for a review. If it later turns out your staff really do need offline capability or barcode scanning, that internal tool becomes a very well-specified brief for a genuine app — built with real usage data behind it rather than a guess.

One honest caveat: this line moves. Browser capabilities keep expanding and the gap between a well-built mobile site and a simple app narrows every year. We would not bet heavily on where it sits in 2030. But that uncertainty argues for the cheaper, more reversible option today, not the more expensive one.

What to do next

Before you commission anything, do three things this week. Open your own site on a mid-range Android phone on mobile data, not office Wi-Fi, and time how long until you can read something. Look at your analytics for the share of visits on mobile and where those people leave. Then write one sentence describing what an app would do that the site cannot — if you cannot finish the sentence, you have your answer.

If the answer is a faster, more capable site, that is where the money should go. If you genuinely tick one of the conditions above, we would rather help you scope it properly than sell you a wrapper. Either way, tell us what your customers are actually trying to do on their phones and we will tell you honestly which of the two it needs.

Questions we get asked