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.

iOS

Build native iOS mobile applications with Bini.js.

iOS Overview

Bini.js allows you to build native iOS mobile applications using Tauri v2. Your React app runs inside a WKWebView with full access to native iOS APIs and features.

Native iOS App

Real native WKWebView, not a wrapper

Code Signing

Xcode-managed automatic signing

Auto Plugin Wiring

bini-native wires iOS permissions

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

Requirements

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

  • On macOS: Xcode, Xcode Command Line Tools, CocoaPods, Node.js, and Rust with iOS targets - everything runs locally.
  • On Windows or Linux: Node.js, Git, a GitHub account, and the ability to push a repo. The iOS build itself runs on GitHub Actions.
You cannot produce a native iOS .app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for iOS. 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 iOS app entirely on your own machine - no CI required.

Step 1: Install the tools

  • macOS 11 (Big Sur) or higher
  • Node.js 20.19.0 or higher
  • Xcode - Download from the Mac App Store
  • Xcode Command Line Tools - run xcode-select --install
  • CocoaPods - run sudo gem install cocoapods
  • Rust via rustup. Tauri automatically adds the required iOS targets for you.

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting iOS, install its dependencies, and install its pods:

>_Terminal
$ npx create-bini-app@latest my-app --platform ios
$ cd my-app
$ npm install
$ pod install --project-directory=src-tauri/gen/ios

Or run the interactive prompt and select iOS:

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◻ Desktop (Windows, macOS, Linux)
◻ Android
◼ iOS
↑/↓ to navigate • Space: select • Enter: confirm

Step 3: Develop and build locally

Run ios to launch on the simulator or a connected device, then ios:build to produce the app bundle:

>_Terminal
$ npm run ios
>_Terminal
$ npm run ios:build

Build in GitHub Actions

Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:

>_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 iOS 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
Tip: Xcode handles signing automatically with your Apple ID for development builds. For CI builds, you can skip local Xcode setup entirely.

Windows

A native iOS .app cannot be produced on Windows - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Windows.

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

Workflow for Windows Users

Since the scaffold does not offer iOS as an option on Windows, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.

  1. Scaffold the project with Android: npx create-bini-app@latest my-app --platform android
  2. Develop and test your app locally using npm run android.
  3. Run npm run deploy and choose iOS.

Build in GitHub Actions

Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:

>_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 iOS 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
Why not build locally? Tauri's iOS build needs Xcode and Apple's signing toolchain, which do not exist on Windows. GitHub Actions on macos-latest is the supported path.

Linux

A native iOS .app cannot be produced on Linux - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Linux.

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

Workflow for Linux Users

Since the scaffold does not offer iOS as an option on Linux, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.

  1. Scaffold the project with Android: npx create-bini-app@latest my-app --platform android
  2. Develop and test your app locally using npm run android.
  3. Run npm run deploy and choose iOS.

Build in GitHub Actions

Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:

>_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 iOS 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
Why not build locally? Tauri's iOS build needs Xcode and Apple's signing toolchain, which do not exist on Linux. GitHub Actions on macos-latest is the supported path.

Development

Running ios opens your app on the iOS Simulator or a connected device. This requires a Mac with Xcode installed (see the macOS section):

>_Terminal
$ npm run ios

This launches your app with:

  • Hot reload for frontend changes
  • Native iOS integration
  • Auto-wired native APIs via bini-native
  • Safari Web Inspector for debugging

Setting Up a Simulator

  1. Open Xcode
  2. Go to Settings → Platforms
  3. Download a simulator for your target iOS version
  4. Run npm run ios

Building

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

>_Terminal
$ npm run ios:build

The build outputs land in src-tauri/gen/ios/:

Output Files

src-tauri
gen
ios
build
my-app.app
my-app.ipa
  • my-app.app - iOS app bundle (for simulator/testing)
  • my-app.ipa - iOS App Store package (for distribution)
The build output is a native iOS app that runs on iOS 13.0 and above.

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.

  • An "Apple Distribution" certificate exported as a .p12 file (for CI builds).
  • The password for the .p12 file.
  • Your 10-character Apple Team ID.
  • A provisioning profile (.mobileprovision) for CI builds, or use Xcode's automatic signing for local development.

Local Signing

For local development, Xcode handles signing automatically. You can either open the project in Xcode or run:

>_Terminal
$ npx create-bini-app sign ios

In Xcode, select the project → Signing & Capabilities → choose your Team.

GitHub Actions Signing

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

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

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 IOS_CERTIFICATE with the base64-encoded string of your .p12 file.
  4. Add IOS_CERTIFICATE_PASSWORD with the password for your certificate.
  5. Add IOS_MOBILE_PROVISION with the base64-encoded string of your .mobileprovision file.
  6. Add APPLE_DEVELOPMENT_TEAM with your Apple Team ID.
  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 App Store distribution, you need an Apple Developer account and provisioning profiles. Development builds use Xcode's automatic signing.

Deployment

You can build the iOS app locally on macOS using npm run ios:build, or let GitHub Actions build it for you by running npm run deploy.

Deploying via GitHub Actions

npm run deploy generates .github/workflows/ios.yml and pushes your project to GitHub:

>_Terminal
$ npm run deploy

Deployment Flow

  1. Run npm run deploy to generate the CI workflow and push to GitHub.
  2. GitHub Actions builds the signed IPA (if secrets are set) and attaches it to the run as an artifact.
  3. Download the artifact and upload it to App Store Connect manually.

Store Submission

Once you have a signed .ipa or .app, you can distribute it. Depending on your goals, you have two options:

  • TestFlight: Upload the .ipa to App Store Connect for beta testing with external users.
  • App Store: Submit the .ipa to the App Store for public release.

TestFlight

TestFlight allows you to distribute beta builds to up to 10,000 external testers. Upload the .ipa to App Store Connect (via Xcode, Transporter, or the App Store Connect API), and invite testers via the App Store Connect dashboard. See the TestFlight guide for the specific steps.

App Store

To publish on the App Store, you need an Apple Developer Program membership. Upload the .ipa to App Store Connect, fill out the app metadata and screenshots, and submit it for review. See the App Store submission guide for the specific steps.

Tip: For local development and testing, Xcode can install the app directly onto your device via ios:build. For distribution, you must use App Store Connect.

Android

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

Windows

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

macOS

Build a native macOS app with Developer ID signing and notarization.

Linux

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

Was this helpful?
PreviousAndroid
NextDeployment

On this page

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

iOS

Build native iOS mobile applications with Bini.js.

iOS Overview

Bini.js allows you to build native iOS mobile applications using Tauri v2. Your React app runs inside a WKWebView with full access to native iOS APIs and features.

Native iOS App

Real native WKWebView, not a wrapper

Code Signing

Xcode-managed automatic signing

Auto Plugin Wiring

bini-native wires iOS permissions

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

Requirements

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

  • On macOS: Xcode, Xcode Command Line Tools, CocoaPods, Node.js, and Rust with iOS targets - everything runs locally.
  • On Windows or Linux: Node.js, Git, a GitHub account, and the ability to push a repo. The iOS build itself runs on GitHub Actions.
You cannot produce a native iOS .app directly from Windows or Linux. Tauri v2 has no supported local cross-compilation path for iOS. 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 iOS app entirely on your own machine - no CI required.

Step 1: Install the tools

  • macOS 11 (Big Sur) or higher
  • Node.js 20.19.0 or higher
  • Xcode - Download from the Mac App Store
  • Xcode Command Line Tools - run xcode-select --install
  • CocoaPods - run sudo gem install cocoapods
  • Rust via rustup. Tauri automatically adds the required iOS targets for you.

Step 2: Create the project

Create the Project

Create a new Bini.js project targeting iOS, install its dependencies, and install its pods:

>_Terminal
$ npx create-bini-app@latest my-app --platform ios
$ cd my-app
$ npm install
$ pod install --project-directory=src-tauri/gen/ios

Or run the interactive prompt and select iOS:

>_Terminal
$ npx create-bini-app@latest
>_Terminal
◆
Platforms?
◻ Web Application
◻ Desktop (Windows, macOS, Linux)
◻ Android
◼ iOS
↑/↓ to navigate • Space: select • Enter: confirm

Step 3: Develop and build locally

Run ios to launch on the simulator or a connected device, then ios:build to produce the app bundle:

>_Terminal
$ npm run ios
>_Terminal
$ npm run ios:build

Build in GitHub Actions

Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:

>_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 iOS 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
Tip: Xcode handles signing automatically with your Apple ID for development builds. For CI builds, you can skip local Xcode setup entirely.

Windows

A native iOS .app cannot be produced on Windows - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Windows.

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

Workflow for Windows Users

Since the scaffold does not offer iOS as an option on Windows, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.

  1. Scaffold the project with Android: npx create-bini-app@latest my-app --platform android
  2. Develop and test your app locally using npm run android.
  3. Run npm run deploy and choose iOS.

Build in GitHub Actions

Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:

>_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 iOS 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
Why not build locally? Tauri's iOS build needs Xcode and Apple's signing toolchain, which do not exist on Windows. GitHub Actions on macos-latest is the supported path.

Linux

A native iOS .app cannot be produced on Linux - Tauri relies on Xcode, Apple's signing toolchain, and CocoaPods, none of which run on Linux.

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

Workflow for Linux Users

Since the scaffold does not offer iOS as an option on Linux, you should first scaffold an Android project, develop and test your app there, and then let GitHub Actions build the iOS app for you.

  1. Scaffold the project with Android: npx create-bini-app@latest my-app --platform android
  2. Develop and test your app locally using npm run android.
  3. Run npm run deploy and choose iOS.

Build in GitHub Actions

Run npm run deploy and choose iOS. bini-deploy writes .github/workflows/ios.yml and pushes your project to GitHub. The workflow builds the iOS app on a macos-latest runner:

>_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 iOS 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
Why not build locally? Tauri's iOS build needs Xcode and Apple's signing toolchain, which do not exist on Linux. GitHub Actions on macos-latest is the supported path.

Development

Running ios opens your app on the iOS Simulator or a connected device. This requires a Mac with Xcode installed (see the macOS section):

>_Terminal
$ npm run ios

This launches your app with:

  • Hot reload for frontend changes
  • Native iOS integration
  • Auto-wired native APIs via bini-native
  • Safari Web Inspector for debugging

Setting Up a Simulator

  1. Open Xcode
  2. Go to Settings → Platforms
  3. Download a simulator for your target iOS version
  4. Run npm run ios

Building

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

>_Terminal
$ npm run ios:build

The build outputs land in src-tauri/gen/ios/:

Output Files

src-tauri
gen
ios
build
my-app.app
my-app.ipa
  • my-app.app - iOS app bundle (for simulator/testing)
  • my-app.ipa - iOS App Store package (for distribution)
The build output is a native iOS app that runs on iOS 13.0 and above.

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.

  • An "Apple Distribution" certificate exported as a .p12 file (for CI builds).
  • The password for the .p12 file.
  • Your 10-character Apple Team ID.
  • A provisioning profile (.mobileprovision) for CI builds, or use Xcode's automatic signing for local development.

Local Signing

For local development, Xcode handles signing automatically. You can either open the project in Xcode or run:

>_Terminal
$ npx create-bini-app sign ios

In Xcode, select the project → Signing & Capabilities → choose your Team.

GitHub Actions Signing

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

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

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 IOS_CERTIFICATE with the base64-encoded string of your .p12 file.
  4. Add IOS_CERTIFICATE_PASSWORD with the password for your certificate.
  5. Add IOS_MOBILE_PROVISION with the base64-encoded string of your .mobileprovision file.
  6. Add APPLE_DEVELOPMENT_TEAM with your Apple Team ID.
  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 App Store distribution, you need an Apple Developer account and provisioning profiles. Development builds use Xcode's automatic signing.

Deployment

You can build the iOS app locally on macOS using npm run ios:build, or let GitHub Actions build it for you by running npm run deploy.

Deploying via GitHub Actions

npm run deploy generates .github/workflows/ios.yml and pushes your project to GitHub:

>_Terminal
$ npm run deploy

Deployment Flow

  1. Run npm run deploy to generate the CI workflow and push to GitHub.
  2. GitHub Actions builds the signed IPA (if secrets are set) and attaches it to the run as an artifact.
  3. Download the artifact and upload it to App Store Connect manually.

Store Submission

Once you have a signed .ipa or .app, you can distribute it. Depending on your goals, you have two options:

  • TestFlight: Upload the .ipa to App Store Connect for beta testing with external users.
  • App Store: Submit the .ipa to the App Store for public release.

TestFlight

TestFlight allows you to distribute beta builds to up to 10,000 external testers. Upload the .ipa to App Store Connect (via Xcode, Transporter, or the App Store Connect API), and invite testers via the App Store Connect dashboard. See the TestFlight guide for the specific steps.

App Store

To publish on the App Store, you need an Apple Developer Program membership. Upload the .ipa to App Store Connect, fill out the app metadata and screenshots, and submit it for review. See the App Store submission guide for the specific steps.

Tip: For local development and testing, Xcode can install the app directly onto your device via ios:build. For distribution, you must use App Store Connect.

Android

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

Windows

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

macOS

Build a native macOS app with Developer ID signing and notarization.

Linux

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

Was this helpful?
PreviousAndroid
NextDeployment

On this page

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