In this guide 6 sections
Decide by the job, not the format. A website tells people about you and is read by anyone. A web app lets signed-in users do work in a browser. A mobile app is for tasks that need the phone itself, such as the camera, location or offline use. Many businesses need only the first two.
Start with who uses it and what they do
Three words get mixed up in most conversations. A website shows information to anyone who visits. A web application lets people sign in and do work. Mobile apps are installed on a phone.
Before choosing, write one sentence for each group of users. A customer reads your services. A dealer places an order. A field technician records a visit. Each sentence points to a different format.
Do not begin with the format. Begin with the task.
- Visitors who only read: a website
- Users who sign in to place, approve or track: a web app
- Staff on the move who record work: a web app, or a mobile app if needed
- Customers who must be reached on the phone: a mobile app or messages
What a website does well
A website is public. Search engines read it, anyone can open it, and nobody needs an account. It suits services, product lists, contact details, a blog and enquiry forms.
It can also take simple actions. A visitor can send a request, book a call or pay an invoice through a payment link. These are small tasks that do not need a login.
Once people need to see their own records, a website alone stops being enough.
When you need a web application
A web app holds data that belongs to each user and to your business. A dealer sees only their orders. A manager approves a request. An accountant exports a statement.
It runs in a browser on a laptop or a phone, so nothing needs to be installed. Updates reach everyone at once. Access can be set by role.
For most internal tools, portals and dashboards, this is the right starting point. A browser on a phone often covers field staff too, as long as the screens are built for small displays.
When a mobile app is worth building
An installed app earns its place when the phone itself is part of the job. Common reasons are the camera for scanning, location for check-ins, notifications that must arrive quickly and work in areas with weak signal.
It also costs more to keep running. Android and iPhone versions need separate care, and each release goes through a store review. Staff must update the app on their own phones.
Ask a simple question. Would the task fail in a browser? If not, start with the web app and add a mobile app once the need is proven.
- Scanning barcodes or documents with the camera
- Recording a visit with location and a photo
- Working offline and syncing later
- Sending alerts that must reach a phone at once
A worked example and how to stage the choice
Take a distributor with a public catalogue, forty dealers and six delivery staff. The catalogue is a website. Dealers placing and tracking orders need a web app with logins. Delivery staff capture a signature and a photo, so a mobile app may suit them.
Even here, the order matters. Build the website and the dealer portal first. Watch how delivery staff actually work. Then decide whether a mobile app is needed or a phone-friendly web page is enough.
GullySystem’s web and mobile application work starts by listing users and tasks, so the format follows from them.
Format decision sheet
Fill in a grid with a row for each user group. Columns cover the task, whether they sign in, whether the phone camera, location or offline use is needed, and the format that fits. Fill it in with your team before asking any vendor for a quote.
Open a blank worksheet to printQuestions owners ask
Can one product be a website and a web app?
Yes. The public pages and the signed-in area can share one address and one design. Visitors see the public part, and signed-in users see their own records.
Is a mobile app better than a mobile-friendly website?
Not by default. A mobile-friendly web app covers many tasks. A mobile app is better only where the camera, location, offline use or fast alerts are needed.
Should we build all three at once?
Rarely. Start with the one that serves your first user group. Add the next once people use it and the need is clear.
Do customers expect a mobile app?
Some do, but many are happy with a good web page, WhatsApp messages and email. Ask a few real customers what they would use.