Slack Desktop - Electron |work|

If you have used Slack on Windows or Linux (and even macOS today), you are using an Electron application. But the journey to get there was not just about following a trend—it was a fundamental architectural rewrite that saved the product from crumbling under its own weight.

| Issue | Slack’s Mitigation | |-------|-------------------| | High RAM usage | Unloads unused workspaces; compressed heap snapshots | | Larger installer size (~120MB) | LZMA compression; split into shared Chromium + app code | | Occasional UI jank | Off-main-thread rendering for heavy animations | | Battery impact | Throttles background timers when window hidden | slack desktop electron

While this allowed for rapid initial development, it created severe scaling issues as Slack grew: If you have used Slack on Windows or

To combat Electron’s reputation for being resource-intensive, Slack underwent a significant architectural rewrite : Performance Optimization Here is a deep dive into

: Modern versions of the Slack desktop app support native Wayland rendering on Linux, though it may require specific command-line flags like --ozone-platform-hint=auto to avoid blurry text on HiDPI displays. Performance Optimization

Here is a deep dive into the Slack Desktop Electron architecture.

In late 2017, Slack released a completely rewritten desktop client. They moved away from the "website in a box" model to a proper native-feeling application using .