Do you need a mobile app, or just a good website?

"We want an app" is one of the most common things we hear. It's also the request we talk people out of most often.

Not because apps are bad. Because an app is a much bigger commitment than it looks from the outside, and for maybe three quarters of the businesses that ask, a website that works properly on a phone does the same job for a fraction of the cost.

What an app really costs

The build is the cheap part. What follows it:

• Two platforms. iOS and Android behave differently, and testing doubles.
• Store review. Apple and Google both have to approve every release. A typo fix can take days to reach your users, and reviewers reject builds for reasons that have nothing to do with your code.
• A developer account, forever. Apple charges annually. Let it lapse and your app disappears from the store.
• Forced maintenance. New OS versions ship every year and quietly break things. An app nobody has touched in eighteen months usually will not build, let alone run.
• Getting installed at all. This is the one people underestimate most. You have to convince someone to give up storage space for you. A website needs a tap on a link.

None of that is a reason to never build an app. It's a reason to be sure.

When you genuinely need one

There is a real dividing line, and it's about what the phone can do rather than what it shows:

• It has to work without signal. A delivery rider in a basement, a field inspector out of coverage, a market stall on a bad day.
• You need the hardware properly. Continuous camera use, barcode scanning, GPS in the background, Bluetooth to a printer or a scale.
• Push notifications matter. Not marketing blasts — things like "your order is ready" that have to arrive when the app is closed.
• Your staff live in it all day. At that level of use, native speed and a home-screen icon stop being luxuries.

If one of those is true, build the app. That's what it's for.

When you don't

If what you actually need is to show information, take bookings, sell products, or let customers check something occasionally, a website will serve you better. It's cheaper, it ships the same day you approve a change, it appears in Google, and nobody has to install anything.

A good one already handles the phone properly: it fits small screens, works on mobile data, and can be installed to the home screen as a progressive web app — icon and all — without either store's involvement.

The middle ground we usually recommend

Start as a mobile-first website. If real usage later proves you need the camera or offline mode, build the app then, on top of a product you've already proven people want.

That's not theory — it's what we did ourselves. SnapSibo is built in Flutter, which means the same codebase produces the web app and the mobile apps. Teams can start using it in a browser today, and the native builds follow without rewriting the product. It's a receipt scanner, so it genuinely needs the camera; even then, starting on the web let us find out what the app should be before committing to app-store cycles.

How to decide in one question

Ask what breaks if the app doesn't exist.

If the answer is "customers would have to open a browser instead" — you don't need an app. If it's "our riders can't record deliveries in the basement" — you do.

Not sure which one you are? Tell us what the business does and where things get slow. Sometimes the honest answer is that you need neither yet, and we'll say that too.