DocsPluginsShowcaseReleases
npmStar us on GitHub

Getting Started

IntroductionInstallationProject StructureLayouts and PagesLinking and Navigating

Routing

Folder-Based RoutingFile-Based RoutingDynamic RoutesParallel RoutesIntercepting RoutesCatch-All RoutesMDX & Markdown Pages

Special Files

Loading UIError BoundariesTemplateDefaultNot Found

Data Fetching

LoadersActionsAccessing Route Data

Metadata

Metadata & SEOOpen Graph & TwitterIcons & Favicons

API Routes

API Routes OverviewPlain Function HandlersHono IntegrationDynamic API Routes

Environment Variables

OverviewPrefixes & Client ExposureUsing in API Routes

Styling

CSS OverviewTailwind CSSCSS Modules

Platforms

WebWindowsmacOSLinuxAndroidiOS

Deployment

Deployment OverviewProduction ServerStatic ExportHosting Providers

A native React framework for building cross-platform applications from a single codebase.

Resources

  • Documentation
  • Plugins
  • Showcase
  • Releases

Community

  • GitHub Discussions
  • Reddit
  • Discord
  • LinkedIn

More

  • npm
  • GitHub
  • Issues
  • License

© 2026 Bini Cooperation.

macOS

Build native macOS desktop applications with Bini.js.

macOS Overview

Bini.js allows you to build native macOS desktop applications using Tauri v2. Your React app is wrapped in a WKWebView binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.

Native Binary

macOS app bundle (.app) with Developer ID signing

Code Signing

Developer ID and notarization support

Native APIs

Full access to macOS APIs via Tauri

macOS desktop apps are built using Tauri's WKWebView backend. Your app runs in a native window with full system access.

Requirements

Building macOS desktop apps requires different tools depending on your operating system. See the section for your OS below.

  • On macOS: Node.js, Xcode Command Line Tools, Full Xcode, and Rust - everything runs locally.
  • On Windows or Linux: Node.js, Git, a GitHub account, and the ability to push a repo. The macOS build itself runs on GitHub Actions.
You cannot produce a native macOS .app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for macOS. The recommended way is GitHub Actions on a macos-latest runner, described in each section below.

macOS

On macOS you can scaffold, develop, and build the app entirely on your own machine - no CI required.

Step 1: Install the tools

  • Node.js 20.19.0 or higher
  • Rust (stable toolchain via rustup)
  • Xcode Command Line Tools - run xcode-select --install
  • Full Xcode (for building and notarization) - Download

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:

>_Terminal
$ npx create-bini-app@latest my-app --platform desktop
$ cd my-app
$ npm install

Or run the interactive prompt and select Desktop (Windows, macOS, Linux):

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm
Tip: Pass --app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.

Step 3: Develop and build

Run tauri:dev to open your app in a native window, then tauri:build to produce the app bundle:

>_Terminal
$ npm run tauri:dev
>_Terminal
$ npm run tauri:build
Tip: Use create-bini-app sign desktop to set up Developer ID signing and notarization.

Windows

A native macOS .app cannot be produced on Windows - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.

Your Windows machinenpm run deployGitHub Actions (desktop.yml)macos app bundle

Step 1: Install the tools

Install Node.js 20.19.0 or higher and Git for Windows - Download.

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:

>_Terminal
$ npx create-bini-app@latest my-app --platform desktop
$ cd my-app
$ npm install

Or run the interactive prompt and select Desktop (Windows, macOS, Linux):

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
↑/↓ to navigate • Space: select • Enter: confirm
Tip: Pass --app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.

Push and build in CI

Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:

>_Terminal
$ npm run deploy
>_Terminal
◇
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm
◇
GitHub repository URL?
https://github.com/you/my-app
◇
Branch to push to?
● main (default)
○ + New branch...
◇
No .env.signing found. Run create-bini-app sign now?
●Yes/○No
◇
Sign macOS for GitHub Actions?
●Yes/○No
◇
Generate deployment files and push to GitHub?
●Yes/○No
◆
Commit message (press Enter for the default):
chore: add deployment configuration

Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.

Download the App

  1. Open your repository on GitHub and go to the Actions tab.
  2. Open the latest Desktop workflow run.
  3. Under Artifacts, download the macOS bundle (or, if a release was created, download the .dmg from the Releases page).
Why not build locally? Tauri's macOS build needs Xcode and Apple's signing toolchain, which do not exist on Windows. Cross-compiling from Windows to macOS is not supported. GitHub Actions on macos-latest is the supported path.

Linux

A native macOS .app cannot be produced on Linux - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.

Your Linux machinenpm run deployGitHub Actions (desktop.yml)macos app bundle

Step 1: Install the tools

Install Node.js 20.19.0 or higher and Git with your package manager, for example sudo apt install git on Debian and Ubuntu.

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:

>_Terminal
$ npx create-bini-app@latest my-app --platform desktop
$ cd my-app
$ npm install

Or run the interactive prompt and select Desktop (Windows, macOS, Linux):

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
↑/↓ to navigate • Space: select • Enter: confirm
Tip: Pass --app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.

Push and build in CI

Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:

>_Terminal
$ npm run deploy
>_Terminal
◇
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm
◇
GitHub repository URL?
https://github.com/you/my-app
◇
Branch to push to?
● main (default)
○ + New branch...
◇
No .env.signing found. Run create-bini-app sign now?
●Yes/○No
◇
Sign macOS for GitHub Actions?
●Yes/○No
◇
Generate deployment files and push to GitHub?
●Yes/○No
◆
Commit message (press Enter for the default):
chore: add deployment configuration

Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.

Download the App

  1. Open your repository on GitHub and go to the Actions tab.
  2. Open the latest Desktop workflow run.
  3. Under Artifacts, download the macOS bundle (or, if a release was created, download the .dmg from the Releases page).
Why not build locally? Tauri's macOS build needs Xcode and Apple's signing toolchain, which do not exist on Linux. Cross-compiling from Linux to macOS is not supported. GitHub Actions on macos-latest is the supported path.

Development

Running tauri:dev opens your app in a native macOS window. This requires a Mac with the requirements installed (see the macOS section):

>_Terminal
$ npm run tauri:dev

This launches your app in a native macOS window with:

  • Hot reload for frontend changes
  • Native window with menu bar integration
  • Access to macOS APIs
  • Devtools for debugging
On Windows or Linux, tauri:dev runs the Windows/Linux desktop app, not the macOS one. Use web development while iterating, and let CI build the macOS binary.

Building

Build a distributable macOS application with tauri:build. On macOS this runs locally; on Windows and Linux it runs in GitHub Actions (see those sections):

>_Terminal
$ npm run tauri:build

The build outputs land in src-tauri/target/release/bundle/:

Output Files

src-tauri
target
release
bundle
macos
my-app.app
dmg
my-app_0.1.0_aarch64.dmg
  • macos/my-app.app - The app bundle
  • dmg/*.dmg - Disk image for distribution (recommended)
  • my-app.pkg - Installer package (if configured)
The build output is a native macOS application that runs without any additional dependencies.

Code Signing

Bini.js supports Developer ID signing and notarization for macOS binaries. Set it up or redo it at any time with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.

Prerequisites

Signing requires an Apple Developer account. If you do not have one, enroll in the Apple Developer Program.

  • A "Developer ID Application" certificate exported as a .p12 file.
  • The password for the .p12 file.
  • Your 10-character Apple Team ID.
  • For notarization: an App Store Connect API key (Issuer ID, Key ID, and .p8 file) or your Apple ID and app-specific password.

Local Signing

To sign the .app locally on your Mac, import your .p12 certificate into your login keychain:

>_Terminal
$ npx create-bini-app sign desktop ./cert.p12 "pw" --identity "Developer ID Application: Your Name (TEAM_ID)"

GitHub Actions Signing

If you want the GitHub Action runner to sign the .app automatically, you must provide the certificate and notarization credentials via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:

>_Terminal
$ npx create-bini-app sign macos --ci-only

Signing values go into the git-ignored src-tauri/tauri.macos.conf.json, which Tauri merges automatically on macOS only, so the committed tauri.conf.json never points at a certificate that only exists on your machine:

{}src-tauri/tauri.macos.conf.json
{
  "bundle": {
    "macOS": {
      "signingIdentity": "Developer ID Application: Your Name (TEAM_ID)",
      "entitlements": "entitlements.plist"
    }
  }
}

Adding Secrets Manually

To sign and notarize the macOS build in GitHub Actions, you must add your credentials as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:

  1. Go to your repository on GitHub and navigate to Settings → Secrets and variables → Actions.
  2. Click New repository secret.
  3. Add APPLE_CERTIFICATE with the base64-encoded string of your .p12 file.
  4. Add APPLE_CERTIFICATE_PASSWORD with the password for your certificate.
  5. Add APPLE_SIGNING_IDENTITY with your identity string.
  6. Add KEYCHAIN_PASSWORD with a random password for the temporary keychain.
  7. For notarization, add APPLE_API_ISSUER, APPLE_API_KEY, and APPLE_API_KEY_P8 (or use APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID).
For production distribution, Developer ID signing and notarization are required to avoid Gatekeeper warnings. Never commit .env.signing, the .p12, or tauri.macos.conf.json.

Store Submission

Once you have a signed and notarized .app or .dmg, you can distribute it. Depending on your goals, you have three options:

  • Direct Download: Host the .dmg on your website or GitHub Releases. This is the most common option for desktop apps.
  • Mac App Store: Submit your app to the Mac App Store using App Store Connect.
  • Package Managers: Distribute via Homebrew for command-line installs.

Mac App Store

To publish on the Mac App Store, you need an Apple Developer account, an App Store distribution provisioning profile, and to upload your app using Xcode or Transporter. See the App Store submission guide for the specific steps.

Direct Download

If you are distributing directly, upload the signed and notarized .dmg from src-tauri/target/release/bundle/dmg/ to your website or GitHub Releases. Users can then download and install the app manually.

Package Managers

For command-line installs, you can submit a Cask to Homebrew. Users install your app with a command like brew install --cask my-app.

  • Homebrew: Submit a Cask to the Homebrew/homebrew-cask repository.
Tip: For direct download, always sign and notarize your app. Unsigned apps trigger Gatekeeper warnings, which deter users from installing your app.

Windows

Build a native Windows app with Authenticode signing and NSIS/MSI installers.

Linux

Build a native Linux app with AppImage, .deb, and .rpm bundles.

Android

Build a native Android app with keystore signing and Play Store support.

iOS

Build a native iOS app with App Store distribution and TestFlight.

Was this helpful?
PreviousWindows
NextLinux

On this page

  • macOS Overview
  • Requirements
  • macOS
  • Windows
  • Linux
  • Development
  • Building
  • Code Signing
  • Store Submission
Edit this page on GitHub

macOS

Build native macOS desktop applications with Bini.js.

macOS Overview

Bini.js allows you to build native macOS desktop applications using Tauri v2. Your React app is wrapped in a WKWebView binary, providing a native experience with full system access. The desktop target covers Windows, macOS and Linux from one src-tauri/.

Native Binary

macOS app bundle (.app) with Developer ID signing

Code Signing

Developer ID and notarization support

Native APIs

Full access to macOS APIs via Tauri

macOS desktop apps are built using Tauri's WKWebView backend. Your app runs in a native window with full system access.

Requirements

Building macOS desktop apps requires different tools depending on your operating system. See the section for your OS below.

  • On macOS: Node.js, Xcode Command Line Tools, Full Xcode, and Rust - everything runs locally.
  • On Windows or Linux: Node.js, Git, a GitHub account, and the ability to push a repo. The macOS build itself runs on GitHub Actions.
You cannot produce a native macOS .app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for macOS. The recommended way is GitHub Actions on a macos-latest runner, described in each section below.

macOS

On macOS you can scaffold, develop, and build the app entirely on your own machine - no CI required.

Step 1: Install the tools

  • Node.js 20.19.0 or higher
  • Rust (stable toolchain via rustup)
  • Xcode Command Line Tools - run xcode-select --install
  • Full Xcode (for building and notarization) - Download

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:

>_Terminal
$ npx create-bini-app@latest my-app --platform desktop
$ cd my-app
$ npm install

Or run the interactive prompt and select Desktop (Windows, macOS, Linux):

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm
Tip: Pass --app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.

Step 3: Develop and build

Run tauri:dev to open your app in a native window, then tauri:build to produce the app bundle:

>_Terminal
$ npm run tauri:dev
>_Terminal
$ npm run tauri:build
Tip: Use create-bini-app sign desktop to set up Developer ID signing and notarization.

Windows

A native macOS .app cannot be produced on Windows - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.

Your Windows machinenpm run deployGitHub Actions (desktop.yml)macos app bundle

Step 1: Install the tools

Install Node.js 20.19.0 or higher and Git for Windows - Download.

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:

>_Terminal
$ npx create-bini-app@latest my-app --platform desktop
$ cd my-app
$ npm install

Or run the interactive prompt and select Desktop (Windows, macOS, Linux):

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
↑/↓ to navigate • Space: select • Enter: confirm
Tip: Pass --app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.

Push and build in CI

Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:

>_Terminal
$ npm run deploy
>_Terminal
◇
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm
◇
GitHub repository URL?
https://github.com/you/my-app
◇
Branch to push to?
● main (default)
○ + New branch...
◇
No .env.signing found. Run create-bini-app sign now?
●Yes/○No
◇
Sign macOS for GitHub Actions?
●Yes/○No
◇
Generate deployment files and push to GitHub?
●Yes/○No
◆
Commit message (press Enter for the default):
chore: add deployment configuration

Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.

Download the App

  1. Open your repository on GitHub and go to the Actions tab.
  2. Open the latest Desktop workflow run.
  3. Under Artifacts, download the macOS bundle (or, if a release was created, download the .dmg from the Releases page).
Why not build locally? Tauri's macOS build needs Xcode and Apple's signing toolchain, which do not exist on Windows. Cross-compiling from Windows to macOS is not supported. GitHub Actions on macos-latest is the supported path.

Linux

A native macOS .app cannot be produced on Linux - Tauri relies on macOS-only toolchains (Xcode, code signing, notarization). The Tauri team's own recommendation is to build macOS apps on a macos-latest runner in CI.

Your Linux machinenpm run deployGitHub Actions (desktop.yml)macos app bundle

Step 1: Install the tools

Install Node.js 20.19.0 or higher and Git with your package manager, for example sudo apt install git on Debian and Ubuntu.

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting desktop (Windows, macOS and Linux share one src-tauri/) and install its dependencies:

>_Terminal
$ npx create-bini-app@latest my-app --platform desktop
$ cd my-app
$ npm install

Or run the interactive prompt and select Desktop (Windows, macOS, Linux):

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
↑/↓ to navigate • Space: select • Enter: confirm
Tip: Pass --app-name "My App" and --org com.acme to skip the native naming prompts, and --sign / --nosign to control code-signing setup.

Push and build in CI

Run npm run deploy and choose Desktop. bini-deploy writes .github/workflows/desktop.yml — a matrix job that builds Windows, macOS and Linux on their own GitHub runners — stages everything, and pushes to your repository:

>_Terminal
$ npm run deploy
>_Terminal
◇
Platforms?
◻ Web Application
◼ Desktop (Windows, macOS, Linux)
◻ Android
◻ iOS
↑/↓ to navigate • Space: select • Enter: confirm
◇
GitHub repository URL?
https://github.com/you/my-app
◇
Branch to push to?
● main (default)
○ + New branch...
◇
No .env.signing found. Run create-bini-app sign now?
●Yes/○No
◇
Sign macOS for GitHub Actions?
●Yes/○No
◇
Generate deployment files and push to GitHub?
●Yes/○No
◆
Commit message (press Enter for the default):
chore: add deployment configuration

Once pushed, the workflow runs on real windows-latest, macos-latest and ubuntu-latest runners and uploads the installers as run artifacts.

Download the App

  1. Open your repository on GitHub and go to the Actions tab.
  2. Open the latest Desktop workflow run.
  3. Under Artifacts, download the macOS bundle (or, if a release was created, download the .dmg from the Releases page).
Why not build locally? Tauri's macOS build needs Xcode and Apple's signing toolchain, which do not exist on Linux. Cross-compiling from Linux to macOS is not supported. GitHub Actions on macos-latest is the supported path.

Development

Running tauri:dev opens your app in a native macOS window. This requires a Mac with the requirements installed (see the macOS section):

>_Terminal
$ npm run tauri:dev

This launches your app in a native macOS window with:

  • Hot reload for frontend changes
  • Native window with menu bar integration
  • Access to macOS APIs
  • Devtools for debugging
On Windows or Linux, tauri:dev runs the Windows/Linux desktop app, not the macOS one. Use web development while iterating, and let CI build the macOS binary.

Building

Build a distributable macOS application with tauri:build. On macOS this runs locally; on Windows and Linux it runs in GitHub Actions (see those sections):

>_Terminal
$ npm run tauri:build

The build outputs land in src-tauri/target/release/bundle/:

Output Files

src-tauri
target
release
bundle
macos
my-app.app
dmg
my-app_0.1.0_aarch64.dmg
  • macos/my-app.app - The app bundle
  • dmg/*.dmg - Disk image for distribution (recommended)
  • my-app.pkg - Installer package (if configured)
The build output is a native macOS application that runs without any additional dependencies.

Code Signing

Bini.js supports Developer ID signing and notarization for macOS binaries. Set it up or redo it at any time with create-bini-app sign. If you only need signing for GitHub Actions, use the --ci-only flag.

Prerequisites

Signing requires an Apple Developer account. If you do not have one, enroll in the Apple Developer Program.

  • A "Developer ID Application" certificate exported as a .p12 file.
  • The password for the .p12 file.
  • Your 10-character Apple Team ID.
  • For notarization: an App Store Connect API key (Issuer ID, Key ID, and .p8 file) or your Apple ID and app-specific password.

Local Signing

To sign the .app locally on your Mac, import your .p12 certificate into your login keychain:

>_Terminal
$ npx create-bini-app sign desktop ./cert.p12 "pw" --identity "Developer ID Application: Your Name (TEAM_ID)"

GitHub Actions Signing

If you want the GitHub Action runner to sign the .app automatically, you must provide the certificate and notarization credentials via GitHub Secrets. Use the --ci-only flag to configure it without setting up local signing:

>_Terminal
$ npx create-bini-app sign macos --ci-only

Signing values go into the git-ignored src-tauri/tauri.macos.conf.json, which Tauri merges automatically on macOS only, so the committed tauri.conf.json never points at a certificate that only exists on your machine:

{}src-tauri/tauri.macos.conf.json
{
  "bundle": {
    "macOS": {
      "signingIdentity": "Developer ID Application: Your Name (TEAM_ID)",
      "entitlements": "entitlements.plist"
    }
  }
}

Adding Secrets Manually

To sign and notarize the macOS build in GitHub Actions, you must add your credentials as repository secrets. bini-deploy does not upload secrets automatically. You must add them manually:

  1. Go to your repository on GitHub and navigate to Settings → Secrets and variables → Actions.
  2. Click New repository secret.
  3. Add APPLE_CERTIFICATE with the base64-encoded string of your .p12 file.
  4. Add APPLE_CERTIFICATE_PASSWORD with the password for your certificate.
  5. Add APPLE_SIGNING_IDENTITY with your identity string.
  6. Add KEYCHAIN_PASSWORD with a random password for the temporary keychain.
  7. For notarization, add APPLE_API_ISSUER, APPLE_API_KEY, and APPLE_API_KEY_P8 (or use APPLE_ID, APPLE_PASSWORD, APPLE_TEAM_ID).
For production distribution, Developer ID signing and notarization are required to avoid Gatekeeper warnings. Never commit .env.signing, the .p12, or tauri.macos.conf.json.

Store Submission

Once you have a signed and notarized .app or .dmg, you can distribute it. Depending on your goals, you have three options:

  • Direct Download: Host the .dmg on your website or GitHub Releases. This is the most common option for desktop apps.
  • Mac App Store: Submit your app to the Mac App Store using App Store Connect.
  • Package Managers: Distribute via Homebrew for command-line installs.

Mac App Store

To publish on the Mac App Store, you need an Apple Developer account, an App Store distribution provisioning profile, and to upload your app using Xcode or Transporter. See the App Store submission guide for the specific steps.

Direct Download

If you are distributing directly, upload the signed and notarized .dmg from src-tauri/target/release/bundle/dmg/ to your website or GitHub Releases. Users can then download and install the app manually.

Package Managers

For command-line installs, you can submit a Cask to Homebrew. Users install your app with a command like brew install --cask my-app.

  • Homebrew: Submit a Cask to the Homebrew/homebrew-cask repository.
Tip: For direct download, always sign and notarize your app. Unsigned apps trigger Gatekeeper warnings, which deter users from installing your app.

Windows

Build a native Windows app with Authenticode signing and NSIS/MSI installers.

Linux

Build a native Linux app with AppImage, .deb, and .rpm bundles.

Android

Build a native Android app with keystore signing and Play Store support.

iOS

Build a native iOS app with App Store distribution and TestFlight.

Was this helpful?
PreviousWindows
NextLinux

On this page

  • macOS Overview
  • Requirements
  • macOS
  • Windows
  • Linux
  • Development
  • Building
  • Code Signing
  • Store Submission
Edit this page on GitHub