Perry vs Tauri
Tauri combines a compiled Rust core with HTML, CSS, and JavaScript rendered in an operating-system webview. Perry compiles supported TypeScript through LLVM and maps Perry UI to platform widgets. Tauri benefits from web frontend compatibility; Perry targets a no-webview UI model.
What is Tauri?
Tauri's official architecture documentation describes a Rust core plus HTML rendered in a webview, with communication between the webview and native side. It uses the operating system's webview rather than bundling a browser engine into every application.
What is Perry?
Perry parses TypeScript and JavaScript with SWC and compiles supported code ahead of time through LLVM. Native builds do not require an external Node.js installation or JavaScript engine, but they do statically link the Perry runtime and garbage collector. Perry is pre-1.0, implements a practical language and Node.js subset, and offers an optional embedded V8 fallback for code that needs engine semantics.
Side by side
| Feature | Perry | Tauri |
|---|---|---|
| UI rendering | Platform widgets where supported | HTML/CSS/JavaScript in the system webview |
| Native-side language | TypeScript compiled through LLVM | Rust core, with optional Swift/Kotlin/plugin bindings |
| Browser engine distribution | No browser engine for native UI | Uses the OS webview instead of bundling one |
| Frontend ecosystem | Perry UI | Web frameworks and browser tooling |
| Targets | 11 documented targets plus preview | Desktop and mobile targets documented by Tauri |
Where Perry wins
- +Real platform-widget UI model
- +One TypeScript language for supported UI and application logic
- +Wearable, TV, and Web/WASM target scope
Where Tauri wins
- +Mature web frontend ecosystem
- +Small apps without bundling a browser engine
- +Rust plugin and backend ecosystem
- +Broader compatibility with existing HTML/CSS frontends
When to choose Perry
Choose Perry when platform widgets and its broader target model outweigh the smaller current ecosystem.
When to choose Tauri
Choose Tauri when an HTML/CSS frontend, system webview, and Rust-native backend/plugin model fit your team and product.
Verdict
Both avoid Electron's bundled-browser model, but Tauri remains a webview architecture while Perry uses platform widgets. That difference matters more than an isolated binary-size number.