A local tool needs a table, a few charts, and some buttons. Somewhere in the planning meeting, it acquires an entire desktop application.

Before that happens, I want to nominate the browser already sitting on the machine.

I call this Borrowed UI, or BUI: a local process does the work, and a browser tab provides the interface. The established name is a local web UI. The architecture is old. I’m just giving my enthusiasm an acronym.

Three tools that already get it

pprof is the cleanest example. It can print a report of expensive functions, or open a local web interface when a visual inspection helps. Same profiling data, another way to look at it. A graph does not have to become a whole desktop product.

With pprof installed and an existing profile file, its web mode looks like this:

pprof -http=localhost:8080 profile.pb.gz 

Graph visualizations can require Graphviz. This is an example of an optional interface, not a promise of zero dependencies. pprof documentation.

Syncthing is the background-service version. Its browser GUI lets you inspect and configure synchronization. The GUI and REST API share a port, normally on loopback. The work belongs to a running process; you visit the control panel when you need it. Syncthing’s GUI documentation.

Jupyter is the richer version. The browser edits the notebook, while a server and execution kernel handle the other side. Close the tab and the kernel can keep running. Reopen the notebook and reconnect. Useful separation—and a reminder that “I closed it” needs a precise meaning. Jupyter Notebook documentation.

Jupyter is not a tiny installation. It illustrates the boundary, not a diet plan.

When borrowing makes sense

I’d consider BUI for a local data explorer, profiler, backup monitor, or service configuration tool. Especially when the useful part already works as a CLI or background process and the interface is something you need occasionally.

Browsers are good at tables, text selection, charts, responsive layouts, and accessible controls when we build them properly. The local process can own validation, credentials, durable state, and cancellation. The tab doesn’t need a second interpretation of the rules.

This also avoids distributing a browser engine with every application. It does not make the browser’s memory or CPU use disappear. Somebody still pays the rendering bill.

When the window earns its keep

If your product depends on native menus, global shortcuts, file associations, or a carefully controlled window lifecycle, a native app or system WebView may be a better fit. If the whole interaction is one command and three lines of output, opening a tab is probably a small ceremony nobody requested.

You also inherit browser compatibility, port conflicts, startup and reconnection work. Closing the tab and stopping the process are different actions. Say so. Offline use needs local assets and capabilities; localhost is not an offline strategy by itself.

And localhost is not a security policy. Bind to loopback by default, validate Host and Origin, protect state-changing requests, and deliberately secure any wider network exposure. Syncthing’s documentation explicitly calls for authentication and HTTPS when exposing its GUI beyond the local machine.

I don’t think every desktop app should become a tab. I think this option deserves a place in the initial discussion. When a tool mostly needs to work quietly and occasionally explain itself, the browser is a pretty good place for that explanation.

This essay revisits ideas from my earlier BUI article with different examples.

Cover photo by Sebastian Bednarek on Unsplash.