
Kinnari
Android Development Lead
Kinnari leads native Android development: the Android side of the apps the mobile team builds and maintains.
For apps and web products that already exist and have stopped moving: a developer left, a project stalled, an AI builder hit its limit, or a store deadline is due. Our in-house team in Rajkot, India starts by reviewing what you have and telling you what we find.
What we take on
A list of what you hold and what is missing: source code, signing, store accounts, servers, databases and third-party services. A missing item can change the whole plan, so it comes first.
Whether it builds from the repository, what is out of date, where it is fragile, and whether keys are exposed or APIs unprotected, with priorities. We agree the scope, any cost and what you will receive before it starts.
One repeatable build, a working release process and crash reporting, with the worst faults fixed before new features start.
What to fix, what to refactor and what to rebuild, with the reason for each.
The unfinished features completed, tested on real devices where you can supply them, and released to the stores or your server.
OS and SDK updates, security fixes, library updates, monitoring and small features, under terms agreed with you.
Technologies: Swift · Kotlin · Java · Flutter · React · Node.js · PHP / Laravel · Firebase
Situations we can help with
You may have partial code, missing signing keys, or an account in someone else's name. We work out what can be recovered and what each gap means before you spend on new work.
Tools such as Lovable, Bolt, Replit and Base44 are a fast way to prove an idea. Trouble tends to start with real users and real data: open database rules, secret keys in the front end, sign-in that fails in unusual cases, and changes that break something else.
Since 31 August 2026, Google Play requires new apps and updates to target Android 16 (API 36). Existing apps that target below Android 15 (API 35) stop reaching new users on newer Android versions. Google changes this each year (checked 5 November 2026). We update the build and libraries, fix what the change breaks, and prepare the resubmission. Approval stays with Apple or Google.
The kinds of work involved: changing a payment flow when a provider's requirements change, merging separate apps for different user roles into one, and keeping an Android app on the current target API level.
A PHP or similar system can usually be improved in stages while the business keeps running. We map what it does, put backups and tests around the important flows, move one small part to prove the route, then deal with the parts most likely to fail.
Our longest published engagement ran from 2018 to 2023: iPhone, Apple Watch and Android apps and their back end for a client's sports sensor, kept going across product versions.
We have not published a takeover case study. Ask us what we have done that is closest to your situation.
Who you work with

Android Development Lead
Kinnari leads native Android development: the Android side of the apps the mobile team builds and maintains.

iOS Development Lead
Dharmesh leads native iOS development: iPhone and Apple Watch apps.

Flutter Development Lead
Vivek leads Flutter development, where one Dart codebase serves both iOS and Android.

Backend Development Lead
Rajesh leads backend development: the APIs, databases and business logic that web and mobile apps depend on.
Related
Questions
Often, but it depends what is missing. Take Android signing. If the app uses Play App Signing, which apps created since August 2021 must, Google holds the signing key and the account owner can ask for a lost upload key to be reset. If an older app kept its own signing key and that key is lost, it cannot be reset, and the usual route is a new listing with users moved across. We check this first, because it changes the plan.
No. We decide part by part, and you see the reasoning. A full rewrite is one possible answer among several, and the old app still has to serve your users while any rebuild happens.
Yes, we take on this kind of work under the same process. We review security and data access first, then either harden what exists or move the important parts to code any competent developer can maintain.
Yes. We raise the target API level, update the libraries that need it, fix what the change breaks, test and prepare the release. We need the source code, the upload key and Play Console access. If the key is missing, the first question above applies.
Yes. It usually covers OS and SDK updates, security fixes, monitoring and small changes. How much time is included and how urgent faults are handled are agreed with you in the contract.
No. We fix the technical causes and prepare the resubmission, but approval stays with Apple or Google.
What the product does and what went wrong, what access you hold today, and any deadline. You do not need to prepare a specification.
Start a project
What the product does, what went wrong, and what access you still have. If you are facing a deadline, say so.
Your message goes to Ghanshyam Gadhiya, partner and CEO, who replies by email. If it is easier, you can also reach us on WhatsApp.