← All guides

Choosing what to build

Do you need a website, a web app or a mobile app?

By Ryno van Eeden · CodeStudioWorks

The short answer

Start with a website when customers mainly need information and a way to contact, book or buy. Consider a web app for repeat tasks, accounts and custom workflows. Consider a mobile app when the way people use their phones is central to the product.

Describe the task before choosing the technology

“Customers need to book a visit” is a clearer starting point than “we need an app.” Describe who will use it, how often, what they need to accomplish and what happens afterward. The answer may be an existing tool connected to a website, rather than a new custom product.

When a website is enough

A service business may need clear pages, proof of work, an enquiry form and a booking link. A website can support those journeys without asking visitors to install anything. Content, mobile usability and a straightforward next step matter more than adding features customers will not use.

When a web app makes sense

A customer portal, staff dashboard or tailored booking workflow may need accounts, permissions, saved information and business rules. A web app gives those tasks a browser-based interface. Scope the administration side too: someone needs to manage users, correct mistakes and support the process.

When to explore a mobile app

A mobile app may suit a product people use repeatedly on their phones, especially when device features or offline behaviour are important. First define those requirements. A mobile release also needs testing, distribution and ongoing updates, so compare the full ownership effort with a browser-based option.

Build one complete journey first

For a booking product, a useful first release might let a customer choose a slot, receive confirmation and let staff manage the booking. Add loyalty schemes or complex reporting later if evidence supports them. Keep the first scope small enough to test with real users.

Your planning checklist

  • Name the main user and their task.
  • Estimate how often they will return.
  • Identify device or offline requirements.
  • Check whether an existing tool solves the problem.

Put the plan into practice

Tell me about your business and the next step you have in mind. We can work out an appropriate scope together.

Explore the relevant service ↗