Browser prototype vs VST/AU: the path to building your first plugin

· 7 min read

Almost every musician who wants to build their own audio plugin asks the same question: Should I jump straight to VST/AU, or is a browser prototype “real” enough? For vibe coding and first projects, the honest answer is usually: start with a playable browser prototype— then take the native path when the idea is proven.

What “plugin” usually means

A native plugin (VST, AU, CLAP, etc.) loads inside a DAW. You get tight host integration, low-latency audio paths, and the workflow you already know—but you also inherit SDKs, compilers, signing, host quirks, and a longer feedback loop to hear your first tone.

What a browser prototype gives you

The Web Audio API runs in Chrome, Firefox, Safari, and Edge. A small HTML/JS project can open with a double-click, wait for a Start click (browser autoplay rules), and play sound—no install, no DAW, no linker errors. You can still design like a plugin: knobs, DSP-ish behavior, a clear job (pad, click, sampler toy). That prototype is step one on the path to a VST/AU—not a consolation prize.

Side-by-side for beginners

  • Time to first sound — Browser prototype: minutes. Plugin SDK: hours to days before “hello sine.”
  • AI vibe-coding fit — Assistants are strong at HTML/JS; native C++/JUCE stacks need more toolchain babysitting.
  • Sharing — Web: send a zip or host a page. Plugin: per-OS builds and installers.
  • DAW integration — Native plugin wins. Browser is for proving the idea, learning the loop, then porting with a clearer spec.
  • Scope risk — “Make me a synth plugin” balloons. “Prove a freeze pad as a prototype” stays sticky-note sized.

When a native plugin is the right first target

Choose native earlier if you already ship plugins, have a working JUCE (or similar) template, and your idea requires host automation, MIDI from the DAW, or sample-accurate sync that a browser page cannot deliver for your use case. Even then, many pros prototype behavior in simpler hosts first.

A path that compounds

  1. Prove the plugin idea as a browser prototype that already makes sound
  2. Vibe-code one feature at a time until the sticky-note job is done
  3. Use a JUCE / VST-AU learning path to take it native—with a clearer spec and less guesswork

You learn the describe → edit → listen loop without fighting the toolchain. That skill transfers when you open an SDK.

Where Vibepatch sits

Spec → Scaffold is for people who want to build plugins: personalized scope, playable browser prototype, Cursor prompts, and a JUCE learning path. A compiled VST/AU is not included in the $49 offer—you get the honest first mile plus the map to native, not a finished DAW binary. If you asked for a VST in your intake, you’ll still get a working browser prototype of that idea plus a clear “won’t do (yet)” in the scope—so you hear progress instead of waiting on a plugin build farm.