Build Multi-target Tauri Apps
Build, debug, test and prepare Tauri 2 apps for Windows, Linux, macOS, iOS and Android. Share frontend/domain behavior while checking native permissions, plugins, WebView differences and platform evidence. Optional browser deployment has explicit native-feature replacements or unavailable states.
Initial package version: 0.1.0. Marketplace package; publication is gated by PR review and CI, while native consumer acceptance requires separate target evidence. This original synthesis adapts capabilities from Build iOS Apps, Build Web Apps, Build macOS Apps and Test Android Apps. It does not copy their skill text or require them to be installed. Adaptation and 43-source research ledger.
Skills
| Skill | Use |
|---|---|
| tauri-app-builder | Start here for a new app or multi-target adaptation |
| tauri-architecture | Typed IPC, state, cancellation and persistence |
| tauri-frontend | Accessible responsive UI and rendered iteration |
| tauri-native-build | Target setup, build/run/debug and native integrations |
| tauri-security | Capabilities, custom commands, CSP, resource scopes and secrets |
| tauri-testing | Rust/frontend tests, native E2E and mobile device QA |
| tauri-performance | Renderer/Rust/native profiling and lifetime proof |
| tauri-distribution | Artifacts, CI, signing, updates and release preparation |
Shared references ship inside the skills tree and load by topic. Use only the workflow needed; no full lifecycle ceremony for a small edit.
Example requests
- Build this existing Tauri app for macOS, Windows, Linux, iOS and Android; report target gaps.
- Adapt this frontend into a Tauri app while retaining its current framework.
- Fix Android keyboard/back behavior and verify the real installed app.
- Restrict this Rust command to the intended window and prove denied callers fail.
- Investigate memory growth after repeating this flow, with comparable captures.
- Prepare desktop packages and mobile release gates without publishing.
Prerequisites and boundaries
Use consumer repository's package manager, locked frontend/Rust dependencies and local Tauri 2 CLI. Selected native targets require their documented SDK/toolchain and authorized device. iOS requires full Xcode on macOS; Android requires matching SDK/NDK/JDK/Gradle and Rust ABIs. Windows/Linux/macOS packages require supported native build hosts and runtime libraries. No SDK installation is performed by this plugin.
Browser automation, Xcode tools, adb and profilers are optional capabilities detected at runtime. Missing tools have explicit fallback or not-run evidence; no invented tool APIs. Native Tauri plugins are dependencies of the consumer app, distinct from this Codex plugin.
Current WebdriverIO embedded automation supports desktop macOS, Windows and Linux; direct official tauri-driver supports Windows/Linux. Provider/version setup must be verified, and instrumentation stays in test-only builds. Browser mocks cannot prove real IPC ACLs, OS permissions or native lifecycle behavior.
Signing, notarization, store submission, release publication, deployment and device/data reset need exact authority. Build/test requests do not imply them. See security policy and operating contract.
Validation and contribution
From marketplace repository root, using its selected Python environment:
python scripts/check_plugin.py plugins/build-multi-target-tauri-apps --layout source
python scripts/check_distribution_bundle.py plugins/build-multi-target-tauri-apps
python scripts/check_marketplace.py .
python -m unittest discover -s tests -p 'test_*.py' -v
These check package structure, local links, exact distribution closure and marketplace integration. They do not prove native app behavior, fresh Codex routing, visual plugin-card rendering or storefront compliance. Validate consumer changes using the target evidence matrix in testing reference. Keep original prose/artwork, refresh affected sources, preserve unrelated changes and commit only coherent scope. No credentials or captures belong in the distribution.