Contact emails
mgi...@chromium.org, owe...@chromium.org
Spec
https://github.com/WICG/get-installed-related-apps/blob/master/EXPLAINER.md
Summary
Allow sites to determine whether the user has installed their corresponding app, where the “candidates” to be checked are drawn from the related_applications key in the manifest.
Installed applications must attest that the origin is allowed to read their installed state. On Android this is done via Digital Asset Links (“Android app statement lists” part only; we ignore website statement lists).
This API is motivated largely by the need for websites using push notifications to determine whether their corresponding native app is installed to prevent sending duplicate notifications.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/0xXsJYdkaWg/2NwHKmZBEAAJ
Note: This was a combined “intent to implement and experiment”, but it’s so old that we are proposing a fresh experiment with a new timeline and goals.
Goals for experimentation
Determine whether the API design is ergonomic
There have been suggestions for alternate designs, such as making it a single method isAppInstalled, that takes some metadata and returns a promise. We aim to seek developer feedback during the trial about the decision we have made here.
Determine whether the API solves the notification de-duplication issue
Hear from developers who use this in practice whether it solves their issue.
For example, it’s possible that the user may have the app installed, but be logged in with a different account (which cannot be detected with this API). It’s not clear to what extent these edge cases not being solved by this API are blockers for developers.
Experimental timeline
Enabled:
2017-04-13: M59 branch to dev channel.
2017-05-04: M59 in beta channel.
2017-06-06: M59 in stable channel.
2017-08-01: M60 in stable channel.
2017-08-08: Feedback from M59.
2017-09-12: M61 in stable channel.
2017-09-19: Feedback from M60.
Disabled:
2017-10-24: M62 in stable channel. Experiment ends.
2017-10-31: Feedback from M61.
Any risks when the experiment finishes?
No
Ongoing technical constraints
Relies on specific features of Android, so is only available on that platform at the moment. Special technical complexity: can’t be “onion souped” fully yet because the Blink side of the code relies on fetching the Web App Manifest, which is defined in Chrome. Therefore, we need a module in content/renderer. Work is ongoing to port this to Mojo so that we can remove the code from content/renderer.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Android only as that is where the feature requests for de-duplicating notifications have come and as related_applications isn’t used for desktop today.
OWP launch tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=587623
Link to entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
☆PhistucK
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.