What problem does it solve?
Tauri v2 development fails in confusing ways when commands are not registered, capabilities/permissions are missing, IPC is miswired, or build configuration (dev URLs, targets, Cargo settings) is inconsistent across desktop and mobile.
Core Features & Use Cases
- Rust command correctness (#[tauri::command]): Implement reliable request-response functions with proper handler registration and error handling.
- IPC patterns for frontend-backend communication: Use invoke, events (emit/listen), and channels (streaming) with the right payload expectations.
- Capabilities & permissions setup: Configure capabilities and permission identifiers so Tauri security gates don’t block required APIs or plugins.
- Cross-platform build & deployment guidance: Align tauri.conf.json and Cargo.toml for desktop and mobile, including mobile Rust targets and shared lib structure.
Quick Start
Ask the AI: "Help me set up a Tauri v2 Rust command and call it from the frontend, including the required capabilities and a working tauri.conf.json devUrl for my setup."