Install guidance separates what works offline from live hockey details that must be checked after reconnecting.
Installable web foundation
PuckReady now has app metadata, manifest icons, and mobile shortcuts for programs, tournaments, saved lists, and parent rules.
Static guides can survive brief offline use
Offline caching is limited to resource and guide pages that carry clear freshness expectations.
Live listings still require a connection
Program, tournament, registration, sanctioning, roster, cost, and travel-permit decisions should be checked online and confirmed with the organizer.
Native app gate
Native mobile waits for proof.
A native app would add app-store maintenance, platform testing, support, privacy review, and release operations. The PWA lets PuckReady learn whether families return often enough to justify that overhead.
Join the no-payment value testInstallability proof
What PuckReady checks before calling the PWA usable.
Installable manifest
Standalone display, PuckReady icons, and hockey-planning shortcuts are exposed through /manifest.webmanifest.
Service worker registration
The browser registers /sw.js only on secure origins or local development.
Offline fallback
Offline mode points families back online before acting on current listings or registration details.
Current listings stay network-only
Program, tournament, data, API, and admin routes are excluded from static offline caching.
Mobile route smoke
Changed public routes are checked at mobile widths before handoff.