App reactivation

Got a legacy app? We bring it back to life

The project has not built in years, the app dropped out of the store, or it was left behind by a team that is long gone. We start with a free analysis, then a low-cost one-off reactivation — and maintenance only once you actually need it.

/* symptoms */

When mobile app reactivation makes sense

If any of these sound familiar, the app can usually be reactivated — without rewriting it from scratch.

  • The project no longer builds with current tooling
  • Google Play or the App Store keeps rejecting releases
  • The app was delisted over unmet targetSdk requirements
  • Libraries are several major versions behind
  • Years have passed since the last release
  • The team that wrote the app left long ago
  • Nobody can tell whether it can still be revived
/* reactivation_path */

Three steps, no commitment up front

We do not start with a maintenance contract. First we find out what state the project is really in.

// 01

Free project analysis

no cost

We get repository access and check what blocks the build, how far behind the libraries are and how much work stands between the app and a release. You get the findings in writing, with an estimate.

What you get

A risk-free start

// 02

One-off reactivation

one agreed scope

We bring the project to a state where it builds, passes store review and can be developed further. One estimate, one scope, a release at the end.

What you get

The app back in the store

// 03

Flexible maintenance

as needed

After reactivation you decide whether we hand the app back to you or take over its maintenance for as many hours a month as you choose.

What you get

Calm growth after reactivation

/* reactivation_scope */

What reactivation involves

We agree on the exact scope after the analysis — below is what shows up in it most often.

> Build and tooling

  • Fixing the build on current Gradle and Xcode versions
  • Migrating the project to supported language versions
  • Restoring and cleaning up the release configuration
  • Setting up CI/CD if the project has none

> Dependencies and code

  • Upgrading libraries to supported versions
  • Fixing breakage caused by outdated code
  • Adapting the code to newer Android and iOS versions
  • Replacing libraries that are no longer maintained

> Store and release

  • Raising targetSdk and deployment target to store requirements
  • Filling in required declarations: privacy, permissions
  • Removing the causes of earlier rejections
  • Shipping the reactivated version to the App Store and Google Play
/* store_removal */

App gone from the store? It can usually be restored

An app that dropped out of Google Play or the App Store rarely needs a rewrite. The cause behind the store hiding or pulling it has to go, and a fixed version has to ship.

Hidden on Google Play over a low targetSdk

Google Play stops offering apps that miss the target API level requirement to new users on newer Android versions. We raise targetSdk, fix what breaks on newer system versions and ship an update.

Removed for a store policy violation

A missing privacy policy, an incomplete data safety declaration or permissions the app does not justify. We remove the cause, complete the declarations and resubmit the app for review, or prepare an appeal.

Pulled from the App Store as outdated

Apple may remove an app that has not been updated for a long time. We bring the project up to the current Xcode and SDK, fix bugs on current iOS versions and submit a new version for review.

App disappeared from Google Play? The API 36 deadline → What the target API 36 deadline means and how to restore the app step by step.