manifest documentation is out of date

[PaulKinlan]

Page Affected: https://developers.google.com/web/fundamentals/web-app-manifest/

What needs to be done? The article does not reflect the current state of how Chrome (and other browsers) use the manifest - for example, note at the end says you can't update the manifest (you can now with web apk and we should detail the process clearly). We now also need a 512 icon for splash screen iirc. We should check and confirm how safari use's this data. I see a lot of people using description now, we should at least document it even though it's not used in Chrome.

There's probably a lot more I missing, that we can add as best practice.

[tomayac]

As we're at it, consider adding documentation on:

• "screenshots" (spec deeplink)
• "iarc_rating_id" (spec deeplink)

Both properties could (but as far as my analysis goes currently aren't) used by Microsoft for the Windows Store.

[PaulKinlan]

I think it's worth ignoring these until there is usage of it.

On Wed, Apr 11, 2018, 14:59 Thomas Steiner notifications@github.com wrote:

As we're at it, consider adding documentation on:

• "screenshots" (spec deeplink https://www.w3.org/TR/appmanifest/#screenshots-member)
• "iarc_rating_id" (spec deeplink https://www.w3.org/TR/appmanifest/#iarc_rating_id-member)

Both properties could (but as far as my analysis goes currently aren't) used by Microsoft for the Windows Store.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/google/WebFundamentals/issues/6029#issuecomment-380461980, or mute the thread https://github.com/notifications/unsubscribe-auth/AACxxgM7cmIeF0IXUHPcqRbzbmG6P0Qeks5tngw5gaJpZM4TPilx .