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

@mounirlamouri, I understand the intent, but I'm still worried that it's super easy to screw up and that we are going to end up with a confusing long list of icons that mix badges, splashscreens, normal icons, and other things we add in the future. 

I can understand why badges would be grouped with normal icons, but, as I've demonstrated elsewhere, splashscreen differ a lot from application icons (e.g., in games). The fact that Chrome used the app's icon  as a splash screen was a design choice by the Chrome team (and I agree that it makes for a great fallback), but I don't know if everyone would want to follow that showing an icon as a splashscreen is always a great idea. 

That's why I propose separating splashscreen into its own member... or, as a compromise, we could have splashscreen as "purpose", but would like to see a splashscreen member also added.  

WDYT? 

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

Received on Tuesday, 15 November 2016 08:48:45 UTC