Web App, PWA or Native App for Internal Tools: How to Choose for Your Staff
November 11, 2026 · 7 min read · Etzal Group Team
A distribution company asks a vendor for "a mobile app for our salespeople". The vendor builds native apps for both platforms. Eight months and a considerable budget later, the salespeople have an app for taking orders. Half of them have phones too old to run it well, every bug fix waits days for store review, and the sales administrators in the office, who needed the same screens on a laptop, are still using spreadsheets. A responsive web app would have served everyone in half the time. The choice between a web app, a PWA or native app should follow from what the staff need to do, on which devices, in which conditions.
The three options
Responsive web app. A website that adapts to the screen. Opened in a browser on any device. Nothing to install.
Progressive web app, PWA. A web app with extra capabilities: installable to the home screen, full-screen, able to work offline for chosen functions, and able to send notifications on supporting platforms.
Native app. Built for a specific platform and installed through an app store or a device management system. Full access to the device.
Between them sits a fourth approach: cross-platform native, where one codebase produces installable apps for both major platforms. It reduces duplication and still involves app distribution.
Eight questions that decide it
1. Who uses it, and on what?
- Office staff on laptops, and field staff on phones? A web app or PWA serves both from one build.
- Only field staff, on phones the company supplies? Any option is possible.
- Staff using their own phones, of varied age and brand? Web and PWA are the most forgiving.
2. Does it need to work without a connection?
- Always connected: web app.
- Occasional gaps, light data: PWA.
- Hours or days offline, large data, many photos, background sync: native is the safer choice. Test a PWA on the real devices before relying on it.
3. What device features does it need?
- Camera for photos, basic location, file upload, barcode scanning by camera: available to web apps.
- Notifications: available to PWAs on current platforms, with some conditions such as installation to the home screen on certain devices.
- Bluetooth devices such as printers and scanners, NFC, background location tracking, precise sensors, integration with other apps: native is more dependable. Web support exists for some of these and varies by platform.
List the features you need and check each on the actual devices. Platform support changes, so verify at the time of the decision.
4. How often will it change?
- Web and PWA: an update is live for everyone as soon as it is released.
- Native: each update is submitted, reviewed and then installed by each user. Some users stay on old versions for months, and your servers must keep supporting them.
For internal tools that change weekly in their first year, this difference is large.
5. How will it reach users?
- Web and PWA: a link.
- Native through public stores: review rules apply, and internal-only apps can be awkward to publish.
- Native through private distribution or device management: suitable for company-owned devices, and it requires that infrastructure.
6. How demanding is the interface?
- Forms, lists, approvals, dashboards, search: web is entirely adequate.
- Heavy graphics, maps with thousands of points, smooth gestures, video processing: native performs better.
7. What is the budget, for building and for the years after?
Roughly, from least to most costly:
- Responsive web app.
- PWA, with offline design adding to it.
- Cross-platform native.
- Separate native apps for each platform.
The gap widens over time. Two native apps mean two sets of updates, two sets of tests and compatibility work with every new operating system version.
8. What skills does the team have?
A team strong in web technology will deliver a better PWA than a mediocre native app, and the reverse. Ask who will maintain it in three years.
Side by side
| Web app | PWA | Native app | |
|---|---|---|---|
| Install | None | Optional, from browser | Store or device management |
| Works on laptop and phone | Yes | Yes | Phone and tablet only |
| Offline | No | Yes, for designed parts, with limits | Yes, fully |
| Notifications | Limited | Yes, on supporting platforms | Yes |
| Camera, location, files | Yes | Yes | Yes |
| Bluetooth, NFC, background tasks | Limited | Limited, varies by platform | Yes |
| Updates | Immediate | Immediate | Per release, per user |
| Old devices | Tolerant | Tolerant | Depends on OS version |
| Cost to build | Lowest | Low to medium | Highest |
| Cost to maintain | Lowest | Low | Highest |
Typical cases
Approvals, leave requests, expense claims, dashboards. Web app or PWA. Used on any device, changes often, no special hardware.
Sales order taking in the field, mostly connected. PWA. Offline for the catalogue and draft orders, sync when connected, usable by office staff on laptops too.
Inspections with photos in basements and plant rooms. PWA if the offline periods are short and photo volume moderate. Native if technicians work a full day offline with hundreds of photos.
Warehouse scanning with dedicated handheld devices. Native, or the device maker's recommended approach, for reliable scanner integration.
Delivery drivers with continuous location tracking. Native. Background location is where web apps are most restricted.
Field staff printing receipts on a Bluetooth printer. Native, unless you have tested web printing on your exact devices and printers.
A portal for customers or dealers. Web app or PWA. Asking outside users to install an app is a barrier.
A sensible default
For most internal business tools:
- Start with a responsive web app built as a PWA from the beginning. It costs little more and keeps options open.
- Design the server interface cleanly, so that another client can be added later without rebuilding the back end.
- Add a native app only for the roles that prove to need one, when a specific limitation is demonstrated in real use.
This sequence gets a working tool to everyone quickly, and spends native budget only where it earns its place.
Test before committing
For any requirement that might push you to native, run a short proof on the real devices.
- Offline: load a realistic day of data and photos, go offline for the realistic period, and sync.
- Hardware: connect the actual printer or scanner model.
- Notifications: confirm they arrive on the staff's actual phones, locked and in a pocket.
- Performance: try it on the oldest phone in use.
Two days of testing replaces months of argument.
Security either way
- Sign-in through the company's identity provider, with multi-factor authentication.
- Encrypt data stored on the device, and store as little as needed.
- Sessions that expire, and remote sign-out when a device is lost or a person leaves.
- For company devices, device management adds control: required screen lock, remote wipe, restricted installs.
- The server enforces permissions. Never trust the app alone, whatever its type.
Common mistakes
- Choosing native because "app" sounds more serious.
- Forgetting office users who need the same tool on a laptop.
- Assuming a PWA can do anything a native app can, without testing on the real devices.
- Assuming it cannot, from information several years out of date.
- Ignoring old and low-end phones.
- Not planning for users who never update.
- Underestimating maintenance of two native apps.
- Deciding the technology before listing what staff need to do.
We help clients make this choice from their real tasks and devices, and build in whichever form fits, as part of Enterprise Software. If you have been told you need a mobile app and are not sure why, contact us.
Summary
List who will use the tool, on which devices, with what connectivity and what hardware. A responsive web app serves connected users on any device at the lowest cost. A PWA adds installation, limited offline use and notifications from the same codebase. A native app is justified by long offline work, background tasks, Bluetooth or NFC hardware, or demanding graphics. Start with a web app built as a PWA, test the doubtful requirements on real devices, and add native only where real use proves the need.
Frequently asked questions
What is a progressive web app?
A progressive web app, or PWA, is a website built to behave like an installed app. It can be added to the home screen, open full screen, work with a poor or absent connection for the parts designed to, and send notifications on supporting devices. It is delivered through the browser instead of an app store, from one codebase for all devices.
Is a native app always better than a web app?
No. Native apps have the fullest access to device features and the smoothest performance, at the cost of building and maintaining separate versions and distributing through app stores or device management. For forms, lists, approvals and dashboards, which is most internal software, a well-built web app or PWA does the job at lower cost.
Can a web app work offline?
A PWA can, for the parts designed for it. Data is stored on the device and synchronised when a connection returns. The storage limits and background behaviour are more restricted than in a native app and differ between platforms, so heavy or long offline use should be tested on the actual devices before committing.
Related service
Website Development
Fast, SEO-ready websites that turn visitors into customers.
