Re: [w3c/manifest] Clarify ServiceWorkerRegistrationObject’s purpose (#800)

@mgiuca @aarongustafson .  With EdgeHTML packages we had this idea of "precaching", in which an app that was downloaded form the store would silently load the initial page to prime the cache at install time.  This was to avoid the initial page load experience. I know a few Microsoft "productivity" apps that used it, but it wasn't often used.  We suggested the change to registration object so we could put that same type of experience in place with the more logical service worker cache calls.
  I would say it is still a very nice idea (helpful any time a PWA is installed from a source other than a button on a page that is already loaded) but not a current priority. Step one is just getting the content from the manifest to use for an external install.
  Also my two cents on the nested SW, I think it will be a needed feature for enterprise adoption.  We need a way for Service Workers to play nice together when multiple teams are working on the same site, and site hierarchies doesn't follow team structure :)

-- 
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/800#issuecomment-536601882