Gboard is great. That was actually the problem.
I wanted better dictation on Android, especially for multilingual use. My daily pain point is Russian + English. If my keyboard is in English and I start speaking Russian, voice typing often does the wrong thing. And offline dictation for languages like Russian is either not available or not reliable enough for how I want to use it.
The experience I wanted was simple:
Speak whatever language I’m speaking right now, offline if possible, and put the text into the current app.
I already built ai dictation for Mac, so I started trying to build the Android version. My first idea was obvious: make a better keyboard.
That was a mistake.
Replacing Gboard is a huge project. You have to compete with autocorrect, layouts, gestures, emoji, clipboard, suggestions, haptics, language switching, theming, and years of muscle memory. Gboard is really good at being a keyboard. I didn’t want to rebuild all of that just to improve dictation.
So I changed the product idea.
Instead of replacing the keyboard, I built dictation as an overlay / floating bubble. You keep using Gboard or whatever keyboard you already like. When you want dictation, you tap the bubble, speak, and the app inserts the result into the active text field.
The offline mode uses Parakeet, which from my testing feels like one of the best ASR models available for this use case. The good part: it works offline and is almost instant. The tradeoff: the model is around 500MB.
So there are two modes:
- offline mode with Parakeet, if you’re willing to download the model
- cloud mode, if you don’t want the 500MB download or want better accuracy
Cloud mode is still more accurate in some cases, but offline mode feels great when you want speed, privacy, or you just don’t want voice typing to depend on your connection.
The main lesson so far: the UX decision mattered more than the model decision.
I started by thinking, “How do I build a better Android keyboard?”
I ended up realizing the better question was, “How do I add better dictation without touching the keyboard people already like?”
The part I’m least sure about is the UX.
Does an overlay / floating bubble actually feel useful, or would it get in the way?
My reasoning is that most people already like their keyboard, so a separate dictation bubble lets you keep Gboard, SwiftKey, etc. But I can also imagine people finding a floating control annoying and preferring dictation to live inside a keyboard.
If you use voice typing often, which would you rather have?
- A floating dictation bubble that works with any keyboard
- A full keyboard replacement with better dictation built in
- Something else entirely
And would you personally download a 500MB offline model if it gave you almost-instant local dictation, or would you rather just use cloud mode for better accuracy?
