Deciding

Do You Need an App, or Is a Website Enough?

For most companies, a website is enough, and it is the thing to build first. An app is worth its ongoing cost only when there is a repeat action that a website does badly.

The short answer

If there is no clear thing an app would do better than your site on a phone, you do not need one yet. If customers or staff do the same task with you every week and it needs a camera, offline use, a login they keep, or a notification, an app will pay for itself. Build the website first either way: an app for a company nobody can find is an app nobody installs.

The signs, side by side

A website is enough when

  • People find you by searching, visit, and call or book.
  • Most visitors are new or occasional, not weekly.
  • What they need is information, proof and a way to reach you.
  • You do not yet have a base of repeat customers who would install anything.
  • There is no budget for keeping software alive next year.

An app earns its keep when

  • The same people do the same task with you every day or week: booking, ordering, checking in, reporting.
  • The task needs the phone: camera, GPS, offline use, push notifications.
  • Your staff run the business off a group text and a spreadsheet, and both are breaking.
  • An off-the-shelf tool exists but makes you work its way at a cost you can measure.
  • You can name the person who will answer "what does it cost per month to run".

The middle option people forget

A web app that installs to the home screen and works like an app without an app store. For forms, lists, lookups, bookings and dashboards it does the job at a fraction of the cost of building for iPhone and Android separately, and it changes as fast as a website. It is the right first step for most internal tools and for most customer-facing apps that do not need the phone's hardware.

The mistake that costs the most

Building the app before the audience exists. The company has a good idea, spends the budget on the app, launches it, and finds that people who use a business twice a year do not install its app. Meanwhile the website that would have brought those people in was never built. Earn the repeat customer first; then build them the app, if they still ask for it.

What to do next

If the website side is the gap, read business websites. If you can name the repeat task and the people who do it, read business apps and then what drives the cost. If you are still unsure, describe the task in an email and you will get an honest answer, including "not yet".

Questions people ask

Can I have both?

Yes, and the order matters: website first, because it is how people find you, then an app for the repeat task once you know what it is. Building both at once doubles the scope before either has proven itself.

My competitor has an app. Do I need one to keep up?

Not because they have one. Ask what their customers do in it every week. If you cannot name that action, their app is probably a cost to them, not an advantage. If you can, and your customers do the same thing, that is a real reason.

Is a web app a real app?

To the person using it, yes: it opens from the home screen, fills the screen, and can work with a poor connection. What it cannot do is use every phone feature or sit in the app store. For most business tasks neither matters.

Tell us what the business needs it to do

A short message is enough to start: what the company does, what the website or app has to do for it, and when you need it. You will get a reply from a person.