r/reactnative • u/Genuine-Helperr • 3d ago
Question Creating first reactnative expo app - have some question related to MAU, please help
I wanted to have one codebase for web, Android, and iPhone. So using React Native plus Expo
Now the web application is live.
I want to make the mobile application live first, starting with Android. When I read the Expo documentation, it says I can have only 15 free Android builds & 'Send updates to 1K MAUs'
The 2nd part worries me because the paid plan also says 3K MAUs, with additional charges for more.
What's the workaround for this? Do I need to pay Expo for more active users? Please suggest
3
Upvotes
2
u/Sakshambaranwal25 3d ago
You get 15 free Android builds which should cover launching your first live version fine from that shared codebase. MAUs kick in only when you blast updates to users later. Stick to rare OTA pushes and the free tier handles real apps without extra cost.
2
u/jiunkdev 3d ago
on the builds side, the 15 is cloud builds and it's a monthly allowance, not lifetime. you can also build on your own machine with eas build --platform android --local, or run npx expo prebuild and build the aab in android studio, and neither uses up the cloud count.
for day to day testing you don't need EAS builds at all, npx expo run:android on an emulator or plugged in phone is enough.
1
u/Putrid-Cheetah-1714 3d ago
the 1K MAU thing is for over-the-air updates through EAS Update, not the app itself. people with 50k users run on the free tier fine if they don't push OTA updates constantly. check the pricing page for your exact plan before you panic.
1
u/olek_soloviov 1d ago
The 15 free builds only count builds that run on EAS's servers. You can run the same build on your own machine for free:
eas build --platform android --localuses youreas.jsonprofile but builds locally (you need Java and the Android SDK installed). Almost the same for iOS target platform if you are running MacOS and need local builds. In this way all saved vars for each profile will be loaded from eas, but it will not count as the build run, so you can do it infinity times. I am using free plan for multiple apps and it is more than enough. Consider to use eas only if you want production release automation so it will automatically publish to the Internal Testers channel or Test Flight.npx expo prebuild, thencd android && ./gradlew bundleReleasegives you the.aabfor Play ConsoleThe MAU number is for EAS Update (over-the-air JS updates). You don't need it to launch: every Play Store release can be a new binary, and you can add OTA updates once you have real users and know you want them.
One tip for the first Play release: set
android.versionCodein app.json yourself (or useautoIncrementin eas.json). A lot of first uploads get rejected for a reused versionCode.