Re: [w3c/manifest] Add screenshots object (#477)

> But I'm concerned about adding this and then no stores using it

Ah, that makes more sense. However I am not sure I agree with the concern. I am quite certain that my team would be interested in using it.

>We don't have any conformance requirements related to stores

We (spec folks) don't have any requirements of the browsers, either. They can be determined, and cataloged, but that is no guarantee that  it won't change the moment we go to CR. Much in the same way, we can easily get the requirements for the major app stores (happy to do so myself if desired), and normalize them.

>  I guess I'm looking for commitment that screenshots will be used before adding anything.

I know that Edge is extremely interested in using them.

> I'm also hesitant because I saw how badly it went with the Firefox Store: manifest data was ingested, then developers made modifications during the store's app submission process (e.g., fixed typos), and then they updated their manifest elsewhere, and now everything falls out of sync (store's data doesn't match manifest data... it leads to much sadness).

I am not clear on what the issue is - that user has manifest data. Stores A and B ingest it, user updates the data on Store A, and as a result Store B is out of date?


I think we may be viewing this from two different viewpoints. I believe this would work great a way to seed store data, not necessarily mirror all of the store content across platforms. If a user wants to customize the data after the fact, I don't see the harm in it.


-- 
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/477#issuecomment-242179741