Skip to content
Version 2Active developmentInfrastructure completeDesktop application under construction
All posts
EngineeringJuly 6, 20264 min read

Why we chose Rust

A communication app lives or dies on trust and responsiveness. It handles your messages, your identity, and one day your calls. We wanted a core that is fast, predictable, and hard to get wrong - so the core of LynxDock is written in Rust.

Rust gives us memory safety without a garbage collector, which means a small, calm resource footprint and no surprise pauses. It's a good fit for a desktop app that should feel instant and stay light, even on modest hardware.

The desktop app is built on Tauri: a Rust core with a web front-end. Storage, identity, workspace, and messaging all live in Rust, exposed to the UI through a handful of typed commands. The server, when it arrives, will be Rust too.

Rust also anchors our protocol. The wire types are defined once in Rust and generated into TypeScript, so the client and a future server can never quietly drift apart. CI fails if the generated types are out of date.

None of this is visible in the UI - and that's the point. The right foundation is the one you never have to think about.