If you’re hiring someone to build a React Native app, you’ll get quotes that are very far apart.
A cheap quote is not always bad but a vague quote is bad.
This list is how I check if a quote is real, or just a guess.
15 Questions to Ask
1) What is included and what is not included?
Ask them to write it down in 5–10 bullet points.
2) Who owns the code repo on day one?
If they say we’ll share later, that’s a problem. You should have access from the start.
3) Will you use Expo or not? Why?
Plain answer you want: Expo is fine for most apps. If we need phone-specific work, we may not use Expo (or we will use a different setup).
4) Will you write any iPhone/Android-specific code?
If yes, ask: which feature needs it and how much time it adds.
5) What is the app’s first version (v1)?
Ask them to list the v1 screens/features. This stops extra work surprises later.
6) How many screens are you assuming?
Even a rough screen count is useful. Quotes change a lot when screens double.
7) What backend work is included?
Ask: Do you build the server, database, and APIs or is that extra?
8) Is an admin panel included?
Many quotes skip this. Ask what the admin can do (users, content, orders, refunds, etc.).
9) Which third-party services are included?
Examples: login, payments, SMS, email, maps, analytics, crash reports, storage. Ask them to list each service and who pays for it.
10) What is included for testing?
Ask:
- How many devices they test on
- iOS + Android versions
- Who fixes bugs found after release
11) Who will handle App Store / Play Store release?
Ask: Do you set up accounts, certificates, signing, store listing, screenshots, and the first release?
12) What happens if Apple/Google rejects the app?
Rejections happen. Ask if the quote includes at least one round of fixes.
13) What is the timeline, and what are the checkpoints?
Ask for 3–5 checkpoints, like:
- Clickable screens
- Working login
- Working main flows
- Testing
- Store release
14) How do changes work?
Ask:
- What counts as a change
- How changes are priced
- How you approve changes
15) What do you need from me to start?
A good team will ask for things like:
- A short feature list
- Sample apps you like
- Brand/logo
- Admin rules
- Payment rules
- Content you want in the app If they ask for nothing, they may be guessing.
A Simple Rule
If they can’t answer these questions in writing, don’t pay yet.
If you want, use my copy/paste scope template.
I also keep a one-page checklist and a simple scope template here (with a printable PDF).
If you post your app idea (main screens + any services like payments/SMS/maps), I’ll tell you which parts are usually missing from quotes.
Top comments (0)