Practical knowledge
Website or web app: what fits your need?
The interfaces may look similar, but their roles, architecture and management differ. Choose by the user task before technology.
Questions about this topic?
Martien van Vliet · Development
Start with user behaviour
Public information and enquiries typically need a website. Repeated tasks, accounts, permissions and status need application logic. A public site and separate app can coexist.
Consider data and exceptions
Editing data, multiple process states and roles require attention to authorisation, logging, validation and recovery.
Keep the first version focused
Identify the core user, main task and most important exception. A usable first version provides evidence for the next decision.
Two examples from our work
Scott Multi Diensten helps visitors explore services and contact the team. CRRM supports workshop work orders, customers and planning. The task determines the solution.
Prepare the first discussion
Describe one user, the task and obstacle, the data they need and existing systems. We can assess an initial step without quoting an entire platform immediately.
Practical checklist
- One main user and task
- Required data and permissions
- A defined first version
Further reading: official background information
A suitable next step
Want to apply this?
Explore the related service or discuss your situation with our team. First an introduction, then a clear proposal.