ElmonyDocs

Guides

Build a mobile app

Elmony's mobile workflow uses Expo, React Native, and EAS. Capacitor upgrades are no longer the primary mobile path.

Choose the right publish path

Mobile app

Use Expo/EAS builds and submit native binaries to Google Play or App Store Connect. Use RevenueCat for store subscriptions and in-app purchases, and Firebase for mobile authentication, Firestore, Storage, and native configuration.

Website

Publish a browser app through Elmony Hosting, GitHub, or Vercel. Websites do not need EAS credentials or app-store submission records. See the publishing guide .

Mobile workflow

  1. 1. Start a mobile project

    Choose Mobile App to begin in the design editor. Builder Step 2 creates the linked Expo SDK 55 and Expo Router codebase after you save the design.

  2. 2. Finish the design handoff

    Build the screens in the design editor, then continue to Builder Step 2. Elmony creates the code project and carries the design context into the builder.

  3. 3. Preview on a device

    Run the project, open Publish, and scan the Device preview QR code with Expo Go for SDK 55. Your computer and phone must be able to reach the preview server.

  4. 4. Prepare a release

    Use the Publish panel to connect Expo, configure EAS, run preflight checks, create preview or production builds, and submit a finished production build.

Device preview

Open the builder's Publish panel while the preview server is running. The Device preview card shows an Expo Go QR code and a copyable device URL. Install the Expo Go build for SDK 55 on Android or iPhone, then scan the code.

Expo Go is for development preview. A store release still requires an EAS production build, platform credentials, store records, and store review.

Connect the mobile services

  • Expo / EAS : save an Expo access token, choose the Expo owner, and configure the EAS project.
  • Firebase : connect a Google account and configure Auth, Firestore, Storage, rules, and native app identifiers when the project needs them.
  • RevenueCat : prepare Test Store billing for preview and Google Play or App Store products for a release. Direct Stripe checkout is an advanced mobile option; most store billing should use RevenueCat.

Build and submit

  1. In Publish, connect Expo and configure EAS for the selected app.
  2. Set the app name, icon, splash artwork, package name, and bundle identifier.
  3. Run the preflight checks and resolve every blocking issue.
  4. Create a preview build for device testing before creating a production build.
  5. Connect the Google Play or App Store Connect account and link the corresponding store app record.
  6. Check Store & billing readiness, then submit a successful production build. The first Android upload may need to be completed manually in Play Console before automated submissions can continue.

Older Capacitor projects

Elmony's current mobile stack is Expo/EAS, and the previous App Details upgrade controls are not shown. An existing Capacitor project can remain a web-plus-Capacitor codebase, but it does not gain the current Expo publishing workflow through an in-app upgrade.

For the supported mobile path, create a Mobile App project, finish the design-to-Builder handoff, and move the required screens, data, and assets into the new Expo project. Keep the original project and its Git history until the Expo version has passed device and store testing.

Troubleshooting

  • QR code does not open: keep the preview server running, confirm the phone can reach the computer, and copy the device URL to test it directly.
  • Preflight fails: review the diagnostics in Publish. You can copy them, attach them to chat, or ask Elmony to diagnose and fix the project.
  • Android signing fails: prepare or import Android credentials, then sync the signing SHA-1 to Firebase when Google sign-in is enabled.
  • Submission is blocked: make sure the production build finished, the store account is connected, the app record is linked, and the RevenueCat release key exists for that platform.