Gave AI control of my Google Pixel 10 to fix my keyboard app
It's stupidly hard to get right, and impossible to really build out alone.
Try it out @ yaps.ai :)
It's stupidly hard to get right, and impossible to really build out alone.
Try it out @ yaps.ai :)
Hey everyone, I'm u/rich_awo, a founding moderator of r/YapsAI.
This is our new home for everything Yaps - the voice layer for your Mac and the Android keyboard that types as fast as you talk. If you're using Yaps for dictation, notes, read-aloud, or you're just curious about voice-first computing that runs entirely on-device, you're in the right place.
Quick context on why I built it: I was frustrated with voice dictation that either shipped my audio to a server somewhere, it had bad UX, or it just felt slower than just typing. Yaps runs the whole pipeline locally! Transcription, cleanup, read-aloud - so your voice never leaves your device, and it's fast enough that you forget you're not typing.
Both free to try at yaps.ai.
What to post
Anything you think people here would find useful - workflows, demos, tips, bug reports, feature requests, "I tried this and it broke" posts, "I tried this and it changed how I work" posts. Comparisons with other tools, questions for me or for the community, complaints, ideas. The only thing I'll ask is that we keep it on topic - no engagement bait or low-effort spam.
Community vibe
Friendly, honest, and direct. I'd love to know when something doesn't work so I can actually get it fixed. We're early, and every report shapes where the product goes next. That said, be respectful, to the mod(s) and others.
How to get started
Thanks for being part of the very first wave. Let's build something useful here.
Richard
https://reddit.com/link/1te1mua/video/a1gptbh1vb1h1/player
I gave Codex complete control of my device for end-to-end testing, and it worked great!
Essentially I built an offline AI dictation app but I wanted to maintain a fully functional keyboard that was as robust as Gboard. I quickly realized most people don't do this because building good keyboard is crazy difficult. Anyway, quickly became clear that getting this right was going to make or break the app and so I got Codex to figure out how to test the whole thing e2e, so that it could test tap typing and glide typing for itself.
Tldr: It's worked brilliantly!
Now I can spend more time focussed on the Yaps desktop app (which Codex does well testing too), while it works through the different languages to get down the latency and word error rate. It's optimising everything directly on my device, tap typing, glide typing, autocorrect, dictionary gaps, bigrams, trigrams, etc... It even finds helpful resources for expanding vocabulary and understanding how people talk common phrases, all of that kind of stuff.
This stuff never ceases to amaze me.
I just launched my first solo app (Yaps AI) in a very long time and initially I was completely focussed on making sure everything looks pretty and so I had this really nice dark theme that blended really well, a clear logo and kept colours really on brand.
Fast forward 1 week, I've got some users, its growing, but the numbers aren't anything crazy. I watched a video on App store optimisation and realised I had probably prioritised the wrong things.
All obvious stuff I guess in hindsight but a lesson learnt nevertheless. 😅
Also in case it's helpful, raw claude for the before, and claude.ai/design for the new screenshots.
Before:
After: