The difference is persistent workflow
A public website primarily helps people discover, evaluate and contact a business. A web application lets people create or change meaningful state: manage a booking, approve a task, upload a document or track a project. Many products combine both.
The distinction changes the engineering work. A brochure page can be served as static HTML. A client workspace needs identity, permission checks, validation, storage and rules for simultaneous changes. A visually simple table can require more operational design than an animated homepage.
Describe the state transitions
Consider a booking request. “Show the calendar” is only one requirement. Define whether a date is requested, temporarily reserved, confirmed, cancelled or unavailable. Decide who can change each state and what happens when two people request the same slot.
| Question | Website-oriented answer | Application-oriented answer |
|---|---|---|
| Does the visitor change stored records? | Usually submits an enquiry | Creates or updates business objects |
| Who sees the data? | Public content | User, team or organisation-specific views |
| What if a request repeats? | Avoid duplicate enquiries | Preserve transaction rules and history |
| What needs support? | Content and delivery | Users, permissions, incidents and data |
Plan separate public and private surfaces
Keep public content indexable where appropriate. Keep personal workspaces out of the sitemap and enforce access on the server. Hiding a menu item or adding noindex does not protect a record.
A shared design system can connect the two experiences without sharing every permission. Marketing content should not need the same access as customer messages.
Start with one complete workflow
Choose the smallest useful path from input to operational outcome. Define roles, business states, exceptions and acceptance tests before adding dashboards. Garda Racing is an example of a public journey connected to operational features. Explore web applications and portals when your requirement includes continuing work after the first enquiry.
A practical question
Should a public website and private application share a database?
They can, but a shared database is not permission to share access. Public content, customer records and staff operations need explicit grants, row rules and separate server operations.