Yaps's answer

B2C solution, so the user base is broad.

Yaps's answer

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.

ForthWrite's answer:

ForthWrite learns your writing style from your actual sent mail, not a generic prompt. Every draft sounds like you wrote it because it was trained on how you actually write. It also auto-drafts replies before you open your inbox, so your email is partially handled before your day starts.

Yaps's answer

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.

ForthWrite's answer:

Most AI email tools give you a blank box and a "write for me" button. ForthWrite builds a voice profile from your sent history and gets more accurate with every draft you edit or send. Unlike ChatGPT or Gemini, it works natively inside Gmail and Outlook with no copy-paste. Unlike Lavender, it writes the draft, not just scores it.

Yaps's answer

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.

ForthWrite's answer:

Professionals who send high volumes of relationship-critical email and cannot afford to sound generic: lawyers, financial advisors, recruiters, account executives, consultants, and founders managing their own inbox.

Yaps's answer

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.

ForthWrite's answer:

Built out of frustration with AI writing tools that produce text that sounds nothing like the person sending it, and as a way to handle large amounts of daily email. The core insight was that your sent mail is the best training data you already have, and no tool was using it.

Yaps's answer

• 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

ForthWrite's answer:

Next.js, React, Supabase, Anthropic Claude, OpenAI, Stripe, Vercel, Chrome Extensions API