Most advice on choosing an app developer stops at "check the portfolio and read reviews". That is a start, but it does not protect you from the problems that actually hurt businesses after launch: an app listed under the developer's own store account, source code you cannot get, a server only they can log into, and nobody to fix the app when a new Android or iOS version breaks it.
This guide covers the checks that prevent those problems. Use it while you compare vendors, and ask every one of them the same questions.
Quick answer: To choose a mobile app development company, check apps they have actually published in the stores, confirm in writing that you will own the store accounts, source code, server and signing keys, ask how the backend and user data are secured, and get post-launch support terms in writing. Walk away from any vendor who avoids these questions.
Check their apps in the stores yourself
A portfolio slide is easy to make. A live app is much harder to fake. Ask for links to three apps the company built that are live on Google Play or the App Store, then spend twenty minutes on each.
- Developer name on the listing: for client work it should usually be the client's company. If every app sits under the agency's own account, ask why, because that is how they may plan to publish yours.
- Last updated date: an app that has not been updated in a long time may have no one supporting it.
- Low-star reviews: read the one- and two-star reviews for crashes, login failures and payment problems, and check whether anyone replies.
- Your own test: install it on an ordinary mid-range phone. Does it open quickly, cope with a weak connection and explain why it needs each permission?
- A reference call: ask to speak to the business owner behind one of those apps. That is the surest way to confirm the company really built it and supported it afterwards.
Also ask who in their team worked on that app and whether the same people will work on yours.
Who will own the store accounts, code and backend
Ownership is where most disputes between businesses and app developers start. Agree on every item below before work begins, and put it in the contract.
| Asset | Who should own it | What to ask |
|---|---|---|
| Apple Developer account | Your company, as an organisation account | Will you help us enrol in our own name? Apple asks organisations for a D-U-N-S number, so start early. |
| Google Play Console account | Your company | Will the app be published from our account, with your team added as users? |
| Source code repository | Your company, with the developer given access | When and how will the full source code be handed over, and is that written into the contract? |
| Signing keys and certificates | Your company, stored safely | Who holds the Android upload key, keystore passwords and iOS certificates after launch? |
| Server and cloud account | Your company | Is the backend hosted in an account billed to us and controlled by us? |
| Payment, SMS and maps accounts | Your company | Are the gateway, SMS provider and API keys registered in our name? |
| Database and admin panel | Your company | Can we export all our data at any time, in a standard format? |
If a vendor is relaxed about all seven rows, that is a good sign. If they become vague about two or three, expect the same vagueness the day you want to change developers.
Ask about the backend and security before the design
Buyers spend most of their meetings on screens and colours. The problems that cost money usually sit on the server: an API that returns another customer's data, an OTP check that can be skipped, or passwords stored carelessly. Ask these questions early.
- Login and sessions: how do users sign in, and how are tokens refreshed and revoked?
- Data storage: where will customer data be stored, who can access it, and how are backups taken?
- Testing: how do you test security before release? Do you follow the OWASP Mobile Application Security guidance?
- Permissions: will the app request only the phone permissions it truly needs?
- Privacy: how will consent and the privacy policy be handled under the Digital Personal Data Protection Act, 2023?
For the full list of checks, read the mobile app security testing guide. If you plan to publish on Android, the Google Play Store publishing checklist shows what the store asks for before it approves an app.
Post-launch support: what to put in writing
An app is never finished. Phones change, operating systems change and store policies change. Agree on these points before you sign.
- The warranty period, during which bugs in delivered features are fixed at no extra cost.
- A clear line between a bug fix and a new feature that is priced separately.
- How you raise a request, who responds and how urgent issues are handled.
- Whether updates for new Android and iOS versions are part of the monthly plan.
- The monthly support price, what it includes and the notice period to end it.
- What the handover looks like if you leave: documentation, credentials and a call with your new team.
If you already know you will need ongoing help, ask for the support and maintenance terms alongside the build quote, not after launch.
Red flags to walk away from
- Their account, your app: they offer to publish your app from their own store account "to save time".
- No ownership clause: they will not write source-code and IP ownership into the contract.
- A price before questions: they give a fixed price before asking about user roles, integrations or the admin panel.
- No specification: the only scope document is a feature list in a chat message.
- A website in disguise: what is sold as an app is your website wrapped in a webview, which usually feels slow and clumsy on a phone. Ask which framework they will use.
- Nothing live: they cannot show a single live app, or every sample is the same template with a different logo.
- Full payment upfront: payments should follow milestones you can see and test.
- Silence on hosting: they avoid saying where the backend will run and who pays for it.
How EthicsComputer can help
EthicsComputer builds Android, iOS, Flutter and React Native apps for businesses across India and abroad. Every project includes a mutual NDA, a written specification, milestone sign-off, and full source-code and IP handover on completion. We typically guide you through creating the Apple and Google developer accounts in your organisation's name, so the listings are yours from the first release. See the mobile app development service, or mobile app security testing if you already have an app that needs checking.
Comparing app developers right now?
Send us your requirement and ask us every question in this guide before you decide.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.