Zentax Differentiation & Vision

Thank you for your interest in Zentax! It's an exciting time for the project, and we’re happy to share more details on how we plan to carve out a unique space alongside established solutions like Tauri, Slint, and Flutter Desktop.

1. Benchmarks (Coming Soon)

Since Zentax is currently in its early implementation phases (Compiler & Initial Renderer), we don’t have official release-grade benchmarks yet.

However, our architecture is built with the following performance targets:

Startup Time

Target startup time is under 50ms. Since Zentax compiles directly to native binaries without relying on a JavaScript runtime or embedded WebView, application launch is nearly instantaneous.

Memory Usage

We aim for a baseline memory footprint of approximately 10–20MB for a simple application, significantly lower than frameworks that depend on browser engines or large runtime environments.

Render Performance

Using tiny-skia for the initial rendering backend and a future specialized Vulkan/WebAssembly renderer, Zentax targets 120FPS+ sustained UI performance with minimal CPU and GPU overhead.

2. Architecture Overview

Zentax is built entirely in Rust and follows a modular architecture.

Core Components

• zen-compiler

  • Multi-pass compiler
  • Transforms .zen files into an efficient reactive AST

• zen-runtime

  • Signal-based reactive runtime
  • Tracks dependencies at the component level
  • Updates only affected UI subtrees

• zen-renderer

  • Backend-agnostic rendering engine
  • Custom Flexbox layout system
  • Utility-first styling support

• zen-cli

  • Project scaffolding
  • Package management
  • Build tooling

Rendering Pipeline

graph TD
    Source[".zen Source"] --> Compiler["Zen Compiler (Rust)"]
    Compiler --> AST["Reactive AST"]
    AST --> Runtime["Signal Runtime"]
    Runtime --> Layout["Flexbox Engine"]
    Layout --> Renderer["Native Renderer (Vulkan/Skia)"]
    Renderer --> Display["OS Window"]

3. Reactive & Component Model

Zentax adopts a declarative, component-first architecture.

Unlike React, which relies on Virtual DOM diffing, Zentax uses a Signal-based reactivity system inspired by technologies such as:

• SolidJS
• SwiftUI
• Leptos
• Modern Reactive Systems

Benefits

Zero-Cost Reactivity

State changes trigger direct updates to the rendering tree without maintaining a virtual representation of the UI.

Fine-Grained Updates

Only affected components are re-rendered, minimizing unnecessary work.

Utility-First Styling

Styling is integrated directly into the language, allowing developers to write:

Here is how your example would look in Zentax:
Your HTML/Tailwind Snippet:

<div class="flex-row justify-center p-4">
    Hello World
</div>

The Zentax Equivalent:

container "flex-row justify-center p-4" {
    text { 
        value: "Hello World" 
    }
}

This approach feels immediately familiar to web developers while remaining fully native.

4. Why Zentax?

Zentax vs Tauri

Zentax eliminates the WebView entirely, removing IPC bottlenecks and browser-related overhead.

Zentax vs Slint

While Slint excels at lightweight native interfaces, Zentax focuses heavily on Developer Experience (DX) and familiarity for web developers.

Zentax vs Flutter Desktop

Zentax is designed to feel like a true part of the operating system while still providing complete control over appearance and behavior.

5. Long-Term Compatibility Strategy

Our vision is to make Zentax the Unifying UI Language across desktop and web platforms.

Current Focus

• Linux Desktop
• Windows Desktop

Future Targets

WebAssembly (WASM)

Compile the Zentax renderer to the web through:

• WebGPU
• WebAssembly

This enables developers to deploy the same UI language across desktop and browser environments.

Stable ABI

A stable ABI strategy ensures:

• Long-term binary compatibility
• Reusable component libraries
• Smooth compiler evolution
• Forward compatibility across releases

Current Development Status

We are actively working toward:

• Phase 5: Full Runtime
• Advanced Renderer Features
• Dashboard Components
• System Tools
• Package Ecosystem

More examples and showcases will be released as development progresses.

Vision Statement

Zentax aims to combine the performance of native applications, the developer experience of the modern web, and the flexibility of a custom UI language into a single cohesive platform.

Follow Progress

Stay updated through the official roadmap and project repositories as Zentax continues to evolve.