Your first app
Voussoir is a Rust shell around the platform webview, with the frontend built by Bun.
The Rust side owns the window, the security policy and the commands the page can
call; the frontend is ordinary TypeScript, JSX, CSS or HTML. Nothing about
shipping requires Node, Bun or a bundler at runtime: voussoir build produces a
single native binary with the frontend embedded.
voussoir init notes
cd notes
voussoir dev
That is the whole setup. init writes a working app, dev starts the frontend
server and launches the shell against it.
What you get
notes/
voussoir.json name, window size, entry page, optional allowlist
index.html entry page, bundled by Bun
src/main.ts frontend code
src/style.css
native/Cargo.toml the shell crate
native/src/main.rs windows, shell-service commands, the release loop
native/commands/src/lib.rs your commands; hot-reloaded in dev
native/src/assets.rs generated by the CLI, do not edit
Two Rust files matter. native/commands/src/lib.rs holds the command table and
is rebuilt on save while voussoir dev runs. native/src/main.rs configures the app
and registers commands that need the app itself, such as opening a window.
The smallest real app
native/commands/src/lib.rs:
use voussoir::serde_json::{json, Value};
pub fn greet(payload: &Value) -> Result<Value, String> {
let name = payload.get("name").and_then(Value::as_str).unwrap_or("world");
Ok(json!(format!("Hello, {name}!")))
}
src/main.ts:
const message = await window.voussoir.invoke<string>("greet", { name: "you" });
document.querySelector("#out")!.textContent = message;
index.html loads src/main.ts and the shim installs window.voussoir before any of
your scripts run. There is no import, no provider, no bundler plugin.
Run, build, package
| Command | What it does |
|---|---|
voussoir dev | Bun dev server with HMR, shell watching for Rust edits |
voussoir dev --verbose | the same, plus structured diagnostics on stderr |
voussoir build | bundle the frontend, compile the release binary |
voussoir build --size | the same, then print the binary size |
voussoir package | build, then wrap it in an installer for this OS |
voussoir doctor | check the toolchain and say what is missing |
voussoir doctor is the first command to run when something does not build; it
reports the missing piece by name instead of letting a linker error surface two
minutes later.
Where to go next
- Commands & payloads explains the contract every call goes through.
- Security model explains the policy you are getting for free.
- Multi-window covers labels, per-window allowlists and lifecycle hooks.