React Native has matured to the point where cross-platform doesn't mean compromised. But the path from working local build to published app store listing is paved with signing certificates, permission declarations, and review guidelines that can turn a 2-day task into a 2-week ordeal if you're not prepared.
Before You Write a Line of Production Code
- Register your Apple Developer account ($99/year) and Google Play Console account ($25 one-time). Both require 48-72 hours for new accounts.
- Decide on your bundle identifier / package name early — it's painful to change later and affects everything from push notifications to deep links.
- Set up your release signing keys. For iOS, generate your distribution certificate and provisioning profile. For Android, generate your keystore file and store it securely — losing it means you can't update your app.
Critical App Store Requirements Often Missed
Privacy nutrition label (iOS): Apple requires you to declare every data type your app collects and how it's used. Go through this carefully — incorrect declarations are a common rejection reason.
Permission descriptions: Every permission your app requests (camera, location, contacts) requires a plain-language description of why in your Info.plist. Vague descriptions like "for app functionality" will get rejected.
Screenshots: Apple requires screenshots at exact device dimensions. You'll need at least 6.7" (iPhone 15 Pro Max) and 12.9" (iPad Pro) sizes. Use a tool like Picasso or AppLaunchpad to generate them programmatically.
The Review Process
Apple's review typically takes 24-48 hours for first submissions, and often longer. Common rejection reasons: missing privacy policy URL, app crashes on launch, broken in-app purchase flow, misleading description. Build time into your launch plan for at least one round of rejections.
Google Play is faster (usually a few hours to a day) but has become stricter about data safety section accuracy.