Do you need a mobile app, or is a good mobile website enough?

"We want an app." It is the most common sentence in a first meeting, and it usually arrives before we know what the client sells.

What we tell them, and what we will tell you here: we build apps, it is part of how we make a living, and even so most people who ask for one do not need it. A properly built website that works on a phone does the job for far less, shows up on Google, and needs nobody to install anything.

This post is so you can decide for yourself.

First, what is the actual difference?

A website opens in the browser. Anyone reaches it from a link, from Google, from an ad, from WhatsApp. No download, no store. When you update it, everyone sees the update immediately.

An app is installed from the App Store or Google Play. It can send push notifications, use the camera and location more deeply, and work offline in some cases. But between you and the customer sits a step called "install the app", and that step loses a lot of people.

In between there is the progressive web app (PWA): a website the customer can pin to their home screen as an icon, that can send notifications on Android, and behaves almost like an app. It is not a fix for everything, but it covers a lot of ground.

When an app genuinely earns its place

1. Use is frequent and daily

The customer opens it every day or every week: delivery orders, transport, a driver app, a field staff app. When use is frequent, the icon on the home screen and the notifications actually matter.

2. You need the device itself

Continuous barcode scanning, background location tracking, high-quality document capture, one-tap Apple Pay, working without a connection. The browser can do some of this, but not as smoothly.

3. Notifications are the service

"Your order is on its way", "your appointment is in an hour", "the driver has arrived". If the notification is the service rather than an extra, the app earns its place. (WhatsApp can cover many of these cases without an app, which deserves its own post.)

4. You have field staff or drivers

A driver or technician app is a different thing from a customer app. An employee uses it all day and needs location, camera and notifications. Here the app is the foundation, not a luxury.

When it does not

The business and services website

A clinic, an office, a restaurant, a services company. The customer wants to know what you do, where, how much, and how to reach you. That is a website. An app here gets installed by one person and deleted a week later.

The store that is just starting

Before you have customers who buy repeatedly, an app costs you twice: building it, then convincing people to install it. A fast mobile store lets the customer arrive straight from the ad and buy in the same session.

When the reason is "the competitor has an app"

The competitor may be wrong. Ask: how many of their customers actually use it? You usually cannot get an answer, and that is the answer.

When you want to show up on Google

Google does not index inside apps. Content that lives inside an app brings you no new customer from search. A website does.

The difference in cost and time

An app is not a copy of the website. It is two builds (iOS and Android) if done separately, or one build on a shared technology like Flutter (which is how we work), but either way it also needs:

• A backend that serves the app, which is the same one that serves the website.
• An admin dashboard to run it from.
• Store accounts (Apple and Google) and a review that takes days with every update.
• Ongoing maintenance, because mobile operating systems change every year.

A website needs only the first two. That is why the cost difference is not small, and the difference in time to launch is bigger. We wrote about what drives the price of a website separately; the same logic applies to an app with more line items.

The path we recommend to most clients

1. Start with a fast mobile website that does what the customer actually wants: see, order, book, pay. And make sure it shows up on Google.
2. Put WhatsApp in the middle: confirmations, reminders and follow-ups reach the customer on WhatsApp without installing anything. This covers most of "we need notifications".
3. Watch usage for two or three months: how many customers come back, how often, and what they do.
4. When you see genuinely repeated use, build the app on the same backend. You do not start from zero; the site and the system exist, you add the mobile interface.

In that order, if it turns out you need an app, you build it knowing what people use. And if you do not, you have saved a large sum.

Questions we hear a lot

"But an app looks more premium." What looks premium is a service that works from the first tap. An app with a long install-and-register path makes a worse impression than a site that opens in a second.

"We want both." Possible, but not at the same time. Start with what brings customers (the website), then what serves repeat customers (the app).

"We have an old app nobody uses." Usually because it never needed to be an app. See what people actually do in it, and put that on the website.

The short version

An app is a tool for a customer who comes back to you every day, or an employee who works in it all day. A website is a tool for a customer who is searching for you and wants to reach you quickly. Most small businesses need the second first, and some never need the first at all.

If you are not sure where you fall, book a free consultation. If you do not need an app, we will say so, and it will be the cheapest advice you get this year.