PWA or native app: which one?
For internal teams, a PWA usually does the job. It is a website that installs on the phone, opens full screen, receives notifications and updates itself, with no store and no review. For a product sold to the public, with a subscription and a store presence, a native app is the way.
| Criterion | PWA | Native app |
|---|---|---|
| Distribution | Link or QR code | App Store and Google Play |
| Updates | Immediate, for everyone | Go through store review |
| Camera, QR code, GPS, notifications | Yes | Yes |
| In-app subscription | No | Yes |
| Cost to maintain | Lower | Higher |
Where have we used each one?
Most of our operations systems run as PWAs. That is how a boat pilot records the departure and arrival of each trip and how a crew member runs the inspection checklist on board. See the offshore passenger transport case and the vessel inspection case.
In the health app we went native, with React Native and Expo, because the product needed store subscriptions, Sign in with Apple and a daily-use experience.
What comes with the app?
An app almost never stands alone. It needs an API, a database and a panel for the team that manages content and users. We deliver all three and the store release, including developer accounts, listing copy and screenshots.