Electrobun v1 - Someone Finally Told Electron It's Fat
On February 6, 2026, After Two Years of Obsessive Work (I Can Attest to That), Yoav - the Developer Behind Blackboard - Released Electrobun v1.
A stable release. Not beta, not alpha, not “play around with it and tell me what broke.” A real release. And for anyone who lives and breathes desktop app development with JS, this is probably the most exciting news you’ll hear this year.
But before you roll your eyes and say “another Electron killer? Come on” - let me explain why this time it’s actually different.
The Problem Everyone Knows (and Ignores)
If you’ve ever built a desktop app with Electron, you know exactly what kind of suffering I’m talking about. You write a simple app. Say, a fancy todo list - because who doesn’t need another one. And suddenly you discover that your cute little bundle weighs 100MB. For a task list. It’s like sending an 18-wheeler to deliver a single letter.
Startup time ranges from 2 to 5 seconds. Memory consumption? 100 to 200 megabytes just to wake up. And after installation? Electron apps bloat from an 80MB installer to 500MB and beyond with the dreaded cache of their private Chromium browser. Every Electron app is essentially an entire Chrome browser just pretending to be a nice application.
And despite all this, Electron has dominated and continues to dominate the market. Why? Because the DX was simply the most convenient (personally, I have my doubts about that). JavaScript everywhere, a massive ecosystem, and most developers prefer to absorb the bloat rather than learn Rust (hi Tauri).
So What Exactly Is Electrobun?
Electrobun is a framework for building cross-platform desktop applications written in TypeScript, running on Bun as its runtime, and using native bindings written in Zig, C++, and Objective-C. It supports macOS 14+, Windows 11+, and Ubuntu 22.04+.
But the real magic is in the architecture.
All Options Are Open
Here’s the most important thing you need to understand about Electrobun, and what sets it apart from all competitors: it’s agnostic about the WebView engine.
By default, Electrobun uses the built-in WebView of your operating system. On macOS that’s WebKit, on Windows it’s Edge WebView2, and on Linux it’s WebKitGTK. The implication? Your app weighs roughly 12-14 megabytes (most of which is the Bun runtime itself). Not 150MB…
But - and this is where Electrobun truly shines - if you need perfect consistency across platforms and you don’t want to deal with differences between various WebViews, you can simply set bundleCEF: true in your config file. And boom - you’ve got embedded Chromium just like Electron, but with all the other advantages of Electrobun.
And there’s another forward-looking angle: thanks to the agnostic architecture, when rendering engines like Servo and Ladybird are ready - they’ll be drop-in alternatives. Change one line in your config and you’ve got a new engine. That’s brilliant architectural design.
Bun - The Runtime That Changes the Game
Electron uses Node.js under the hood. Electrobun uses Bun. And the difference isn’t just in the names.
I wrote in detail about my experience with Bun right here:
oriel haim
An Update System You Won’t Believe Exists
This is where Yoav did something that makes me tip my hat. He took the venerable bsdiff algorithm for binary diffing and translated it from C to Zig, upgraded it with SIMD, and added zstd compression. The result? A library called zig-bsdiff, and that’s what powers Electrobun’s update system.
Instead of downloading the entire app from scratch with every update (like in Electron, where an update can weigh 100MB+), Electrobun downloads only the delta - the difference between the current version and the new one. The result? Updates as small as 14 kilobytes. Not mega. Kilo.
Want to ship updates to your app the way you deploy a website? Every day? Every hour? With Electrobun that’s realistic, because neither you nor your users are paying a bandwidth tax. You host the files on S3, R2, GitHub Releases - whatever works for you - and that’s it.
What’s Included in V1? (Hint: Everything)
The stable release includes a complete, production-ready package: cross-platform window management with full control, native application menus and context menus, global keyboard shortcuts, clipboard access, OS dialogs, WebView partitions, session storage, find-in-page, system tray, draggable regions in HTML, and encrypted, fully-typed RPC between the main process and the WebView. On top of that, there’s a CLI tool that handles bundling, code signing, notarization, and installer creation with full automation.
In short: you install, run bunx electrobun init, pick a template (there’s a wide selection), run bun run build - and you’ve got a desktop app.
Code signing and notarization? Configure a few environment variables and add notarize: true to your config. That’s it. No fighting with Xcode, no crazy CI scripts.
What’s Still Missing?
Electrobun is v1, not v10. There’s no mobile support (it’s on the future roadmap, though I don’t see a real use case for it). The ecosystem and community are still small compared to Electron (which is already an established industrial machine). The documentation is good but young. And while Windows and Linux support is official, macOS is still the most mature platform.
The Bottom Line
Electrobun isn’t just another “Electron killer” that will disappear in six months. It’s a project with a clear vision, meticulous architecture, and a real production application running on it. It solves real problems that developers live with every day - ridiculous bundle sizes, heavy updates, embarrassing startup times, and the tedious DX of code signing and notarization.
The biggest advantage? You stay in TypeScript. No need for Rust (Tauri), no need for C++ (native), no need for Go (Wails). You write TypeScript for the main process and for the WebViews, and you get performance approaching native.
If you’re planning a new desktop app - whether it’s a dev tool, a productivity app, an MVP for a startup, or even a game - Electrobun deserves a serious look. At 14 megabytes for the bundle, 14 kilobytes for updates, and 50 milliseconds for startup, it’s hard to argue with the numbers.
