Re: [w3c/manifest] Add splashscreen as a `purpose` (#510)

Right now we have an already gigantic array of `icons`. Splash screens obviously don't fall into that category in my mind.

**If we can avoid any breaking change to the existing `icons` member, that would be great.** The benefits of PWAs are hard to resist. Companies are already realizing HUGE improvements in app install & activation rates, along with dramatic reductions in cost per user acquisition. Some crazy forward-looking devs like me are already using it for production apps. I know, that's nuts, right? But I know of several large enterprise companies who are doing the same.

In addition to the "crazy people are already using this spec in prod" argument, let's go with internal consistency. Since `icons` already sets precedent for a member dedicated to a particular type of asset, I would really prefer that we follow that precedent and add a separate member for `splashscreens`, as well.

I know engineers like to detect patterns and lump everything that feels the same from an engineering perspective into one pile, but shorter lists are ergonomically better, too, and easier to scan.

[Check out how crazy the icons list gets](https://gist.github.com/ericelliott/90602152915b615b761c113f82243146#file-manifest-json) when you try to include just a couple vendor's recommended icon sizes for various devices. Now imagine adding all the different splashscreen sizes and formats.

Giving us separate members gives us a more scannable manifest.

-- 
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/510#issuecomment-261184736