Mobile app vs web app: check the device capabilities you need

Choose between a web app and an installed mobile app by testing the capabilities your users need. Both can support accounts, shared data and connected workflows. The deciding requirements often involve device access, interrupted connections, background work and distribution.

This checklist helps a business describe those requirements before accepting a technology recommendation. It complements the broader app or website decision guide.

Describe the behaviour, not just the feature name

“Needs a camera” is incomplete. Does the user upload an existing photo, take a picture inside the app, scan a barcode continuously or operate specialist equipment? Those are different requirements.

The same applies to location. Choosing a place on a map is different from recording a route while a phone is locked. Ask the developer to demonstrate the exact behaviour on the devices you expect people to use.

A capability review to use in your brief

• Installation: can a browser link serve the audience, or is installation a genuine requirement? Test the installation steps on supported devices.
• Camera and files: check capture, upload size, orientation, permissions and recovery from a failed upload.
• Location: specify whether location is needed once, while the app is open or in the background. Test permission refusal and unavailable location.
• Notifications: define which events justify an alert, how permission is obtained and how users find the information if notifications are disabled.
• Offline work: identify what can be read, created or changed without a connection and what must wait.
• Device integration: name any scanners, Bluetooth devices, biometrics or operating-system services the task relies on.
• Distribution: decide how users find, install and update the product, and who owns the relevant accounts.

Mark each item essential, useful or unnecessary for the first release. That makes it possible to choose an approach around the real task instead of paying for capabilities the business does not need.

Offline is a set of decisions

A PWA can use service workers and local storage to support parts of a journey when connectivity is unreliable. The behaviour must be designed. MDN's offline and background operation guide explains the web technologies and their limits.

Decide what happens to a draft, which data may stay on the device and how conflicting changes are resolved. A record saved locally is different from one received by the office. The interface should make that distinction clear.

An illustrative test with demo data

Imagine a field worker completing an inspection report. This is a hypothetical scenario, not a client case. Use a test account and a made-up inspection. Ask the team to demonstrate the following on a representative phone:

1. Open the assigned job and capture a photograph.
2. Disconnect before sending. Check that the draft remains recoverable.
3. Close and reopen the app. Confirm what is still available.
4. Reconnect and send. Confirm receipt on the office side.
5. Repeat the action. Check that it does not create a second report.
6. Sign out. Check that private job information is protected as agreed.

A successful test supports that specific combination of requirements and devices. It does not prove that every browser or operating-system version will behave identically. Record the supported combinations and repeat important checks when the product changes.

When an installed app may be worth it

An installed app deserves closer investigation when the task depends on capabilities that a browser cannot reliably provide on the supported devices. Native, cross-platform and hybrid approaches each have different implementation and maintenance considerations. Our hybrid app guide explains the bridge and plugin questions.

A web app may be a strong fit when convenient access by link, use across phones and computers, and centrally delivered updates suit the workflow. Make the choice after the essential tests, with the full ownership costs in view.

Cloudfusion can help assess the uncertain capabilities through our software and digital product service. Start with the behaviour that must work and the people who depend on it.