Re: [w3c/manifest] # Proposal: Add `start_failure_callback` and `fetch_failure_callback` to the Web App Manifest (Issue #1191)

JerryJWChan left a comment (w3c/manifest#1191)

Thank you for the closure. I’d like to respectfully emphasize that this proposal addresses a real user experience gap for installed PWAs, where users may lose access to apps unexpectedly without understanding why.

While I understand the position that browsers can handle missing data with error pages, I believe the assertion that “that’s just the nature of the web” overlooks the web’s creative and evolving nature. The web has continuously advanced through new ideas and APIs that meet emerging user expectations, and PWAs are no exception.

This proposal aims to align the PWA specification with those expectations, ensuring installed apps behave more like native apps and providing a more reliable, user-friendly experience. I’d be happy to provide examples or discuss potential approaches that maintain consistency with the spec while addressing this UX concern.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1191#issuecomment-3471243360
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1191/3471243360@github.com>