How to hire an app developer when you’re not technical
Last reviewed 3 November 2026
You can’t judge code, and every developer says they’re great. You can still judge how they work, how they explain things and what they’ve shipped. Here’s how to do that.
Write down what the first version must do, then speak to two or three developers or teams who have launched similar apps. Ask to see live apps, listen for clear explanations, make sure the code and accounts will be yours, and start with a small paid step before committing to the whole build.
Start with what you need built
Before you speak to anyone, write one page: who the app is for, the problem it solves, and the three to five things the first version must do. It doesn’t need to be technical. It makes quotes comparable, and it shows you quickly who listens.
Freelancer, agency or small studio?
We’re a small studio, so bear that in mind, but each option can be the right one.
| Option | Works well when | Watch out for |
|---|---|---|
| Freelancer | The job is small and clear, or you already have someone technical to check the work | One person is a single point of failure. Design, testing and backend may fall outside their skills |
| Small studio | You need a whole product built and want to talk directly to the people building it | Limited capacity, so check who will do your work and when they can start |
| Larger agency | You need many specialists, formal processes or a big team | You may meet senior people in the sale and work with others on the project |
| Your own hire | The product is proven and you’ll need development long term | It’s hard to hire well without technical experience, and it’s a lasting commitment |
Where to look
- Founders you know. A recommendation from someone who has launched is the best signal you can get. Ask what went wrong as well as what went right.
- Marketplaces such as Upwork. Read the written reviews and look at repeat clients, more than the star rating.
- The credits of apps you like. Developers often list their work, so you can ask their clients directly.
Questions to ask
- Can you show me live apps you built, and what was your part? Download them and use them.
- May I speak to a past client? Good teams usually have someone who’ll talk to you.
- Who exactly will work on my project? Ask to meet them.
- What would you leave out of the first version? Someone who only says yes isn’t thinking about your budget.
- How often will I see working progress? You want the real app on your own phone regularly, not only status reports.
- Will the code and accounts be in my name from day one? The answer should be a simple yes. See what to put in the contract.
- What happens when you stop working on it? Ask about handover and documentation before you need them.
- Have you taken apps through App Store review? Ask what got rejected and how they fixed it. An honest answer is a good sign.
- Do you use AI tools, and how do you check their work? Using them is normal. Not reviewing the output isn’t.
- What could go wrong with my project? Good developers can name real risks straight away.
Warning signs
- A price or date given before they’ve understood what you need.
- They agree with everything and never ask “why?”.
- You can’t understand their explanations, and they get impatient when you ask.
- The code or store accounts would stay in their name.
- A large payment upfront, with nothing tied to working results.
- No live work they can show you, or client references they keep avoiding.
How to compare quotes
Put the quotes side by side and check that they cover the same things: design, backend, testing, App Store and Google Play submission, and fixes after launch. A much lower quote often leaves some of these out, or assumes less than you do. Ask each team what’s excluded. Our guide to app costs explains what drives the differences.
Start small
You don’t need to bet everything on one conversation. Pay for a small first step, such as a clickable prototype or a technical plan. You’ll learn how they communicate and whether they deliver, and you’ll keep the result either way.
Questions founders ask
Do I need a technical co-founder first?
Not to build a first version. You do need someone you trust to make technical decisions and explain them clearly, and that can be a good development partner. Our MVP page explains how we work with non-technical founders.
Should I hire offshore or locally?
Judge the people, not the map. What matters is the work they’ve shipped, how clearly they communicate, and whether your working hours overlap enough to talk things through.
How do I check their code if I’m not technical?
Pay an independent developer for a short review once there’s something to read. Also keep access to the code repository yourself, so anyone you trust can look at it.