Questions to Ask Before Hiring an App Developer
By CodexierPublished 5 min read
Hiring someone to build an app is a bigger commitment than hiring for a website. The code runs on devices you do not control, releases go through Apple and Google review, and the app needs updates for as long as it exists. A good portfolio does not tell you how a developer handles any of that. The questions below do. Use them in the first meetings with freelancers or agencies, and compare the answers side by side.
Process and communication
- How do you go from our idea to a fixed scope, and what do you need from us for that?
- How often will we see and try a working version of the app?
- Who is our day-to-day contact, and who actually writes the code?
- How are changes to the scope priced and approved?
- What tools do you use for tasks, feedback and releases, and will we have access?
Code ownership and accounts
This is where most painful app projects go wrong, usually discovered when the relationship ends. The contract should transfer ownership of the code to you, and the accounts should be yours from the start. Our guide to IP clauses in software contracts covers the wording.
| Question | Good answer | Worrying answer |
|---|---|---|
| Who owns the code? | You, on payment, stated in the contract | We license it to you |
| Where is the code stored? | In a repository your company owns, with our access | On our servers, we send it at the end |
| Whose Apple and Google developer accounts? | Yours; we are invited as team members | We publish it under our account |
| Backend, database and push services? | Set up in your cloud accounts, billed to you | Included in our hosting, cannot be moved |
| Which open-source licences are used? | Listed, all compatible with commercial use | Not sure |
Testing and release
- Which devices and OS versions do you test on, and do you test on real phones, not only simulators?
- Do you write automated tests, and for which parts?
- How do we test versions before release, for example through TestFlight and Google Play internal testing?
- Who prepares store listings, screenshots, privacy labels and review notes?
- What happens if Apple or Google reject the app, and is that included in the price?
- Do you set up crash reporting and basic analytics from the first release?
A developer who has been through store review many times will answer these quickly and mention the common rejection reasons unprompted.
Maintenance after launch
An app is never finished. Apple and Google release new OS versions every year, change store rules and require updated build tools, and libraries in the app need security updates. A developer who does not raise this before you sign is either inexperienced or planning to bill it later. See what app maintenance costs for the full picture.
- What does a maintenance agreement include, and what does it cost per month?
- How quickly do you respond to a critical bug or a store rejection?
- How long will you support the framework and versions you choose?
- If we switch developers, what do we get: documentation, build instructions, credentials?
Answers that should worry you
- A fixed price and date given before anyone has asked about users, features or integrations.
- We can build anything, with no questions about what your users actually need.
- Reluctance to put the code in your repository or the app in your developer account.
- No mention of testing, store review or maintenance until you ask.
- A team you never meet, with the actual work subcontracted to people not named in the contract.
Decision rule: prefer the developer who asks you the most questions about users and scope, and gives the clearest answers on ownership and maintenance, over the one with the lowest price or the flashiest portfolio. When not to hire an app developer at all: if your users mainly need to find information or book a time, a mobile-friendly website or a web app may do the job for far less. If an app is right, our cross-platform MVP app service answers all of the above in writing, and you can book a short call to test us with this list.
Frequently asked questions
Should I hire a freelancer or an agency for an app?
A freelancer can be cheaper and closer, but you depend on one person for building and maintenance. An agency costs more per hour but has backup and more roles. Either way, the ownership and maintenance questions matter most.
Is it a bad sign if the developer will not give a fixed price immediately?
Usually the opposite. A reliable fixed price requires a defined scope. Many good developers offer a short paid planning phase or prototype first, then a fixed price for the build.
What should the contract include?
Scope, price and payment plan, how changes are handled, ownership of code and accounts, testing and acceptance, warranty period, and what maintenance after launch includes and costs.
Do I need to understand the technology to ask these questions?
No. The questions are about process, ownership and responsibility. Compare how clearly different developers answer; clarity is a good signal on its own.
Want to test a developer with this list?
Start with us. In a free 15-minute call you can ask every question above, and we tell you honestly whether you need an app or something simpler.
Book a free 15-minute call