A Windows-first desktop status hub for seeing the important things happening on your computer without switching between apps.
Glance Bar keeps a compact status-center window close at hand. It is designed to surface useful desktop activity—such as what is playing, download progress, and focus sessions—while staying quiet when there is nothing worth interrupting you for.
The first product release is focused on three everyday states:
- Media — see what is playing and use available playback actions.
- Downloads — follow meaningful progress, completion, and failure states.
- Focus — see an active focus session and its completion state.
System performance and provider health support those experiences. Developer-oriented sources such as Git, Docker, npm, and AI tasks are engineering capabilities, not the success criteria for the first user-facing release.
- Less context switching: understand a state change without hunting for its source app.
- Predictable display: priority, manual selection, and automatic return rules determine what is visible.
- Privacy-safe by design: platform data is normalized into coarse, bounded facts before it reaches the UI.
- Desktop-native controls: tray actions, preferences, window positioning, fullscreen avoidance, and autostart belong to the desktop shell.
| Platform | Status |
|---|---|
| Windows | Primary development and validation target. |
| macOS | Platform modules compile; individual capabilities may report unsupported. |
| Linux | Platform modules compile; individual capabilities may report unsupported. |
Do not treat compile-time support as feature parity. A capability is only available when its native path, provider state, fallback behavior, and validation evidence all exist.
- Node.js 20 or later
- Rust stable toolchain
- The platform prerequisites required by Tauri 2 for your operating system
npm install
npm run devOpen /desktop for the product-facing surface or /showcase for the demo and visual-QA surface.
npm run tauri -- devProvider -> HubEventBus -> aggregation -> resolver/scheduler -> template UI
Native commands and events stay behind Tauri/runtime boundaries. Providers normalize source data; the scheduler decides which useful status to show; React templates render the selected state.
For the full design, read the architecture overview and event flow.
npm run typecheck
npm run lint
npm run test:vitest
npm run qa
cargo check --manifest-path src-tauri/Cargo.toml
cargo clippy --manifest-path src-tauri/Cargo.toml -- -W clippy::all- MVP launch plan
- Product requirements
- Product roadmap
- Repository guide
- Provider SDK
- Contribution guide
Historical material lives in docs/archive/ and does not describe the current implementation.
See LICENSE.