ZeroNative: A New Zig‑Based Cross‑Platform Framework Challenging Tauri

ZeroNative overview

ZeroNative is a Vercel‑labs project announced 9 May 2024. The source code lives at vercel-labs/zero-native on GitHub (Apache‑2.0). After two days the repository had 2.5 k stars, 12 pull requests, 109 forks. Zig accounts for 74.6 % of the codebase; the remainder is Objective‑C++, Objective‑C and C. The current release is v0.1.9 and the README marks it “pre‑test”. Installation is performed with npm install -g zero-native. Documentation is hosted at zero-native.dev and includes Quick Start, Web Engines, App Model, Bridge, Security and Packaging.

ZeroNative enables developers to write UI with familiar front‑end frameworks while the native runtime is implemented in Zig, producing desktop and mobile applications.

Supported front‑ends: Next.js, Vue, Svelte, Vite, React.

Supported desktop OS: macOS, Linux, Windows.

Supported mobile platforms: iOS, Android (via a C ABI library).

Optional WebView engines: WKWebView, WebKitGTK, WebView2, or bundled Chromium/CEF.

Comparison with Electron and Tauri

Electron combines Node.js with a full Chromium stack, providing a large ecosystem but resulting in large binaries and high memory usage.

Tauri uses a Rust shell together with the system WebView, yielding small binaries and fast startup, at the cost of requiring Rust knowledge and limited mobile support.

ZeroNative follows a third approach:

The shell is written in Zig.

WebView can be either the system‑provided lightweight engine or a bundled Chromium/CEF for consistent rendering.

Desktop and mobile are supported from day one, embracing a cross‑platform mindset.

Choosing Zig instead of Rust is intended to further reduce binary size, accelerate compilation, and simplify C ABI integration for iOS and Android, while avoiding the borrow‑checker overhead in glue code.

Architecture

ZeroNative’s runtime is organized into three layers:

App : Zig objects that describe application metadata and lifecycle.

Runtime : Manages the event loop, window handling, bridge communication and platform services.

WebViewSource : Loads HTML, URLs or local resources into the chosen WebView engine.

Application configuration is expressed in an app.zon manifest, which declares metadata, icons, window settings, Web engine choice and security policies.

Front‑end code accesses native capabilities through the bridge call window.zero.invoke(). The bridge enforces size limits, origin validation and permission checks. By default the WebView is treated as an untrusted source; native commands must be explicitly opted‑in, following a sandbox model similar to Tauri’s IPC design.

Why Zig instead of Rust

Small binary and low memory usage : Zig’s aggressive size control is suited to scenarios where startup speed and package size matter.

Fast compilation : Zig’s short compile cycles feel closer to scripting languages, addressing a common complaint about Rust’s compile time among Tauri users.

C ABI friendliness : Zig integrates smoothly with iOS, Android and various system WebViews, satisfying ZeroNative’s cross‑platform requirements.

No borrow checker : The borrow checker in Rust can slow development of glue code; Zig leaves safety responsibilities to the developer.

Current status

Version v0.1.9 is marked “pre‑test”.

11 releases have been published over a short period.

The project is hosted under the vercel‑labs organization and is experimental; graduation to a Vercel product is not guaranteed.

Documentation is complete, but large‑scale production validation is still pending.

Reference

https://github.com/vercel-labs/zero-native