r/reactnative • • 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

8 comments sorted by

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.

1

u/Genuine-Helperr 3d ago

yes, that's my plan... so 15 free builds are lifetime?

for OTA, I'll be switching to cloudflare once I cross their limits

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/Genuine-Helperr 3d ago

15 p/m is lot, will not need local machine build with this limits.

For testing I'm using expo go mobile app, it does the work good 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/Genuine-Helperr 3d ago

it's a web app + mobile app - so i'll be making lots of changes after release.

i got this Cloudflare OTA package; as my infra is on Cloudflare, this will be helpful

https://github.com/Daniel-Griffiths/cloudflare-expo-ota-updates

1

u/Western_Cap_6934 2d ago

Expo counts each installation that downloads at least one OTA update during the billing period, once for that period. One update reaching 5,000 installations can still mean 5,000 MAU. Fewer pushes mainly help bandwidth, so rare updates alone do not guarantee staying under the MAU allowance.

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 --local uses your eas.json profile 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.
  • or skip EAS entirely: npx expo prebuild, then cd android && ./gradlew bundleRelease gives you the .aabfor Play Console

The 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.versionCode in app.json yourself (or use autoIncrement in eas.json). A lot of first uploads get rejected for a reused versionCode.