Getting an app built is exciting, and it is also where many people lose money. The usual story: a low quote, a vague promise, months of delay, and in the end an app that looks nothing like what was imagined, with source code the client does not even own.
Most of these problems can be avoided with the right questions at the start. We build Android apps for clients and publish our own apps on Google Play, and these are the questions we would want any client to ask us.
About the work
1. Can I see apps you have actually published?
Ask for Google Play links, not just screenshots. Install the apps. Are they fast? Do they look finished? Are they updated regularly? Live apps with real users tell you more than any portfolio PDF.
2. Will I see and approve the design before coding starts?
This is the single most important question. Changing a design costs little. Changing code that is already built costs a lot. A good developer shows you clickable screen designs first and starts coding only after you approve them.
3. What exactly is included in the price?
Get a written list of screens and features. “Login, home, profile, payments” is not enough. Each feature should be described in a sentence or two, so both sides agree on what “done” means.
4. Who handles the Play Store launch?
Publishing involves a developer account, store listing, screenshots, privacy policy, data safety form and, for new personal accounts, a closed testing period before production. Make sure someone experienced handles this, or your finished app may wait weeks for approval.
About money and ownership
5. Who will own the source code and the Play Store listing?
You should. The app should be published on your Google Play developer account, and you should receive the full source code. Get this in writing.
6. How will payments be split?
A common, fair structure is payments tied to milestones: after design approval, after a working test build, and after launch. Avoid paying the full amount upfront.
7. How will the app earn money?
If you plan ads, in-app purchases or subscriptions, discuss it now. AdMob setup, Google Play Billing and app-ads.txt are easier to build in from the start than to add later.
About quality
8. Which devices and Android versions will you test on?
India has a huge range of phones, from budget devices with little memory to the latest flagships. Ask how the app will be tested on low-end phones and slow networks.
9. Will it work in my users’ language?
If your users prefer Hindi or a regional language, plan multi-language support from day one. Translating a finished app is much harder than building it in.
10. How will user data be protected?
Ask where data is stored, how backups work and what happens if a user changes phones. A good answer is specific, not “it is secure”.
About after launch
11. What support do I get after the launch?
Every app needs fixes after real users arrive. Agree on a support period, what it covers and how quickly issues will be handled.
12. Who will keep the app updated?
Google regularly raises the required Android target version, and apps that fall behind can be hidden from new users. Ask who will handle these yearly updates and at what cost.
Red flags to watch for
- A quote given without asking about your users or features.
- No live apps you can install and try.
- Refusal to show designs before development.
- The app published on the developer’s account instead of yours.
- Full payment demanded upfront.
How we work at Virat Bharat
We follow the process above for every project: a conversation to understand your idea, screen designs you can click through and approve, development with regular test builds, then the Play Store launch and support after it. Our own apps, Kharchi, Padho and WinDoc PDF, are live on Google Play, so you can see the quality before you talk to us.
Have an app idea? Tell us about it and we will reply with a clear quote, usually within 24 hours.
