The question behind the question
A fair share of the enquiries we get start with "we want an app". When we ask what the app should do, the answer is often a list of things a website already does: show the menu, take a booking, display opening hours, let people buy something. What the business actually wants is for customers on their phones to have a better time, and for more of them to buy or book.
That is a reasonable goal. It just doesn't always need an app. Sometimes it does, and when it does, a website can't fake it. The point of this piece is to help you tell the two apart before you spend money on the wrong one.
We build both, so we don't have a horse in the race. We'd rather you build the thing that pays for itself.
What an app genuinely does better
There are a handful of things native apps do that websites either can't do or do noticeably worse. If your idea leans on one or more of these, an app is worth a serious look.
Push notifications are the obvious one. An app can tap someone on the shoulder: your order is ready, your appointment is tomorrow, your loyalty reward has unlocked. Websites can send notifications too, but support across phones is patchier, people are less willing to allow them, and they don't carry the same weight as a notification from an app sitting on the home screen.
Working offline is another. A tradesperson filling in a job sheet in a basement, a site manager doing an inspection in a half-built tower, a driver checking deliveries out in the country. An app can store everything locally and sync when the signal comes back. A website can be built to do some of this, but an app does it more reliably. We wrote about this in more depth in offline-first PWAs.
Device hardware is the third. Scanning barcodes quickly, using Bluetooth to talk to equipment, tracking location in the background, tapping a card against the phone, using the camera heavily. Browsers have opened up a lot of this over the years, but apps still get fuller, more dependable access.
Then there's frequency. If people use your product every day or several times a week, an icon on their home screen and a login that stays put make a real difference. A gym member booking classes, a staff member clocking on, a customer reordering the same supplies every fortnight. The app becomes a habit.
Finally, logged-in relationships. When every user has an account and the whole experience is about their own data, their orders, their bookings, their history, an app tends to feel more natural than a website people have to log back into.
What a good mobile website already covers
For a lot of businesses, the customer journey looks like this: someone searches, finds you, checks you out, and then calls, books, enquires or buys. They might do that once, or a few times a year. That journey happens almost entirely on the open web, and an app plays no part in it. Nobody downloads an app to decide whether to hire a plumber.
A fast, well-built mobile site handles that journey well. It loads quickly on a patchy connection, puts the phone number and the booking button where a thumb can reach them, keeps forms short, and lets people pay with the wallet already on their phone. It is found by search engines and by AI assistants, which an app isn't. It can be shared in a text message with a single link. And there's nothing to install.
Progressive web apps, or PWAs, sit in between. They are websites that can be added to the home screen, work partly offline and feel more like an app once they're there. For some businesses that middle ground is exactly right: an app-like experience for regulars, without the app stores. For others it's a halfway house that satisfies nobody. It depends on how much of the list above you really need.
If your current mobile site is slow, cramped or awkward, fixing that is almost always the first job, whether or not an app comes later. Most of your new customers will meet you there first. That is the work we do under responsive web design, and it often moves the needle more than people expect.
The friction nobody mentions in the pitch
Apps come with costs that don't show up in the first quote.
The first is the download. Every person who uses your app has to find it in a store, install it, and usually create an account. Each of those steps loses people. For a business that relies on new customers rather than regulars, that is a big ask.
The second is the app stores themselves. Apple and Google both review apps before they're published and again with each update. Reviews usually go smoothly, but sometimes an update is held up or rejected for reasons that take a few rounds to work through. The stores also have rules about how you can take payments for some kinds of digital goods, which matters if that is part of your model.
The third is maintenance. Phones get new operating system versions every year, and each one can change how things behave. Apps need to be updated, tested and resubmitted to keep working well, and to stay listed. A website needs maintenance too, but you control when changes go live and everyone gets them at once. With an app, some of your users will be on an old version for months.
The fourth is that you usually end up with both. Even businesses with a great app still need a website for search, for first impressions, and for people who won't install anything. So the real decision is often website alone, or website plus app.
None of this is a reason not to build an app. It's a reason to make sure the app is doing something the website can't. We cover the budget side in detail in what a mobile app costs in Australia.
Honest signals for each
When we're working through this with a client, these are the questions that usually settle it.
- How often will people use it? Daily or weekly use points towards an app. A few times a year points towards a good website.
- Are your users mostly existing customers, or new ones? Apps serve people who already know you. Websites are how strangers find you.
- Does it need to work without signal? If the answer is yes and it's important, that favours an app or a carefully built offline-capable PWA.
- Does it need the camera, Bluetooth, background location or other hardware? If it's central to the product, that leans app.
- Would you send notifications people actually want? Order updates and reminders, yes. Promotions every few days, probably not, and people will turn them off.
- Is the app itself the product? If you're building a service people subscribe to and use on their phones, the app isn't a marketing channel, it's the business.
- Who will look after it in two years? If there's no budget for ongoing updates, a website is the safer bet.
If most of your answers point one way, that's usually the right call. If they're split, it often makes sense to start with an excellent mobile website or PWA, see how people use it, and build an app once you know which features matter.
Where we usually land
Most of the small businesses we talk to need a better mobile website first. Faster pages, clearer calls to action, booking and payments that work on a phone without a fight. That improves things for every visitor, including the ones who would never install an app.
Some genuinely need an app: field teams who work offline, membership businesses with daily users, services where the phone is the product. For those, we build mobile apps alongside the website and connect them to the same back end, so customers see the same bookings, orders and account details wherever they are.
And some are somewhere in between, where a PWA gives regulars a home-screen experience without the cost of two app store listings.
If you're weighing this up, tell us what you want customers to be able to do on their phones and how often they'd do it. We'll give you a straight answer on whether that's an app, a website, or both, and what each would involve. Get in touch and we'll talk it through.
