DEV.to uses a markdown-friendly editor that accepts system dictation the same way as any large text area in the browser.
Why voice input pairs well with DEV.to
Most people who work in DEV.to type all day. The thinking is fast, but the fingers get in the way. Voice input flips that balance. You speak the raw thought, the words land in the field, and you spend your energy on the edit rather than on the mechanics of typing. For developers, indie hackers, and open source contributors, that shift means articles, discussion posts, and comments land in half the time, and the tone stays warmer because the wording comes from real speech rather than a keyboard performance. Zahvox is built for exactly this loop and works next to DEV.to without replacing it.
Turn on system dictation before you open the app
On macOS press the Fn key twice inside the target field to trigger dictation.
On Windows press the Windows key plus H to open the voice typing bar.
On ChromeOS enable Dictation in Settings then Accessibility then Keyboard and input.
On iPhone or iPad tap the microphone on the keyboard and speak into any input field.
On Android open the Gboard settings, enable Voice typing, then tap the mic key.
Give the browser or app microphone permission the first time you try, then keep the permission set to Allow.
Set up DEV.to for a clean dictation session
Open DEV.to in a stable window, dismiss any modal that would steal focus, and click into the exact field you want to dictate into. Voice input follows the caret, so the field must be selected before you speak. Close side panels that autofocus their own search boxes, mute noisy tabs, and keep only one browser window active. If DEV.to supports keyboard shortcuts to open a new draft, use them so the caret lands in the body without a stray click.
Technical article vs discussion vs comment
Technical articles carry the story with code blocks added on the edit pass. Discussions stay concise and question-driven. Comments hold a single point. Speak in each shape and DEV.to threads read well.
Speak in patterns that DEV.to rewards
Say punctuation out loud so the sentence lands finished, not raw.
Keep one thought per sentence and one topic per paragraph.
Use short numbered lists for anything you would later scan quickly.
Repeat the person or project name once in every paragraph so search picks it up.
End each paragraph with the next step so the reader knows what to do.
Use Zahvox for the careful pass
System dictation is fine for the raw capture. For anything that reaches a customer, a teammate, or a public surface, take one more pass in Zahvox. Paste the raw text, tighten the wording, remove filler, and copy it back into DEV.to. That extra minute is why the writing sounds like a person who thought about it, not a person who spoke into a phone in traffic. Try the free Zahvox tool at /tool and keep it open in a pinned tab.
Fix the four things that break dictation
No sound reaches the app: check the microphone in the operating system sound panel first.
Wrong microphone selected: pick the same input in the OS and in the browser site settings.
Permission denied: open browser site settings, set Microphone to Allow, and reload the tab.
Words appear in the wrong field: click back into the target field before you speak again.
Punctuation missing: say the punctuation out loud instead of relying on smart insertion.
Habits that keep the workflow durable
Keep a short glossary of names, product terms, and abbreviations that dictation tends to miss. Add them to the operating system dictation dictionary if the platform allows it. Save a small library of intros, sign-offs, and boilerplate as text snippets so voice input only has to fill in the specific detail. Do a five minute review at the end of each DEV.to session to catch anything the ear missed. Over a week those small habits are the difference between voice input that feels like a toy and voice input that shortens the workday.
