Take a look at my own numbers from the last three months: 167,820 words dictated! But what is the impact? An average person types around 45 words a minute and speaks around 150. So an hour of typing produces about 2,700 words, and an hour of talking produces about 9,000. Same hour, three times the output. I spend the difference on longer prompts and fuller answers to my team, and I didn't add another hour to my day to get there :)
My own numbers are the small story. Worldwide, people have run 683,838 phrases through Lispr and skipped about seven months of typing. Seven months! Counted in working hours that is 1,232 of them, one person sitting at a keyboard eight hours a day from January through to the end of July, and nobody had to be that person. Those hours went straight back into people's lives.
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 ?
Lispr
@toukoum Thanks Raphaël! On the trigger key: that's not normal, both left and right Option should work out of the box. We're checking the logs on our side right now. Can you tell me which keys you tried and your macOS version? Also check Lispr's settings menu: you can already pick a custom trigger key there, so if Option conflicts with something on your setup, switch it.
On money: the first 1,000 users got Lispr free forever, and the free tier stays for everyone with normal daily use. Down the road we'll charge heavy users, priced in line with similar tools in this space. Running costs are low, so keeping it free is not a trick.
And since you brought up money: if you have ideas on what you'd pay for, I'd love to hear them. That answer is worth more to us than the upvote.
@toukoum @konstantin_karpushin1 I just launched the app and my first impressions are really positive. It also feels very generous that you’re making it free forever for early adopters — really appreciate that.
I was just curious about one thing: since there are no accounts, how will the app recognize who was among the first 1,000 users and keep that free-forever access active over time?
Lispr
@toukoum @vitalik Thanks Vitalii, glad the first impressions held up! Good question. No accounts today, but every install carries its own install ID on the device. That's the marker we'll use: when optional accounts arrive later, early installs get linked to them and receive a forever-free badge. And to be clear, the free tier itself isn't a trial that expires: normal daily use stays free for everyone. The badge just locks the promise in for the people who trusted us first.
@toukoum @konstantin_karpushin1 Thanks for the clarification, Konstantin! That makes sense. Wishing you lots of success with the product and its continued growth — it’s especially great to see a Ukrainian product being built with such care.
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.
Lispr
@krekeltronics Thanks Patrick, you named the design principle better than we did. The trust boundary was a day-one constraint: the mic opens on key-down and closes on release, and macOS's own orange indicator confirms it, so you don't have to take our word for anything. Same reason there's no account. Fewer things to trust means fewer things to audit.
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.
Lispr
@martin_tanner Thanks, Martin! Right Ctrl is the default on Windows, but you can remap it in the settings menu. Fair point that this isn't obvious. We'll make the key options easier to find in the UI.
The download flag is a reputation warning. Chrome and Windows show it for any new executable until enough people have downloaded it, wherever it's hosted, so a common repository wouldn't dodge it. We sign every build and it passes the security checks; the warning ages out with download volume, as you guessed. Appreciate the heads-up.
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.
Lispr
@qifengzheng Sharp read, and yes, the trade is real: latency became a network function the moment we chose hosted inference. That's why the audio streams while you're still speaking (Opus, 20 ms packets) instead of uploading a file after release, and the connection is pre-warmed on key-down. By the time you release the key, most of the audio is already on the other side. The numbers we publish are production percentiles with the network included: 346 ms median, 1.25 s p99.
@konstantin_karpushin1 streaming opus packets is a smart mitigation for the happy path — the case i meant is upstream drop mid-utterance, backend transcribes what it got, cursor sees a truncated line with no failure signal. an audible cue on connection loss would close that seam.
Lispr
@qifengzheng Myroslav here, CTO at Codebridge. You named the seam correctly, thank you. And we made two releases since then.
0.94 added a beacon at the start of every transcription plus a watchdog on the transcribing state.
0.95 replaced the flat 30-second timeout with a channel-inactivity deadline. After 20 seconds of silence on the socket, the client falls over to the file-upload path with the full audio, so a mid-utterance drop gets you either the complete transcript on the second path or an error with the audio kept in History to retry. The insert fires once, on key release, from a single resolved result. A transcript arriving after that generation gets discarded rather than pasted.
Your case is a bit narrower than that, though, and we will be working towards a complete solution.
I've been using the app since the launch, and I absolutely love it. I'm using it now to write this comment.
Before I started using this app, I was using Mac dictation, and as a result, I've trained myself to say punctuation and formatting as I'm talking out loud.
I'm wondering if there's any way to do that within the app? New paragraph, for example, if I talk this out loud the way I normally do, comma, it's going to punctuate things in a rather weird way dot, dot, dot. That isn't necessarily great.
Lispr
@anthony_sanna1 Hello! Happy to hear that.
As for your question, two parts here: the technology we are using and your app settings.
Whisper infers punctuation from how you speak, mostly from pauses and where your pitch falls at the end of a clause.
Lispr has no command grammar, so "comma" and "new paragraph" get transcribed as words. However, it also has three modes that exist in Settings → Formatting. Off inserts the raw transcript and skips the formatting pass entirely. Light adds punctuation, paragraphs and lists without deleting anything you said. Concise does all of that and also strips filler words and repeats, which means it can drop a word here and there. Speak the way you'd speak to a person and the commas and periods land on their own.
So, try out different modes, and tell us if there are still something is missing.
Uppply
Congrats on the launch!
just wanted to understand how is @Lispr different from Wispr flow?
Lispr
@malikankush Thanks! Two differences matter most.
Speed. Lispr pre-warms the connection when you press the key and streams audio while you speak, so the production median is 346 ms from release to text. Side by side, that's the difference you feel in the first minute.
Translation. Hold a second key and your words land translated, in any of 32 languages. Wispr Flow transcribes in many languages but doesn't advertise translation. The case our users love: vibe coding. Models are trained mostly on English, and English prompts burn fewer tokens. So you think out loud in Ukrainian or Spanish, hold the translation key, and a clean English prompt lands in your terminal.
Also free, no account. Full comparison, including where Wispr Flow wins: lispr.ai/blog/lispr-vs-wispr-flow
Now input method apps basically all have this function, right?
Lispr
@huafeis Fair question! Some apps have dictation built in, yes. But it's different in every app, and missing in plenty of them, so you never build the habit: each tool has its own button, its own behavior, its own quirks. Lispr is one gesture that works identically everywhere you have a cursor: hold the key, speak, release. Same muscle memory in your email, your terminal, your chat, your browser. That's when dictation stops being a feature you occasionally remember exists and becomes how you type.
And the things built-in methods don't do: hold a second key and your speech lands translated into another language (32 targets), mid-sentence language switching, and a Vocabulary that learns your brand names.