Foldwren

What is a web app, and how is it different from a website?

Plain definitions of websites and web apps, everyday examples like booking tools and portals, and how to tell when your site has become software.

A website mostly tells you things. A web app lets you do things. That is the simplest line to draw, and it holds up better than most technical definitions.

The two blur into each other, which is why the terms get thrown around loosely in quotes and sales calls. Knowing the difference helps you understand what you are being asked to pay for.

The plain definitions

A website is a set of pages that present information: who you are, what you offer, where you are, how to get in touch. Every visitor sees more or less the same thing. A cafe's site with a menu, opening hours and a map is a website.

A web app is software that runs in a browser. It responds to what each person does, usually remembers them, and stores or changes information. Internet banking is a web app. So is an online calendar, a rostering tool, or the screen where you track a parcel.

Neither needs to be downloaded from an app store. Both open at a web address. The difference is in what happens once you are there.

Examples you probably use already

Most small business owners use several web apps a day without calling them that.

  • Booking tools. A customer picks a service, sees live availability, chooses a time and gets a confirmation. The page is different for every person and every minute.
  • Accounting software in the browser. You log in, see your own invoices, and change data that is saved for next time.
  • Client portals. A customer of an accounting firm logs in to upload documents and see where their return is up to.
  • Quote calculators. A builder's site that asks for room dimensions and finishes, then produces an estimate.
  • Online stores. A shop with a cart, accounts and order history is a web app sitting on top of a website.

Notice that several of these live inside an ordinary website. That is normal. Your marketing pages and your app-like features can share the same address and the same look.

When does a site become an app?

There is no official threshold, but these are the signs we look for:

  1. People log in. Once visitors have accounts, you are storing data about them and showing each person something different.
  2. The page changes based on input. Filters, calculators, live availability and multi step forms that react as you go.
  3. Information is saved and comes back later. Order history, saved preferences, a half finished application.
  4. Different people have different permissions. Staff see one thing, customers another, managers a third.
  5. It talks to other systems. Payments, calendars, stock levels, your accounting package.

One of these on its own is a feature. Several together mean you are building software, and the project should be planned like software.

Why does the distinction matter to you?

It affects three things: cost, risk and upkeep.

A brochure website has a fairly predictable scope. Pages, words, photos, a contact form. A web app has logic, and logic has edge cases. What happens if two people book the same slot at the same second? What if a payment succeeds but the confirmation email fails? What does a customer see if their account is suspended? Someone has to design an answer for each of those.

Web apps also hold data, often personal data. That brings responsibilities around security and privacy. The rules depend on your business and what you collect, so check the official guidance from the privacy regulator or ask an adviser before you start storing customer records.

And apps need ongoing care. Software that handles bookings or payments cannot be left untouched for years the way a simple brochure site sometimes is.

Should you build it or rent it?

Here is our opinion. If an existing product already does the job, rent it. Booking, invoicing, email marketing, online stores and membership billing are all well served by established tools. Products such as Calendly, Shopify and Stripe exist because these problems are common, and they are maintained by teams far larger than any small business could fund.

A custom web app makes sense when your process is unusual enough that off the shelf tools force awkward workarounds, and when that process is central to how you make money. Say you run a regional winery with a wine club that has its own rules about allocations, pick up events and swaps. If no existing tool handles it without three spreadsheets on the side, a small custom app might pay for itself in saved hours.

Questions to ask before you commission one

  • What exactly will a user be able to do that they cannot do now?
  • Who are the different types of users, and what should each one see?
  • Where will the data live, and who is responsible for backing it up?
  • Is there an existing tool that covers most of this, and what would we lose by using it?
  • Who fixes it when something breaks at nine on a Saturday night?
  • What is the smallest version that would still be useful?

Spend the most time on that last question. A web app that does one job properly beats a larger one that does six jobs halfway, and it gives you something real to learn from before you spend more.

Your order