Skip to content

How to hire an app developer: 10 questions to ask

How to hire an app developer without regret: 10 questions to ask app developers about their work, code ownership, cost and support after launch.

4 min read

How to hire an app developer: a checklist clipboard, a phone, a key for code ownership and a question bubble

Once a business owner knows roughly what an app costs, the next question is harder: "Who should I trust to build it?"

I sit on the other side of these conversations as a developer, so I've seen how they go. Most bad projects don't fail because of code. They fail because nobody asked the right questions at the start. The price looked good, the demo looked nice, and three months later the app is half-done and nobody owns the store account.

So if you're working out how to hire an app developer you can trust, here are the 10 questions I'd ask before paying anyone, and the answers I'd want to hear.

Before you ask anything

Write a short brief first. One page is enough: who will use the app, the three things they do most, and anything you already have, like a website or a logo.

Without a brief, every developer quotes a different app, and you can't compare anything. With one, the answers below start to mean something.

Questions about their work

1. "Can I see apps you've shipped, and can I install them?" Screenshots and Figma designs are easy to make. A live app on Google Play or the App Store is not. Install one, use it for ten minutes, and ask which parts they built themselves.

2. "Who will actually build my app?" Some people win the project and then pass it to someone else. That isn't always bad, but you should know. Ask who writes the code, who you'll talk to every week, and what happens if that person leaves.

3. "Have you built something like this before?" Payments, offline mode, maps, live chat: each one has its own traps. A developer who has solved your hardest feature before will save you weeks. If they haven't, that's fine, as long as they say so honestly.

Questions about how they build

4. "Native or cross-platform, and why for my app?" There's no single right answer, so be careful of anyone who gives the same answer to every client. A good developer will ask about your users, your budget and your plans for iOS before choosing.

5. "How will I see progress?" You shouldn't wait three months to see your app. Ask for a test build on your own phone every week or two, through Google Play's internal testing or Apple's TestFlight.

6. "How do you test before release?" The answer I like to hear includes real, cheap Android phones. Many of your users in Bangladesh won't have a flagship phone. An app that's smooth on the developer's phone can be painful on a budget one.

Questions about money and ownership

7. "Who owns the code and the store accounts?" This is the most important question on the list. The answer should be: you do. The source code should be in a repository you can access, and the app should be published from your own Google Play and Apple developer accounts.

Google Play charges a one-time $25 fee, and Apple charges $99 a year. Pay them yourself, in your company's name. With Android's new developer verification, the account owner matters more than ever. Moving an app away from someone else's account later is slow and painful.

8. "How do you charge, and what's not included?" Fixed price or monthly, both can work. What matters is the list of things outside the price: server costs, store fees, SMS and payment gateway fees, design changes, and new features. Pay in milestones tied to working builds, not dates.

Questions about after launch

9. "What happens after launch?" Every app needs updates. Google and Apple change their rules every year, like Google Play's 16 KB page size deadline. Ask how long bug fixes are free after launch, and what ongoing maintenance costs. A common rule of thumb is 15 to 20% of the build cost every year.

10. "What will you need from me?" Good developers ask this before you do. They'll need your content, your logo, quick answers to questions, and someone who can make decisions. Slow feedback is one of the most common reasons projects run late, and it's usually not the developer's fault.

Red flags I'd walk away from

  • A price far below everyone else, with no clear list of what's included.
  • No live apps to show, only designs and promises.
  • They want to publish the app from their store account.
  • No written scope. Just "don't worry, we'll handle it."
  • Android, iOS and a website, all "done in two weeks."

The bottom line

Hiring a developer isn't only about skill. It's about trust, ownership and clear answers. Ask these 10 questions, write down what they say, and compare the answers, not just the prices.

And if you'd like to ask me these questions about your own app idea, get in touch. I'm happy to answer every one of them.

Comments

No comments yet — start the conversation.

Leave a comment

Comments are moderated. Your email is never shown.

All posts