Voice to Text for Frontend Developers
You spend your days building interfaces, not writing documentation. But those component prop descriptions, accessibility alt texts, and Figma comment replies still need to happen. Blurt lets you speak them instead of type them. Hold a button, say what you need, release. Text appears wherever your cursor is — in VS Code, Figma, Storybook, anywhere. Your hands stay on the keyboard building. Your voice handles the words around your code.
The Typing Problem
Documenting component props that nobody ever documents
Your design system has 47 components and exactly 3 have proper prop documentation. You know you should write JSDoc comments explaining what each prop does and what values it accepts. But after wrestling with CSS for three hours, typing out 'Controls the horizontal alignment of child elements' feels exhausting. So you don't. Next month, you're reading your own code wondering what 'variant' actually does.
Writing meaningful alt text for images
The accessibility audit flagged 23 images without alt text. You know alt text matters. You want to write something better than 'image' or 'icon.' But describing each image in words — 'A person using a laptop while sitting at a wooden desk in a sunlit office' — takes 30 seconds of typing per image. Multiply by 23. Your fingers hurt just thinking about it.
Responding to design feedback in Figma
The designer left a comment asking why the button padding looks different from the mockup. You know exactly why — the design system uses 8px base units and the mockup had 7px which would break the spacing grid. Explaining that out loud takes 10 seconds. Typing it takes a minute. You've got 12 more comments to address before the review meeting in an hour.
CSS comments explaining why you did that weird thing
You just wrote a CSS hack to fix a Safari-specific flexbox bug. Future-you will wonder why there's a random transform: translateZ(0) in there. But typing 'Safari has a rendering bug where flex children don't respect percentage heights inside a grid container, this forces GPU acceleration' feels like writing a blog post. So you leave no comment. The mystery lives on.
Your wrists are not going to survive another redesign
Component library migration. Design system v3. Yet another pixel-perfect implementation. Each project means thousands of lines of JSX, CSS, and documentation. Your mechanical keyboard sounds great but your wrists feel terrible. The standing desk helped your back. Nothing is helping your hands. You're googling 'RSI prevention for programmers' at 2am.
How It Works
Blurt works in every tool frontend developers use — VS Code, Figma, Storybook, Chrome DevTools, GitHub, Slack. Anywhere you can place a cursor.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening.
Talk naturally
Describe the prop, explain the CSS choice, reply to the Figma comment. Blurt adds punctuation.
Release and done
Text appears at your cursor. No copying, no pasting, no extra clicks.
Real Scenarios
Writing JSDoc comments for component props
Your Button component has 8 props and zero documentation. Cursor above the interface, hold button, say 'variant controls the visual style. Accepts primary, secondary, or ghost. Defaults to primary.' Release. Move to the next prop. In two minutes, you've documented what would have taken ten minutes to type. The component is finally usable by someone other than you.
Adding alt text during accessibility audits
The audit report is open. 23 images need descriptions. Find the first image, hold button: 'A customer service representative wearing a headset smiles while typing on a keyboard.' Release. Next image. You're describing pictures as fast as you can see them. What felt like an hour of tedious typing becomes 15 minutes of talking.
Replying to Figma design review comments
The design review has 14 comments waiting for your response. Click the first comment, hold button: 'Good catch. The border radius differs because we use 4px for small interactive elements and 8px for containers. I matched the existing pattern from the card component. Happy to adjust if you want visual consistency here.' Release. Click next comment. The review that felt like homework becomes a conversation.
Documenting CSS workarounds and browser hacks
You just spent 45 minutes fixing a Chrome-specific grid bug. The fix looks weird but it works. Cursor above the hacky CSS, hold button: 'Chrome 120 has a subpixel rendering issue with gap in nested grids. This explicit height prevents the one-pixel gap at certain viewport widths.' Release. Future-you just got saved hours of debugging.
Writing Storybook story descriptions
Your component library needs documentation for each story. Click into the description field, hold button: 'This story demonstrates the loading state of the DataTable component. The skeleton rows match the expected row height to prevent layout shift when data loads. Pass an array of column widths to customize the skeleton appearance.' Done. Each story gets real documentation instead of 'Default story.'
Explaining responsive breakpoint decisions
The PR has a question about why you chose 768px instead of 800px for the tablet breakpoint. Hold button: 'We use 768px because it aligns with iPad portrait width. Mobile below 768, tablet 768 to 1024, desktop above 1024. Matching device boundaries prevents awkward in-between states.' Posted in 8 seconds instead of typing for a minute.
Why frontend developers choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone icon or enable via Settings |
| Speed | Text appears in under 500ms | 2-3 second delay feels slow in fast workflows |
| Technical terms | Handles JSX, CSS properties, component names | Often mangles technical vocabulary |
| Punctuation | Adds punctuation and capitalization automatically | Requires saying 'period' and 'comma' out loud |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt