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

> However, we've had feedback from developers around their existing web apps loaded in an app host rather than the browser where they'd like a loading indicator to be displayed during navigation instead of a blank page. 

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. 

> We've seen that the platform offered loading indicator is enough almost all the time.

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.  

Apologies if this is obvious on Windows, I've just not experience it so it's new to me. Just trying to understand what the experience would be like (particularly if the navigation never completes or takes an excessive amount of time, or if it results in "choppy" navigations that transition between this transition screen and the next loaded page). 

> Our thought was to have the app host show the loading indicator automatically if the developer opted in through the manifest. It could be off by default and the manifest attribute would serve as a toggle.

Yep, got that. 

-- 
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-245806499