What drives the cost
1. How old the project is
An app last touched two years ago is a short job. One last touched many years ago has to pass through several generations of Android, Gradle and library changes first.
2. Whether it builds today
A project that still compiles is the cheap case. A project with build errors, missing dependencies or abandoned libraries needs reviving before the real update even starts.
3. Which libraries it uses
Retired support libraries, discontinued third-party SDKs and old networking, image or ads libraries each add work. A library that no longer exists has to be replaced, not just updated.
4. Native code (C/C++ or .so files)
Native libraries need extra checks, including 16 KB page size support. A prebuilt library can only be rebuilt by its owner.
5. In-app purchases
If your app sells anything, the Play Billing Library version matters, and old billing code can need rewriting.
6. How much testing the app needs
Logins, payments, notifications, maps, camera and file access all behave differently on newer Android versions, and all need checking.
Three example scopes
These are typical shapes of the work, not prices. Your quote depends on your code.
| Small | Medium | Large | |
|---|---|---|---|
| Last updated | 1 to 2 years ago | 3 to 5 years ago | Many years ago |
| Builds today? | Yes | With errors | No |
| Libraries | Mostly current | Some retired (support libraries, old SDKs) | Several discontinued, need replacing |
| Extras | None | Old billing or ads SDK | Native code, billing and more |
| Main work | Version bump, behaviour fixes, testing | AndroidX, Gradle, library updates, fixes, testing | Revive the build first, replace libraries, then everything in Medium |
What does not change the price
- How many screens the app has, if they do not need redesigning.
- How long the app has been on Google Play, or how many users it has.
- Whether the code is Java or Kotlin. We keep it in the language it was written in.
How we quote
We do not publish a price list. After a free app check you receive one fixed price and a delivery date before any work starts. If the billing code needs rewriting, that part is quoted separately, before work starts.
What to send for a quick, accurate quote
- The source code, as a GitHub invite or a zip file. We do not need your keystore, passwords or Play Console access.
- A screenshot of the Play Console message, if you have one.
- Whether the app sells anything inside the app.
- Whether it has native
.sofiles, if you know. - A test login, if the app needs an account to reach its main screens.
Frequently asked questions
Why do you not list prices?
Because the work depends on the code. A fixed price after seeing the project is more honest than a range that may not fit your app.
Is the app check really free?
Yes. You get the check first, then a fixed price and a delivery date, and you decide after that.
Do you need my keystore or Play Console login?
No. We work on the source code, and you upload the finished build yourself.
Keep reading
Want a fixed price for your app?
BrightRevamp updates older native Android apps (Java and Kotlin) to Google Play's current rules. Same app, same design, same features.
Email us about your appSources
- Google Play target API level requirement (Android Developers)
- Migrate to Google Play Billing Library 8 (Android Developers)
- Support 16 KB page sizes (Android Developers)
Checked against the official documentation on 8 Oct 2026. Rules change, so confirm the dates in your Play Console.