Voice to Text for iOS Developers

You're already on a Mac building for Apple platforms. Blurt fits right into your workflow. Hold a button, speak your code comments, App Store descriptions, or TestFlight notes, release. Text appears wherever your cursor is — in Xcode, App Store Connect, Slack, GitHub, anywhere. No context switching. No flow interruption. Your hands stay on the keyboard where they belong.

Free to start Works in Xcode, Slack, GitHub No configuration needed

Download Blurt Free

The Typing Problem

Writing App Store descriptions after weeks of building

You've spent three weeks perfecting your app. Now App Store Connect wants a compelling description, promotional text, and keyword-stuffed subtitles. Your brain is wired for Swift syntax, not marketing copy. You stare at the blank text field, knowing this description will make or break your downloads. The words just won't come.

Documenting SwiftUI views you'll forget in a month

You just built a clever custom ViewModifier that handles dark mode, dynamic type, and accessibility in one elegant chain. Future-you will have no idea why it works. You should write a comment explaining the magic. But after hours of wrestling with preview crashes and modifier order, the thought of typing more makes you skip it and move on.

TestFlight release notes nobody wants to write

Beta testers are waiting. You've fixed the crash and added that feature they requested. Now you need to explain what changed in TestFlight. You know what you did — you could explain it in 20 seconds out loud — but typing release notes for the fifth time this week feels like punishment. So you write 'Bug fixes and improvements' again.

Explaining your code in PR descriptions for team review

The feature branch is ready. Your team needs context on why you refactored the network layer and what trade-offs you made. You could type a detailed explanation, but Xcode just hung again during indexing and you've lost patience for more typing. The PR goes up with a two-word description. Code review becomes a guessing game.

Your wrists ache from Xcode's keyboard-heavy workflow

Between Command-clicking through symbol definitions, typing code, responding in Slack, writing JIRA updates, and crafting App Store copy — your hands never rest. That ergonomic keyboard helped with RSI symptoms, but you're still typing thousands of words daily. You're wondering how many years of iOS development your wrists can survive.

How It Works

Blurt works in every app iOS developers use daily — Xcode, App Store Connect, Slack, GitHub, TestFlight, and anywhere else you can type on macOS.

Hold your hotkey

Press your chosen shortcut. A small indicator shows Blurt is listening.

Talk naturally

Say your comment, release note, or App Store copy. Blurt handles punctuation.

Release and done

Text appears at your cursor. No copying, no pasting, no extra steps.

Real Scenarios

Writing App Store descriptions that actually convert

Your app is ready for submission. Instead of staring at App Store Connect trying to write marketing copy, hold your button and talk through what makes your app special: 'Track your daily water intake with beautiful widgets and smart reminders. Syncs with Apple Health. No subscription required.' Three paragraphs spoken in 30 seconds instead of 15 minutes of agonizing over word choice.

Adding documentation comments to your Swift code

You just wrote a complex async function that handles retry logic with exponential backoff. Cursor above the function, hold button, say 'Fetches user data with automatic retry on network failure. Uses exponential backoff starting at 1 second, max 3 retries. Throws NetworkError if all retries exhausted.' Documentation done in 8 seconds. Your API will actually make sense to teammates.

Writing TestFlight release notes testers will read

New build is uploading. Hold your button and explain what changed: 'Fixed the crash when opening notifications on iOS 17. Added haptic feedback to the main button. Improved VoiceOver labels throughout the settings screen.' Testers get useful context in 10 seconds instead of the dreaded 'Bug fixes' placeholder.

Explaining SwiftUI decisions in code comments

You spent an hour figuring out why GeometryReader was breaking your layout. Hold button, leave a comment for future-you: 'Using PreferenceKey here instead of GeometryReader to avoid layout thrashing. The parent view needs child sizes before the first render pass.' That debugging session won't be repeated in six months.

Quick Slack replies during Xcode indexing

Xcode is indexing again and a teammate asks about the API endpoint format. Instead of typing while waiting, hold your button and say 'The user endpoint returns JSON with a nested profile object. Check the UserResponse model in the Networking folder for the exact structure.' Reply sent in 5 seconds, hands still hovering over the keyboard for when indexing finishes.

Writing detailed PR descriptions for code review

Your refactor is ready for review. Hold and speak: 'Migrated the persistence layer from UserDefaults to SwiftData. This gives us better type safety and automatic iCloud sync. Breaking change: existing local data will need migration, handled in AppDelegate on first launch.' Reviewers know exactly what they're looking at. No back-and-forth questions.

Drafting App Store review responses

A user left a 2-star review about a bug you already fixed. Hold your button: 'Thanks for the feedback. We fixed this issue in version 2.3 released last week. Please update and let us know if the problem persists. We'd love to hear from you.' Professional response in 8 seconds, not 3 minutes of careful typing.

Why iOS developers choose Blurt over built-in dictation

	Blurt	macOS Dictation
Activation	Single hotkey, instant start	Click microphone icon or double-tap Function key
Speed	Text appears in under 500ms	2-3 second delay before transcription starts
Technical terms	Handles SwiftUI, async/await, and API terms well	Struggles with Swift keywords and framework names
Reliability	Consistent accuracy across sessions	Often fails silently or requires restart
Xcode compatibility	Works in every Xcode text field	Sometimes conflicts with Xcode's input handling

Frequently Asked Questions

Does Blurt work in Xcode and App Store Connect?

Yes. Blurt works anywhere you can type on macOS. That includes every text field in Xcode — code comments, documentation, search, even the console. It also works in App Store Connect for descriptions, release notes, and promotional text.

Can Blurt handle Swift and iOS terminology?

Blurt handles technical terms well. Words like async, await, ObservableObject, and ViewModifier transcribe correctly. Framework names like SwiftUI and UIKit work fine. For highly specific custom types, occasional edits might be needed.

Will Blurt interfere with Xcode keyboard shortcuts?

No. You choose your own hotkey during setup. Pick any combination that doesn't conflict with Xcode's shortcuts. Most developers use a modifier combo like Control-Option-Space or similar.

Can I use Blurt while on a Slack huddle or Zoom call?

Yes. Blurt captures audio through your microphone independently of call software. You can be muted on your call and still dictate text. Just make sure you're muted before talking to Blurt.

How much does Blurt cost?

Blurt offers first 1,000 words free — enough to try it properly. Pro is $10/month or $99/year for unlimited words. No credit card required for the free tier.

Is Blurt only for macOS?

Yes, Blurt is macOS only. But as an iOS developer, you're already on a Mac — it's a perfect fit. Blurt lives in your menu bar and works in every app you use for development.

Start Typing Faster Today

Free to try — no credit card required

Download Blurt