Install & navigate

Busloom uses the same project and protocol engine on Windows, macOS, and Linux, but installation and update behavior differ by package. Once the application opens, the workbench layout is consistent: project resources stay on the left, documents open in editor groups, global actions stay in the app bar, and runtime facts remain visible in the status bar.

Choose the package

The AppImage must be executable before launch. A DEB installs through the distribution's package installer or apt; it is not opened as a document. Linux WebKit rendering depends on the host graphics stack, so a blank window should be diagnosed as a WebKit/driver problem before changing Busloom project settings.

First launch

1. Review the terms

   Busloom requires acceptance of the Terms of Use and Privacy Policy before the workbench opens. Community is restricted to private, non-commercial use.

2. Choose Community or trial

   Continue in Community immediately or start the seven-day Professional trial. Declining the trial does not remove the later option from License & activation.

3. Start without a project

   A clean installation opens the start screen. Busloom does not silently create a project, connection, or default register view.

4. Create or open

   Create an empty project, open an existing .busloom.json file, or open a session/report artifact directly for Replay.

Workbench anatomy

Native application menu

File, Edit, Window, Help, preferences, documentation, and platform-standard window actions. Windows and Linux keep this menu visible because it also carries application-level commands.

App bar

Command palette search, the active connection profile, connection state, and compact runtime controls. Selecting a profile does not connect until the connection action runs.

Project switcher

The active project name and dirty state. Use it to reach project actions without hunting through open tabs.

Sidebar

Project-owned views, Trends, automation, diagnostics, and settings. The resizable width is local layout state, not project data.

Editor tabs and groups

Each view, diagnostic, settings page, or Replay artifact opens as a tab. Split right/down to compare evidence without changing the underlying acquisition source.

Floating action bar

Context controls for a live view, Trend, or Raw Traffic surface. Dragging changes only the current session; relaunch restores its original position.

Status bar

Connection, session request/error counts, last timing, project filename, encoding, and other compact runtime facts.

Where to look for an action