Website, web app or both?
Choose a public website when the main job is to let anyone understand your business and contact you. Choose a web app when people need to do ongoing work with data that is saved and shared. Choose both when strangers first need information and known users then need a working area. Start with the smallest option that covers the real tasks.
Start with what visitors need to do
List the tasks in plain verbs: read prices, compare services, send an enquiry, book a slot, upload a document, check an order. The labels overlap. A brochure site can have a contact form, and a web app can be open without a login. What matters is the work being done.
Tasks that only need people to read and ask a question point to a website. Tasks that change or depend on saved records point to an app.
Ask who works with the data
Static pages show the same content to everyone. Dynamic pages are assembled by a server, which can check submitted input, read from a database and send notifications, as MDN explains in its introduction to the server side. That capability, not the word you use, is what separates a simple page from an app.
- Is the information the same for every visitor, or personal to a customer or team member?
- Do several people edit the same records?
- Does anyone need to see their own history or status?
- Does a submission need to trigger something, such as an email to staff?
Weigh the simplest fit and who runs it
More function means more to look after: accounts, backups, updates, support questions and privacy duties. Decide who will own those before building. If nobody can, a simpler site with a clear contact route is often the better first step.
You can also stage the work. Publish the public website first, then add a small app area once the repeated tasks are clear.
An illustrative example
Imagine a small cleaning company. Customers want to see services, areas covered and how to ask for a quote. That is a website. Staff also want a shared schedule showing who is at which address, with notes after each visit. That is a web app, used only by the team. The company needs both, but the public site can stand alone and the schedule can come later. This example is hypothetical.
Decision checklist
Answer these before asking for a quote. Each answer narrows the scope.
- Who are the three most common visitors, and what is each trying to do?
- Which tasks end with reading, and which end with saved information?
- Does anyone need to sign in, and why?
- Which records must be shared between staff or customers?
- What should happen automatically after a form is sent?
- Who will update content and handle problems after launch?
- What is the one task that must work on day one?