av-launcher
Tray launcher shell for the web-server apps
What it does
Several apps in this fleet are local web servers: srt-router, flock, RFutils and others. Each one needs the same small things — choose an interface, choose a port, start, stop, open the UI, sit in the system tray. This is that shell, written once.
The panel is an original card design that themes itself to each app's own web UI, with the palette carried in the app's launcher.toml. It is built with Tauri v2 — a small native app rather than a bundled browser — so the tray cost is a few megabytes, not a Chromium.
- Network interface and port selection before the server starts
- Start, stop and open the web UI from the menu bar
- Themes itself per app from launcher.toml
- Tauri v2 — native, not a bundled browser
- Reused rather than reimplemented — srt-router, flock, RFutils, WebLinked, openrcs and oxbow all ship it
Where it stands
Released at v0.2.1 and in use by several apps in the fleet. The Rust backend compiles and the panel UI has been exercised via its mock backend, The tray app has now been run on real Windows, where Start did nothing at all: Tauri's resource dir comes back as a verbatim \\?\ path, so no bundled binary resolved. v0.2.1 ships that fix along with three more Windows defects. On main since, and not yet in a release: a serve mode in which the launcher serves a static site itself, in-process — which is what gives every browser tool in the fleet a desktop app — and one universal macOS installer in place of two per-arch ones. macOS has not been run end to end against a live server.