Skip to main content

Mobile Build Overview

WaveMaker enables building React Native mobile applications for iOS and Android through three methods: AppChef (cloud GUI), wm-reactnative-cli (local/CI-CD), and Expo EAS Build. Each method generates signed APK, AAB, or IPA packages ready for testing or app store submission.

Build Methods​

Cloud-based build service with web interface.

Use when:

  • Quick builds without local setup
  • No Android SDK or Xcode installed
  • GUI-based workflow preferred
  • Team testing with QR codes

Limitations:

  • 25 apps maximum
  • 10 builds per app
  • Certificate upload required

Learn more: AppChef

Command-line tool for local or CI/CD builds.

Use when:

  • CI/CD pipeline integration needed
  • Enterprise on-premise builds
  • Certificate security critical
  • Unlimited builds required

Requirements:

  • Node.js 18.16.1, Java 11, Maven 3.8.6
  • Android SDK (for Android)
  • macOS + Xcode (for iOS)

Learn more: CLI Builds

Expo EAS Build​

Cloud builds using Expo infrastructure.

Use when:

  • Expo ecosystem integration
  • Custom native code with expo-dev-client
  • Automated certificate management

Pricing:

  • Free: 30 builds/month
  • Production: $29/month (unlimited)

Learn more: Expo Builds

Prerequisites​

For All Methods​

From WaveMaker Studio:

  • Export React Native zip from Studio
  • Application configured (name, ID, version)

Certificates:

Android:

  • Keystore file (.keystore or .jks)
  • Keystore password, key alias, key password
  • Generate: keytool -genkey -v -keystore release.keystore
  • Learn more: Android Keystore Generation

iOS:

  • P12 certificate (Development or Distribution)
  • Provisioning profile (.mobileprovision)
  • Apple Developer account ($99/year)
  • Learn more: iOS Certificates

Method-Specific Prerequisites​

AppChef:

  • Web browser only
  • AppChef account (included with WaveMaker)

CLI:

  • Android: Android SDK, ANDROID_HOME variable
  • iOS: macOS, Xcode, CocoaPods
  • Install CLI: npm install -g @wavemaker/wm-reactnative-cli

Expo:

Build Outputs​

Android​

APK (Android Package Kit):

  • Direct device installation
  • Testing and internal distribution
  • Single file for all devices

AAB (Android App Bundle):

  • Google Play Store required format (new apps)
  • Optimized, smaller downloads
  • Cannot install directly

iOS​

IPA (iOS App Store Package):

  • All distribution methods
  • Provisioning profile determines installation:
    • Development: Registered devices only
    • Ad Hoc: Up to 100 registered devices
    • App Store: App Store distribution only
    • Enterprise: Unlimited devices (internal)

Build Types​

Development Builds​

Purpose: Testing, debugging, QA

Android:

  • Debug keystore (auto-generated)
  • APK output
  • Installable via QR code

iOS:

  • Development certificate required
  • Device UUID registration required
  • Development provisioning profile

Production Builds​

Purpose: App store submission

Android:

  • Production keystore required
  • AAB output (Play Store)
  • Code signing with release certificate

iOS:

  • Distribution certificate required
  • App Store provisioning profile
  • TestFlight or direct App Store upload

Comparison​

FeatureAppChefCLIExpo
SetupNoneNode, Java, SDKsExpo CLI
Build locationCloudLocal/CI-CDCloud
iOS buildsAny OSmacOS onlyAny OS
Build limits25 apps, 10 builds/appUnlimited30/month (free)
CostFreeFreeFree/Paid
QR codesAuto-generatedNoNo
CI/CDLimitedExcellentGood
Best forQuick testingProduction CI/CDExpo ecosystem

Quick Start​

1. Export from Studio:

File → Export → React Native Zip

2. Choose build method and follow guide:

3. Configure app details:

  • Application name, ID, version
  • Platform settings
  • Certificates

4. Build and test:

  • Trigger build
  • Download APK/AAB/IPA
  • Install on devices or submit to stores

Build Documentation:

Publishing Documentation:

External Resources: