Website or web app: what's the difference and what you actually need

A website presents content: you open it, read a page, look at some photos, at most fill in a form. A web app is a tool you actually use: you have an account, your data stays saved from one visit to the next, and something happens every time you open it. That line between the two moves the price too, quite a lot.

I get this question more often than you would think, usually from someone who has already written to two or three developers and heard back quotes ranging from 1,000 to 15,000 euro for "the same project". The problem, almost always, is that they are asking for a website when what they need is an app, or the other way around. Here I try to put some order into it, with examples you will recognise straight away.

What actually changes between a website and a web app

The difference is not in the technology I build them with: both a website and a web app can run on Vue or Nuxt, the tools I use every day. People often just say "app", or web application in full: they mean the same thing, and I use the two terms as synonyms through the rest of this piece. The difference is in what happens when you use them.

A website presents information. Whoever opens it reads, looks, at most writes into a contact form that goes out by email. There is nothing to save for them, no password to log in with, and if they come back tomorrow they find exactly the same page.

A web app does something with you inside it. You book a table and that booking sits in a database. You log in with an email and a password and find your history there. You upload a file, the tool processes it, and the result is saved for when you return. State, meaning the memory of what you have done, is the real dividing line. If the site has to remember you between one visit and the next, it stopped being a website. It is an application.

Concrete examples of a website and a web app

On the website side you find the brochure site of a tradesperson, a law firm's blog, a restaurant page with the menu and opening hours, the landing page for an ad campaign. Five or six pages, maybe a contact form: no login, no personal data saved beyond whatever you send me by email.

On the web app side you find a booking system for a beauty salon, a dashboard showing a shop's sales in real time, a portal where clients download their invoices, a configurator that calculates a quote based on what the user selects, an internal tool that replaces the spreadsheet colleagues keep passing around by email.

There is also a grey zone, and it is the most common one. An e-commerce site is a website that sells, but the moment you add customer accounts, a persistent cart, and a members area with order history, you already have a small web app dressed up as an online shop. The same goes for a blog with comments, or a site with a members-only area for an association.

How to tell if you need a website or an app

Try answering three questions before you write to anyone.

Does the visitor need to log in? If so, you are already talking about an app, even a small one. Does the site need to remember something between one visit and the next, a cart, a booking, a progress bar? Same answer. Do you need a panel where someone on your team edits data that others then see, in real time? That is web app territory too.

If you answered no to all three, you need a website, probably a simpler one than you think. If you answered yes to even one, you are describing a tool, not a shop window, and it needs to be designed as one from the first line of code.

Website and web app compared

What the difference actually costs

The price jump between the two worlds is real, and it has a precise reason. A website, even a good one, stays a job of content and structure: copy, images, a clear hierarchy, basic SEO. A web app adds a piece the website does not have, the logic running behind it, the database holding the data, the security around who can log in, the testing of what happens when something goes wrong.

That is why a professional website moves between 800 and 6,000 euro, while a web app typically starts at 6,000 euro, and a first MVP, the minimum version that already works and that you can show to real users, usually costs between 8,000 and 20,000 euro. Above that threshold come more complex features: payments, integrations with other systems, managing several user roles. And the price grows with them.

The advice I give almost every time someone arrives convinced they need a full platform is to start smaller. A website with a well-built form and a light internal tool is often enough to cover the first year of activity. The real web app gets built once the numbers justify it, not before.

If you are still not sure which side your project falls on, I cover it elsewhere too: which type of site to choose if you only need to present your business is in showcase site, e-commerce or landing page, while if your project looks more like custom software I have written about what that costs in how much does custom software cost. And if you want a figure tuned to your case, the services page has a configurator that answers in a couple of minutes.