Notifying users of changes to your #PWA is hard. We’re thinking about ways to make it easier by enabling you to include a version number and point to an HTML change log, RSS/Atom feed, or similar from within your web app manifest. Feedback appreciated!https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VersionHistory/explainer.md …
-
-
Replying to @AaronGustafson @slightlylate
I feel like we've had a lot of these "metadata" fields that don't actually affect the app behavior, and they don't seem to have been used much.
@marcosc isn't a fan of this type of field. Perhaps we should coalesce them into a separate "metadata.json" file, linked from manifest?3 replies 0 retweets 0 likes -
Replying to @mgiuca @AaronGustafson and
I agree with Matt... it's probably time to consider splitting off things into a separate resource.
@slightlyoff, can you quantify what "operational issues" you're thinking about?1 reply 0 retweets 0 likes -
Replying to @dominickng @mgiuca and
Servers deploying mutiple files instead of one in the correct order across global frontends is tricky. Is there evidence of pain that should cause us to prefer multiple files, e.g. download time? If it's just editor preference, that seems like something we could off on.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @dominickng and
Other issues: how will we surface a missing metadata file on devtools? If I delete a manifest for an app but not the metadata file, what happens? Is this metadata file scoped exactly the same way? How does it interact with origin-wide configs like Origin Policy? Versioning?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @dominickng and
With enough elbowgrease from everyone, I presume all of this can be worked out. Just wondering why we need to work it out *now*; that's all.
1 reply 0 retweets 1 like -
Replying to @slightlylate @mgiuca and
The more we put into manifest now, the harder it is to take it out later. It's good to be thinking about future sustainability - as Matt points out, downloading the manifest blocks installation and smaller mandatory resources benefit everyone
1 reply 0 retweets 0 likes -
Replying to @dominickng @mgiuca and
Agree we should be about thinking about sustainability. Curious if we have evidence in hand that additions are an issue.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @dominickng and
Agreed. Parsing JSON is not terribly costly and if you’re only planning to tap into a handful of keys for the install process initially, it seems pretty inconsequential.
2 replies 0 retweets 0 likes
I'm looking to see if we have data on manifest sizes, e.g. from HTTP Archive
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.