Do you need an app, or a website?

"We want an app" is one of the most common opening lines in this work, and one of the least examined. The reasoning underneath it is almost always sound. Everything happens on phones. An app sits on the home screen. Apps feel like a serious business.

All true. And for most businesses that say it, the app is still the wrong purchase — not because apps are bad, but because the thing they want is available for a fraction of the cost.

What people actually mean

Ask a few questions and the wish usually resolves into one of these:

"We want to be on their phone." A website is on their phone. That is where most of them visit it from. If it is slow or awkward there, the problem is the site, not the absence of an app.

"We want to send notifications." Fair, and this one genuinely favours an app — but only if people will accept them. Most notification permissions are declined, and most that are granted get muted within a month. WhatsApp and email reach people more reliably for most Indian businesses.

"Our competitor has one." Worth checking whether anyone uses it. App store listings show review counts. A competitor's app with eleven reviews in two years is not a threat.

"It will look more professional." An app nobody downloads looks like nothing at all, because nobody sees it.

What an app costs that a website does not

The build is only the beginning.

Two platforms. iOS and Android, each with its own rules, even when built from a shared codebase.

Store review. Apple and Google approve every release. Rejections happen for reasons that are not always obvious, and each round costs days.

Mandatory maintenance. Both platforms release a major version each year. An app that is not updated eventually stops working, and it stops working silently — you find out from a customer.

Getting installed. This is the one that sinks most of them. A website needs someone to click a link. An app needs them to find a store, search, download, wait, open, and often sign up. Every step loses people, and you pay for the app either way.

A website with one interested visitor beats an app with one download and no second opening.

When an app is genuinely right

The pattern is clear when it is there.

People use it repeatedly, by choice. Daily or weekly, not twice a year. Repeat use is what justifies the install.

It needs something a browser cannot do properly. Background location, offline operation, deep hardware access, reliable push for something time-critical.

The app is the product. If customers pay for the thing the app does, it is not marketing — it is what you sell, and it should be scoped as a product.

You have an audience already. An app is a way to serve people who have chosen you. It is a poor way to find people who have not.

The middle option nobody mentions

A well-built website can be installed to a home screen, work offline for the parts that matter, and look like an app when opened. It costs a fraction of two native builds, needs no store approval, and updates the moment you publish.

It is not right for everything. It is right far more often than it is suggested, because there is less money in suggesting it.

Check it with your own customers first

You can test the app idea this week, for almost nothing. Ask ten of your best customers one question: would you open this again next month, and for what? Do not describe the app. Describe the task, such as reordering or checking an order, and listen for whether they ask for it or politely agree.

Then look at what you already have. If your site analytics show most visitors arriving on phones and leaving from one slow page, that is a site problem. If a WhatsApp link already handles the booking or the reorder, ask what an app would do that the link does not. When the honest answer is "nothing yet", the app can wait, and so can the money.

One limit on the website route is worth knowing. On iPhones, web notifications only work once the site has been added to the home screen, and many people never do that. If reliable push is the real requirement, that points back toward an app, or toward WhatsApp.

If you do build one, build less first

The usual app brief is a long list, and every item on it is a screen on two platforms. The version worth paying for first does one thing the people who already know you will use repeatedly. Booking, reordering, tracking an order, checking a balance. Not the whole business on a phone.

Launch that to the customers you already have, watch whether they come back, and add the rest only where they ask for it. If nobody opens the small version a second time, you have learned that for a fraction of the cost of the large one, and that result is worth more than the app. What an app costs in India, and what pushes the number up, is worth reading before you decide how large the first version should be, and the cost calculator will place either option in a band in a few questions.

How to decide in one question

Will the same person open this more than once a month, on purpose?

Yes, and there is a real reason a browser will not do — build the app, and scope it as a product.

No — build the website properly, make it fast on a phone, and put the difference into something that brings people to it.