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

I think the payments stuff is a bit of a distraction here, because I still think their proposed reliance on manifest is a step against the extensible web, and @marcoscaceres example above shows that developers could choose to use JSON (or YAML, or whatever) really easily.

That aside, I'm open to service worker being referenced in the manifest. @RobDolinMS:

> **New Device / Back-up and Restore** - When migrating to a new device, a user may "back-up" the list of apps from their old device and then "restore" their apps on the new device.

The service worker scope & script URL could just be backed up along with the app here right?

> **Install now, first run later** - Similar to above. I personally hit this over the weekend while traveling with my two-year-old child. I browsed a list of apps/games for age < 5 and installed a few of these. Then, when on the 4.5 hour cross-country flight (without Wi-Fi), I tried to run these apps.

I agree this requires a declarative service worker registration, but we already have `<link rel="serviceworker">`, is this enough?

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