Choosing a mobile app company is a test of delivery evidence, not portfolio aesthetics. Ask who writes the code, how they test on real devices and what happens after launch.
Key takeaways
- EAS Build, Submit and Update cover the build, store and JS update workflow.
- Ask for a named team, roles and the percentage of time they will spend on your app.
- Review a real app in the store, then ask what the team would change about it.
- 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
- Check code ownership, repository access, signing certificates and store account ownership.
- A good company will explain trade-offs, not promise every feature for a fixed low price.
A practical plan
- Write a scorecard. Three outcomes for the first 90 days and the skills required.
- Shortlist three companies. Similar scope, platform and compliance constraints.
- Run a paid discovery. A small architecture and UX sprint is more predictive than a sales demo.
- Check references. Ask a former client what went wrong, not just what went well.
- Review the contract. IP, code access, store accounts, warranty, support and exit.
- Start with a slice. Build one workflow end-to-end before committing to the full roadmap.
Decision guide
| Area | What to check | Why it matters |
|---|---|---|
| Portfolio | Store links + outcomes | Logos are not evidence |
| Team | Named roles and availability | Who actually writes the code? |
| Process | Weekly demo, QA, release plan | Avoid black-box delivery |
| Ownership | You own code and store accounts | Never let the vendor hold the keys |
| Security | Device, data and secret handling | Mobile apps are a public attack surface |
| Exit | Documentation and handover | Plan for the relationship ending |
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
No. Compare the team, the scope and the total cost of ownership. A low quote that excludes backend, QA or store launch is not cheaper.
Not necessarily. Time-zone overlap, written communication and a clear process matter more than the office location. Test the working relationship with a paid discovery.
You should. The company can have delegated access. Keep control of the account, signing certificates and the domain/backend.
One complete user journey: sign up, perform the core action, see the result and recover from an error. That proves the stack, the process and the team.
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 development company: guide for founders”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/expo-app-development-company-guide-for-founders.





Comments
No comments yet.