Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AndrewwCO/Pana-Baker/llms.txt

Use this file to discover all available pages before exploring further.

During development you run Panahashi Baker through Expo Go, which lets you iterate quickly without a native build. When you are ready to distribute the app — to testers, through the Play Store, or through the App Store — you use EAS Build to compile a proper native binary. EAS Build runs on Expo’s cloud infrastructure, so you do not need Xcode or Android Studio installed on your machine for the build itself.
Expo Go is the fastest way to develop and test. Scan the QR code from expo start on a physical device and the app loads instantly. EAS Build is for production distribution — use it when you are ready to ship, not during daily development.

​
Available scripts

The following scripts are defined in package.json: 
"scripts": {
  "start":   "expo start",
  "android": "expo run:android",
  "ios":     "expo run:ios",
  "web":     "expo start --web"
}
  • start — Starts the Expo development server. Open Expo Go on your device and scan the QR code.
  • android — Builds and runs a local debug build on a connected Android device or emulator. Requires Android Studio.
  • ios — Builds and runs a local debug build on a connected iOS device or Simulator. Requires Xcode on macOS.
  • web — Starts the app in a browser via react-native-web.

​
Building for production with EAS

1

Install EAS CLI

Install the EAS command-line tool globally:
npm install -g eas-cli
2

Log in to your Expo account

eas login
If you do not have an Expo account, create one at expo.dev before running this command.
3

Build for Android or iOS

Run the build command for your target platform. EAS queues the build on Expo’s servers and streams logs back to your terminal.
eas build --platform android
When the build finishes, EAS provides a download link for the APK (Android) or IPA (iOS).
4

Download and distribute

  • Android — Install the APK directly on a device, upload it to the Google Play Console, or share the download link for internal testing.
  • iOS — Upload the IPA to App Store Connect using Transporter or eas submit, then distribute through TestFlight or the App Store.

​
iOS requirements

Building for iOS requires an active Apple Developer account ($99/year). EAS will prompt you to authenticate with Apple and may ask for provisioning profile and certificate details during the first build. You cannot distribute an iOS IPA without this account.

​
App identifiers

The bundle identifiers are set in app.json and must match what you register in the Apple Developer portal and Google Play Console: 
{
  "ios": {
    "bundleIdentifier": "com.panahashi.baker"
  },
  "android": {
    "package": "com.panahashi.baker"
  }
}
Do not change these after you have submitted a build to either store — changing the identifier creates a new app entry.

Firebase Auth setup

Configure authentication before building for production.

Connecting to your backend API

Set the production API URL before your EAS build.

Build docs developers (and LLMs) love

Get started for freeTalk to us