The short version
Discord is moving its entire client to Rust: Electron goes away on desktop, and React Native goes away on mobile. CTO Stanislav Vishnevskiy announced the change on X on November 4, 2026 and showed an early Windows build using about 290MB of RAM. For companies weighing how to build cross-platform mobile and desktop apps, the pattern Discord picked, one shared native core with platform-specific UI, is now backed by one of the largest consumer apps on the market.
What exactly is Discord changing?
Discord’s desktop app has been an Electron app for years: a web interface packaged with its own copy of the Chromium engine and Node.js. That approach let one team ship the same product on Windows, macOS and Linux, but every Electron app carries a full browser runtime, and memory use grows with every open view. Discord is now rebuilding the client as a native Rust application.
“We’ve been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there,” Vishnevskiy wrote. “That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust.” Replying to followers, he added that the new desktop interface uses GPUI rather than Tauri, according to Windows Latest.
| Layer | Today | New client |
|---|---|---|
| Desktop shell | Electron (Chromium + Node.js) | Native Rust app on GPUI |
| Mobile UI | React Native | Native UI on each platform |
| Shared app logic | JavaScript across web-based layers | Rust, shared by desktop and mobile |
| Status | In production | Early builds; user testing “soon” |
How much lighter is the Rust build?
The only public number so far is a screenshot Vishnevskiy posted of an early Windows build, labeled Discord Phoenix, using about 290MB of RAM. The Verge points out that the current Windows app can easily climb past 1GB once a user is active in a handful of servers. That is a large gap, but it comes from one machine and an unfinished app with fewer features, so treat it as a direction rather than a benchmark.
The choice of GPUI matters for the comparison. Tauri, the best-known Rust alternative to Electron, still renders a web interface, only inside the operating system’s own webview instead of a bundled Chromium. GPUI, the UI framework developed for the Zed code editor, draws the interface directly on the GPU with no web layer at all. That removes the browser engine entirely, which is where most of Electron’s overhead lives.
What it means for US & EU software teams
The headline is not “everyone should rewrite in Rust.” Discord already ran Rust across its infrastructure and voice stack for eight years, which is why it can own a native UI framework that is far younger and less documented than Electron. Most product teams do not have that depth, and a full client rewrite freezes feature work for months. The more useful lesson is architectural: Discord is putting business logic in one shared core and keeping the user interface native on each platform.
That shared-core pattern is available to teams of any size. Rust, Kotlin Multiplatform and C++ can all host shared logic, while the UI stays in SwiftUI, Jetpack Compose or a desktop toolkit. Teams currently on React Native or Electron should not panic: both remain the fastest route to shipping on several platforms with a web-skilled team. But if memory, battery, startup time or app size are already hurting reviews or retention, Discord’s move is a reason to measure those costs and price the alternatives.
Staffing is the hidden cost. Rust engineers who can also build polished desktop and mobile UI are scarce and expensive in both the US and the EU. Before committing, estimate who will maintain the native core in three years, not only who can build the prototype.
How should teams evaluate their cross-platform stack now?
- Measure first. Record memory, CPU, cold-start time and install size on the low-end devices your users actually have.
- Find the real bottleneck. Many Electron and React Native performance problems come from heavy views, leaks or chatty state updates that can be fixed without a rewrite.
- Compare the options honestly. Electron, Tauri, React Native, Flutter and a shared native core trade off speed of delivery, performance and hiring differently.
- Extract shared logic gradually. Move networking, sync, encryption or media code into a shared native module before touching the UI, as Discord did with Rust over several years.
- Plan for skills. Budget for training or hiring before you adopt a young framework, and keep a fallback if it stalls.
Frequently asked questions
What did Discord announce?
On November 4, 2026, Discord co-founder and CTO Stanislav Vishnevskiy said on X that the company is moving its whole client to Rust. The desktop app will no longer be built on Electron, and the mobile apps will drop React Native, keeping native user interfaces but sharing application code with desktop through Rust.
How much memory does the new Discord app use?
Vishnevskiy shared a screenshot of an early Windows build using about 290MB of RAM. The Verge notes that the current Electron-based Windows app can easily reach 1GB or more once a user is active in a few servers. These are early, single-machine figures, not a published benchmark.
Which framework is Discord using instead of Electron?
According to Vishnevskiy, the new desktop interface is built with GPUI, a Rust UI framework best known as the UI layer of the Zed code editor, rather than Tauri. Tauri also uses Rust but usually renders a web interface inside the operating system webview; GPUI draws the interface natively on the GPU.
When will the Rust version of Discord be released?
Discord has not given a date. Vishnevskiy said the company hopes to get the new client into testing with users soon.
Should my team move off Electron or React Native too?
Not automatically. Discord has run Rust in production since 2018 and has the engineers to own a native UI stack. For most products, Electron, Tauri, React Native, Flutter or a shared native core can all work; the right choice depends on memory and performance targets, team skills, release cadence and how much code you need to share across platforms.
Sources
Stanislav Vishnevskiy, Discord CTO, on X (primary source, November 4, 2026)
The Verge — Discord is ditching Electron and its new app uses less RAM (November 5, 2026)
Windows Latest — Discord is killing its Electron app, and the Rust rebuild uses just 290MB (November 5, 2026)