You need something a website cannot do
For businesses with bookings, accounts, or a genuine need for an app.
Most businesses that ask for an app do not need one. An app has to be found, installed and kept — which means you need an audience before it makes sense, and if you have that audience you usually already have a business.
But some jobs genuinely need one: offline use, device features, repeat daily use, or a booking system a website cannot handle well. Working out which side you are on is the entire decision.
This sounds like you if…
- You take bookings or appointments and the current process is manual
- Customers would use it several times a week, not once a year
- You need something to work offline or use the phone hardware
- You have been quoted for an app and want a second opinion
What this actually involves
Deciding whether it should be an app at all
An honest look at whether a website, a booking tool, or an existing platform does the same job. This conversation saves people money more often than it makes us any.
The smallest useful version
One job done properly beats five done partially, and it is the only realistic way to find out whether people will use it.
Both platforms without building twice
One codebase covering iPhone and Android, so you are not paying for and maintaining two separate products.
What happens after launch
Apps are not finished at launch. Store requirements change, operating systems update, and an unmaintained app eventually stops working.
Questions people ask
Do I really need a mobile app?
Only if people will use it repeatedly, or it needs something a browser cannot do — offline use, the camera, notifications, hardware. If someone would use it once or twice a year, a website does the same job without asking them to install anything, and costs far less to build and maintain.
How much does an app cost in Australia?
Meaningfully more than a website, because there is more to build and it has to be maintained against changing store and operating system requirements. A focused first version doing one job well is the sensible starting point; a full-featured app built before anyone has used a simple one is where budgets disappear.
Can one app work on both iPhone and Android?
Yes. A single codebase can cover both, which avoids paying for and maintaining two separate products. It is the right default for most business apps; building separately for each platform is only worth it when you need deep platform-specific behaviour.
What about a booking system instead of an app?
For most appointment-based businesses, booking on your website is better than an app: nothing to install, works from a search result or a link, and far cheaper. Reserve an app for when the customer relationship is genuinely ongoing and daily.
Ready to see how we'd do it?
Have a look at the work, the process and what is included before you speak to anyone.
See how we build appsGet this sorted properly
Tell us where you are up to and you will get a straight answer from someone who has done this work before — what it takes, what it costs, and the order to do it in.
What working with us actually looks like
A fixed price, written down
A free call, then a proposal with the scope and the number on it. No hourly drip, and no invoice that surprises you.
A person replies, not a sequence
We read every enquiry ourselves. If we are not the right fit we will say so and point you somewhere better.
One project manager throughout
The same person from the first call to launch, so you never re-explain the business to somebody new.
Built to bring in work
Enquiries, bookings and sales are the measure. A site that looks good and produces nothing has not done its job.
Would rather talk? Call 0491 570 006 or email info@stackwisesolutions.com.
Something else on your mind?
These are the other problems people come to us with.