Store submission is a product and compliance task. Apple and Google review the app, its metadata, privacy behaviour and payments; a technically working build can still be rejected for a policy issue.
Key takeaways
- EAS Build, Submit and Update cover the build, store and JS update workflow.
- Apple reviews against the App Store Review Guidelines; Google reviews against Play policies.
- Privacy manifests, permission prompts and data-safety disclosures must match the app's actual behaviour.
- Plan the store submission and first year of maintenance before you start building.
What changes with Expo + React Native
- EAS Build, Submit and Update cover the build, store and JS update workflow.
- Development builds let you use native libraries that are not in the Expo Go sandbox.
- Config plugins change native project settings without ejecting.
- Over-the-air updates must stay within store policy and be compatible with the installed native binary.
Build and release path for Expo + React Native
| Stage | What happens | What to check |
|---|---|---|
| Build | EAS Build creates signed iOS and Android binaries in the cloud | Keep the build profile and credentials documented |
| Native code | Development builds and config plugins handle libraries outside Expo Go | Test a clean install, not only a dev-client update |
| Updates | EAS Update can ship JS changes within store policy | Runtime versions must match the native binary |
| Store | EAS Submit automates upload; review still needs your account | You own the Apple and Google accounts |
What the work actually requires
- Digital goods sold in the app usually need the platform's in-app purchase system; physical goods and services differ.
- Screenshots, descriptions and age ratings are part of the review, not marketing decoration.
A practical plan
- Prepare the accounts. Developer accounts, agreements, tax and banking.
- Complete the listing. Name, subtitle, description, keywords, screenshots and age rating.
- Declare data use. Privacy manifest, data safety form and permission reasons.
- Test the review build. No placeholder content, working demo account and no broken links.
- Submit and monitor. Respond to reviewer questions quickly and keep the build available.
- Plan the release. Manual, phased or automatic; have a rollback and support plan.
Decision guide
| Area | What to check | Why it matters |
|---|---|---|
| Apple | App Store Review Guidelines | Privacy, payments, minimum functionality |
| Play developer policy | Data safety, permissions, ads and payments | |
| Privacy | Manifest + disclosures | Must match actual SDK behaviour |
| Payments | IAP vs external | Digital goods usually require IAP |
| Metadata | Screenshots and description | No misleading claims |
| Review time | Varies | Plan a buffer before a launch date |
Platform rules to check
- Apple: privacy manifest, permission purpose strings, in-app purchase rules and review guidelines.
- Google: data safety form, permissions, target API level and Play policy.
- Both: account deletion, privacy policy, accessibility and accurate store metadata.
First-year budget for Expo + React Native
| Line | What it covers | When it lands |
|---|---|---|
| Discovery and design | Journey, prototype and UI system | Before build |
| App build | Screens, state, API integration and tests | Main build phase |
| Backend/admin | API, database, roles and reporting | Alongside the app |
| Integrations | Payments, push, maps, analytics | Mid-build |
| Store launch | Assets, review, signing and release | At the end |
| Maintenance | OS updates, dependencies and fixes | Every year |
Launch checklist
- A test build signed with the production key, installed on a clean device.
- Account creation, login, logout and account deletion all work.
- Push notifications, deep links and offline states have been tested.
- Privacy policy, store data disclosure and permission text match the app.
- Screenshots, description and support URL are accurate and localised where needed.
- Crash reporting and analytics are live before the first release.
Store review risks for Expo + React Native
| Risk | Why it happens | How to reduce it |
|---|---|---|
| Missing privacy details | SDK data use is not disclosed | Audit SDKs and complete the forms |
| Broken demo account | Reviewer cannot sign in | Provide a working test account |
| Payments rule | Digital goods bypass in-app purchase | Use the required store billing |
| Minimum functionality | The app is only a website wrapper | Add real native value |
| Misleading metadata | Screenshots or claims do not match | Show the real product |
Post-launch metrics for Expo + React Native
- Expo + React Native: crash-free sessions and the top crash groups for this release.
- Activation: the user completes the first meaningful action.
- Retention: return rate after one day, seven days and thirty days.
- Store conversion: page views to installs.
- Support contacts per hundred active users.
- Release adoption after an update.
Common mistakes
- Choosing a stack before defining the core user journey.
- Estimating by screens instead of workflows, roles and integrations.
- Leaving store submission, analytics and maintenance out of the budget.
- Testing only on a fast simulator instead of a mid-range real device.
- Treating the client as trusted for prices, roles or business rules.
Frequently asked questions
It varies. Apple often reviews within a few days, Google can be faster or slower. First submissions and policy-sensitive apps take longer. Never plan a launch date with zero buffer.
Common reasons include incomplete metadata, broken demo accounts, privacy mismatches, misleading screenshots, payment-rule violations and minimum-functionality issues. Read the reviewer note and fix the cause, not just the symptom.
Rules vary by platform, region and app type. Check the current guidelines and get legal advice before designing the flow.
Yes, in practice. Both stores require privacy disclosures and a policy that matches the app's data collection.
Sources and further reading
- Expo documentation (docs.expo.dev)
- EAS Build (docs.expo.dev)
- EAS Submit (docs.expo.dev)
- EAS Update (docs.expo.dev)
Related reading
Planning a mobile app?
Send the user journey, the platforms and the integrations. I will help you scope a realistic first release and a maintenance budget.
How to cite this guide: Nur Hossain Repon, “Expo app store submission: guide for founders”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/expo-app-store-submission-guide-for-founders.





Comments
No comments yet.