An API for querying and managing digital products to facilitate in-app purchases from web applications, in conjunction with the Payment Request API (which is used to make the actual purchases). The API would be linked to a digital distribution service connected to via the user agent. In Chromium, this is specifically a web API wrapper around the Android Play Billing API.
Similar to Payment Request: this API is used to talk to specific store backends, and so its usage is tailored to the specific store. The reason it's a proposed web standard is so that the same code (which is specific to one store) is portable across browsers.
Gecko: Negative (https://github.com/WICG/digital-goods/issues/5) A Firefox developer expressed skepticism that this was healthy, saying that it could be done with a REST API instead (note that this would exclude Play Billing as a backend).
WebKit: No signal
Web developers: Positive (https://discourse.wicg.io/t/proposal-web-payments-digital-product-management-api/4350)
Used in tandem with the Payment Request API.
- General API design. Determine whether developers need to access more data that would be exposed through the Play Billing API but is not exposed through our web API. - Specifically, we would like to know whether the API is suitable for abstracting over other non-Play stores. While running an experiment with the current implementation won't tell us this, it will set up real-world clients and we can then try their sites on other implementations.
- M87 (2020-11-17): Experiment begins
- M90 (2021-04-13): Experiment ends
No, Android and Chrome OS only (the two platforms where we have Play Store integration).
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHqYdcatXRwJ4tvh%3DRkJ0jg3Z_so2ikfYYLg5GFfuZEuSLGthw%40mail.gmail.com.