- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 16 Aug 2016 20:01:26 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/477/240301146@github.com>
> This (albeit loosely) reflects the current state of icons as well. an iOS icon != android icon. Also true for related_applications as well. Yes, please see https://github.com/w3c/manifest/issues/361. We are working on solving that too. > My point is that I don't see how platform differences in stores should prevent developers from being able to optionally include screenshots in a standard way. I don't disagree. But I'm concerned about adding this and then no stores using it (because they might have specific requirements - and also because of manifest data synchronization/data-authority problems - which I discuss below). With icons it's different: it's the browser, as a conforming user agent, in control of the life cycle and placement of the icon on the homescreen. We don't have any conformance requirements related to stores. > There will always be specificities that the spec doesn't/shouldn't cover. But if a store ingests a site with a manifest as a store app, they would undoubtedly allow for a person to "claim" that app in the store to modify the metadata further (adding videos, release notes, etc). Again, I don't disagree. I guess I'm looking for commitment that screenshots will be used before adding anything. That's how we've added the other features of the spec: we've always had at least one implementer say "yes, we are totally supporting/implementing this". 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). This is why I think stores should manage their own data - because keeping store + manifest data in sync is really hard. -- 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-240301146
Received on Wednesday, 17 August 2016 03:01:53 UTC