Use official browser and platform docs for claims about installability, API behavior, and store policy. Use local examples only for implementation texture.
Authoritative Sources
Source
Use it for
web.dev Learn PWA
Overall curriculum and conceptual flow
web.dev install criteria
Chrome prompt requirements and beforeinstallprompt behavior
Chrome install criteria update
Current caveat that menu install no longer universally requires a service worker fetch handler
web.dev manifest guide
Manifest identity, icons, screenshots, scope, and install UI
web.dev service worker guide
Lifecycle, scope, registration, update model, and first-load caution
web.dev offline data guide
Cache Storage, IndexedDB, Storage Manager, quota, and persistence
MDN PWA/API pages
API reference and browser compatibility anchor
Chrome DevTools PWA debugging
Manual install, manifest, service worker, cache, push, sync, and storage inspection
Microsoft Edge PWA docs
Windows PWA behavior, capabilities, and Microsoft Store packaging
Chrome TWA docs
Android Trusted Web Activity wrapper model and Digital Asset Links
MCP Sources Used
MCP source
Use it for
Context7 /googlechrome/workbox
Workbox precaching, runtime caching, fallback, expiration, and background sync examples
Context7 /microsoft/playwright
Service worker policy, offline mode, permissions, and testing limitations
Context7 /pwa-builder/pwabuilder
PWABuilder packaging service shape and Microsoft Store package generation
local-docs peteretelej-fitness-coach-app
Lab PWA design examples with Vite, service worker caching, IndexedDB, and queues
Source Gaps
PWABuilder docs were JavaScript-heavy during plan research and did not fetch cleanly. Use Context7 plus Microsoft docs unless you open the docs in a browser.
Exact iOS/iPadOS install, push, notification, and storage behavior changes over time. Verify on real target OS versions before shipping.
Store policy is executable release work. Re-check Google Play, Apple App Store, Microsoft Store, Samsung, and Huawei policy before submitting wrappers.