Re: [manifest] Integration with service workers (#161)

@skddc : the goal with the SW requirement is that the lack of offline for an installable app _be attributed to the app_. If apps insist on providing poor user experiences, our goal as a UA is to help users understand that it isn't a failing of the web as a platform. Requiring a SW helps in this area because it:

 - Sets the baseline assumption at "installable things work offline". Top-10 apps will do the work to provide an offline experience and, as a UA, we will work to prevent installation of those that suck -- if they're only as good as current web pages, they can live in a tab forever. Even if you can game it for a little while, the lines will have been set.
 - Provides developers with the ability to shoot themselves in the foot with "best viewed in" banners, creating a market for other apps that aren't as poorly written and can work in more UAs more of the time.
 - Through use, raises user expectations of this new class of app.

And does all of that without either preventing apps from running without SWs in tabs or preventing users from manually clicking "add bookmark to homescreen" for things they know they want to keep but which don't otherwise meet the criteria.

New UI, new rules. Seems fair to me.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/161#issuecomment-73146278