Installing a PWA does not guarantee offline operation

An installed application can still fail when its network connection disappears during a critical task.

I treat installation and offline operation as separate promises, each requiring its own acceptance tests.

A manifest describes application identity and presentation, while cached responses require deliberately implemented request handling.

MDN distinguishes installation from service workers, rather than treating them as equivalent capabilities.

Teams should test launching without connectivity, unavailable content, and recovery before advertising dependable offline use.

If Offline reliability depends on explicit cache policy, installation alone cannot establish a reliable disconnected experience.

Because Cross-platform PWAs still need capability-based fallbacks, acceptance criteria must cover unsupported environments as well.

An installation badge should describe access convenience, never substitute for evidence about disconnected behavior.