How to choose an app development company in India: a 12-point checklist
Twelve practical checks — from code ownership and keystores to QA and AMC terms — that separate a reliable app development partner from an expensive mistake.
India has thousands of app development companies, from two-person studios to large IT firms. Prices vary by a factor of five or more for what looks like the same brief on paper. The difference between a good and a bad choice rarely shows up in the proposal — it shows up six months later, when you need a bug fixed, want to switch vendors, or discover your app is published under someone else's developer account.
Use the checklist below before you sign anything. It is written from the vendor side of the table: these are the questions we would want a careful client to ask us.
Ownership and control
1. You own the source code — in writing
The contract should state that all source code, designs and assets created for the project become your property on payment. Ask for access to a Git repository (GitHub, GitLab or Bitbucket) under your organisation from the first sprint, not a zip file at the end. Regular commits are also the best progress indicator you will get.
2. Store accounts, keystores and cloud accounts in your name
This is the most common and most painful trap. Your Google Play Console and Apple Developer accounts should be registered to your company, with the vendor added as a user. The Android signing keystore (or Play App Signing upload key) and its passwords must be handed over and stored safely by you. The same goes for Firebase, AWS or other cloud accounts, domain registrars and third-party API keys. If a vendor publishes under their own account, moving the app later can be difficult or, in some cases, impossible without losing your listing and reviews.
3. NDA and IP clauses before you share details
A reasonable company will sign a mutual NDA before you share your idea in depth. Check that the main agreement also covers confidentiality, IP assignment, and what happens to your data when the engagement ends.
Key tip: Ask one simple question in the first call: "If we part ways after launch, what exactly will you hand over, and how long will it take?" A confident, specific answer — repository, keystore, credentials, documentation, within days — is a strong signal.
Commercials and contracts
4. Fixed price vs time and materials — understand the trade-off
| Model | Works best when | Watch out for |
|---|---|---|
| Fixed price | Scope is clear, screens and flows are documented, MVP-sized project | Vendors padding estimates, or pushing back on every small change as a "change request" |
| Time & materials | Evolving products, ongoing development, uncertain requirements | Budget drift without clear sprint goals and weekly reporting |
| Dedicated team | Long-term products needing continuous development | Paying for idle capacity if your roadmap is thin |
Many good engagements combine them: a fixed price for a well-defined MVP, then time and materials or a monthly retainer afterwards.
5. Milestone-based payments
Tie payments to delivered, testable milestones — approved designs, a working beta, store release — not to calendar dates. A typical pattern is an advance of 20–30%, with the rest spread across milestones. Be wary of anyone asking for most of the money upfront.
6. A written scope with acceptance criteria
The proposal should list features, platforms, supported OS versions, admin panel functions, third-party integrations and what "done" means for each. Vague scopes lead to arguments. If the vendor cannot produce this document, they probably have not understood your project. For budget context, see our breakdown of app development costs in India.
Capability and process
7. Verify the portfolio properly
Don't stop at screenshots. Ask for live Play Store and App Store links, check that the developer name or credits make sense, read recent reviews, and install a couple of apps. Look for work similar to yours in complexity — a payments-heavy app, a real-time app, a large admin system. Ask whether you can speak to a past client. Companies that run their own products, like our in-house product suite, can also show you long-lived apps they maintain themselves.
8. Meet the people who will actually build it
Sales teams are often excellent; what matters is the project manager, designers and developers assigned to you. Ask who they are, how many other projects they are handling, and whether the team is in-house or subcontracted. Subcontracting is not automatically bad, but you should know about it.
9. A real QA process
Ask how testing is done: test cases, device coverage (including budget Android phones), regression testing before each release, and bug tracking you can see. "Our developers test it" is not a QA process. Dedicated QA and testing is one of the best predictors of a smooth launch.
10. Communication rhythm and transparency
Agree on a weekly or sprint-end demo, a shared task board, a single point of contact, and response times. You should be installing test builds every one to two weeks. If you only see the app at the end, you are taking a big risk.
After launch
11. Post-launch support and AMC terms
Every app needs maintenance: Android and iOS updates, new store policies, SDK deprecations, security patches and bug fixes. Ask about the free warranty period after launch (commonly 1–3 months for bugs in delivered scope), and what an annual maintenance contract (AMC) covers — response times, number of hours, whether small enhancements are included. AMC fees are typically quoted as a percentage of build cost per year or as a monthly retainer. Our maintenance and support page explains what a sensible plan includes.
12. Store publishing and compliance experience
Ask whether they will handle store listings, privacy policy, data safety forms, target API level updates and review rejections. Experienced teams know the common pitfalls; see common App Store rejection reasons for a sense of what can go wrong.
Red flags that should make you pause
- A quote given within minutes, without questions about users, flows or integrations.
- Prices far below everyone else, with no explanation of how.
- Reluctance to put code ownership or account ownership in writing.
- No access to the repository or test builds until "the end".
- Promises of "unlimited revisions" or delivering a complex app in two weeks.
- Portfolio apps that cannot be found on the stores, or all use the same template.
- Pressure to sign quickly with a large upfront payment.
Questions to ask in the first meeting
- Which of your past projects is closest to ours, and what was difficult about it?
- Who exactly will work on our project, and are they full-time employees?
- How will we see progress each week, and how do we install test builds?
- What is not included in this quote that we are likely to need?
- What happens if a key developer leaves during the project?
The quality of the answers matters more than the answers themselves. Specific, unhurried replies usually indicate a team that has done this many times.
A quick scoring approach
Shortlist three companies. Score each out of 5 on ownership terms, portfolio relevance, team quality, process and QA, support terms, and price clarity. Price should influence the decision, but it should not be the only column. A slightly higher quote from a team that scores well on everything else is almost always cheaper over the life of the app.
Want to run this checklist on us?
We are an in-house team in Surat building Android, iOS, web and SaaS products, and we are happy to answer every question on this list in writing. If you are evaluating vendors, reach out to Lead Infosoft — even if you end up choosing someone else, we will tell you honestly what to look for in your specific project.
Frequently asked questions
Who should own the Google Play and App Store accounts?
Your company should. Register the developer accounts in your name and add the vendor as a user, and make sure you hold the signing keystore and its passwords.
Is a fixed-price or time-and-materials contract better?
Fixed price suits a clearly defined MVP; time and materials suits evolving products. Many projects use fixed price for the first release and a retainer afterwards.
What does an app AMC usually include?
Typically bug fixes, OS and SDK compatibility updates, store policy compliance, security patches and a set number of support hours. Confirm response times and whether small enhancements are included.
How can I verify an app development company's portfolio?
Ask for live store links, install the apps, read recent reviews and request a reference call with a past client. Check that the work is comparable to your project in complexity.
