We would like to extend the experiment by two milestones to end in M101 (inclusively), instead of the current origin trial end of M99.
Reason this experiment is being extended
The motivation is twofold.
- We need more time to collect feedback from the experimental partners.
- We would like to introduce changes that are requested by the web developers and collect data on those changes during the origin trial.
The changes in question are DGAPI 2.1
, which are non-breaking additions. The new version:
- Adds to DigitalGoodsService:
- Promise<sequence<PurchaseDetails>> listPurchaseHistory();
- Adds to ItemDetails:
- ItemType type;
- sequence<DOMString> iconUrls;
- unsigned short introductoryPriceCycles;
- Adds enum ItemType.
Contact emailsmgi...@chromium.org, gle...@chromium.org, rou...@chromium.org
Currently under review in https://github.com/WICG/digital-goods/pull/40
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.
Search tagspayments, billing
TAG reviewhttps://github.com/w3ctag/design-reviews/issues/571 TAG recommends making a Chrome-specific API. Other issues addressed.
TAG review statusIssues addressed
Goals for experimentation
- 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.
Ongoing technical constraints
We would like to avoid stopping the experiment in between the phases to avoid unnecessarily disrupting current users of the API while we work on the next iteration.
We have had several requests from developers to make the API easier to debug, but it is difficult due to the interaction with a backing service based in an app/store context. We are looking for suggestions (https://github.com/WICG/digital-goods/issues/33) on how we might improve the debuggability of the API.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?No
No, Android and Chrome OS only (the two platforms where we have Play Store integration).No
Requires code in //chrome?False