WebView2 And Webview Fragmentation
Tauri uses the platform webview instead of bundling Chromium by default. That makes apps smaller, but it moves rendering and runtime differences into your test matrix.
Platform Differences
| Platform | Backend | What to test |
|---|---|---|
| Windows | WebView2 | Runtime install mode, Evergreen updates, enterprise policies, GPU behavior |
| macOS | WKWebView | Safari/WebKit CSS and API behavior, signing/notarization, automation limits |
| Linux | WebKitGTK | Distro packages, library versions, fonts, GPU, sandbox, media support |
| Android | Android WebView | Device WebView version, low-end performance, permissions, viewport/layout |
| iOS | WKWebView | App Store policy, WebKit behavior, simulator/device differences |
When Fragmentation Hurts
Fragmentation becomes expensive when the app depends on:
- Advanced CSS or browser APIs that differ across engines.
- Complex drag/drop, clipboard, file, media, or graphics behavior.
- Pixel-perfect layout and typography.
- Heavy canvas/WebGL/WebGPU usage.
- Enterprise Windows machines with constrained runtime policies.
Testing Strategy
Use browser tests for fast renderer logic.
Use mocked IPC for command payloads.
Use WebDriver for running desktop app smoke.
Use release artifacts for packaging and webview runtime proof.
Use physical or emulator/device tests for mobile.Electron Comparison
Electron bundles Chromium. That costs disk and memory, but it reduces rendering variability. If the product is a complex UI where consistent browser behavior dominates native shell size, Electron may be the pragmatic choice.
Gotcha: Smaller bundles are not free. You pay with platform-webview testing and release notes that say exactly which OS/runtime combinations are supported.