// the find
meshtastic/network-management-client
A Meshtastic desktop client, allowing simple, offline deployment and administration of an ad-hoc mesh communication network. Built in Rust and TypeScript.
A Tauri desktop client for managing Meshtastic LoRa mesh networks, targeting emergency response and off-grid communication scenarios where you need to see the whole network topology, not just your own node. Built with a Rust backend handling serial/BT/TCP device comms and a React/Redux frontend for map visualization and device configuration. This fills a real gap — the official Meshtastic apps are single-node focused, this one tries to manage the network as a whole.
The Rust/Tauri stack is the right call here: serial port access and BT handling belong in native code, not Electron's Node.js shim layer. The graph data structure in src-tauri/src/graph/ is a proper separate domain with its own DS and API modules, not just tacked onto device state. The devcontainer setup is solid — you can actually develop this without fighting your local Rust/Node environment. The topology collection work is non-trivial: they wrote an RFC, got protocol buffer changes merged upstream, got firmware changes merged — that's real project discipline, not just a UI wrapper.
Last push was November 2025 and the README's contribution call-out reads like a project that ran out of steam — offline maps, DMs, remote node config, and QR channel import are all still unchecked. The Redux saga architecture is heavyweight for what is essentially a state machine syncing to a serial device; the complexity will make onboarding contributors harder than it needs to be. No UI test suite at all ('currently the project does not have a UI testing suite') for a project with this much interaction complexity is a real gap. The algorithm analysis features — Betweenness Centrality, etc. — have no on-map UI yet, meaning the most interesting differentiating functionality is backend-only with no way to actually use it.