Free Web Speech API, why pay?

[gene howell]

 Just curious on why there is a paid version when I can use the free HTML5 version for free all I want. I literally make millions a calls a day and have been for some time. Anyone know if this is truly going away? Is there a difference in the two? 

[PhistucK]

> Anyone know if this is truly going away?

Why "truly"? Have you heard it is going away? If so, where?

The free version is only useful from within Chrome. I think Android WebView cannot use it (though once it can, it will probably use the offline speech recognition in Android, though this is just an assumption).

So if you want to use it from a native application, you simply cannot.

Regarding the differences, I imagine the cloud speech API is more customizable and gives you more types of data (natural language processing) than only transcripts.

☆PhistucK

On Tue, Jun 26, 2018 at 7:44 PM gene howell <ghow...@gmail.com> wrote:

 Just curious on why there is a paid version when I can use the free HTML5 version for free all I want. I literally make millions a calls a day and have been for some time. Anyone know if this is truly going away? Is there a difference in the two? 

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html...@chromium.org.
To post to this group, send email to chromiu...@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-html5/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[gene howell]

In the beginning there was always talks about this being free only temporarily. This is before the 60 limits and such. I guess that is how they limited it but that is easily bypassed. I am doing 5-10 minute long conversions thousands of times a day. 

 My apps are chrome apps so i am good with it just being Chrome. Hey if Google is good with my use then I am not complaining. I just have been hearing "through the grapevine" for a year or two that this would be discontinued as a free option. 

 BTW we have been able to do some source edits and make this work beyond chrome but currently it is janky. I am sure with more work it could be made to work far more smoothly. 

[PhistucK]

There was an issue on the issue tracker that asks to remove it -

crbug.com/726188

It was merged to a "decide what to do with this" issue instead -

crbug.com/699882

I guess plans were not discussed yet. So I do not think you will get an official answer at the moment.

(I am building on this API a bit right now, but it is sort of a bonus feature that does not work so well anyway and that I will be fine without)

Regarding non-Chrome usage of this specific API - while it is indeed possible, it is not allowed and illegal. If you use your own API key, it has a low quota (50 requests per day or something) that cannot be increased. If you are using the API key of Chrome, well, it is totally illegal and you probably cannot based commercial products on this.

☆PhistucK

[gene howell]

Thanks for the link! Very interesting. I guess my big concern is do I continue to develop on it not knowing the future. I have no doubt I am abusing it some with all my calls however it is a great test for the Chrome guys to see it in a quick paced production environment. :P I doubt too many people are using it as much as I am. I am sure someone has looked at the server and said WTF...haha

 I am definitely not using it on anything but Chrome. I never proceeded with that project. It was more fiddling.  

[PhistucK]

It is a good question.

I do not think you are abusing it, this is the purpose of the API. It is like you would think you abuse indexed databases if you stored a lot of stuff in them. ;)

I think Firefox is still fiddling with the question as well (whether to ship at all).

I think Edge at some point indicated positive signals about it, but I guess the stance of Chrome might have affected their decision and it is now again "Under consideration" without any priority.

No good answer...

On the other hand, crbug.com/487255 could be a positive signal of a future... Or an indication of disparate groups within the Chrome team.

☆PhistucK