Edge is implementing it, so Chrome will not be the only one.
https://developer.microsoft.com/en-us/microsoft-edge/platform/status/webspeechapiinput/?q=speech

Firefox has also implemented it:
https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API#Browser_compatibility

This SpeechRecognition API is used by several sites, including:

- google.com to implement Voice Search
- docs.google.com to implement Voice Typing
- translate.google.com to implement Voice Input

#2 - not exactly. The information is not so complete or up to date.
Their platform status page shows speech recognition as under consideration and if you look at their linked bug, you will see that it is only available to their web user interface equivalent (and only on desktop) and some backend issues (and no one seems to be working on it).

https://platform-status.mozilla.org/
https://bugzilla.mozilla.org/show_bug.cgi?id=1248897

Thanks for the details.  Edge implementing potentially changes things for sure, but we'd still need someone to own bugs, spec issues, etc.

Note that there is a UseCounter for the constructor that's up around 1% of page views: https://www.chromestatus.com/metrics/feature/timeline/popularity/1269

But this will trigger even just for feature detection code that never actually uses the API.  So I'm adding a UseCounter on SpeechRecognition.start() to measure how often someone actually uses it.

587 hits for webkitSpeechRecognition in HTTP Archive (~0.1% of top 500k sites).
https://docs.google.com/spreadsheets/d/1uH0Hx61fNZNS8kxFnMiVZf5gzb-kwf74Z7SK4jg5Erk/edit#gid=1004973723

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/793a817301622f653c43ec9ad8869b4b1e373b0a

commit 793a817301622f653c43ec9ad8869b4b1e373b0a
Author: rbyers <rbyers@chromium.org>
Date: Fri May 26 21:22:39 2017

Add UseCounter for SpeechRecognition

BUG= 726188 

Review-Url: https://codereview.chromium.org/2901373002
Cr-Commit-Position: refs/heads/master@{#475134}

[modify] https://crrev.com/793a817301622f653c43ec9ad8869b4b1e373b0a/third_party/WebKit/Source/core/frame/UseCounter.h
[modify] https://crrev.com/793a817301622f653c43ec9ad8869b4b1e373b0a/third_party/WebKit/Source/modules/speech/SpeechRecognition.idl
[modify] https://crrev.com/793a817301622f653c43ec9ad8869b4b1e373b0a/tools/metrics/histograms/enums.xml

rbyers@, I added two use counters after yours and merged into M60 branch.

Now UseCounter.h reads in trunk:
    ....
    kNetInfoEffectiveType = 2013,
    kV8SpeechRecognition_Start_Method = 2014,
    kTableRowDirectionDifferentFromTable = 2015,
    kTableSectionDirectionDifferentFromTable = 2016,
    // The above items are available in M60 branch.

and in M60:
    kNetInfoEffectiveType = 2013,
    kTableRowDirectionDifferentFromTable = 2015,
    kTableSectionDirectionDifferentFromTable = 2016,
    // The above items are available in M60 branch.

I could add a comment in trunk saying that kV8SpeechRecognition_Start_Method is not in M60, or would you like to merge crrev.com/475134 into M60 so that the comment would become true?

wangxianzhu@ I don't think I can justify asking merge approval for mine, so the comment would be nice but I wouldn't worry much about it.  Those comments are never perfect in practice (and the only person whose really likely to be confused by it is me <grin>).  I need to fix chromestatus.com to avoid milestone confusion on UseCounters generally anyway.  

dev channel data SpeechRecognition's 'start' method shows ~0.01% of page views.  This is fairly high indicating it's not obviously a good candidate for removal.

See issue 570968 instead.

This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge