Loqua is LIVE on Product Hunt today, and welcome to the family!
AI keeps getting smarter yet using it feels more tiring: prompting, switching apps, screenshotting, explaining context again and again. Often the problem isn't the AI; it's that we still have to learn how to talk to it.
So we built more than better voice typing. Just say what you want, and Loqua understands your app, screen, language, and tone dictate in Gmail, ask about a chart you're looking at, tell Codex or Claude Code what to change, set reminders, open apps, or have a page read aloud.
We believe voice agents are a necessary path to AGI and a core part of physical AI. As a model-first team, Loqua is our first step: our own multimodal model for better transcription, translation, and multimodal Q&A, with deeper agentic, long-horizon abilities rolling out.
If this resonates, we'd love your support
An upvote unlocks a promo code, and sharing earns extra days. Try it and tell us what you'd want it to do next.
Upvote & try Loqua:
[Website link]: https://theloqua.ai/
[Product Hunt link]: https://www.producthunt.com/prod...
Lessie AI
Would this work well for developers writing documentation, PR descriptions, and technical explanations?
Loqua
@alexia_li Definitely! Voice can be especially useful for getting technical explanations and documentation out quickly.
Loqua
@alexia_li We are developers, everything works better now lol!
Regarding the 'understand what's on your screen' feature, is that reading text, or real understanding of what application you're using?
Btw, Congratulations @joshua_zhou731 @ema_miao & team @Loqua 🚀✌️
Paste
Dictation tools always mangle product names and internal jargon, which is half of what I'd be dictating. Is there a way to teach Loqua custom words, or does it pick them up from whatever's on screen? That part would decide it for me.
Loqua
@protsenkoalexandra Totally get that, product names, acronyms, and internal jargon are exactly where generic dictation tends to get frustrating.
Loqua supports a personal dictionary, so you can add names and domain-specific terms you use a lot instead of hoping the model guesses them correctly every time. Screen context can also help when a term is visible, but we don’t rely on that alone.
If that’s the deciding factor for you, I’d definitely stress-test it with your real vocabulary, that’s exactly the kind of use case we want to get right.
The hands free angle feels super practical. Did that become a bigger use case after you guys started building it?
Loqua
@nathan_holdstein36 Definitely. We started more from the “less typing, less context switching” angle, but once we began using it day to day, the hands-free part became much more obvious.
There are a surprising number of moments where your brain is free but your hands aren’t, and voice suddenly feels less like a convenience and more like the natural interface.
I hate having to stop what I’m doing just to open another app. Can Loqua handle most of these little tasks without making me switch around?
Loqua
@sathesharayu12 That’s exactly the kind of friction we’re trying to reduce. On Mac, Loqua can already handle things like opening apps or webpages, creating reminders and calendar events, searching Maps, taking screenshots, and controlling things like Wi-Fi or Bluetooth.
It won’t handle every desktop task yet, but the goal is that more of those tiny “stop what I’m doing and click around” moments can just become a quick voice command.
Great Product! But I have a question does Capture to Ask hold up on all screens like a spreadsheet or code editor, or is it mainly reliable on simpler layouts like the calendar and chat view shown here?
Loqua
@sidraarifali It’s not limited to simple layouts, we’ve designed Capture to Ask for things like spreadsheets, dashboards, code editors, docs, and other dense screens too.
That said, the more complex the screen, the more important it is to capture the relevant area rather than everything at once. For a spreadsheet or code editor, that usually gives Loqua much cleaner context and a better answer.
So yes, those are definitely target use cases for us, not just calendar/chat-style screens.
Buffup.AI
most voice tools fail badly when dictating terminal commands or nested JSON structures. am curious if your underlying model treats code syntax natively or if i still have to manually edit brackets later.
Loqua
@sansa_grey Great question, for exact terminal commands or heavily nested JSON, I wouldn’t claim perfect syntax-level accuracy yet. Those cases are much less forgiving than normal prose, since one bracket or character can matter.
Loqua is already useful around coding workflows and technical explanations, but for dense structured code we’d still recommend reviewing the output. Improving this is definitely an area we care about.
Loqua
@sansa_grey That is the way we are aiming to, a truly hands free coding experience. Try variable names, terms, complex logic together with CC & Codex, it reads coding context so all the dictation feels much better. We will keep improving the model for better performance!