Dictating into Xcode with Parakeety

Xcode's prose surfaces, in rough order of payback:

• Doc comments. The /// triple-slash blocks above public API. Type the slashes; dictate the description, the parameter explanations and the discussion. Xcode renders them inline in Quick Help and in the Documentation Compiler output.
• Source Control commit messages. The Source Control, Commit sheet that opens before each commit. The single best place to dictate; almost nobody types commit messages at full information density.
• Markdown files. READMEs, internal docs, DocC markdown articles, release notes drafts. Whole files of prose; the highest-volume dictation surface in most repos.
• Scheme description and pre-action notes. The "what does this scheme do" notes that you forget to write at the time and need six months later.
• Breakpoint conditions and action logs. The condition you type into a breakpoint, the log message it prints. Often a sentence; dictation suits.
• Issue Navigator notes and TODOs. Inline annotations you leave inside source files for yourself or for the next person.
• AI assistant chat. Whichever AI tooling you have plugged into Xcode (the built-in predictive completion has limits; many devs run Copilot for Xcode, an MCP-based assistant, or similar). Dictate the prompts.

You finish a Swift package that wraps an internal API. Before publishing, you write the public-API documentation. Typing, most engineers settle for one-sentence doc comments. Dictated, you naturally write the version that actually answers the questions a user of the API will have:

"Returns a stream of decoded events from the upstream session. The session is opened lazily on the first subscription and closed when the last subscriber cancels. Backpressure is handled by the underlying URLSession, which means slow consumers can cause server-side keepalive pings to be dropped; if your consumer needs at-least-once guarantees, buffer the stream before subscribing. Cancellation propagates upstream and tears down the session within one read cycle. Throws if the initial handshake fails; never throws after the first event has been delivered."

About thirty seconds dictated. Typed, the same content is over two minutes, which is why most projects never get it. The Quick Help readout in Xcode is consequently useful to anyone calling the API.

• Type the comment delimiters first. /// for line doc comments, /** */ for block doc comments. Xcode will help you with the parameter scaffold; dictate into each section as it lights up.
• DocC markdown is dictation-friendly. The .docc bundles with .md article files are pure prose; whole-file dictation works well.
• Source Control sheet does not auto-focus the message field every time. Click into the message area before holding the key; otherwise the words may land in the diff sidebar instead.
• Section key does not clash with Xcode shortcuts. Xcode's shortcuts lean on Cmd, Shift and Option combinations; the default Parakeety key (§) is free.
• Backtick in code and DocC. If you type § or backtick yourself, Parakeety reserves it while running. Dev mode hands it back: a tap types the character, a hold dictates.
• Multi-window layouts work. Parakeety follows the cursor across monitors and across the Editor / Assistant / Canvas split. Click into the surface you want, then dictate.
• Apple's DocC documentation. Apple's DocC documentation explains the markup syntax for doc comments and article files; those are the Xcode surfaces where dictation pays back most.

Apple-platform projects often contain references that ought not leave the device: WWDC-seeded feature names, internal codenames for in-development apps, customer-facing strings in apps that have not yet launched. Parakeety's audio path stops at the Mac; those names appear in the transcript but never in any audio file on someone else's server. The text leg of an AI-assistant integration (if you have one configured) is governed separately by that tool's settings and your team's policy.

The wider engineering perspective is in Parakeety for engineers and developers; the Cursor-specific workflow companion piece is Dictating into Cursor with Parakeety; and on-device speech-to-text on Apple Silicon covers why the audio path can stop at the Mac at all.

Parakeety is a Mac menu-bar app. Hold the section key, talk, release; your words paste at the cursor in whichever app you were typing into, including every input surface inside Xcode. Audio never leaves the machine. There is a free 7-day trial with no card required. After that it is $30 once.

Try Parakeety free →