Introduction
The mobile stack we use for builds, updates, and notifications.
Our mobile stack stays the same regardless of project complexity. We optimize for predictable releases, fast iteration, and a consistent push notification setup across iOS and Android.
When to use this guide
- You are building a React Native app that needs builds, OTA updates, or push notifications.
- You want a consistent mobile release process across iOS and Android.
- You need a predictable setup that works the same way for MVPs and large-scale apps.
Prerequisites
- A React Native (Expo) project is initialized.
- Team has access to Apple Developer and Google Play Console accounts.
Estimated pricing
- Free – $20/month depending on EAS build volume and team size.
- Expo free tier covers most early-stage needs but require you to wait in build queues. Paid plans add more build concurrency and team seats.
Stack
- EAS — builds, submissions, and OTA updates
- FCM / APNs via Expo Notifications — push notifications for Android and iOS
What you will implement
- Account setup for Expo (EAS), App Store Connect, and Google Play Console.
- Local tooling setup (
eas-cli). - Push notification configuration with Firebase and APNs.
- OTA update workflow for shipping fixes without app store review.
Verify
- App builds successfully via EAS for both iOS and Android.
- Push notifications are delivered on both platforms.
- OTA updates reach devices without requiring a new binary.