Intent to Prototype: PWA manifest unique id - desktop

85 views
Skip to first unread message

Phillis Tang

unread,
Jun 16, 2021, 4:29:41 PM6/16/21
to blin...@chromium.org, desktop-pwas-team

Contact emails

phi...@chromium.org, desktop-...@google.com

Explainer

https://github.com/philloooo/pwa-unique-id/blob/main/explainer.md

Specification

None

Summary

Define an optional id field in the app manifest that's used to globally identify the web app. If the id is not specified, start_url will be used as the default id.



Blink component

Blink

Motivation

The appmanifest spec doesn’t explicitly define what uniquely identifies a PWA. Currently, on the desktop versions of Chromium-based browsers and Firefox on Android, PWAs are uniquely identified by app's start_url and Android Chromium-based browsers use manifest_url instead. This is confusing to developers. Also it made developers unable to change their start_url and manifest_url. Having a stable id allows apps to update other metadata like start_url and manifest_url, and have a consistent way to reference apps across browser platforms, PWA stores and other external entities. This feature tracks the launch process for implementation on the desktop side, as the Android implementation will be done with a different timeline. They will both follow the same specification.



Initial public proposal

https://github.com/w3c/manifest/issues/586

TAG review

None

TAG review status

Pending

Risks



Interoperability and Compatibility

None



Gecko: No signal

WebKit: No signal

Web developers: No signals


Is this feature fully tested by web-platform-tests?

No

Flag name

None

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1182363

Launch bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1182361

Link to entry on the Chrome Platform Status

https://www.chromestatus.com/feature/6064014410907648

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages