How to Hire an App Developer: Questions and Red Flags

To hire an app developer, find candidates through referrals, a filtered marketplace or an agency, then judge their live app, their past clients and a small paid test. Ask every candidate the same six questions, walk away from the six red flags, and get code ownership, store accounts and milestone payments in writing before anyone starts. The developer worth hiring is the one who pushes back on your feature list.

The Developer Who Says Yes to Everything Will Cost You | 13 min 50 sec | Published October 9, 2026 | Watch on YouTube

Key takeaways

There are three places to find a developer: a referral, a marketplace such as Upwork, or an agency. Referrals are slowest and safest.
You can judge a developer without reading code by downloading an app they built, calling two past clients and running a small paid test.
Ask every candidate the same six questions on a 15-minute call, including "what would you cut from my idea?"
The worst red flag is a developer who says yes to everything. In a study of 1,471 IT projects, one in six overran its cost by 200% on average.
Without a signed agreement, a contractor generally owns the code they write. Put code ownership in the contract.
Set up the Apple ($99 a year) and Google Play ($25 once) accounts in your own name, then give the developer access.

What the video covers

0:00 How do I hire an app developer?
0:36 Where do I find a good app developer?
3:12 I'm not technical. How do I know if they're any good?
5:41 What do I ask them on the first call?
7:36 What are the red flags?
10:04 How do I protect my idea and my money?
12:44 What's the one thing to remember?

Where do you find a good app developer?

There are three places to find an app developer for hire: a referral from a founder who has already shipped an app, a freelance marketplace such as Upwork, or an app development agency. Each one carries a different risk. A referral is the slowest route but the safest, because someone you trust has already taken the risk. A marketplace gives you the widest choice at the lowest prices, but anyone can create a profile, so the vetting is on you. An agency costs more because you are hiring a team (project manager, designer, developers and testers) whose job is to get the app shipped. Start with referrals, use a marketplace only with filters and a paid test, and choose an agency when the app needs more than one skill. Whichever route you use, the checks in the next sections apply equally.

Route	What you get	Main risk	Check before you sign
Referral	A developer another founder already trusts	Slow, small pool	Ask the referrer if they would hire the same person again
Freelance marketplace	Wide choice, low entry price	Profiles and reviews are easy to polish	Read what reviews say, not the star count; run a small paid test first
Agency	A full team with testing and project management	Higher cost; junior staff doing senior-sold work	Ask who writes the code and meet them

On cost, a simple app from a US or Western European agency typically lands between $15K and $60K, and teams in Asia or Eastern Europe often quote about half. Our own app development cost breakdown shows how that number is built from hours multiplied by an hourly rate, and our companion video explains why two quotes for the same app can differ so much. For the freelancer-versus-team decision in more depth, read freelance app developer vs agency.

If your app is simple, you may not need to hire anyone. AI builders can produce a working simple app in a weekend, and we cover what they leave out in our video on building an app with AI.

How can a non-technical founder tell if an app developer is good?

You do not need to read code to judge a developer. You judge three things you can see: their work, their past clients and how they handle a small test. Work means downloading an app they built and using it for ten minutes. Does it load fast, does it crash, and would you be happy if your app felt like that? Past clients means speaking to two of them and asking one question: would you hire them again? Then do your own check by messaging the founder of an app the developer did not point you to. The small test is a short paid task, such as a clickable prototype or one screen built properly, which shows how they communicate under real conditions. Think of it like buying a car: you cannot rebuild the engine, but you can test drive it.

Developers will only hand you their happiest clients, so the independent message to a founder they did not choose is where honest answers come from.

The paid test is the strongest signal of the three. Over a week or two, you see how fast they reply, whether they ask good questions, and whether they tell you something you did not want to hear. A developer who asks what your users are trying to do is a better bet than one who starts building at once.

What should you ask an app developer on the first call?

Keep the first call to about fifteen minutes and ask every candidate the same questions, writing the answers down so you can compare them afterwards instead of from memory. We use six: have you built an app like mine, and can I download it; who will actually write the code; how do you test it; what happens if I change something halfway through; how will we stay in touch, and how often; and what would you cut from my idea. Add one more before you hang up: who owns the code and the accounts when this is done? Each question shows how the developer works rather than what they claim. The last two are the most revealing. A real answer to the cut question usually saves you money, and a vague answer on ownership is a reason to stop.

Who writes the code? Founders often speak to a senior person on the call and then see the work handed to someone junior. Ask to speak to the person who will build it.
How do you test? A good answer names a tester, a list of phones they check on, and time set aside. "We test as we go" means your users will do the testing.
What if I change something halfway? You will, so you want a clear process and a price. A vague answer is usually a surprise bill later.
How will we stay in touch? Look for a short demo every week or two, not silence for a month and a big reveal.
What would you cut? "Nothing, it is all great" tells you something too.

For a written checklist you can send before the call, our guide on how to choose an app development agency lists the plain-language questions a non-technical founder should get answered in writing.

What are the red flags when hiring an app developer?

Six red flags are worth walking away for. In order from least to most serious: they want the full amount upfront; they cannot show you a live app in a store; there is no testing line in the quote; they want to start building on day one with no planning; they promise to add more developers when the project runs late; and they say yes to everything. The last one is the worst. A developer who accepts every feature, deadline and price without a question or an opinion is either not thinking about your project or not telling you the truth about it. Good developers push back. They tell you what usually works, what does not, and which half of your feature list can wait for version two. Pushing back is a sign they are working on your behalf.

The yes-to-everything flag is expensive for a reason the data backs up. A study of 1,471 IT projects by Bent Flyvbjerg and Alexander Budzier found that the average cost overrun was 27%, but that one in six projects overran by 200% on average. The risk is the project that blows up, not the average one, and projects blow up when nobody said no early. Cutting scope on day one is the cheapest risk control there is.

The "add more developers" flag comes from Fred Brooks's well-known book on software management, The Mythical Man-Month. His point is that new people on a late project must first learn it, and someone already on the team has to stop to teach them, so the project slips further. If a developer's answer to a delay is a bigger team, ask what is actually behind the delay.

The "start building on day one" flag is about cost of change. Changing a plan costs almost nothing, and changing a built app costs a lot.

How do you protect your idea and your money?

Ideas are rarely stolen, because a good developer already has paid work and an idea alone is worth little without execution. What goes missing is the money and the code, so protect three things in writing. First, own the code: in the US, work by an independent contractor is not automatically yours, and the Copyright Office says a work made for hire needs a signed written agreement. Second, keep every account in your own name: the Apple and Google developer accounts, the database, the domain and the code repository. Third, pay in milestones, releasing each payment when a piece is delivered and working. Do this homework once before you sign, then let the developer do the job. Good developers choose their clients too, and checking on them every day drives the best ones away. A short written agreement covering all three points costs little to draft and removes most of the ways this relationship goes wrong.

The ownership point is the one founders find hardest to believe. The US Copyright Office explains that a work made for hire by a non-employee needs a signed written agreement that expressly says so, and that without one the creator is generally the initial owner. Paying for the code does not transfer it. Your contract should say the code is yours once you have paid for it, and most countries work along similar lines, so ask a lawyer to check the wording for your jurisdiction.

The account point is about leverage. If a developer publishes your app under their own store account because it is quicker, moving it later is a process, and on Apple, the Account Holder must start an app transfer. If that person has disappeared, you are stuck. Google works in a similar way: a transfer request is raised from the original developer account and reviewed by Google support. Set up your own accounts first and give the developer access. The cost is small: $99 a year for Apple and $25 once for Google.

Apple also treats the account type as meaningful. Under Apple's enrollment rules, an organization account lists the legal entity as the seller, while an individual account lists your personal legal name. Apps in highly regulated fields such as banking and healthcare should be submitted by a legal entity, not an individual developer under the App Review Guidelines. Decide which account type fits your app before the developer starts.

Item	Should be in	How to check
Source code	Your repository, with a written assignment	Contract clause; you can see the repo
Apple developer account	Your name or your company	You are the Account Holder
Google Play account	Your name or your company	You hold the registration
Database and hosting	Your billing account	Invoices come to you
Domain	Your registrar login	You can renew and change DNS
Payments	Milestones tied to working delivery	Each payment names a deliverable

What we see across 300+ apps

We founded ApsteQ in 2015 and have shipped 300+ apps, which have gained 52M+ installs. We also hire developers ourselves, so we have sat on both sides of this conversation. These are our views, drawn from that experience and not from a study.

The pushback test is the best filter we know. After the first call, the candidates who cut your feature list and explained why are the ones worth a paid test.
Smaller and live beats complete and late. Real users tell you what to build next.
Ownership questions should come early. Developers who are comfortable with your accounts and your repository are usually comfortable with everything else.
Price is the weakest signal. The cheapest quote is often the one that says yes to everything. Compare quotes by scope and process, using the same list of questions.
Salary data is a sanity check. The US Bureau of Labor Statistics reports median pay of $135,980 a year for software developers in May 2025, which is roughly $65 an hour before benefits and overhead, by our arithmetic. A quote far below what a team could afford to pay is worth a question.

We price per project and we will tell you what to cut. If you want a second opinion on your idea before you hire anyone, see our app development service, or read the longer written guide, hire mobile app developers.

Frequently asked questions

How much does it cost to hire an app developer? A simple app from a US or Western European agency typically costs $15K to $60K, and teams in Asia or Eastern Europe often quote about half. Freelancers usually cost less than agencies. Our cost guide shows how hours and hourly rates build the price.

Should I hire a freelancer or an agency? A freelancer suits a small, well-defined job where you can manage the work yourself. An agency suits an app that needs design, development, testing and project management, because one team covers every role. Our freelancer versus agency comparison goes through the trade-offs.

Do I need an NDA before talking to a developer? Usually not for a first call. Ideas rarely get stolen, and many developers will not sign before they know the project. Once you work together, a contract with a confidentiality clause is reasonable. The money and the code need protecting more than the idea does.

Who owns the code when I pay a developer? Not automatically you. Under US copyright law, work by a non-employee is a work made for hire only with a signed written agreement that says so. Your contract should state that the code is yours once you have paid, and a lawyer should check the wording for your country.

How should I pay an app developer? Pay in milestones: a deposit up front, then payments as each piece is delivered and working. Paying the full amount upfront is a red flag, because you lose your leverage on quality and on delivery dates. Tying each payment to a named, working deliverable keeps both sides honest.

Can I build the app myself with AI instead of hiring? For a simple app, often yes. AI builders can produce a working app in a weekend. Once the app handles payments, sensitive data or many users, hiring becomes the safer route. We explain the limits in our AI app building video.

Want us to look at your idea before you hire anyone?

Tell us what you plan to build. We will say what we would cut, and what it should cost.

Book a strategy call

How to Hire an App Developer: Questions to Ask and Red Flags