.svg){kind=small}
The two terms get used interchangeably, but they lead to very different projects. Getting it right early stops you paying for an app when you needed a website — or stretching a website into something it was never built to do.
A website is mostly read
Visitors come to learn about you, read articles, compare services and get in touch. The content changes, but the structure stays the same. Most business sites, portfolios and blogs sit here, and a CMS lets your team update them without calling a developer.
A web app is mostly used
People log in, enter information, and expect it to be there next time. Booking systems, client portals, dashboards, internal tools. Each user sees something different, and the hard part is the logic behind the screens rather than the screens themselves.
Questions that settle it
- Do people need an account?
- Does each person see different information?
- Does it need to store what people enter and do something with it?
- Would an hour of downtime actually stop your business?
Two or more yeses and you're probably describing an app.
Why it matters for the budget
A website's cost is mostly design and content. An app's cost is mostly in the parts nobody sees: data, permissions, testing, and keeping it running. That's why an app that looks simple can take several times longer than a site that looks elaborate.
The common middle ground
Plenty of projects are a website with one app-like feature — a quote calculator, a members' area, a booking form. That's fine. It usually makes sense to build the site first and treat the feature as its own clearly scoped piece.
