3 ms·
Combining an engine to interpret voice commands with textual keyboard input seems like the best approach here. You get all the useful fuzziness of voice with no
by scrumper 7y ago
Combining an engine to interpret voice commands with textual keyboard input seems like the best approach here. You get all the useful fuzziness of voice with none of the transcription errors (or revolting workplace noise pollution).
I'm fairly well sold on some sort of "omnibar" interface concept where you just tell the computer what you want with a keyboard. Alfred, Spotlight, Google search, Wolfram Alpha, iCal's smart add (you can just type "2pm next Friday"), the Action palette in IntelliJ, VS Code and Sublime's command palette, and so on. That, just... everywhere. And if you're alone, sure, use voice instead. Just don't deprecate the keyboard: still the most reliable way to get accurate text into a computer.
- mikob 7y agoExactly, voice works amazingly as a "3rd interface" complementing keyboards and mice which aren't completely accurate, either, fwiw. Voice gives us more speed, frees up UI clutter and can free up our hands. I'm working on a tool that explores this area more: https://www.lipsurf.com https://www.lipsurf.com
- scrumper 7y agoOops I was a bit unclear. I meant, include the engine part that matches English statements to commands and parameters but hook it up to a keyboard-driven text box instead of a microphone. So it's: written text->'AI'->command vs. speech->'AI'->command (Edit: and sure, voice as an adjunct per my first comment.)