Installation & Build (Mobile)

The XetaSuite mobile app is built with React Native and Expo (SDK 55). It communicates with the XetaSuite backend via the Sanctum API and features an integrated voice assistant.

Prerequisites

• Node.js 20+
• npm 10+ or yarn
• Expo CLI (npx expo)
• EAS CLI for cloud builds (npm install -g eas-cli)
• An Expo account (free)
• For native Android builds locally: Android Studio with a configured Android SDK
• For native iOS builds locally: macOS + Xcode 15+

Tip

For production builds, EAS Build (cloud) is recommended and requires no local native environment.

Installation

1. Clone the repository

   git clone https://github.com/XetaSuite/Mobile.git
   cd Mobile

2. Install dependencies

   npm install

3. Configure environment variables

   Create a .env file at the root:

   EXPO_PUBLIC_API_URL=https://api.xetasuite.com

   For local development, point to your backend:

   EXPO_PUBLIC_API_URL=http://192.168.1.x:8000

   Caution

   Use your machine’s local IP address (not localhost) — the Android emulator cannot resolve localhost to the host machine.

4. Log in to Expo

   eas login

Running in development

Expo Go (quick)

Starts a development server compatible with the Expo Go app:

npx expo start

Scan the QR code with the Expo Go app on your phone.

Caution

Expo Go does not support all native modules (notably expo-speech-recognition). Use a dev client to test these features.

Dev Client (recommended)

Build a development client including all native modules:

# Build the dev client via EAS (cloud)
eas build --profile development --platform android

# Then start the server
npx expo start --dev-client

Android Emulator

With Android Studio configured:

npx expo run:android

Production build

Production builds are generated via EAS Build (Expo Application Services).

Android (AAB — Google Play)

eas build --platform android --profile production

The generated .aab file is ready for submission to the Google Play Store.

iOS (IPA — App Store)

eas build --platform ios --profile production

The generated .ipa file is ready for submission to the Apple App Store.

Both platforms simultaneously

eas build --platform all --profile production

Note

The production profile in eas.json uses autoIncrement: true — the Android versionCode and iOS buildNumber are incremented automatically with each build.

Available EAS profiles

Profile	Distribution	Format	Usage
development	Internal	APK	Testing with dev client
preview	Internal	APK	Internal testing before release
production	Store	AAB / IPA	Publishing to stores

Submitting to stores

Google Play Store

eas submit --platform android --latest

Apple App Store

eas submit --platform ios --latest

Tip

--latest automatically submits the most recent successful EAS build. You can also specify a build with --id <build-id>.

app.json configuration

Key application settings are in app.json:

{
  "expo": {
    "name": "XetaSuite-Mobile",
    "slug": "xetasuite-mobile",
    "version": "1.0.0",
    "android": {
      "package": "com.xetasuite.app"
    },
    "ios": {
      "bundleIdentifier": "com.xetasuite.app"
    }
  }
}

Caution

The Android package and iOS bundleIdentifier cannot be changed after the first store publication.

Required permissions

Android (android.permission.*)

Permission	Reason
RECORD_AUDIO	Voice assistant — voice transcription
MODIFY_AUDIO_SETTINGS	Microphone management during voice sessions
FOREGROUND_SERVICE	Keep audio session alive in the foreground
FOREGROUND_SERVICE_MEDIA_PLAYBACK	Foreground audio playback

iOS (Info.plist)

Key	Reason
NSMicrophoneUsageDescription	Microphone access for the voice assistant
NSSpeechRecognitionUsageDescription	System speech recognition (iOS)