A Progressive Web App (PWA) is a web app that behaves like a native mobile app — installable to the home screen, runs full-screen without browser chrome, works offline, supports push notifications. ActiveManage produces a PWA-capable shell out of the box; the controls in this section let you tune it.
What Makes a PWA
- Manifest: A JSON file declaring the app's name, icons, theme colour and start URL.
- Service worker: Background JavaScript that caches assets, handles push, and works offline.
- HTTPS: Required — browsers won't install PWAs from insecure origins.
- Responsive design: The app must work well at phone and tablet sizes.
- Discoverable installation prompt: Browsers show an “Install” option in the menu or address bar.
Why Bother
- No app store gatekeeping: Users install with one tap; no Apple/Google review needed.
- One codebase: Same site works in browser and as an installed PWA.
- Offline support: Useful for field workers, intermittent connections.
- Push notifications: Even when not in the foreground.
- Home screen presence: Brand visibility next to native apps.
Where PWAs Shine — and Don't
- Great for: Internal tools, B2B SaaS, marketplace apps, content sites, field service.
- Less ideal for: Apps requiring Bluetooth, NFC pairing, deep OS integration (calendar add-ons, photo library access — all improving but still limited).
- iOS gotchas: Push notification support landed only in iOS 16.4 and requires the user to add the PWA to their home screen first.
Worked Examples
- Field service technicians: Install the PWA on their phones; works offline at remote sites; pushes job assignments to the device.
- Healthcare staff portal: Installed PWA replaces the browser shortcut; sign-in persists; biometric unlock works on supported devices.
- Marketplace seller app: Mobile-optimised PWA for managing listings and chatting with buyers; install banner appears after second visit.
- Internal status board: PWA mode used in kiosk style on dedicated tablets in the operations centre.