Why the questions to ask app developer before hiring matter more than the quote
Most app projects that go wrong fail on ownership, missing scope or absent support, not on coding skill. The questions to ask app developer before hiring are designed to surface those gaps while you still hold the money and the decision.
A low quote is attractive until you learn it covers only the app screens, not the server, the admin panel or publishing. A skilled developer can still leave you stranded if the app sits on their Play Console account and they stop replying. A friendly team can still ship something that breaks on the next Android update if nobody agreed who maintains it.
Treat the conversation like a short interview. Ask the same questions of every developer on your list, write down the answers, and compare them side by side. The developers worth hiring will welcome it because it shows you are a serious client. The ones who get irritated or vague have told you something useful for free.
Questions to ask about an app developer's portfolio and live apps
The first questions to ask an app developer before hiring are about proof: ask for apps you can install today, and exactly what the developer did on each. A portfolio of screenshots proves design taste, not delivery.
Good follow-ups separate real builders from resellers. If they say “we built this app”, ask whether they built the backend too, who designed it, how long it took and whether they still maintain it. Ask what went wrong on that project and how they fixed it. Someone who actually built it will answer in detail without looking anything up.
- Which two or three live apps are closest to mine, and can I install them now?
- What exactly did you do on each: design, app code, backend, publishing?
- Is that app still maintained by you? When was the last update?
- Can I speak to the owner of one of those apps?
- What was the hardest problem on that project and how did you solve it?
- Can you show me a small piece of code you wrote, even from a sample project?
Some client work is covered by confidentiality, and that is fair. But a developer with years of work and nothing at all to show, not even a demo project, is a risk you should price in.
How to check an app developer's live apps yourself
Asking questions is half the job; the other half is checking. Install the app, use it for ten minutes on an ordinary phone, and read the store listing carefully. You will learn more than any sales call can tell you.
On the Google Play listing, look at the developer name, the “updated on” date and recent reviews. If the developer name is the client’s business, that is a good sign the client owns the account. If every portfolio app is published under the developer’s own name, ask why. Check whether the app opens quickly, whether screens load without long spinners on mobile data, and whether the login, search and forms work.
Look at recent reviews for crash complaints or “stopped working after update” comments; they show how the app is maintained, which is exactly what you are buying after launch. On iPhone, do the same in the App Store. If the developer claims a web admin panel, ask for a demo login to see it. Ten minutes of this beats an hour of slides, and it costs you nothing.
Who owns the code, accounts and data? Questions to settle in writing
Of all the questions to ask an app developer, ownership comes first. You should own the source code, the code repository, the store listings, the cloud and database accounts, the domain and any third-party API keys. Ask the developer to confirm each one in writing before any payment.
This is not a formality. India’s Copyright Act, 1957 makes the author of a work its first owner by default, with an exception for employees working under a contract of service, and section 19 says an assignment of copyright is valid only in writing signed by the assignor. A freelancer or outside firm is not your employee, so a written agreement that assigns the code to you is what makes it yours. We are not lawyers; have your own lawyer review the clause, but make sure one exists.
- Will the code repository be created in my account, with me as owner, from day one?
- Will the agreement assign copyright in the code to me on payment, in writing?
- Which open-source or paid libraries will you use, and are their licences fine for commercial use?
- Will all API keys (maps, SMS, payments, push notifications) be registered to my business?
- Will I have admin access to the database and cloud console, not just the app?
Whose Play Console and App Store account will the app be published on?
Yours. The app should be published under a Google Play Console account and an Apple Developer account opened in your name or your business name, with the developer added as a user. Publishing on the developer’s account makes you dependent on them for every update.
The costs are small and paid by you: Google Play charges a one-time US$25 registration fee, and the Apple Developer Program costs US$99 per membership year. Apple’s enrolment page says organisations need a D-U-N-S number and must be a legal entity able to sign contracts, so start that early if you are enrolling as a company. Google’s Play Console help also says that new personal developer accounts must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Ask your developer how they plan for that, because it affects your launch date.
Moving an app later is possible through the transfer processes both stores offer, but it depends on the original account holder cooperating. Getting it right at the start is far easier.
- Will you help me open the Play Console and Apple Developer accounts in my name?
- If I enrol as an organisation, have you allowed time for the D-U-N-S number?
- How will you handle the 12-tester, 14-day closed test for a new personal Play account?
- What access level will you need, and will you remove it when we stop working together?
Questions to ask about the backend, database and hosting
Backend questions to ask an app developer before hiring are simple: ask where the app’s data will live, who pays for it, and what it will cost when you have a thousand and then ten thousand active users. The backend is the most commonly skipped part of an app quote.
Almost every useful app has a server side: user accounts, orders, bookings, content, notifications. That might be Firebase, Supabase, a Node.js or Python API on AWS or Google Cloud, or a managed service. Each has different running costs and different lock-in. A good developer names the choice, explains why, and estimates monthly running cost in plain words. A weak one says “we will handle hosting” and keeps it on their account.
- Which backend will you use and why is it right for my app?
- Will the cloud account be in my name, with billing to my card?
- What is the expected monthly cost at launch and as users grow?
- Is there an admin panel in the quote, and what can I do from it?
- How are backups taken, and have you ever restored one?
- If I change developers, can the new one run the backend without you?
Our approach: another of us sets up the cloud project in your account, explains the expected running cost before launch, and documents how to deploy it. The admin panel appears as its own line in the quote so you can see what it costs.
Should you ask which framework the developer will use?
Yes, and more importantly, ask why. Flutter, React Native and fully native Swift and Kotlin can all produce good apps; what matters is that the choice fits your features and that someone else could maintain it later.
Cross-platform frameworks such as Flutter and React Native let one codebase run on Android and iOS, which usually lowers cost and keeps both versions in step. Native development makes sense for heavy device features, complex animations or apps that must adopt new platform APIs the day they appear. A developer who can only offer one option for every project is selling what they know, not what you need.
Also ask about maintenance consequences. Google Play now requires new apps and updates to target a recent Android API level; Android’s developer documentation states that from 31 August 2026 new apps and app updates must target Android 16 (API level 36), with some exceptions. Every framework needs regular updates to keep up with that. Our comparison of native and hybrid apps goes deeper.
Questions about scope, estimate and payment milestones
Among the questions to ask app developer before hiring, scope questions save the most money. Ask for a written feature list with every screen, and a payment schedule where each payment follows a build you can install and test. Vague scope is how a project doubles in cost.
A decent estimate lists screens, user roles, backend work, the admin panel, integrations (payments, maps, SMS, WhatsApp), publishing and testing as separate items. It says what is not included. It explains what happens when you ask for something new mid-project: a change note with its own price and time, agreed before work starts.
- Can I see every feature and screen listed in writing before I pay?
- What is explicitly not included in this price?
- How are changes handled once we start: new quote, time impact, approval?
- What will I be able to install and test at each payment stage?
- Is the price a starting estimate or tied to this exact scope?
If you are unsure which billing model to accept, our guide to fixed price versus time and material explains when each one protects you.
Who will actually build my app? Questions about the team
One of the most revealing questions to ask an app developer is who will do the work. Ask for the names of the people writing your code and who you will speak to each week. Many projects are sold by one person and built by someone you never meet.
Subcontracting is not automatically bad, but you deserve to know. Ask how many projects the developer is running at once, what happens if the main developer falls ill, and whether anyone else already knows the codebase. For solo freelancers, ask what their backup plan is. For firms, ask whether the people on the sales call will be on the project.
With us the answer is simple: one of us writes the app and front-end code, another of us handles backend, cloud, AI features and data, and the third of us manages the project and your updates. All three can see the code, so one person being away does not stop the work. We are a small freelance team, so we are honest that we suit apps that three people can build well, not programmes that need twenty developers at once.
Questions to ask about testing before the app goes live
Testing questions to ask an app developer before hiring cover devices, builds and bug tracking. Ask which real devices they test on, how you will receive test builds, and how bugs are reported and tracked. An app that works only on the developer’s own phone is not finished.
Good answers mention a range of Android phones including a low-end model, at least one iPhone, internal testing and closed testing tracks in Play Console, and TestFlight for iOS. You should be able to install builds yourself at each milestone and report issues in a shared list rather than scattered chats.
- Which Android phones and iPhones will you test on, including an older budget model?
- Will I get test builds through Play Console testing tracks and TestFlight?
- How do I report bugs, and how will I see their status?
- Do you test slow networks, no network and interrupted payments?
- Who submits the app for store review, and what happens if it is rejected?
What should post-launch support include? Questions to get in writing
The support questions to ask an app developer before hiring decide your costs for years. Ask what is covered after launch, for how long, what counts as a bug versus a new feature, and how quickly they respond. Apps need care after release because operating systems, store policies and libraries keep changing.
A clear support answer names a period, lists what is included (crash fixes, compatibility updates, security patches, small content changes), states how new features are priced, and explains how you contact them. It also covers store-driven work such as target API level updates or privacy form changes, which can arrive whether or not you change anything.
- How long is support included after launch, and what exactly does it cover?
- What is the difference between a bug fix and a change request in your terms?
- Who handles updates required by new Android and iOS versions?
- How do I reach you after launch, and on which days?
- What does ongoing maintenance cost after the included period?
Our standard: two months of free maintenance after launch, then optional maintenance from ₹8,000/mo a month. Response details and anything beyond that are agreed in the written quote and our terms.
Questions about security, privacy and store policies
Privacy questions to ask an app developer are easy to forget. Ask how user data is protected, what personal data the app collects and why, and who prepares the privacy policy and store privacy declarations. Store reviewers and users both check these.
Useful answers describe encrypted connections, secure password handling or third-party login, role-based access in the admin panel, and minimal data collection. Google Play asks developers to declare data collection in the Data safety section, and Apple asks for privacy details in App Store Connect; the developer should help you fill these accurately based on what the app really does. The legal wording of a privacy policy is your responsibility, ideally checked by your lawyer.
- What personal data will the app collect, and is each item necessary?
- How are passwords, tokens and payment details handled?
- Who can see user data in the admin panel, and is access logged?
- Will you help complete the Play Data safety and App Store privacy details?
Answers from an app developer that should worry you
The questions to ask app developer before hiring only help if you listen to the answers. Walk away, or at least slow down, when you hear any of these. Each one has caused real projects to stall or become hostage to the original developer.
- “We will publish it on our account; transferring later is easy.”
- “You will get the APK file at the end.”
- “Hosting is included, you don’t need to know where.”
- “We need the full amount up front to start.”
- “We can build anything in two weeks.”
- “The admin panel is extra, we will discuss later.”
- “We don’t use contracts, trust us.”
- “Support? Just message us any time,” with nothing written
- “Our portfolio is confidential,” with no demo or code sample at all
If you have already hired someone who fits this list and the project has stalled, read our guide on what to do when a developer leaves a project midway.
Questions to ask app developer before hiring if you are not technical
You do not need to judge code to hire well. Ask questions whose answers you can verify without technical knowledge: can I install it, is it in my name, is it in writing, what does it cost each month, and who do I call.
Ask the developer to explain their plan as if you were a new staff member. Ask them to draw the app’s parts: phone app, server, database, admin panel, third-party services. Ask what they would cut if your budget were half. A developer who can explain trade-offs simply usually understands them well. One who hides behind jargon either cannot explain or does not want you to understand.
If possible, pay a small amount for a discovery step: a written scope, screen list and architecture note that you own even if you hire someone else. It is the cheapest insurance in app development, and it gives you a document to compare other quotes against.
Printable checklist of questions to ask an app developer
Here are the questions to ask app developer before hiring, condensed into a scorecard for every call. Mark each answer clear, vague or missing. Two or more “missing” answers on ownership or backend is enough reason to keep looking.
- Live apps I can install, with their exact role on each
- Play Console and Apple Developer accounts in my name
- Code repository owned by me from the first commit
- Written assignment of code copyright to me
- Named backend and cloud account in my name, with monthly cost estimate
- Admin panel listed in the quote
- Every screen and feature listed; exclusions stated
- Payments tied to builds I can install
- Named people building the app
- Real-device testing plan and test builds for me
- Support period, scope and cost after launch in writing
- Privacy and store declarations handled with my approval
Example: a coaching institute in Nagpur interviews three app developers
Here is a hypothetical comparison of how the questions to ask an app developer before hiring play out. Say a coaching institute in Nagpur wants a student app for recorded lectures, tests and fee reminders, and speaks to three developers using the questions on this page.
Developer A offers the lowest price but plans to publish on their own Play account and host the backend on their server “at no extra charge”. Developer B has good live apps but cannot say who will write the code, and asks for most of the money up front. Developer C shows two installable education apps published under the clients’ own names, proposes Flutter with a Firebase backend in the institute’s Google Cloud account, lists the admin panel and publishing as separate lines, and ties payments to test builds.
The institute picks C even though the quote is higher than A’s, because A’s low price hides future dependence and B’s answers leave too much unknown. Scope like this would start on our Android & iOS app plan from ₹40,000, over roughly six to ten weeks. This is an illustration of how to use the questions, not a real client. For education-specific costs, see education app development cost.