PWA or native mobile app development should be based on the tasks people need to complete on their devices. A PWA is a good candidate when you want access through a link and support for different screen sizes. Consider a native approach when the work depends on operating system features or connections to specialist equipment. Before deciding, test the most demanding feature on the phones your users will actually use.
If you are still deciding whether you need an app at all, start with our guide to a mobile app or a website. Here, we assume you already know which business task you want to support.
What is the difference between a PWA and a native app?
A PWA (Progressive Web App) is a web application accessed through a web address. On supported devices, users can add it to their home screen and open it in a separate window. Installation, available features and behaviour depend on the browser and operating system. Google's PWA guide explains how this combines web access with app capabilities.
A native app uses the capabilities of its platform, such as iOS or Android. Alongside separate development for each platform, there are tools that share some of the code. For example, React Native uses native interface components. A shared codebase for Android and iOS therefore does not automatically mean the application is a PWA.
Ask the developer to specify where the application runs, which code is shared and which features require separate work for each platform.
Scroll the table sideways to see all columns.
| Criterion | PWA | Native app |
|---|---|---|
| Access | Through a link; home screen installation where supported. | Installation through the agreed distribution channel. |
| Devices | One web interface can serve phones and computers. | The interface and integrations are built for the supported platforms. |
| Offline work | Developed for selected data and actions. | Also requires local storage and synchronisation rules. |
| Phone features | Support must be checked in the relevant browser. | System capabilities, permissions and restrictions must be checked. |
| Maintenance | Web releases, browser compatibility and updates to locally stored data. | App releases, operating system changes and distribution requirements. |
Which features should you check before choosing?
Describe what the user does precisely enough to test it. "Uses the camera" could mean attaching one photograph to a fault report or continuously reading codes with a dedicated scanner. These are different requirements. The PWA capabilities documentation recommends checking support for each required feature, rather than assuming it works equally on every device.
Are push notifications essential?
A PWA can support push notifications. On iPhone and iPad, Web Push was introduced in version 16.4 for web apps added to the home screen, with permission requested in response to a user action. This is described in the WebKit documentation. Your specification should identify the supported devices and what users see if they do not allow notifications.
What must keep working when the phone is locked?
Uploading a large file and tracking location need separate checks. Native apps do not have unrestricted background execution either: Android and Apple define supported approaches and restrictions. Test with the screen locked, a change of network and an interrupted task.
What does working offline actually mean?
Opening an already loaded screen is different from completing a task without a connection. A PWA needs the necessary on-device data storage to be developed; web.dev explains the available storage mechanisms and their limits. For either type of app, agree which actions can happen offline and how the resulting data will be sent later.
Users should be able to distinguish "saved on this phone" from "received by the server". Decide what happens if two people edit the same record or someone submits an entry again.
Our Livsmedelsstädarna project describes a specific boundary: an inspection already downloaded can continue offline, while starting a new inspection and making the final submission require a connection. This is an example of a defined workflow, not a rule for every web or mobile app.
How should you compare development and maintenance costs?
A PWA can reduce development work if the same web application covers all the required devices. If essential features need extensive workarounds, that initial saving may disappear. A native approach can justify the additional work when it is needed to complete the agreed task reliably.
Compare proposals for the same scope: user roles, system integrations, testing and support after launch. The server, access permissions and administration remain part of the project whichever interface you choose. Our guide to business mobile app costs explains what to separate in an estimate.
An example for a business with field staff
This is a hypothetical example. A service company wants its technicians to view a work order, attach a photograph and record the repair. A dispatcher follows the jobs from a computer. If all the required actions work on the team's phones, a PWA is a reasonable candidate for the first version.
The requirement changes if the technician needs a specialist Bluetooth instrument or a particular task must continue with the screen locked. We would first test the connection to that equipment and check the system restrictions. Those findings determine whether a web approach covers the job or a native component is needed.
How can you prepare to make the decision?
- List the actions users need to complete their work.
- Record the devices and operating system versions you must support.
- Identify what must work offline, in the background or with additional equipment.
- Request a test of the highest-risk feature before commissioning the full development.
Write the acceptance condition before the test. For example, a work order with a photograph must remain saved after a connection drops, and submitting it again must not create a duplicate. Assess speed and reliability through that workflow.
Frequently asked questions
Can a PWA appear in an app store?
Yes, with suitable packaging and compliance with the store's rules. Android supports Trusted Web Activity for opening a web application from an Android app. Publishing it in a store does not itself turn the web interface into a native one.
Is a native app automatically faster?
No. Responsiveness depends on data processing, the network, interface and device. Ask for the actions that matter to your users to be tested on the agreed phones.
Can we move from a PWA to a native app later?
You can, but allow for a new assessment. The server-side system and business rules may remain, while the interface and device integrations may require new development. Ask in advance which parts could be reused.
To discuss mobile app development, send us a description of a user's working day and the devices they use. In a project discussion, we can identify which features to test first and prepare an estimate for a suitable solution.