← Stories

Product choices · Reading draft · 2 min

A website, a web app or a desktop app?

Choose the format around the work people need to do, where they do it and the tools they rely on.

Three device forms arranged on a stone plinth, illustrating different ways to access the same work.
Concept illustration created for this story. It does not depict a customer project or finished product.

Start with the task

A customer comparing services and a colleague checking inspection records need different experiences. Begin with who will use the product, what they need to finish and where that work happens. The format follows those answers.

A website helps someone understand and choose

A website is often the right starting point when people need to discover your business, compare an offer and take a first step. That step might be requesting a sample, sharing a brief or arranging a conversation. Good content, clear navigation and a useful handover matter as much as the page itself.

A web app supports work people return to

A web app gives people an interactive place to complete recurring tasks through a browser. A project workspace, booking tool or reporting view can bring records, actions and status together. Define who can see each record, which changes they can make and what happens when someone returns on another device.

A desktop app can serve a device-specific workflow

Consider a desktop app when the work depends on local files, device capabilities or a particular installed environment. Installation, updates, supported operating systems and access permissions become part of the project. If offline use matters, describe what must work without a connection and how changes will be reconciled later. Offline capability needs to be designed and tested; the format alone does not establish it.

One business may need more than one

Imagine a fictional inspection company. Its public website explains the service and captures an enquiry. A web app lets office staff review reports. Field staff may need a separate interface shaped around their devices and connectivity. Start by testing that field requirement, then choose the smallest combination that supports the complete handover.

Put the decision into the brief

List the users, main task, devices, existing tools and important constraints. Include a recent example of the work. That gives a designer and developer something concrete to compare, including the effort needed to build and maintain each option.

Continue reading

Your next step

Start with your work.

Bring a recent example and the result you want to achieve.

Describe what you want to build ↗How plans work ↗
Converze v76