Lispr

Hold a key, speak, and Lispr writes it anywhere

Mac

Productivity

Artificial Intelligence

Visit WebsiteSee on Product Hunt

hosted whisper to keep it 3.67mb is a sharp trade — but latency's now a network function. the seam is a flaky link: a partial transcript landing silently is the one failure worse than a keyboard.

How does the translation work mid-sentence without it getting confused, especially with technical terms or names that don't translate cleanly?

Nice one. I added voice input to my own app recently and the hard part wasn't transcription at all, it was getting the mic to behave the same on every device. Does hold to talk work in any text field system wide, or is it per app? Congrats on the launch, hope it goes well today!

This is a very neat idea. Love the concept. For clarity on Windows, it only uses the right CTRL key right? Which I don't think I ever use for any other purpose so makes a lot of sense!

Just fyi, Chrome is flagging a security risk on download. I wonder if it would be better hosting downloads from a common repository rather than your own site? Although this is obviously an issue that will disappear over time.

This is the right shape for dictation tools: the trust boundary matters as much as the model. A visible hold-to-talk state, no account, and clear audio handling make it much easier to use in client notes, specs, and prompts without second-guessing the capture path.

Just downloaded and I'm using LISPR to write this message. Seems like a great tool. All the best with the launch.

the no-account, stateless-relay answer to the audit question above was refreshingly honest, more teams would just say "we don't log anything" and leave it there. that raises a question about the vocabulary feature though - if it learns client names and jargon from my dictations over time, that's a profile of sorts even without an account. is that vocabulary list stored purely on-device, or does it live server-side somewhere tied to an install id, since "no persistent identity" and "the app remembers your jargon across sessions" seem like they need to be reconciled somehow

Nice one love it! How to you plan to make money ? and the trigger key isn't working on my mac i tried multiple of them. maybe add the possibility to add custom one ?

Congrats on the launch!
just wanted to understand how is @Lispr different from Wispr flow?

Really interesting. Since Lispr works system wide, have you found any unexpected workflows where users save the most time?

I've been using Lispr on my mac almost every day, and it's honestly become one of those apps I keep coming back to. I work in marketing and also do mentoring, so I spend a huge chunk of my day writing feedback, docs, slack messages, briefs etc. It doesn't magically write everything for me, but it cuts the time I spend writing by a lot. Funny enough, I used Lispr to write this review too 😄

If your job involves writing a lot, I'd definitely recommend giving it a try.

Congrats for you! Wondering how it handles contexts like coding tools versus marketing or social writing, since those are pretty different voice-to-text use cases.

I do marketing for Lispr. But I'm writing this as its heaviest user, because the tool changed how I work before it ever became my job to talk about it.

The biggest surprise was my AI workflow. When I typed prompts, I kept them short and got generic answers back. Speaking, I give the model two minutes of context, examples, and constraints without thinking about my fingers, and the answers improved to the point where colleagues asked what I changed.

The second thing: I live in Poland and run my life in three languages. Ukrainian with family, English at work, Polish everywhere else. Switching the output language is one extra key held at release, so I think in Ukrainian and the message lands in English. Of everything in the app this is what I'd pay for.

Ask me anything about how we use it day to day. The founders are in this thread too.

Hey Product Hunt! CTO here. I wrote most of Lispr's code, so I'll take the technical questions today.

The problem that started this: every dictation flow we tried did the same thing. Record a file, upload it, wait for the transcript. That round trip takes 1.5 to 2.5 seconds, and at that speed you stop trusting the tool and go back to typing.

So we built Lispr around one idea: the network work should happen while you speak, not after. The moment you press the key, we pre-warm the TLS connection. While you talk, audio is compressed to Opus and streamed out in 20 ms packets. By the time you release the key, most of the work is already done. Median latency in production is 346 ms across tens of thousands of dictations. That's the difference between "waiting for a tool" and "it just types."

The app itself is native Swift and AppKit. 3.67 MB, universal binary, runs on macOS 11+, including old Intel Macs. No 2 to 3 GB model download before first use.

The line we will not cross: no account, no transcript logging, and nothing trains a model unless you explicitly opt in. Our relay doesn't store your audio. We built it this way because we dictate our own emails, docs, and code comments through it all day.

Pro tip: nothing types while you speak, and nothing gets sent for you. Text lands at your cursor when you release the key, so in a chat it sits in the input field until you press Enter yourself. Don't like how it came out? Delete it and say it again. And if you hold your translation key as well, what lands is the translation instead, in any of 32 languages.

I'll be in the comments all day. Tell me where it breaks, which app it misbehaves in, and how it runs on your Windows machine. Honest technical feedback is the most useful thing you can give us today.