Update availableOnDevice and installOnDevice parameters #157
Conversation
| @@ -199,6 +199,14 @@ interface SpeechRecognition : EventTarget { | |||
| attribute EventHandler onend; | |||
| }; | |||
|
|
|||
| dictionary SpeechRecognitionAvailabilityOptions { | |||
There was a problem hiding this comment.
What are your thoughts on having separate dictionaries for availability/installation? These two are currently identical, but they allow the availability options to differ from the installation options in the future.
There was a problem hiding this comment.
Can you give an example of what those would be?
Besides the language, I can see the following:
- quality / speed type of thing
- diarization capability
There was a problem hiding this comment.
Some examples of other options might include:
- LLM-based speech recognition
- acoustic echo cancellation
- spoken/unspoken punctuation
- language identification
- Emoji-support
I think in most cases it would be fine to have the same dictionary type for availability/installation, but is this something we want to commit to?
There was a problem hiding this comment.
We could also rename availableOnDevice() and installOnDevice() to available() and install() and include the on-device part (or the options described here: #156 (comment)) in the SpeechRecognitionOptions.
Closes #155
This PR updates the availableOnDevice and installOnDevice parameters to take in a dictionary encapsulating the on-device model options.