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

If a user has a good connection and/or there's not much content to load, I would expect very small delay and thus the user agent might not even need to show the transition screen.

However, if there is lots of content to load and/or the device has a low bandwidth connection, giving a web app developer some easy way to communicate that their app is loading (and has not hung) is valuable.

@marcoscaceres, you're definitely right that developers could write something like this for themselves, but offering an option as easy as adding one line to the web app manifest would lower the bar for web site developers to publish as a web app and get more native-like functionality.

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