Discord Plans to Move Its Desktop App to Rust and Drop Electron

Discord plans to move its desktop app fully to Rust and drop the Electron framework, according to The Verge, which reported the plan on November 5, 2026. The company also intends to drop React Native from its mobile clients. Mobile will keep native user interfaces but will share application code with the desktop app through Rust.

The shift reverses a long-standing stack. In a March 2025 engineering post, Discord said its desktop clients were built with React and its mobile clients with React Native. The desktop applications have been developed on Electron, which wraps web technologies in a native desktop shell. In practice, that means each app ships its own copy of a web browser engine. Discord has also said that Electron lacks explicit support for WebAuthn, the browser-based authentication standard, in a 2023 post about modernizing multi-factor authentication.

The Electron dependency was current until recently. Discord's December 8, 2025 patch notes recorded an upgrade of the desktop app to Electron 37, less than a year before the new plan was reported.

Rust is not new at Discord. Chief technology officer Stanislav Vishnevskiy said the company has used Rust since 2018, across its infrastructure, its voice technology and part of the current client. Discord's 2020 engineering post described a move of services from Go to Rust, citing performance improvements. The desktop plan extends a language already in production on the server side and in real-time voice into the client itself.

The Verge reported that Discord showed a Rust-based Windows client using 290MB of RAM. Discord hopes to put that client in front of users for testing soon. The client is therefore at the testing stage, and no release date has been given.

The broader context here is the cost of the shell. Electron lets a small team ship one codebase across Windows, macOS and Linux using web tooling, and that convenience is why many chat, collaboration and productivity applications adopted it. The trade-off is a bundled browser runtime in each app, plus a rendering and platform layer the developer does not fully control. A Rust client gives Discord direct control over memory use, rendering and operating system integration, at the cost of building or adopting more of the user interface stack itself.

In my view, the mobile element is the part most likely to matter to engineering teams beyond Discord. Sharing application code between desktop and mobile through Rust, while keeping native interfaces on phones, is a different split from both a single cross-platform UI and fully separate codebases. Whether that split holds up across Discord's large feature surface will depend on how much logic can move into the shared layer without forcing compromises on the native front ends.

Discord's stated reasons for the change, beyond the memory figure and the performance theme of its earlier Go-to-Rust work, have not been set out, and the timeline for a shipping desktop client remains open. What the November 5 report does establish is a direction: a company that has run Electron for years, and that has said Electron falls short on WebAuthn, now plans to rebuild its desktop client in the language it already uses for its core infrastructure and voice stack.