Build native desktop apps with zero-native

If you’re tired of shipping 100MB+ Electron binaries just to display a simple UI, you aren't alone. Most modern desktop development has become bloated, trading system resources for developer convenience. But there’s a better way to bridge the gap between web frontends and native performance. If you want to build native desktop apps with web UI and Zig, zero-native is the most compelling tool I’ve seen in years.

The core philosophy here is simple: stop bundling a browser runtime unless you absolutely have to. By leveraging the system’s native WebView (WKWebView on macOS, WebKitGTK on Linux), you get a footprint that is orders of magnitude smaller than anything built on Chromium. You’re essentially writing a thin, high-performance shell in Zig that manages your UI, rather than a massive application that happens to have a window.

Here is why this approach changes the game for performance-critical applications:

1. Tiny Binaries: Because you aren't shipping a full browser engine, your distribution size drops drastically.
2. Instant Rebuilds: Zig’s compilation speed is legendary. When you’re iterating on your native bridge or platform integrations, you aren't waiting for a massive build pipeline to finish.
3. Native Access: Zig calls C directly. If you need to interface with low-level system APIs, codecs, or hardware, you don't need to write complex "glue" code. You just write Zig.
4. Explicit Security: The WebView is treated as untrusted by default. You define your bridge permissions and navigation policies in app.zon, ensuring your app doesn't accidentally expose system-level access to your frontend.

That said, there’s a catch. If you require pixel-perfect rendering consistency across every single OS, the system WebView might frustrate you. Different platforms have different rendering quirks. For those specific use cases, zero-native allows you to opt into bundling Chromium through CEF. It’s a pragmatic trade-off: use the system engine for 90% of your needs, and switch to CEF only when you need that specific rendering guarantee.

Here’s where most people get tripped up: they try to treat zero-native like a standard web framework. It isn't. You are building a native application that happens to use a web-based view layer. You need to think about your window.zero.invoke() calls as a formal API contract between your frontend and your Zig backend. Keep these calls lean, size-limited, and strictly permission-checked.

If you are ready to move away from the bloat of traditional cross-platform frameworks, start by installing the CLI: npm install -g zero-native. Run zero-native init my_app --frontend next to see how the project structure handles the bridge between your React components and the Zig shell. It’s a refreshing change of pace to see a tool that prioritizes system resources and developer speed over convenience-first bloat.

Read the full documentation at zero-native.dev to understand how to configure your app.zon manifest for production. If you’ve been struggling with memory-heavy desktop apps, try this today and share what you find in the comments.