[w3c/manifest] Allow app to load in parallel to splash screen (#559)

Currently when you 'add to home screen' on Android with Chrome and start the app, it appears the process is:

1. Display a splash screen for a couple of seconds.
2. When the splash hides, start loading the page.

If you make a very large web app (we are building a complete game development IDE), it can take a couple of seconds to start up the page, even when offline cached with a SW, and even with lazy-loading as much as possible. (We've seen just executing the main script take as long as a second.) In this case the splash needlessly increases the perceived loading time. We'd rather have something like this:

1. Start loading the page.
2. Display a splash screen for a couple of seconds.
3. Hide the splash and show the page.

This means a significant amount of the load time can be "hidden" behind the splash screen.

However I can imagine not all web apps would want this. For example perhaps another app would have some kind of fade-in transition that is important. So I think there ought to be an option in the manifest to allow the app to load while the splash is showing, e.g. `"loadDuringSplash": true` (todo: bikeshed)

It might be useful to fire an event when the splash screen is hidden so the app can respond to it. This would allow for example a significant fade-in transition to begin at the right time while still taking advantage of pre-loading. Perhaps the Page Visibility API could cover this? If not, maybe there could be a "splashhide" event.

-- 
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/559