WebRADDocumentationExplore WebRAD ↗Native builds and GitHub Actions
Native builds are experimental. WebRAD generates the frontend and a Tauri 2 project. The application uses a system WebView while preserving TypeScript components and events. The IDE runs on Electron; generated native applications use Tauri.
Configure and build
- Open Project Settings → Native Application.
- In Identification, enter Application Name, Application Identifier in the format
com.company.app, Version such as1.0.0, description, publisher, and icon. - In Build, configure platform, architecture, Debug/Release, Bundle Format, and Output Directory.
- Adjust Desktop, Mobile, Network, and Signing references for the target.
- Save. Open Project → Build Application… and choose Target Platform.
- Review Build Requirements. Use How to resolve for pending items and Check again after installing tools.
- Click Build. Follow Build logs and Diagnostics; use Cancel Build to stop.
- After Completed, open the output or copy the artifact path.
The dialog selects the export platform; other options belong in Project Settings. Output updates Output Directory/project name. Public environment values come from Build and publishing → Deploy environment. Available prerequisites do not prove that the resulting application runs or can be distributed.
Targets
| Platform | Local build host | Architectures | Outputs |
|---|---|---|---|
| Windows | Windows | Host, x64, x86, ARM64 | Executable (EXE), NSIS installer (EXE), MSI |
| Linux | Linux | Host, x64, ARM64 | DEB, RPM, AppImage |
| macOS | macOS | Host, Intel x64, Apple Silicon ARM64, Universal | APP, DMG |
| Android | Host with compatible SDK/NDK | ARM64, ARMv7, x64, x86 | APK, AAB |
| iOS | macOS | ARM64 device, ARM64 simulator, x64 simulator | iOS application; IPA for ARM64 devices |
A plain EXE is an executable; NSIS/MSI are installers. AAB is an Android distribution package; use APK for direct installation. IPA requires a device target, signing, and provisioning.
Prerequisites
All native targets require Rust/Cargo, rustup, the target’s Rust toolchain, and Tauri CLI 2. The checklist requires Rust 1.77.2 or later; dependencies resolved during the build may require a newer version.
| Target | Additional tools |
|---|---|
| Windows | Microsoft C++ Build Tools with Desktop development with C++, Windows SDK, and WebView2. MSI also uses VBScript support in the WiX toolchain. |
| Linux | Compiler/linker, pkg-config, and development libraries for WebKitGTK 4.1, GTK3, OpenSSL, and Ayatana AppIndicator. AppImage uses patchelf. |
| macOS | Xcode Command Line Tools and the selected Rust targets. |
| Android | JDK 17+, Android SDK, Platform-Tools, Build-Tools, Command-line Tools, NDK, and Rust targets. Configure JAVA_HOME, ANDROID_HOME/ANDROID_SDK_ROOT, and NDK_HOME. |
| iOS | Full Xcode, iOS SDK, CocoaPods, and Rust targets, on macOS. |
The IDE checks installed tools. Install the listed requirements and restart the IDE when its environment needs refreshing.
Network and signing
In Allowed Network Origins, add one exact HTTP(S) or WS(S) origin per line for services and media used in code. Application CSP and server CORS are separate settings; the backend must accept the WebView’s actual origin.
Signing references stores references: Windows certificate thumbprint, Apple keychain identity/profile, Team ID, and environment variable names for the Android keystore. Certificates, key files, and passwords remain in the system or CI Secrets.
Preview sessions are not transferred to the application. Log in through the WebView and confirm session persistence on the target.
Export to GitHub Actions
- Select a native platform in Build Application.
- Click Export for GitHub Actions.
- Add the exported content to your application repository.
- Review
.github/workflows/native-application.yml, runners, and signing references. - Configure Secrets/Environments and run the workflow on GitHub.
The export includes the compiled frontend and the Tauri project. It does not require a local native toolchain, but does not run the workflow or produce an installer. Export again after changing the WebRAD project. Use a Windows runner for Windows, Linux for Linux, and macOS for macOS/iOS.
Current limitations
Native builds use the web runtime. They do not automatically add filesystem, camera, notification, or download plugins. Video, PDF, popups, storage, and web APIs need verification in the target WebView. Native packages do not use the PWA service worker.
Splash Screen uses the platform’s default startup screen; custom images are not yet supported. Signing, notarization, installation, and store publishing require configuration and verification on the target. The available implementation does not certify every system and device.