Do I need an app or a website?

Almost every business needs a website first. An app makes sense when customers will use it often, need phone features such as notifications or the camera, or expect to find you in an app store.

Can one app work on both iPhone and Android?

Yes. Cross-platform tools such as React Native and Flutter build both from one codebase, which usually costs less to build and maintain.

Software that runs in the browser, like a dashboard, booking system or client portal. Nothing to install, and it works on any device.

Insights Apps

Website, web app or mobile app: which does your business need?

A plain guide to choosing between a website, a web app and an iOS or Android app: what each is for, what each costs to run, and when one codebase for both platforms makes sense.

Updated 20 October 2026 · 2 min read · By Burax

“Should we build an app?” is one of the most common questions we hear. Sometimes the answer is yes. Often the better answer is a great website, or a web app, at a fraction of the cost.

Here is how to tell which one your business needs.

A website: to be found and trusted

A website is how people discover you, decide whether to trust you, and get in touch or buy. It is:

Found on Google and shared by link.
Open to everyone, instantly, with nothing to install.
The right first step for almost every business.

If your goal is more enquiries, bookings or sales from new customers, start here. See our websites and apps service.

A web app: to get work done

A web app is software that runs in the browser: a booking system, a client portal, a dashboard, an internal tool. It suits:

Repeat use by your team or clients, such as logging in to see orders or progress.
Work that is too complex for a website but does not need phone hardware.
Any device, from office desktops to phones, with one build.

Many businesses that think they need an app actually need this. See custom software.

A mobile app: to live on the phone

A native or cross-platform app, from the App Store or Google Play, earns its place when:

Customers use it often, daily or weekly.
You need phone features: push notifications, camera, location, offline use, payments with a tap.
Being in the app stores matters to how people find or trust you.

Examples from our own work: GroFlow, a habit and to-do app people open every day, and KindMap, which uses location to connect people who need help with people nearby.

One codebase or two?

You do not always need separate iPhone and Android apps. Cross-platform tools build both from one codebase, which usually means:

Lower build and maintenance cost.
Both platforms launch together.
Native feel for nearly every kind of app.

Fully native apps still make sense for heavy graphics, advanced hardware features or very large teams.

Running costs people forget

Whatever you choose, budget for life after launch:

	Website	Web app	Mobile app
Hosting	Low	Low to medium	Back end hosting
Store fees	None	None	Apple and Google developer accounts
Updates	Content edits	Features and fixes	OS updates every year, store reviews
Reaching users	Search, links	Login link	Store listing, installs

A sensible order

For most businesses the path looks like this:

A fast website that brings in customers.
A web app or automations that save your team time.
A mobile app once you have customers who want to use you every week.

Each step builds on the last, and nothing is thrown away.

Not sure which you need?

Tell us what you want customers or your team to be able to do, and we will recommend the simplest thing that does it. Start a project.