Build native Android mobile applications with Bini.js.
Bini.js builds native Android applications on top of Tauri v2. Your React app runs inside a native Android WebView with full access to system APIs, permissions, and platform features.
APK for direct install, AAB for Play Store
Keystore signing wired in at scaffold time
bini-native wires Android permissions
Building Android apps requires the same toolchain on every desktop OS (Windows, macOS, and Linux). The only differences are the paths to your SDK and minor device drivers.
JAVA_HOMEANDROID_HOME.ANDROID_HOME points to your SDK path - ~/Library/Android/sdk on macOS, ~/Android/Sdk on Linux, or %USERPROFILE%\AppData\Local\Android\Sdk on Windows.Create a new Bini.js project targeting Android and install its dependencies:
Or run the interactive prompt and select Android:
--app-name "My App" and --org com.acme to skip the native naming prompts.Run your Android app on an emulator or a connected device. This works the same on every desktop OS:
This launches your app with:
bini-nativenpm run androidadb can detect connected phones. On macOS, add the Android SDK platform-tools directory to your PATH so adb is available.Build a release APK or AAB for distribution:
The build outputs land in src-tauri/gen/android/app/build/outputs/:
| Output | Purpose |
|---|---|
app-release.apk | Direct installation on a device (sideloading, internal testing). |
app-release.aab | Android App Bundle for publishing to the Google Play Store. |
Bini.js supports keystore signing for Android binaries. Set it up or redo it at any time with create-bini-app sign android. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires a Java keystore. If you do not have one, you can generate it with keytool or Android Studio's "Generate Signed Bundle / APK" wizard.
.jks, .keystore, or .p12 keystore file.To sign the APK/AAB locally on your machine, provide your keystore, its alias, and its passwords:
This creates a keystore.properties file inside src-tauri/gen/android/ and patches the Gradle signing config for you:
If you want the GitHub Action runner to sign the APK/AAB automatically, you must provide the keystore via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
To sign the Android build in GitHub Actions, you must add your keystore as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:
ANDROID_KEY_BASE64 with the base64-encoded string of your .jks or .keystore file.ANDROID_KEY_ALIAS with your key alias.ANDROID_KEY_PASSWORD with your key password.ANDROID_KEYSTORE_PASSWORD with your keystore password.You can build the APK/AAB locally using npm run android:build, or let GitHub Actions build it for you by running npm run deploy.
npm run deploy generates .github/workflows/android.yml and pushes your project to GitHub:
npm run deploy to generate the CI workflow and push to GitHub.Once you have a signed .apk or .aab, you can distribute it. Depending on your goals, you have three options:
.apk on your website or GitHub Releases. This is common for beta testing, internal apps, and sideloading..aab to the Google Play Console.To publish on the Google Play Store, you need a Google Play Developer account. Upload the signed .aab from src-tauri/gen/android/app/build/outputs/bundle/release/ in the Play Console. See the Google Play Console guide for the specific steps.
If you are distributing directly (e.g., for internal testing), upload the signed .apk from src-tauri/gen/android/app/build/outputs/apk/release/ to your website or GitHub Releases. Users must enable "Install from unknown sources" on their device to sideload it.
For open-source apps, you can submit your project to F-Droid. See the F-Droid submission guide for the specific steps.
.aab, not a .apk. The `.apk` is only for direct download and sideloading.Build a native iOS app with App Store distribution and TestFlight.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native macOS app with Developer ID signing and notarization.
Build a native Linux app with AppImage, .deb, and .rpm bundles.
Build native Android mobile applications with Bini.js.
Bini.js builds native Android applications on top of Tauri v2. Your React app runs inside a native Android WebView with full access to system APIs, permissions, and platform features.
APK for direct install, AAB for Play Store
Keystore signing wired in at scaffold time
bini-native wires Android permissions
Building Android apps requires the same toolchain on every desktop OS (Windows, macOS, and Linux). The only differences are the paths to your SDK and minor device drivers.
JAVA_HOMEANDROID_HOME.ANDROID_HOME points to your SDK path - ~/Library/Android/sdk on macOS, ~/Android/Sdk on Linux, or %USERPROFILE%\AppData\Local\Android\Sdk on Windows.Create a new Bini.js project targeting Android and install its dependencies:
Or run the interactive prompt and select Android:
--app-name "My App" and --org com.acme to skip the native naming prompts.Run your Android app on an emulator or a connected device. This works the same on every desktop OS:
This launches your app with:
bini-nativenpm run androidadb can detect connected phones. On macOS, add the Android SDK platform-tools directory to your PATH so adb is available.Build a release APK or AAB for distribution:
The build outputs land in src-tauri/gen/android/app/build/outputs/:
| Output | Purpose |
|---|---|
app-release.apk | Direct installation on a device (sideloading, internal testing). |
app-release.aab | Android App Bundle for publishing to the Google Play Store. |
Bini.js supports keystore signing for Android binaries. Set it up or redo it at any time with create-bini-app sign android. If you only need signing for GitHub Actions, use the --ci-only flag.
Signing requires a Java keystore. If you do not have one, you can generate it with keytool or Android Studio's "Generate Signed Bundle / APK" wizard.
.jks, .keystore, or .p12 keystore file.To sign the APK/AAB locally on your machine, provide your keystore, its alias, and its passwords:
This creates a keystore.properties file inside src-tauri/gen/android/ and patches the Gradle signing config for you:
If you want the GitHub Action runner to sign the APK/AAB automatically, you must provide the keystore via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:
To sign the Android build in GitHub Actions, you must add your keystore as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:
ANDROID_KEY_BASE64 with the base64-encoded string of your .jks or .keystore file.ANDROID_KEY_ALIAS with your key alias.ANDROID_KEY_PASSWORD with your key password.ANDROID_KEYSTORE_PASSWORD with your keystore password.You can build the APK/AAB locally using npm run android:build, or let GitHub Actions build it for you by running npm run deploy.
npm run deploy generates .github/workflows/android.yml and pushes your project to GitHub:
npm run deploy to generate the CI workflow and push to GitHub.Once you have a signed .apk or .aab, you can distribute it. Depending on your goals, you have three options:
.apk on your website or GitHub Releases. This is common for beta testing, internal apps, and sideloading..aab to the Google Play Console.To publish on the Google Play Store, you need a Google Play Developer account. Upload the signed .aab from src-tauri/gen/android/app/build/outputs/bundle/release/ in the Play Console. See the Google Play Console guide for the specific steps.
If you are distributing directly (e.g., for internal testing), upload the signed .apk from src-tauri/gen/android/app/build/outputs/apk/release/ to your website or GitHub Releases. Users must enable "Install from unknown sources" on their device to sideload it.
For open-source apps, you can submit your project to F-Droid. See the F-Droid submission guide for the specific steps.
.aab, not a .apk. The `.apk` is only for direct download and sideloading.Build a native iOS app with App Store distribution and TestFlight.
Build a native Windows app with Authenticode signing and NSIS/MSI installers.
Build a native macOS app with Developer ID signing and notarization.
Build a native Linux app with AppImage, .deb, and .rpm bundles.