For designers
We handle the rest.
You're three hours into a design problem. The composition is clicking. Now you have to write the rationale — and typing it means context-switching out of the visual mode that took an hour to get into. Resonant lets you narrate it without breaking the state.
The real friction
It starts with: “I'll write up the rationale after I'm done designing.”
You'll be done designing at 6pm. You'll be exhausted. The rationale will get a paragraph — maybe two — and none of the sharpness of the actual thinking. Then the review comes and the stakeholder asks why and the answer that was obvious at 2pm is gone.
Designers produce less documentation than they should, not because they're lazy, but because the cost of leaving the visual mode to type prose is brutally high. Typing is a language-brain activity. Designing is a spatial-brain activity. Switching between them has a tax, and the tax usually gets paid by cutting the documentation.
Resonant lets you narrate rationale, critique, and handoff notes the way you'd explain them standing at the wall in a crit. Your hands stay near the canvas, your eyes stay on the work, and the words land in the doc anyway.
What actually happens
Rationale for a design choice in a critique
“ok so the reason I pushed the CTA to the bottom right instead of keeping it in the card is that the card was getting visually loaded, there was too much competing for attention, and the user's primary task flow is actually scan the list first and then decide, so the CTA wants to live at the end of that scan path not embedded in every item, I also tightened the vertical rhythm to twelve pixels because the old sixteen was making it feel too much like a content site and not enough like a tool”
The CTA moved from inline on each card to the bottom right to reduce visual load — the card was accumulating too many competing elements. The user's primary flow is scan-the-list-then-decide, so the CTA belongs at the end of the scan path rather than embedded in each item. Vertical rhythm tightened from 16px to 12px: the previous spacing read as a content site rather than a tool.
Everything runs on your Mac. Your voice never touches a server — only the finished text leaves your device.
Where it fits
Narrate the reasoning behind a choice the way you'd defend it in a crit. The written rationale ends up with the sharpness of the thinking instead of a flattened summary.
Reviewing a teammate's work? Speak the feedback the way you'd say it walking past their desk. Specific, kind, concrete — not the watered-down version that comes out typed.
Dictate the edge cases, the states you didn't mock, and the reasons behind the spacing decisions. Engineers get the context they need without a twenty-paragraph Figma comment thread.
Portfolio writeups are the documentation designers put off longest. Speak the story of the project the way you'd tell it in an interview. Edit a real draft instead of starting from blank.
How it works
One hotkey activates Resonant anywhere on your Mac. No app switching. No setup. No mode.
Your voice never leaves your machine. Everything is processed locally — fast, private, no cloud dependency.
Filler words removed. Sentences completed. The thought, structured and ready to send.
Privacy
Unreleased product flows, confidential client projects, early-stage concepts, and internal critique feedback are all sensitive by default. Cloud dictation tools transmit the verbal description of that work to third-party servers — which is an NDA problem before it's a privacy preference.
Resonant runs entirely on your Mac. Narration of unshipped features, critique of a colleague's work, and case studies of projects still under NDA never leave the device. The only thing that lands in the doc is the text you chose to paste.