Emergency Help

Your app won't build anymore, and nobody's left who knows it.

The freelancer is gone, the agency went bankrupt, the team was disbanded — no release has been possible for months. Now a deadline or a critical bug forces the issue. I get your app buildable and releasable again and ship a real release to the store.

For managing directors and app owners under acute pressure

The alternative would be a six-figure rebuild or shutting the app down. The rescue makes the existing app operational again, instead of rebuilding it. I reconstruct the build environment, sort out signing, and ship a real release.

„Without a rescue, the app is effectively dead — no more fixes, no policy compliance, and getting pulled from the store is only a matter of time.“

Step 1 · Assessment

Stocktake & rescue plan

I compare the state of the repo against the last store version and take inventory: what's there (code, keys, accounts, backend access), what's missing? From that, a rescue plan with a written fixed-price commitment takes shape.

Step 2

Reconstruct the build environment

I pin or upgrade Gradle, AGP, and JDK versions, and revive or replace dead dependencies and repositories.

Step 3

Sort out signing

I locate the keystore, check the Play App Signing migration, and in the worst case build the strategy for lost keys.

Step 4

Minimal update via the internal track

This proves the chain works end-to-end again before the real release follows.

Step 5

Real release to the store

I ship the release as a staged rollout. I address the acute issue along the way, as far as the timeframe allows; otherwise I flag it clearly as a follow-up step.

Step 6

Rescue documentation & recommendation

I document everything reconstructed, so "only one person knows how it works" doesn't happen again, and give a final recommendation for how the emergency doesn't repeat.

What you get

  • A buildable project again
  • Signing sorted out
  • A published release (at minimum internal/beta, usually production)
  • Rescue documentation of every reconstructed step
  • A written fixed-price commitment after the assessment

Success here means: buildable again plus a release via the agreed track, not every problem in the app solved. The fixed price applies to Android; I assess an iOS rescue separately. A lost keystore without Play App Signing is its own consulting case.

Why an assessment first, instead of a fixed price right away?

Abandoned projects vary enormously in effort. A one-size-fits-all fixed price would have to price in a buffer that the simple cases would end up paying for. That's why it starts with a one-day assessment, followed by a written fixed-price commitment for the rescue. If you commission the rescue, the assessment gets credited in full, so the entry point is effectively free. And the fast start is itself part of the offer.

The details

Emergency Assessment
€1,490 excl. VAT. Start within 48 hours: inventory of code, keys, and buildability, rescue plan, and a written fixed-price commitment for the rescue.
Rescue
from €4,900 excl. VAT, fixed after the assessment. The assessment gets credited in full.
Time investment
2–5 days
What I need
Access to the repository and Play Console, or whatever still exists of them, and a point of contact who can obtain access.
Booking
Book a slot online — the first appointment is also the project start. A formal proposal is available in advance on request; payment by invoice.
Book the Emergency Assessment

Not sure it's a fit? Start with a free 15-minute call: Book an intro call ↗