Re: [w3c/manifest] Add description field to Manifest (#435)

> On 5 Apr 2016, at 7:06 PM, Kenneth Rohde Christiansen <notifications@github.com> wrote:
> 
> We use it when apps are submitted to the store (Play Store, Linux Deepin store, etc etc). In our meeting last time, I believe that @RobDolinMS wanted something similar.
> 
> I see little risk in adding this. It is already use somehow by Crosswalk, ManifoldJS and I believe others (@boyofgreen ?) wanted it for store submission as well, and it is definitely useful for other things as well (like web crawlers)
> 

It's not really a question of risk; it's always been a question of browsers or OSs doing something meaningful with the metadata (I.e., in the past we've resisted and ejected any/all store related metadata - compare the first drafts of this spec, which had author, description, etc.). The aim of this spec should be, and has been, to enable installable web apps in precisely the way Chrome has implement the spec (using installability signals + add to homescreen)... Or, even Safari's add-to-homescreen stands as a good example of the goal  of this spec (despite the propriety aspects and shortcomings of their current offering).

This is to say that interested vendors SHOULD standardize store metadata: But we should do it as a separate effort. It's not, for instance, something Mozilla would support (given we tried that and it didn't go as we imagined).

Now, "description" MAY be of value to both browsers and stores (as the physical web example shows). That's what we need to ascertain. Hope that makes sense. 

The fundamental question is always: how will the browser/OS use this?

> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub
> 


---
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/435#issuecomment-205742086