BUI: Your App, the Browser’s UI

Browser User Interface. Or, if you like, Borrowed UI.

Browser User Interface (BUI): local software that borrows your browser. Examples from Open WebUI, OpenCode, Syncthing, and my ProtoPeek project, plus the trade-offs.

BUI means Browser User Interface in this article. Borrowed UI is the joke: your app brings the native functionality and borrows an installed browser. This is a proposed label for an existing local-web-UI architecture, not a new standard or an invention claim.

A local program serves HTML, CSS, and JavaScript over loopback. The browser presents controls; a native backend performs operations through a guarded API. A CLI can call the same core without opening a graphical interface. CLI feature parity still has to be implemented.

ProtoPeek is a concrete example: its Go process serves an embedded web interface and handles gRPC, HTTP, and local work. Its stable v0.5.0 Downloader uses external aria2c. The pp download command is narrower than the graphical queue and owns a separate engine session. Cloudflare Tunnel controls are newer source; Tailscale integration is planned.

Open WebUI is a substantial self-hosted browser interface for local and cloud AI models. OpenCode web starts a local server; its terminal UI can attach to the same server and sessions. Syncthing has a browser management interface. grpcui launches a browser-based gRPC inspector. These projects illustrate the architecture; they do not use or endorse this proposed BUI label.

BUI avoids distributing a browser engine with the app. It does not make browser memory free, guarantee faster startup, or stop the backend when a tab closes. Measure the native process, incremental browser memory, cold and warm startup, and job lifecycle together.

Occasional inspection, configuration, and download tools are a strong fit. All-day editors and creative tools deserve separate evaluation of native integration, input latency, accessibility, and sustained resource use. A PWA can improve presentation but does not install or launch an arbitrary native backend.

Topics

browser-user-interface
BUI
local-web-ui
desktop-apps
open-webui
protopeek
opencode

Sources

Canonical article URL