Use case · messaging
Voice typing in
Messages.
Texting is the fastest conversation you have, which is exactly why the keyboard is where it jams. Say the sentence, it lands whole about two seconds later, send. Nothing to copy across from anywhere else.
Three steps, once
1. Install.
Four steps, once, on Android or Windows. No account and no card for the free plan.
2. Open Messages.
Open the thread and tap into the message box, exactly as if you were about to type.
3. Press and talk.
Hold the key on Windows, tap the bubble on Android, then talk like a person. Whole sentences land at the cursor about two seconds after you pause.
The beat matters most here. Sentences land whole, so you are never watching half a message rewrite itself while you are still talking, and you never say comma out loud.
Private in Messages, by architecture.
Fastspoken types through the keyboard layer on Android and at the cursor on Windows, so Messages receives ordinary typed characters, exactly as if your hands had done it. On the free plan speech becomes text on the machine in front of you: 0 words of what you said sent to a server, no account, and it still works with the wifi off. The typing is free because it runs on your machine, which is the same reason nothing you say leaves it. See the whole machine.
No server in the loop on the free plan.
Questions about Messages
Does it work with RCS and SMS?
Yes. Fastspoken types through the keyboard layer, so it does not care what kind of message the app sends afterwards.
Can I fix a word before sending?
Yes, it is ordinary typed text. Edit it like anything else, and teach your dictionary a name or a spelling once so it lands right next time.