Progressive web apps (PWA)
A progressive web app installs without an app store, works offline and sends push notifications.
When a PWA can replace a native app
Native apps mean two code bases, app store reviews and higher maintenance costs. A PWA behaves like an app and can still be found via search engines. Typical uses are customer portals and field service tools.
Technology
Service worker caches content for use without a connection
Web app manifest defines name, icon and display
Web push sends notifications after consent, on iOS from version 16.4
HTTPS is a prerequisite for all PWA features
Limits
Not every device function is available in the browser. For some hardware interfaces, or when the app must be in an app store, a native or hybrid app is the better choice. We clarify this before the project starts.
Approach
Define use cases and offline requirements
Define a caching strategy for each content type
Build the interface mobile first, for example with SvelteKit
Test on iOS, Android and desktop
Operation and updates
Updates reach all users via the service worker, without reinstalling. Data captured offline is synchronised at the next connection.