Image Capture Origin Trial results so far

20 views
Skip to first unread message

Miguel Casas-Sanchez

unread,
Mar 27, 2017, 8:14:01 PM3/27/17
to blink-dev

Summary

The Image Capture origin trial started in Chrome M56 (blog post, Android Police). Chrome M58 is the last release it is intended to be available as an Origin Trial. We have now collected various feedback and are sharing it according to the Origin Trials process.


Note we’re publishing feedback before the end of the trial in order to provide time to land code, enable or disable the feature etc in the first release after the trial ends.


Intent to experiment: link


During the TAG Review of the W3C Image Capture Spec (see here), a couple of interop issues were pointed out between the API form and other neighbouring APIs, which culminated with a restructuring of the ways to get/set the photo capabilities/settings (PR).  This happened in parallel to the Origin Trial experiment, so we decided to let it roll through, but didn't want to make too much noise before the end of it.  With the Spec updated in cooperation with Firefox, we have been working in updating the Chrome implementation (bug) and should be ready very soon in M59 Canary. This document has a list of the migrated items.

Contact email

mca...@chromium.org, owe...@chromium.org

Spec and chromestatus.com entry

https://w3c.github.io/mediacapture-image/index.html


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


https://github.com/w3c/mediacapture-image/blob/gh-pages/implementation-status.md

Developer interest

As of March 23rd, 10 origins have registered for access to the origin trial. Tokens were renewed 0 times for this feature.  

Developer feedback

Informal developer feedback was positive.

Lessons learned from our goals for experimentation

Not much given the changes in the Spec going on in parallel.

Timeline

First stable release enabled: Chrome 56, Jan 31, 2017

Usage data (UMA)


There's a single UMA counting the calls to the Image Capture constructor (code). Some metrics:


  • The constructor was called sporadically on Canary, and often no calls were registered for some days; eventually it had peaks of up to ~100 times per day (Mac and CrOs).

  • There were almost no calls logged on Stable, and a few in Beta.

  • Lately there has been a small uptake of uses on Stable (57.x.y.z) and Beta, Android and Win.


Reply all
Reply to author
Forward
0 new messages