However, almost no websites or mobile applications have this feature. Why is that? Is it due to bad developers tools for building voice search (eg. bad usability), because product managers still don't believe in it, because initial testing showed that people want to stop using voice after they land to the website or what is it? What do you think? Have you tried voice search on your application or website?
And even if 50% of all users use voice search, that doesn’t mean 50% of all queries are voice search. Maybe you only want to use it for very specific use cases like weather, and directions.
Personally many websites don’t even have great site search, let alone voice. You should focus on improving that before addressing the 1% of people who would like to use voice search.
I've not used it before but I'm aware of services like Amazon Transcribe. I'm sure a voice search could be build using that, but I'd still need to build it myself.
Things tend to become common place across the web when someone builds a simple plug and play service or widget to solve the problem, but I'm not sure that exists for voice search.
Because people don't need it?
Isn't searching on a page done at the OS level? Or is this more about digging through a contemporary obfuscated UX with menus and pull downs that aren't immediately available?
Wouldn't that be a feature of the virtual keyboard rather than the website/app? My virtual keyboard has voice input.