Yaps Reviews and Details

Questions & Answers

1. Who are some of the biggest customers of Yaps?

   B2C solution, so the user base is broad.

2. What makes Yaps unique?

   It's a cross-platform dictation app that works entirely offline. The Android application is a full-blown custom keyboard that incorporates speech-to-text within a keyboard comparable to Gboard that gives it exceptional UX. While the desktop application comes with a full markdown-backed vault system, the tool also supports text-to-speech across the board.

3. Why should a person choose Yaps over its competitors?

   Yaps is built for people who want voice input to feel native, private, and instant. Unlike many dictation tools, it does not force you into a separate app, floating overlay, or cloud transcription flow. On Android, it is a real keyboard with glide typing, autocorrect, suggestions, and offline dictation built in. On desktop, it works as a quiet system-level voice layer for dictation, read-aloud, notes, and local workflows.

4. How would you describe the primary audience of Yaps?

   Yaps is for knowledge workers, builders, writers, students, founders, and privacy-conscious users who think faster than they type. It especially fits people who write a lot across email, docs, chat, notes, and code, and want dictation without giving up their existing workflow.

5. What's the story behind Yaps?

   Yaps started from a simple frustration: typing was too slow, existing dictation felt clumsy, and too many voice tools depended on the cloud or forced awkward UI changes. The project evolved into a “voice layer” for your devices: hold a key or tap a button, speak naturally, and have polished text appear where you already are. The guiding idea is that Yaps should feel less like a tool and more like a quiet friend that shows up when needed, helps, then gets out of the way. And that's the same rationale behind being able to read out any text on your screen or jotting down quick notes, and the creation of a second brain behind the scenes.

6. Which are the primary technologies used for building Yaps?

   • Desktop app: Tauri 2, Rust, React 19, TypeScript, Vite, Tailwind CSS, Bun
   • Android app: Kotlin, Jetpack Compose, Android IME APIs
   • Shared core: Rust with UniFFI bindings
   • Models: The speech-to-text, text-to-speech, and cleanup are powered by fine-tuned local models.
   • Backend: Cloudflare Workers, Hono, D1, KV, Stripe, Google Play Billing, JWT auth
   • Storage: Local settings plus a file-backed Markdown vault with note history and automation surfaces