This is an intent to extend "Digital Goods API v2.0" not "Digital Goods API" (they are separate experiments).
On Fri, 21 Jan 2022 at 19:32, Rouslan Solomakhin <rous...@chromium.org> wrote: > Hello blink-dev, > > 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. > > 1. We need more time to collect feedback from the experimental > partners. > 2. 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 > <https://github.com/WICG/digital-goods/blob/main/explainer.md#api-v21>, > 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, glen...@chromium.org, > rous...@chromium.org > > Explainerhttps://github.com/WICG/digital-goods/blob/master/explainer.md > > SpecificationCurrently under review in > https://github.com/WICG/digital-goods/pull/40. > > Design docs > https://docs.google.com/document/d/1Jbt2Mzt-xg1cWVlFScBQsoX_pE8Kg1gYpulxUSV8FM0/edit > > Summary > > 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. > > Blink componentBlink>Payments > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPayments> > > Search tagspayments <https://chromestatus.com/features#tags:payments>, > billing <https://chromestatus.com/features#tags:billing> > > TAG reviewhttps://github.com/w3ctag/design-reviews/issues/571 TAG > recommends making a Chrome-specific API. Other issues addressed. > > TAG review statusIssues addressed > > Risks > Interoperability and Compatibility > > 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: No signal ( > https://github.com/mozilla/standards-positions/issues/349) Requested > 2020-05-27 > > WebKit: No signal ( > https://lists.webkit.org/pipermail/webkit-dev/2021-October/032001.html) > Requested 2021-10-08. > > Web developers: Positive ( > https://discourse.wicg.io/t/proposal-web-payments-digital-product-management-api/4350 > ) > > Other signals: rouslan@ presented DGAPI at 2021 TPAC > <https://www.w3.org/2021/Talks/rouslan-dgapi-20211028.pdf> (meeting notes > <https://www.w3.org/2021/10/28-wpwg-minutes.html#t04>) and at a recent PWA > Dev Sync > <https://drive.google.com/file/d/1a_6_QVEQrEeUduc8nPE-uc7PKCr-Yhx7/view> > (meeting > notes > <https://docs.google.com/document/d/1X2j1wKC2T4RONcUGYxGus8Dytv6s2_tVTUSkWDWPza4/edit#heading=h.chc35okxwb9>). > Other browser implementers and app stores do not appear to have > immediate plans to engage with DGAPI. There were some questions, no > objections. > > Ergonomics > > Used in tandem with the Payment Request API. > > > 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. > > > Debuggability > > 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). > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ?No > > Requires code in //chrome?False > > Tracking bug > > https://crbug.com/1250604 > > Launch bug > > https://crbug.com/1288420 > > Estimated milestones > Origin trial extension begins: m100. > Origin trial extension ends: m101 (inclusive). > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5339955595313152 > > Links to previous Intent discussionsIntent to prototype: > https://groups.google.com/a/chromium.org/g/blink-dev/c/vkS3k30lWNs > Intent to Experiment: > https://groups.google.com/a/chromium.org/g/blink-dev/c/wIYqo3F_Vmo > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPV%2BSg_cnrPLmxGxFTLT5KJkqJoOS2h9jf2kuJtwUPXnAP33tQ%40mail.gmail.com.
