Question about Shipping vs Continue Experimenting

36 views
Skip to first unread message

Jiewei Qian

unread,
Dec 3, 2021, 12:16:35 AM12/3/21
to blink-dev, handwriti...@google.com, Glen Robertson, Matt Giuca

Hi blink-dev,


Our Handwriting Recognition API origin trial ends in M97. M98 branches in a week.


We want to get some recommendations on shipping vs continuing experimenting.


At the moment:

  • We have just 1 app using the origin trial (based on received feedback), so there is little risk of burn-in but also only a small amount of feedback

    • Feedback from this developer has been positive

  • We have a draft spec in internal review

  • WPT tests are internal, we can move relevant tests to external 

  • W3C TAG review suggests “the proposal is good to move forward”

  • We’re willing to ship in M98 if recommended, or

  • We're willing to extend the OT and try to get more developers to use it


What’s the recommended approach?




Yoav Weiss

unread,
Dec 3, 2021, 1:14:03 AM12/3/21
to Jiewei Qian, blink-dev, handwriti...@google.com, Glen Robertson, Matt Giuca
On Fri, Dec 3, 2021 at 6:16 AM Jiewei Qian <q...@chromium.org> wrote:

Hi blink-dev,


Our Handwriting Recognition API origin trial ends in M97. M98 branches in a week.


We want to get some recommendations on shipping vs continuing experimenting.


At the moment:

  • We have just 1 app using the origin trial (based on received feedback), so there is little risk of burn-in but also only a small amount of feedback

    • Feedback from this developer has been positive


The OT has been running for 7 milestones now. What's the reason for the lack of sign-ups?
 
  • We have a draft spec in internal review


This part sounds like it may need more work and broader reviews before shipping would be possible.
 
  • WPT tests are internal, we can move relevant tests to external 

  • W3C TAG review suggests “the proposal is good to move forward”

  • We’re willing to ship in M98 if recommended, or

  • We're willing to extend the OT and try to get more developers to use it


What’s the recommended approach?




--
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/CANFkJJnCyuF0pP2UJLmxbabntRVTxXCGqFRM_-BpoUzg65-y1A%40mail.gmail.com.

Glen Robertson

unread,
Dec 3, 2021, 2:29:47 AM12/3/21
to Yoav Weiss, Jiewei Qian, blink-dev, handwriti...@google.com, Matt Giuca
> What's the reason for the lack of sign-ups?
I suspect it's just because it's quite a specialised API and the OT is only available on CrOS.
We've had a few developers express interest on the github repo. There also seemed to be some interest on twitter, with several tweets and a web.dev article from our DevRel folk about the API. So there has been a reasonable effort to get word out about the API. 

If you have any guidance for what to do in this sort of situation, please let us know!

Yoav Weiss

unread,
Dec 7, 2021, 2:06:17 AM12/7/21
to blink-dev, Glen Robertson, Jiewei Qian, blink-dev, handwriti...@google.com, mgi...@chromium.org, yoav...@chromium.org
I'm not sure I have guidance on how y'all can get more OT usage and feedback. It seems to me that y'all are best positioned to assess the developer need and reach out to them to increase engagement. Devrel folks may be able to help.

Without expectation for further engagement, I don't think it makes sense to continue to OT.

Reply all
Reply to author
Forward
0 new messages