Android App Rescue – get a stalled legacy app building again
A scoped rescue engagement for Android apps that have come to a halt: the build fails, the Gradle upgrade is stuck, dependencies are too old for Google Play, or nobody who knew the code is left.
Get in touchTypical situations I step into
- The app no longer builds on a fresh machine or in CI – only on one old laptop nobody dares to touch.
- Google Play blocks updates because the target API level is too low.
- The Gradle or Android Gradle Plugin upgrade is stuck in a chain of breaking changes.
- The developer who built the app has left and there is no documentation.
- Signing keys, build configuration or the release process have been lost.
- The app depends on libraries that are no longer maintained.
When is a rescue the right move?
What gets done
- A reproducible build restored locally and in CI, documented step by step.
- Gradle, Android Gradle Plugin, Kotlin and JDK lifted to a current, supported combination.
- Target and compile SDK raised to levels Google Play accepts, with the behaviour changes handled.
- Expired and abandoned dependencies replaced or swapped out.
- Signing, versioning and the release process restored and documented.
- Regression testing of critical flows so the upgrade does not break functionality.
- A handover with documentation so your team can maintain the app going forward.
What you get
An app that builds on a clean machine and in CI, can be signed and shipped to Google Play, plus a short technical handover describing what changed, what remains and which risks are still open.
Timeline and way of working
Every engagement starts with a timeboxed one to two day assessment that establishes whether the app can be rescued and what it will cost. After that I work in short iterations with continuous check-ins, typically two to six weeks depending on how far behind the codebase is.
Frequently asked questions
Our app is from 2016 and will not build at all – can it be saved?
Almost always. Even very old codebases can be revived through stepwise upgrades. The initial assessment gives you an answer before you commit to more work.
Would a rewrite not be cheaper?
Rarely as a first step. A rewrite typically costs several times more and takes months before anything ships. Getting the app releasable first buys you the room to decide calmly.
Can you work alongside our existing developer?
Yes. A common setup is that I handle the upgrade and the build pipeline while your team keeps shipping features, with shared code review.
What about libraries that no longer exist?
They are replaced with maintained alternatives, or – when that is the smallest intervention – with a thin in-house implementation of exactly what the app uses.
How much of our time does it take?
Expect a kickoff meeting, access to the repository and signing material, and about an hour a week for questions and check-ins.
Got an app that is standing still?
Tell me briefly what happens when you try to build it and I will come back with an assessment.
Get in touch