tauri-apps/wry

Cross-platform WebView library in Rust for Tauri.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 13th, 2026
Created on July 12th, 2020
Open Issues & Pull Requests: 202 (+0)
GitHub issues: Enabled
Number of forks: 540
Total Stargazers: 4,967 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 39.0 hours
Mean response time: 57.0 days
90th percentile: 225.1 days
Tracked items: 161

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in two opened in the past year never receives a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "platform: macOS" is answered fastest, typically in about 4 hours, while "platform: All" waits about 2 days. 47% of tracked open issues have had no activity in three months. Only 31% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 93
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 537 days
Stale 30+ days: 72
Stale 90+ days: 52

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 5

Top labels

  • type: bug (75)
  • type: feature request (45)
  • platform: macOS (29)
  • platform: Linux (22)
  • platform: All (21)
  • platform: Windows (19)
  • status: upstream (15)
  • help wanted (11)

Detailed Description

Wry is a cross-platform WebView rendering library written in Rust for embedding web content in native applications.

Wry solves the problem of rendering web content across different operating systems by providing a unified Rust API that wraps each platform's native web engine. On Windows it uses WebView2, on macOS it uses WebKit, on Linux it uses WebKitGTK, and on Android and iOS it uses platform-native WebView implementations. The library requires a running event loop and a window handle from a windowing library such as tao or winit. It supports creating webviews as child windows within existing windows on macOS, Windows, and Linux, and offers platform-specific builders to handle differences in how each OS manages web rendering, particularly for supporting both X11 and Wayland on Linux through GTK integration.

Wry suits projects that need to embed web content in Rust-based desktop or mobile applications and want to avoid bundling a separate browser engine. It works well with windowing libraries like tao and winit, though developers using winit on Linux must manually initialize and manage GTK alongside the windowing event loop. Android development with wry requires additional setup including environment variables, Kotlin file generation, and JNI bindings through provided macros. The library is recommended for developers who want native web rendering without the overhead of solutions that bundle Chromium or other engines.

Development on the project shows consistent activity with regular commits addressing platform-specific issues and feature improvements. The maintainers actively respond to issues and pull requests, indicating ongoing engagement with the user community. The codebase receives updates to handle edge cases across different platforms, particularly around WebKit linking on macOS and GTK integration on Linux. Documentation is maintained with platform-specific guidance and examples for different windowing library combinations.