Focus on the need, not the acronym
A PWA uses browser technology and can add app-like capabilities. It may suit a portal or repeatedly used tool. Installation alone is not a sufficient requirement: identify the tasks and capabilities that matter.
Offline behaviour must be designed
MDN explains how service workers can cache resources for offline use. This does not mean every record is current or that an order can be confirmed without a server. Show which information is local, when it was updated and what awaits synchronisation.
Test support and conflicts
Test critical features on your audience’s browsers and devices. Include expired sessions, changed records and failed synchronisation. Define conflict handling when multiple people edit the same data. Choose a mobile app if essential capabilities cannot be delivered reliably in the browser.
