Voice to Text for Xcode
You just finished implementing a complex SwiftUI view. Now you need to explain what it does, write the commit message, or add a note about that workaround for the iOS 16 bug. Your brain is still in Swift mode. Switching to typing prose feels like changing gears with a stuck clutch. Blurt lets you speak your documentation, comments, and commit messages directly into Xcode. Hold a button, say what you need, release. Text appears at your cursor. Your hands stay in position. Your flow stays intact. Works everywhere in Xcode — source files, SwiftUI previews, console, source control, anywhere you can type.
The Typing Problem
Commit messages interrupt your coding session
You just spent three hours implementing the new payment flow. The code works. Tests pass. Now Xcode wants a commit message. Your brain is still thinking about edge cases and error handling, not summarizing what you built. You stare at the source control panel trying to context switch. You end up writing 'Updated PaymentView' because typing a real description feels exhausting.
Code comments that explain the why never get written
That workaround for the iOS 16 keyboard bug deserves an explanation. You know exactly why this weird code exists. But after fighting with UIKit for an hour, typing out a paragraph explaining the fix is the last thing you want to do. Future you will spend another hour figuring out why this code looks so strange. The comment never gets written because the effort outweighs the discipline.
SwiftUI preview notes you keep forgetting to add
Your preview provider has three different device configurations and two dark mode variants. You understand why right now. In a month, you won't remember which preview shows the error state versus the empty state. A quick comment above each preview would save future confusion. But you're already moving to the next view. The notes stay in your head, not in the code.
Debugging notes vanish when you close the console
You just spent 45 minutes tracking down a memory leak. The sequence of events that causes it is fresh in your mind. You should document this somewhere. But the bug is fixed, there's a feature waiting, and typing out your debugging journey sounds tedious. Next time this happens, you'll debug from scratch. The tribal knowledge disappears when you close the console window.
Documentation markup that feels like overhead
You wrote a public API. It needs documentation comments with parameter descriptions, return values, and usage examples. You could explain it all verbally in 30 seconds. But typing out the triple-slash markup for each parameter takes ten minutes. The documentation gets skipped. Quick Help stays empty. Other developers guess at what your function does.
How It Works
Blurt works in every context within Xcode — your Swift files, SwiftUI previews, the debug console, source control panel, and anywhere else you can place a cursor.
Hold your hotkey
Press your chosen shortcut anywhere in Xcode. A small indicator shows Blurt is listening.
Talk naturally
Say your commit message, code comment, or documentation. Blurt handles punctuation and capitalization.
Release and done
Text appears at your cursor in Xcode. No extra steps. Keep building your app.
Real Scenarios
Speaking commit messages in source control
You've staged your changes in Xcode's source control navigator. Instead of typing, hold your hotkey and speak: 'Refactor PaymentManager to use async/await. Replace completion handlers with structured concurrency. Add unit tests for network timeout scenarios. Update documentation for new API.' A detailed commit message in 8 seconds instead of 60. Your hands never left the keyboard. Commit, push, and move on.
Dictating documentation comments for Quick Help
You wrote a utility function that other developers will use. Position your cursor above it, hold your hotkey: 'Validates the user session token against the server. Returns true if the token is valid and not expired. Throws an authentication error if the token is malformed or revoked. Call this before any authenticated API request.' Your function now has documentation that appears in Quick Help. 10 seconds instead of 3 minutes of typing markup.
Adding SwiftUI preview annotations
Your preview provider shows the view in different states. Hold button above each preview: 'This preview shows the payment form with a valid credit card entered and the submit button enabled.' Now when you scroll through previews, you know exactly what each one demonstrates. Preview documentation written while the context is fresh.
Explaining workarounds and edge cases
You just implemented a workaround for a UIKit bug that only manifests on iPad mini in landscape mode. Hold your hotkey above the suspicious code: 'This force layout pass works around a UIKit bug where the safe area insets are incorrect on iPad mini during rotation. See Apple radar FB12345678. Remove this when we drop iOS 16 support.' The context is captured before you forget it.
Documenting debugging sessions in code
You finally understand why the memory graph shows a retain cycle. Before fixing it, hold button and add a comment: 'The capture list must use weak self here because the completion handler is stored in the URLSession delegate which outlives the view controller lifecycle. Without weak self, the view controller is retained until the session is invalidated.' Future debuggers will understand immediately.
Console notes during investigation
You're in the debug console testing expressions to understand a crash. You found the sequence that reproduces it. Before you forget, paste into a comment file: 'The crash occurs when calling refreshToken while a network request is in flight. The response handler tries to access the token manager after it has been deallocated. Reproduce by triggering a refresh immediately after logout.' Your debugging journey is preserved.
Inline notes while building views
You're constructing a complex SwiftUI view hierarchy. Hold button mid-flow: 'The ZStack ordering here puts the loading indicator above the content but below the navigation bar overlay. Changing this order breaks the blur effect on the profile image.' Context captured in 5 seconds. Keep building without losing momentum.
Why Xcode developers choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Double-tap Fn or menu bar click |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription starts |
| Swift vocabulary | Handles SwiftUI terms accurately | Often misinterprets async, @State, ObservableObject |
| Reliability | Works consistently in all Xcode panels | Sometimes fails in console or source control |
| Price | $10/month or $99/year | Free (built into macOS) |
| Free tier | First 1,000 words free | Unlimited but unreliable |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt