"We need an app" is one of the most common things we hear — and sometimes it's exactly right. Other times, what the business really needs is a faster website, a better booking flow or a simple system behind the scenes. Here's how to tell the difference.
Start with the job, not the app
Before thinking about app stores, ask: what do you want customers (or staff) to do more easily?
- Order food for collection or delivery
- Book a session, table or appointment
- Use a loyalty card or membership
- Check stock, take orders or manage jobs on the move
Once the job is clear, the right type of build usually becomes obvious.
The three main options
1. A web app
A web app runs in the browser — no download needed. It can look and feel like an app, work brilliantly on phones and even be "installed" to the home screen. For most small businesses this is the sweet spot:
- One build that works on iPhone, Android and desktop
- No app store approval or fees
- Updates go live instantly
- Customers can use it straight from a link, QR code or Google search
Online ordering, booking systems and customer portals are often best built this way.
2. A native app
Native apps are downloaded from the App Store or Google Play. They make sense when you need:
- Push notifications that reach people reliably
- Heavy use of the phone's camera, location or offline features
- A loyal, repeat audience who'll happily keep your app on their phone
The catch: you're maintaining apps for two platforms, dealing with app store reviews, and — most importantly — persuading people to download it in the first place.
3. A better website (plus the right system behind it)
Sometimes the honest answer is that an app would be a costly detour. If customers mainly want to find you, see what you offer and get in touch or book, a fast, well-designed website with a proper booking or ordering system will do more for you — and cost less.
Questions to ask before you commit
- Will people come back often enough? Apps shine for weekly or daily use. For once-a-year purchases, few customers will download anything.
- Who will keep it running? Phones and operating systems update constantly. Budget for ongoing maintenance, not just the build.
- Does it connect to what you already use? An ordering app that doesn't talk to your till, kitchen or stock creates more work, not less.
- How will people find it? An app needs promoting. A web app or website can be found on Google from day one.
Apps for your team, not just customers
Some of the best returns come from internal tools: a simple app that lets staff take orders, update jobs or check bookings from a phone. These don't need app store polish — they need to be quick, reliable and built around how your team really works. They often sit alongside a custom CRM.
How we build
We start with a short discovery session to pin down the job the app needs to do, who'll use it and what it needs to connect to. Then we recommend the simplest build that does that job well — and we'll tell you if you don't need an app at all.
Got an app idea? Tell us about it and we'll give you an honest view on the best way to build it.