Do you need a website, a web app, or a mobile app?
Most people start with a simple question: app or website? It’s the wrong question, and answering it wrong is expensive.
There are actually three things you might be choosing between, not two. And for most businesses, the right answer is not the one that sounds most impressive at the pitch.
Here is how to tell them apart, and how to pick.
The three things people are actually choosing between
A website is what most people picture. Pages you visit in a browser, found through search, used to inform, market and sell. Low barrier, easy to reach, easy to update.
A web app is software that runs in the browser but does real work. Logins, dashboards, forms, data, workflows. Think of the systems your team uses to run the business, delivered through a browser instead of an installed program. A web app can be built as a progressive web app, or PWA, which installs to a device and works offline without ever going near an app store.
A mobile app is a native program installed from the App Store or Google Play. It gets the deepest access to the phone’s hardware and the best performance, at the highest cost.
The word “app” gets used for the last two interchangeably, which is where a lot of wasted budget comes from.
Start with the users, not the technology
Before anyone talks build, answer these:
- Who uses it, and where? The public, or your own team? On a phone in the field, or a desktop in the office?
- How often? Once in a while, or every working day?
- Does it need the device itself? Camera, GPS, offline access, push notifications, biometrics?
- How do people find it? Search and a link, or a deliberate download?
- What is the budget and timeline, and how often will it change?
Your answers point clearly at one of the three. They almost never point at “build everything”.
When a website is enough
If the job is to be found, explain what you do, and let people get in touch or buy, a website does it. It is the cheapest to build, the easiest to update, and the only option search engines can send people straight to. If you are reaching for an app to do a website’s job, stop.
When you need a web app
This is the sweet spot for most business systems, and it is the option people forget exists. A web app runs your process in the browser. No download, no app store approval, and when you fix something every user has the fix instantly. Build it as a PWA and it will also install to a phone and work offline, covering most of what people think they need a native app for, at a fraction of the cost and hassle.
We built exactly this for ARH: a PWA for their engineers’ timesheets that works offline in the field and updates without waiting on an app store review. That flexibility is the point.
When a native mobile app is worth it
Native apps earn their cost when the job genuinely needs the device. Heavy or constant hardware use, demanding performance, reliable push notifications, or a consumer product where being in the app stores is part of how people find and trust you. A social product like a betting or fitness app belongs here. An internal booking system usually does not.
The honest answer for most businesses
Nobody needs a native app for prestige. Plenty of companies spend six figures on one because it felt like the ambitious choice, then watch it sit unused because the actual job was a web app or a better website.
Start with the job. Pick the lightest option that does it well. You can always add to it later, and building the right thing first makes that far easier.
Not sure which one you need?
That is the conversation we have with clients all the time, and we will give you a straight answer even when it is the cheaper one. We have built websites, web apps and native apps for 20 years, so we are not trying to sell you a particular hammer.
Tell us what you are trying to do and we will tell you what it actually needs.