Re: [manifest] Manifest format should support some way of including a splash screen (#9)

That's unfortunate, because I find Chrome's implementation hacky, fragile and insufficient to build a quality experience.

AFAIK Chrome's recommendation is to design a 192px icon for splash screen, and then hope that maybe other sizes will be used elsewhere. That's not good enough.

Design of our app calls for a different style of logo on the splash screen than it uses for the homescreen icon (icon should be larger, with name in our brand font, and without a shadow).

Additionally, on the first run, our app needs to download initial data before it can lay out the homepage (homepage layout is dynamic and server-driven), so we do have our own HTML/CSS splash screen. AFAIK there's no way to guarantee when Chrome decides it has the first useful render of the page, so we risk that Chrome's splash screen and our in-app splash screen will be slightly different and cause jarring jump of the logo.

We'd like to create a seamless experience where splash screen looks the same from the first render by Chrome, until our app has downloaded data (optionally with a progressbar rendered on our HTML splash screen if download takes long).

Implementation of splash screens on iOS is a little bit buggy, but it's *so much better* than what Chrome ships.


---
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/9#issuecomment-201382645