Screen lock by Bluetooth proximity: present/absent is not enough
Why a Bluetooth proximity lock needs a proximity assessment, not a raw present/absent signal; it shipped as SignalLock for macOS, Windows and Linux.
What it does today
Locks the screen on macOS, Windows and Linux when the device you carry moves away; the call rests on a proximity assessment rather than a raw present/absent signal, so fluctuation no longer produces false locks. The menu bar and system tray app is published on all three platforms and ready to install.
- Started
- March 2026 — May 2026
- Left Labs
- Updated
Form
Technologies
This one became a product:
SignalLockAsking whether a Bluetooth device is in range is easy; getting the answer right is a different job. The raw “present / absent” signal lies several times a second, and every lie is a wrong lock.
“Present / absent” lies
An unlocked computer in a shared workspace is a privacy risk, and remembering to lock it should not be the user’s job. The solution tried: treat a Bluetooth device the user already carries (a phone, a smartwatch, earbuds, a BLE tag) as a trusted device, and lock the screen when it leaves range.
The real subject turned out to be the signal itself. A Bluetooth signal fluctuates by nature; the device disappears from a few samples even while it is sitting on the desk. A lock that reads plain visibility locks the screen while the user is still in their chair.
Proximity assessment instead of visibility
The core of the app was built on a proximity assessment rather than plain visibility: a smoothed RSSI value is read together with a last-seen timestamp. The RSSI threshold, the away delay and the smoothing window are all user-adjustable; the defaults (-80 dBm, 20 seconds, 5 samples) were deliberately chosen on the conservative side to minimise false locks.
Never going online on its own
For a tool like this the cloud is the easy road: keep the device pairing on a server, sync the settings, add features like “find my desk”. All of it means an account system and a backend.
The constraint chosen was the opposite: the app makes no network request on its own. There is no backend server, no cloud sync, no account, no telemetry, no analytics; location services are not used and every setting stays on the user’s own machine. The only connection it opens is the update check the user starts from the menu: the request goes to GitHub, and the downloaded package is verified with SHA-256 before it is installed.
The cost is plain — no sync across devices, no remote management — and with no usage data, the default thresholds rest on a conservative choice rather than a measurement. In exchange, a user who wants their screen locked does not have to hand the identity of the phone in their pocket to a server. For a security tool that is the right trade.
One codebase, three platforms
An app that scans Bluetooth continuously and triggers the screen lock touches the lowest layers of the operating system it runs on: the Bluetooth stack, the session lock, the tray icon. All three work differently on macOS, Windows and Linux. The proximity decision, on the other hand, does not depend on the platform at all; the same samples have to produce the same result everywhere.
The path chosen was a single Rust codebase, and the boundary runs exactly along that split. The proximity engine, the settings models and the JSON layer that stores the settings live in a separate crate that touches no platform API. Bluetooth scanning (btleplug), the tray menu, the settings windows written in Slint and the lock service live in a second crate. A threshold fix is made in one place, tested in one place and reaches all three platforms together.
The cost sits in platform integration. The screen lock is a different mechanism on every operating system, and on Linux it also changes with the desktop environment. The tray uses a native backend on macOS and Windows, and StatusNotifierItem over D-Bus on Linux. These parts are written by hand per platform, and this is where platform-specific fixes are most likely to be needed.
The road to the menu bar and the tray
It shipped as a menu bar and system tray app for macOS, Windows and Linux; the product page and the download live on their own domain. Details in the portfolio.