Tauri — open source GitHub project

Tauri builds desktop and mobile applications with a web interface, system WebView, and a Rust core.

What it is

Tauri is a framework for desktop and mobile applications with a web interface. Developers can use familiar HTML, CSS, and JavaScript frameworks for the UI, while writing the system side in Rust and exposing it through a safer API.

The key difference from heavier shells is that Tauri uses the system WebView: WKWebView on macOS and iOS, WebView2 on Windows, WebKitGTK on Linux, and Android System WebView on Android. That helps keep builds smaller, but also ties behavior to platform details.

How it appeared and why it stuck

Tauri appeared as an answer to building cross-platform applications with a web interface without embedding a huge browser in every build. Rust gave the project a strong system layer, while web technologies gave a fast UI path.

The framework stuck with teams that want a balance: use existing web-development skills while getting compact installers, system windows, tray icons, notifications, and packaging for different platforms.

What is inside

The repository contains the Tauri core, bundler, APIs, plugins, integrations with windowing libraries, and architecture documentation. Around it are `create-tauri-app`, a VS Code extension, updater support, and a GitHub Action for builds.

Creating a new app

This example shows the starting path: the generator creates a project, then the interface and Rust commands evolve inside one structure.

Language: Bash

npm create tauri-app@latest
cd my-tauri-app
npm install
npm run tauri dev

Where it helps

Tauri fits internal utilities, local-file apps, developer tools, service clients, private work apps, and products where installer size and system access matter more than a fully identical embedded browser.

If an application needs perfectly identical browser-engine behavior across platforms, Tauri needs more testing. The system WebView gives compactness, but different OS versions can behave slightly differently.

Strengths and limits

The strength is compactness and system integration. Teams can write the interface in a familiar way without shipping a full browser inside each app.

The limitation is that developers need to understand the boundary between the web part and Rust commands, as well as the permissions model. It is not merely a website in a window; it is an application with system capabilities.