Conversational AI is hard to use by voice across devices
People who want conversational AI by voice on phones, smart-home devices, or in their IDEs often find that the assistant they want is not available in that setting. Workarounds can mean difficult setup or continuously streaming audio, with battery or privacy tradeoffs. The evidence shows requests and individual workarounds, not proof that one solution would satisfy every use case.
For people seeking conversational voice assistants across devices. Mentioned from Feb 2024 to Apr 2026 on Bluesky, product forums, GitHub and Hacker News.
9 different people described this problem in 9 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.6/10
- Frequency
- 8.3/10
- Willingness to pay
- 5.8/10
- Momentum
- 5.0/10
- Who pays
- Consumers
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
Never could get the termux method working on my phone, so currently I am having to use hassmic to constantly stream my phone's audio to my HA server, which isn't the best for battery life and is wildly inefficient, but credit to hassmic since it does work
I wish I could set it as my phone's (Android) default assistant. If you built that, I would pay good money for it!
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 7 more quotes from people who have this problem
- Current workarounds, existing solutions and risks