The short answer
- Build for where the work happens: desks get a web app, sites and vans get a mobile app.
- A mobile app earns its cost when people need the camera, offline working or notifications.
- One backend can serve both, so starting with one doesn’t lock you out of the other.
Start with the work, not the device
Ask who does the job, where they are when they do it, and what they need at that moment. The answer usually points to the right front end.
When a web app is enough
- People work at a desk, on a laptop or a large screen.
- The job involves tables, reports, long forms or several things open at once.
- You want changes live the moment you release them, with no app store review.
A well-built web app also works in a phone's browser, which covers occasional use on the move.
When you need a mobile app
- No signal. The work happens in basements, rural sites or vans, and must save offline.
- Camera and files. Photos, scans and signatures are part of the job.
- Notifications. People need to know about a new job or a change straight away.
- Daily use. An icon on the home screen gets used; a bookmarked web page often doesn't.
Why many businesses need both
Estimark is a good example. The office plans, prices and invoices on a laptop. The site team records diaries, photos and safety checks on a phone. Both work on the same job record.
One backend, two front ends
The rules, the data and the permissions live in one place. The web app and the mobile apps are different windows onto it, so you can start with one and add the other later without rebuilding.
Our usual advice
Build first for the people whose work costs most to do by hand today. If that's the office, start with web. If it's the site, start with mobile.