For years, Discord has been where your gaming group, work chat, hobby community and increasingly bizarre collection of servers all live at once. The trade-off has been familiar to anyone who leaves the desktop client open all day: it can eat memory like a browser with 40 abandoned tabs. A Discord Rust app could finally change that.
Discord CTO Stanislav Vishnevskiy says the company is working toward moving its entire client to Rust, the systems programming language prized for performance and memory safety. On desktop, that would mean retiring Electron; on mobile, React Native would go as well, while the user interfaces would remain native.
That may sound like inside-baseball engineering news. It isn’t. For Discord users, this is potentially a practical quality-of-life update: less RAM consumed, fewer slowdowns on modest PCs, and perhaps a desktop app that behaves less like a website wearing a trench coat.
- Discord Rust app development aims to replace Electron on desktop and reduce the hefty memory footprint users often see today.
- The Discord Rust app reportedly used 290MB of RAM in an internal Windows example, far below some current real-world usage.
- Discord plans native mobile interfaces while sharing underlying application code across desktop and mobile through Rust.
- The migration has not received a public launch date, though Discord hopes to begin user testing soon.
Table of Contents
Why the Discord Rust app matters
Electron deserves both credit and blame here. It made it possible for small teams and giant companies alike to ship Windows, macOS and Linux apps using familiar web tools. Slack, Spotify, Notion and Visual Studio Code have all used it in some form. Developers get one broad codebase; users get an app that can feel noticeably heavier than a truly native alternative.
Electron packages Chromium and Node.js with the application. That approach is enormously useful, but it means each app carries a lot of machinery. For a Discord Rust app, removing that layer could make a substantial difference. Open several Electron apps on a laptop with 8GB of memory and the penalty stops being theoretical pretty quickly.
Discord’s current client can reportedly climb beyond 1GB of RAM even for users participating in relatively few servers. Vishnevskiy shared a Windows screenshot showing a new build at 290MB. One test image is not a benchmark, and users should resist declaring victory before the software reaches a wide release. Still, if that figure survives real-world use, it’s a meaningful reduction.
The distinction matters because Discord is not a simple chat window. It maintains text channels, media previews, notification state, animated interface elements, screen sharing, voice processing and often a small mountain of embedded content. Anyone who has joined a busy gaming server during a major launch knows how quickly a supposedly lightweight messaging tool can turn into a full-time workload for a PC.
Discord has been building with Rust for years
This isn’t Discord suddenly discovering a fashionable language. Vishnevskiy wrote on X that the company has used Rust since 2018 across infrastructure, voice technology and parts of the existing client. The Discord Rust app effort represents the company’s attempt to bring that work together. “The holy grail was getting the whole client there,” he said.
Rust’s appeal is straightforward. It gives engineers much closer control over performance than typical web application frameworks, while its compiler catches many classes of memory mistakes before code ships. That makes it attractive for software where latency and reliability matter, particularly Discord’s real-time voice features.
The official Rust project describes the language as focused on performance and reliability. That pitch has helped it spread well beyond hobbyist programming circles: Microsoft, Amazon, Cloudflare and Google have all invested in Rust-related work. The language will not automatically make an app elegant, of course. A badly designed native client can still be slow. But it removes a very large layer of overhead from the starting point.
“That means Electron goes away, and so does React Native,” Vishnevskiy said, adding that mobile would keep native UI while sharing app code with desktop through Rust.
Native mobile UI is the sensible compromise
The mobile part of this plan is arguably as interesting as the desktop rewrite. Discord is not proposing one identical interface across every screen. Instead, it intends to preserve native mobile UI while sharing more of the application’s underlying logic. That is the right call.
Mobile users expect familiar gestures, keyboard behavior, accessibility hooks and platform conventions. A chat app that feels at home on Windows can feel clumsy on an iPhone or Android handset if it tries too hard to be the same thing everywhere. Sharing non-visual code can cut duplication without making every device inherit the same awkward compromises.
For the Discord Rust app, this points to a broader strategy: build a common performance-focused core, then let each platform present it appropriately. It’s harder than simply wrapping a web app, but Discord is large enough that the payoff could be substantial.
The hard part is shipping it without breaking Discord
There’s a reason many companies tolerate Electron’s footprint. Replacing a mature client is risky. Discord has years of features, integrations, accessibility expectations and platform-specific quirks to preserve. Voice chat alone is unforgiving; nobody wants their weekly raid, study group or team stand-up interrupted because a rewrite mishandled an audio device.
Vishnevskiy said Discord hopes to get the new client into user testing soon, but did not provide a public rollout date. That suggests the company knows it has a lot to validate before flipping the switch. A Discord Rust app will need those early test builds to prove more than the promising screenshot.
My read is that the Discord Rust app has a chance to become a useful case study for the rest of the desktop software industry. Electron is not going away — nor should it, frankly, because it remains a practical route to cross-platform development. But the largest apps built on it are reaching the point where convenience has become expensive for users.
Discord is betting that a native Rust foundation can give it the reach of a web-era application without demanding browser-era resources. If it lands near that 290MB figure in ordinary use, Slack, Notion and every other perpetually hungry desktop client may face an uncomfortable question: why are we still asking users to buy more RAM for chat?
