Skip to content
For Developers

Code faster, type less

Your hands belong on the keyboard writing code - not typing commit messages, Slack replies, and documentation. Yaps handles the prose so you can stay in flow. Entirely on your Mac, no data leaves your machine.

See how it works
VS Code
auth.tsTypeScript
Listening…Hold Fn to dictate
0+

Words per minute

0

Network requests

0%

On-device processing

<50ms

Transcription latency

Sound familiar? vs The Yaps way

Same sentence. Watch the difference.

Typing

~40 WPM

0%

Dictation

~150 WPM

0%

Tools for the engineering workflow

Yaps fits into how you already work - not the other way around.

01

Dictate Anywhere on macOS

Yaps works in any text field - your IDE, terminal, Slack, Notion, GitHub, Linear, or email. Activate with a hotkey, speak, and text appears where your cursor is.

02

Hands Stay on the Keyboard

Trigger dictation with a keyboard shortcut, speak your message, and you are back to coding. No mouse, no app switching, no lost context.

03

Private by Default

Your dictated code comments, internal Slack messages, and proprietary documentation never leave your Mac. Zero network traffic for core features.

04

Voice Notes for Ideas

Debugging and hit an insight? Record a voice note. It is transcribed, timestamped, and searchable for when you circle back to the problem.

05

Searchable History

Every dictation and voice note is saved locally. Search by keyword to find that architecture decision you spoke about last week.

06

Works Offline

On a plane, at a conference with bad Wi-Fi, or in a secure facility. Yaps needs nothing but your Mac and your voice.

Real developer workflows

How engineers actually use Yaps day to day.

01

Commit Messages

Describe your changes out loud right after writing the code. Dictated commit messages tend to be more descriptive because speaking is faster than typing.

Fix race condition in websocket reconnection logic - the previous implementation didn't account for concurrent close events

02

Slack & PR Descriptions

Reply to code review threads, write PR descriptions, and respond to teammates - all by voice, without leaving your editor.

Good catch on the null check. I refactored the handler to use optional chaining instead - see the updated diff

03

Documentation

Dictate README sections, API documentation, and architecture decision records. Getting words out fast means docs actually get written.

This module handles authentication token refresh. It uses a sliding window approach to prevent concurrent refresh requests...

04

Code Comments

Add inline comments and docstrings by voice. Explain the why behind your code while the reasoning is still fresh in your mind.

We use a bloom filter here instead of a hash set because the dataset exceeds available memory at scale

05

Standup Notes

Dictate your standup update before the meeting. Speak freely about what you shipped, what blocked you, and what is next.

06

Bug Reports & Tickets

Describe bugs and write tickets by voice. Walk through reproduction steps out loud - the natural flow often catches details you would skip while typing.

Steps to reproduce: open the dashboard, click the settings gear icon, toggle dark mode twice rapidly - the sidebar collapses and doesn't recover

Hear from people like you.

I started using Yaps for commit messages and Slack replies. Now I dictate everything that is not actual code - PR descriptions, docs, code review comments, even my standup notes. It is genuinely faster, and my wrists stopped hurting after the first week. The fact that nothing leaves my machine matters a lot when you work on proprietary codebases.

MC

Marcus Chen

Senior Software Engineer

Ready to ship faster?

Keep your hands on the keyboard for code. Let your voice handle everything else.

Requires macOS 13.0+ (Apple Silicon recommended)