Most small businesses do not need an app. Here are the three signs you do.

We build mobile apps. We are also going to spend most of this article talking you out of one.

"We need an app" is one of the most common things a business owner says, and most of the time it is the wrong instinct. Not because apps are bad, but because the thing the owner actually wants is almost always solved by a fast, well made mobile website. People say "app" when they mean "I want to look modern," or "I want to be on people's phones," or "my competitor has one." None of those are reasons to build an app. They are reasons to look closely at what you are really trying to do.

Here is the part nobody tells you up front. A good mobile website does almost everything people imagine an app doing. It loads from a tap, it works on every phone without anyone installing anything, customers find it through a normal search, and you fix a typo in minutes instead of waiting on an app store. For a restaurant showing a menu, a shop showing products, a service business taking bookings, the mobile web is not the budget option. It is the correct option.

So before you spend real money, the honest question is not "should we have an app." It is "is there something an app does that a website genuinely cannot." Most of the time the answer is no. Here are the three signs that tell when it is yes.

Sign one: people would actually open it every week

An app earns its place on a home screen through repeat use. The math only works when a customer would open the thing often enough to want the icon sitting there. Think about how you use the apps you keep. You open them out of habit, several times a week, because they do something for you again and again.

That is the bar. Genuine, high frequency, repeat use.

• A fitness studio where members book classes, check their schedule, and track attendance multiple times a week. They are coming back constantly, so the icon earns its spot.
• A coffee shop with a real loyalty program, where regulars open the app every morning to pay and collect points. Daily habit, daily value.
• A salon or barber that customers visit once every six weeks does not clear this bar. They will book through a website and never think about you in between. An app would sit unopened.

Be honest about your own rhythm with customers. If someone interacts with your business once a season, an app is a worse experience than a website, because you are asking them to install and remember something they will rarely touch. The website is always there and never in the way.

Sign two: there is a real in person or offline moment the web handles badly

The second sign is physical. An app is justified when something happens in the real world, at your location or out in the field, that a website struggles with. The web is excellent at information. It is weaker the moment a customer needs something fast, in their hand, possibly without a signal.

Watch for moments like these.

• A membership pass or ticket. A museum or gym member who scans a card at the door wants it ready in one tap, working even when the lobby has no reception. A website you log into every time is friction at exactly the wrong moment.
• Fast check in. A studio, clinic, or event where people arrive and need checking in quickly. An app can hold their identity and let them tap in without typing.
• An on site experience. A self guided tour, an audio guide, a map that works in a basement gallery. These lean on the phone itself: location, the camera, offline storage.
• Works without signal. Anything a customer needs in a parking garage, a rural site, or a venue with bad coverage. A native app can hold its data on the device. A website usually cannot.

If your business has one of these moments and it is central to the experience, that is a strong case. If it does not, you do not have one, and no amount of wanting it will create one.

Sign three: notifications people actually want

The third sign is the most abused. "We can send push notifications" is the line that sells half the apps that should never have been built. Notifications are only valuable when the customer genuinely wants them and they carry real information. The moment they become marketing blasts, people turn them off or delete the app, and you are worse off than before.

Good notifications are ones a customer would thank you for.

• A restaurant telling a waitlisted diner their table is ready.
• A repair shop telling a customer their car is done.
• A studio reminding a member that the class they booked starts in an hour, with a tap to cancel if they cannot make it.
• A pharmacy telling someone a prescription is ready for pickup.

Notice what these have in common. They are timely, specific to that one person, and tied to something the customer is already waiting on. Compare that to "20 percent off this weekend," which is the kind of thing that gets an app deleted. If the notifications you imagine sending are promotions, you do not need an app for that. You need an email list or a text. If they are personal and time sensitive, that is a real reason.

The cost nobody mentions

Here is what does not show up in the pitch for an app. The build is the cheap part. The expensive part is everything after.

An app lives in two app stores, and each has its own rules, its own review process, and its own way of breaking. Apple and Google ship new operating systems every year, and an app that worked fine can stop working until someone updates it. That someone is you, or someone you pay, forever. A website you can leave alone for a year and it still runs. An app left alone for a year may not open at all.

Then there is the quiet failure mode we see most: the empty app. A business spends real money, launches, gets a small wave of installs from existing customers, and then the icon sits dark. Nobody had a reason to come back. The app was the goal instead of the result of a need. It is now a line item that costs money to keep alive and earns nothing.

None of this is an argument against apps. It is an argument for being sure.

The path that usually makes sense

For most businesses, the right move is mobile web first. Build a fast website that does the core job well, get it in front of real customers, and watch what they actually do. You can add a home screen install, offline support for key pages, and even web notifications without ever entering an app store. That covers a surprising amount of what people think requires a native app, at a fraction of the cost and the upkeep.

You graduate to a native app when you have evidence, not a hunch. When the website is busy and you can see customers coming back week after week. When you hit a real wall: you need the camera, reliable offline use, fast in person scanning, or notifications people are asking for. At that point an app is not a guess. It is the obvious next step, and you build it knowing exactly why.

How we would handle this with you

This is the conversation we like to have. If you come to us wanting an app, the first thing we will do is ask what you are actually trying to fix, and if a website does it better and cheaper, we will tell you so. We would rather lose the bigger project and keep your trust than sell you something that ends up dark on a home screen.

And we will not ask you to take that on faith. We build a working prototype before you pay anything, so you can hold the real thing, whether that turns out to be a website or an app, and decide for yourself. The point is never to sell you the most expensive option. It is to build you the right one.