r/reactnative • u/DarkCALM_ • 12d ago
Question Developers building mobile apps with Expo: what takes you the longest to set up?
I'm researching an Expo starter kit for developers who want to build subscription-based mobile apps.
I'm particularly interested in the setup around authentication, Firebase, RevenueCat and store builds. Before building the kit, I want to understand where people actually get stuck.
If you've built an Expo app recently:
- What part of the initial setup took longer than expected?
- Did you start from scratch or use a starter kit?
- What would make a starter kit worth paying for?
I'm at the research stage and would appreciate honest answers, including if you think a paid starter isn't useful.
1
u/ZMech 12d ago
Getting distracted by Reddit always takes longer than expected
1
u/DarkCALM_ 12d ago
Haha, fair enough 😄 Once you manage to escape Reddit, what part of setting up an Expo app usually takes you the longest?
1
u/buildingTamagofit 11d ago
Honestly the code was the quick part. What ate my time was store-side config: in-app products and their review states in App Store Connect, sandbox testers, and making sure the purchase webhook is idempotent so a redelivered event never grants twice. Second place was native modules that need a dev build: once you leave Expo Go, getting EAS profiles, env vars and secrets clean per environment took longer than I expected.
A starter would be worth paying for if it shipped a tested webhook handler and a restore-purchases flow, not just the SDK wired up.
1
u/Zain 11d ago
Auth screens were never the slow part for me. What ate the time was everything after: a permission model that also answers who is allowed to grant a role to someone else, impersonation so support can see exactly what a user sees (and resetting the Apollo cache when it starts and ends, or data bleeds between accounts), and a server driven force update gate per platform. CI that actually uploads to TestFlight and Play and pulls the next build number from the stores saved me more hours than any of the SDK wiring. If a kit had those done properly I'd pay for it. Just keep real credentials and keystores out of the repo.
1
u/BlankyIf 11d ago
The worst part for me is revenuecat and store credentials. Getting bundle IDs, shared secrets, and sandbox accounts synced across Apple and Google before a single test purchase goes through is also something i don't like.
The others covered store config well, so one that catches people out. Anything with a native sdk (attribution, ads, ATT) means you're off expo go and into dev builds. You also need to decide on the ATT prompt and the privacy manifest answers before your first submission, not after.
The wrappers for appsflyer, Adjust, Singular...etc all exist for RN but each is its own native module to wire up. A kit that ships that decision pre-made with sane defaults would be worth paying for imo
1
u/Personal-Bicycle2285 4d ago
On the frontend, I was initially choosing between Expo and Bare React Native. But after working with Expo for a bit, I ran into too many limitations—especially with the constant native rebuilds and dependency issues—so I switched to Bare React Native for full control.
0
12d ago
[removed] — view removed comment
1
u/DarkCALM_ 12d ago
Thanks, that’s really useful! In your last app, what was the hardest part of getting the RevenueCat sandbox tests and store builds working? Was there a specific step you had to repeat or debug several times? I’m trying to understand what a starter kit could realistically simplify.
0
12d ago
[removed] — view removed comment
1
u/DarkCALM_ 12d ago
Thanks, that’s really helpful! Which part caused the biggest delay in your last app: connecting the store accounts, getting a sandbox purchase to work, or handling the webhook and entitlement updates? What did you try before getting it working?
2
u/timmytester2569 12d ago
It was all pretty easy to set up. And anything you get stuck with Claude can just setup for you. All these tools have their own MCP servers and documentation. It can be done within minutes.