Your code base knows shadcn, tRPC, Prisma, Redis, and Vercel. Dictation should too. Test with your own phrases—if you edit less, you ship more.
Example outputs. Use the copy blocks below to try your own phrases.
Where it fits
- Explaining a change at the top of a file.
- Writing a clear commit message without losing flow.
- Filing a ticket with real steps and context.
Setup in one minute
- Install Voice Type from the Mac App Store.
- Pick a hotkey that does not collide with your editor.
- Tap the hotkey, talk, and tap again to stop.
Works in VS Code, Xcode, Cursor, JetBrains IDEs, and your browser. The app types wherever the cursor lives.
Try a real phrase
Copy one of these and read it out
Shipped a Next.js app with shadcn ui, tRPC, and Zustand. Deployed on Vercel. Used pnpm and Homebrew. Added memcached as a sidecar.
Upgrade plan: migrate to Postgres with Prisma, add Redis for queues, keep Nginx in front of Node. Switch to TypeScript strict.
Set up GitHub Actions, run Vitest, then publish to npm. Add a changelog and semantic release.
Tip: copy a line, place your cursor in a text field, and read it out. Then try the same line with Apple Dictation. Compare the raw text before any rewrite.
Dictate the same line with the built-in tool and with Voice Type. Watch library names, service names, and edit time. Use your own snippet if you prefer—product names are a great test.
Why technical terms stick
Trim low rumble. Normalise loudness. Cut silence. Feed the recogniser a clear signal. Result: product names and short codes survive the trip.
Room noise and uneven levels blur word boundaries. Result: names and acronyms fall apart, edits pile up.
Voice Type conditions the input before recognition, so technical nouns stay accurate.
Privacy and speed
Audio stays on your Mac. The last chunk finalises quickly, even on older M1 machines, so long PR descriptions and tickets still feel responsive.