Questions to Ask Before Hiring an App Developer
Short answer: Ask an app developer about apps they have shipped, who holds the store accounts, how they test on real devices, what updates cost after launch and what happens if you part ways. Good answers are specific: they name apps you can download, explain their test devices and show a written handover plan. Vague answers, such as "we work with all platforms" or "we own everything, don't worry", should lead you to ask again. Twelve questions cover most of the risk, and you can put them to a freelancer or a studio in the same way.
Questions about experience
1. Which live apps have you released in the last two years, and can a buyer download one today? Live apps are better evidence than portfolios. Check that the app is on the store, that it has recent updates and that its reviews mention the features you want.
2. Which parts of those apps did you build yourself, and which did you connect to third-party services? A developer who built a login system from scratch and one who used a standard sign-in service may both be competent, but you need to know which approach they will take for your app.
3. Have you worked on an app in this category before? For example, a delivery app for a bakery involves order times, cut-off windows and payment refunds that differ from a fitness tracker. Ask how they handled one of those problems.
Questions about process
4. How do you test before a release, and on which devices? The answer should name real phones, both iOS and Android where relevant, and the operating system versions. "We test on simulators" alone is not enough.
5. Who writes the test plan, and will they share it with you? A short plan with twenty or thirty checks is normal for a small app. Ask what happens when a check fails before release.
6. How often will the developer give you a working build to try? Weekly builds through a test service such as TestFlight or Google Play internal testing give you visible progress and earlier warnings. Ask which build number sits on each phone used for testing, so there is no confusion later about what you approved.
7. How will we record decisions and changes? A shared list of requests, with the reason, the date and the approver, saves arguments later.
Questions about ownership and accounts
8. Whose name is on the Apple developer account and the Google Play developer account? The store accounts control your app. Ask for them to be registered in your business name, with the developer added as a member, not the owner.
9. Who holds the source code repository, the signing keys and the app store listing? The signing keys are critical. If the developer loses them, updating the app can become difficult. Ask where they are stored and how you will receive a copy.
Questions about aftercare
10. What does support look like after launch, and for how long? Ask for a timeframe in days or months, what is covered, such as crash fixes and store rejections, and what counts as a new feature.
11. What do monthly updates cost, and when do they become extra? Operating system updates arrive every year, so a plan that covers only the first launch can leave you exposed. Ask for the hourly rate or the monthly retainer in writing.
12. If the relationship ends, what do you receive and how quickly? The right answer lists the code, the build instructions, the store access, the documentation and a date for each.
How to check live apps and references quickly
Spend fifteen minutes before the first call. Open the store listing of two or three apps the developer names. Read the release notes to see how often they update. Look at the lowest-rated reviews, because a pattern of complaints about crashes or login problems tells you more than the five-star ones.
When you speak to references, ask about the one thing that went wrong and how it was handled. Every project has a problem, and a good developer will describe theirs clearly and without blaming the client. If the developer has no live apps you can open, ask why. Some studios work under confidentiality agreements, and that is reasonable, but they should still be able to show a case study with the client's permission, or run a private test build on your own phone so you can see the work for yourself.
Answers to listen for
| Topic | Answer you want | Warning sign |
|---|---|---|
| Live apps | Named apps you can download | Only mockups or unreleased work |
| Testing | Named devices and OS versions | "We test everything" |
| Store accounts | Registered in your business name | Registered under the developer |
| Keys and code | Copies held by you | Held only by the developer |
| Aftercare | Dates, coverage and rate | "Support as needed" |
A small example of a good conversation
Imagine a physiotherapist in Brisbane, whom we will call Sam for this example, is choosing a developer for a booking app with reminders. A strong developer would show two live booking apps, explain how they test push reminders on older iPhones, confirm the store accounts are in Sam's name and provide four months of support at a fixed monthly rate afterwards. A weaker one would say the app is "almost the same as ours" and promise to sort out the accounts later. The second conversation may feel friendlier, but it leaves Sam with the most risk.
FAQ
Should I choose a freelancer or a studio?
A freelancer can be a good fit for a small, focused app. A studio is usually better when you need design, development, testing and support covered by more than one person. Ask both the same twelve questions.
How much should I expect to pay for support?
Prices vary widely by complexity and region. Ask for a written rate, and compare it against the hours the developer expects to spend on a typical month.
Do I really need to see the store accounts?
You do not need the password, but you do need to know whose name is on the account and that you have an administrator role. That is the simplest way to avoid losing control of the app.
Bring your own app idea to our enquiry form and we will run through these questions against it with you.