Re: [w3c/manifest] Add optional Transition Screen member (#478)

> I'm confused, as this problem is solved by service workers?: When you have a service worker in place, and resources cached, you get instantaneous loads. 

Service workers solve the problem when the content is cached but it still exists with fresh content. Take a news or shopping app as examples, in both cases there would be fresh content to be navigated to.

>I'm assuming this means on Windows 10. I'd be really interested in seeing an example. I've never seen this on any other platform, which is why I'm so hesitant to include it. 

I don't believe this is displayed automatically by any UA today but each platform has one or more UI loading indicators. I've attached an image of what the experience would look like on Windows 10. You can ignore the all red background, that should be white page or content starting to populate. What we'd like is to show and focus on is a platform chosen loading indicator.
![loadingscreenexample](https://cloud.githubusercontent.com/assets/7948683/18530251/80d81266-7a85-11e6-9f33-41b4905fe5f1.jpg)

It is fine for this to be an optional switch in the manifest. It could be on or off by default (open to suggestions) but we'd like to give developers the control to toggle the state.

-- 
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/478#issuecomment-247160205

Received on Wednesday, 14 September 2016 21:28:24 UTC