Two terms used interchangeably — that mean very different things
"We need a website" is one of the most common things a developer hears. But often, when you start asking questions, it turns out the client actually needs something quite different: a web application.
This isn't a minor distinction. The difference affects technology choices, development time, cost, and — most importantly — what the end user can actually do.
The simple explanation
A website presents information. It's static or near-static: you read, view images, and perhaps make contact. The content is the same for everyone who visits.
A web app lets users do something. It responds to input, handles data, and gives different answers to different users based on who they are and what they do.
| | Website | Web App | |---|---|---| | Primary purpose | Inform | Perform actions | | Login | Rarely | Usually yes | | User data | No | Yes | | Real-time updates | Rarely | Often | | Examples | Business site, blog | Online banking, booking system, dashboard |
Examples you'll recognise
The distinction is easiest to understand with concrete examples:
Websites:
- Business presentation with a contact form
- Blog or news sites
- Product catalogue without buying functionality
- Portfolio site
Web apps:
- Online banking (you log in, see your balance, transfer money)
- Booking system (you choose a time, pay, receive confirmation)
- Project management tools like Jira or Trello
- Online store with user accounts, shopping cart, and order history
- Internal employee portal
Notice: an online store is a web app. A simple product page without a purchasing function is a website. The distinction isn't about size — it's about interactivity and data.
When is a website enough?
A website is the right solution when you need to:
- Present your business and services
- Publish content like blog posts or articles
- Collect leads via a simple contact form
- Rank in Google for relevant searches
For most Norwegian SMBs, a well-built website — fast, accessible, SEO-optimised — is more than sufficient. There's no reason to pay for the complexity a web app requires if what you actually need is a strong business presentation.
When do you need a web app?
You need a web app when your solution requires one or more of the following:
User accounts and authentication — users log in, have their own data, see personalised content.
Real-time data processing — users submit information and the system responds immediately: calculates prices, generates reports, updates a database.
Complex business logic — access levels, roles, approval flows, calculations that vary per user.
Integration with other systems — the web app fetches or sends data to accounting systems, CRMs, payment providers, or other APIs.
Practical examples for Norwegian businesses:
- Service company that wants to let customers book and manage their own appointments
- Manufacturing company that needs an internal portal for order tracking and inventory insight
- Consulting firm that wants to give clients access to their own project status and documents
- Accounting firm that wants to automate parts of the reporting process
What does it cost?
The cost gap is real:
Website: 15,000–60,000 NOK for most business sites. Low running costs, fast delivery (2–4 weeks).
Simple web app (e.g. booking system, simple portal with login): 60,000–150,000 NOK. Delivery time 6–12 weeks.
Complex web app (many users, roles, integrations, real-time data): 150,000–500,000 NOK+. Requires a longer development cycle and ongoing maintenance.
The price reflects real complexity. A web app has more code to write, more to test, more security to consider (especially if you're storing user data), and more to maintain over time.
Can a solution be both?
Yes — and it's actually very common. A modern Norwegian business site can combine:
- A static marketing site (who we are, what we offer)
- A blog for content marketing and SEO
- A logged-in section for customers or employees
This is a hybrid approach: the static content is a website, the logged-in section is a web app. Next.js is particularly well-suited for this — it lets you build both parts in one codebase, without compromising performance on either side.
Technologies behind web apps
A few terms you'll likely hear in a conversation with a developer:
- React / Next.js — the most common choice for the frontend (what you see) in modern web apps
- Node.js / Express — server-side logic and API layer
- PostgreSQL / MySQL — databases that store user and business data
- JWT / OAuth — authentication methods for login
- REST API — standardised communication between frontend and backend
You don't need to understand all the details — but it's useful to know that a good web app always consists of a frontend (the user interface), a backend (the logic and data processing), and a database (the storage). A website rarely needs all three.
Conclusion
Next time you're considering a digital project, ask yourself this: will my users just read and view content — or will they actually do something?
If the answer is "just read": you need a website. If the answer is "do something": you need a web app. And if the answer is "both": then you need a developer who can build both in one cohesive solution.
Not sure what your project actually requires? Get in touch for a no-obligation technical assessment — it rarely takes more than half an hour to clarify.
Frequently asked questions
What's the difference between a website and a web application? A website presents static information to visitors. A web application allows users to interact, log in, submit data, and perform actions — like booking a service, viewing personalised dashboards, or managing their account.
Is an online store a website or a web app? An online store with a shopping cart, user account, and payment processing is a web app. A simple product catalogue without purchasing functionality is a website.
Can I build a web app with WordPress? WordPress is designed for websites and content publishing. Simple booking features can be added via plugins, but for complex web apps, React/Next.js combined with a dedicated back-end is far more suitable.
How much does it cost to build a web app in Norway? A simple web app with login and basic logic typically starts from 60,000–80,000 NOK. More complex solutions cost more, depending on the number of features, integrations, and users.