Progressive Web App (PWA)
A web application built with standard web technologies that can be installed, work offline and behave like a platform-specific app.
A PWA lets a company offer an app-like experience on mobile and desktop from one web codebase, avoiding separate native builds and app store review for uses such as customer portals or field tools.
A distributor turns its ordering portal into a PWA: it adds a manifest with name, icons and display set to standalone, plus a service worker that caches the product catalog so sales reps can draft orders offline and sync later.
Platform support varies, and iOS restricts some capabilities and install prompts compared with Android and desktop Chrome. PWAs cannot reach every native API, and app store listing requires extra packaging.
A PWA needs a secure HTTPS context, a Web App Manifest and a service worker. The manifest, a W3C specification still at Working Draft, declares name, icons, start_url, scope and display mode. The service worker is a script that runs apart from the page, intercepts network requests and uses the Cache API for offline use, background sync and push notifications. Unlike App Store Product Page Optimization for native apps, discovery happens mainly through the web.
Experience Design
MDN Web Docs — Progressive web apps — https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps; W3C — Web Application Manifest — https://www.w3.org/TR/appmanifest/
