For developers

Say the intent. Keep your hands on the problem.

Turn a spoken implementation thought into a clearer development prompt, then review it before you use it.

Cloud processing · Google account and internet required · New app release pending

The short answer

Voice-to-text for developers starts with explaining the change out loud. Sonicribe can turn that explanation into a structured coding prompt with your own formatting instructions. Keep the goal, constraints and checks visible so you can review the request before handing it to a coding assistant or teammate.

Here is what that could look like

You know what needs to change. Explaining the constraints in a blank prompt can interrupt the thinking that got you there.

Prepared sample · no recording

What you say

In the upload handler, check the file size before sending it. If it is over ten megabytes, show an error. Keep the existing retry behavior.

Example to review

Update the upload handler: • Validate file size before upload. • Show an error for files over 10 MB. • Preserve the existing retry behavior.

Illustrative development prompt. Playback of a prepared example, not live audio recording or processing. Playback duration does not represent processing speed. Actual results can vary.

A workflow you control

Speak. Review. Keep going.

1
Describe the change and its boundaries.
2
Use a formatting prompt to organize the request.
3
Check names, numbers and constraints before pasting.

Examples for everyday work

From a debugging thought to a request someone can act on.

State the behavior you saw and what should stay the same. A useful prompt does not need to guess at the implementation.

Describe a reproducible bug

You can explain the failure while it is still fresh in your mind.

What you say: If I submit the search form with just spaces, it shows every result. It should ask for a search term. This happens on the results page. I have not checked the header search.
Your instruction: Use Location, Steps, Actual, Expected and Unchecked headings. Keep untested behavior separate from observations.
Example draft: Location: Results page Steps: Submit the search form containing only spaces. Actual: Every result is shown. Expected: Ask for a search term. Unchecked: Header search behavior.

Set boundaries for a refactor

Explain the cleanup and the behavior that must survive it.

What you say: Move the repeated date formatting into one helper. Keep the current timezone and empty-value behavior. Do not change the displayed text. Check a normal date and an empty value.
Your instruction: Organize this as Goal, Constraints and Checks. Do not suggest extra changes.
Example draft: Goal Extract repeated date formatting into one helper. Constraints • Preserve the current timezone. • Preserve empty-value behavior. • Keep displayed text unchanged. Checks • A normal date • An empty value

Illustrative examples. Your result depends on your recording and instructions.

Make it your own

An instruction you can reuse

Format my request as Goal, Context, Constraints and Checks. Preserve identifiers, numbers and negations. Include only what I stated; mark missing details as open questions. Do not write the implementation.

Copy this instruction and adapt it to the work in front of you.

The final choices are yours

A quick review before you use it

Read file names, identifiers and units character by character.
Check that “do not” and “keep existing” constraints survived.
Separate observed behavior from suspected causes.
Keep requested checks specific enough to verify.

The features behind this workflow

Custom instructions for the shape of a coding prompt.
Direct transcription when exact wording matters.
History search to find an earlier requirement.

Before you start

Does Sonicribe write or run my code?

This workflow helps you express a prompt. It does not demonstrate code execution, repository access or automatic implementation.

What should I review?

Check identifiers, file paths, numbers and negations. Spoken technical terms can require correction.

What makes a useful voice prompt for a coding assistant?

Say the intended change, the current behavior, what must stay the same and how you would check the result. A formatting instruction can organize those facts; you still review the technical details before using the prompt.

Can I download the new app now?

The new cloud app is planned as a separate DMG and is not available to download yet. This launch does not update existing installed copies. Release status

Your next step

Find a plan for your amount of dictation.

Eligible new accounts get a Free trial of 100 submitted-audio minutes, for up to 14 days. Every feature requires a verified Google account and internet access.

Compare Free, Pro and Max Check release status

Six ways to start with your voice

For the work in front of you.

From a development prompt to a quick reply. Explore a concrete example of how each workflow could fit your day.