Back to Blog

Need a Developer to Take Over Your Existing App? A Rescue Guide

Hiring · Published November 16, 2026

Some of the most urgent emails I get start the same way: “Our developer stopped replying, and now the app is broken.”

Maybe the agency closed. Maybe the freelancer moved on. Maybe the app still works, but Google Play just sent a warning that it will stop accepting updates. Whatever happened, you have a live app, real users, and nobody who knows how it works.

This guide explains how to hand an existing mobile app to a new developer without losing your users, your store listing or your data. I’m an independent mobile engineer based in Canada, working with clients worldwide and specialising in Flutter, iOS and Android. Taking over existing apps is a regular part of my work.

Signs you need a takeover, not just a quick fix

  • The previous developer or agency is unreachable or no longer available.
  • The app crashes on new phones or new iOS and Android versions.
  • Google Play or Apple is warning that the app doesn’t meet current requirements.
  • Nobody can build the app anymore, so even a one-line text change is impossible.
  • New features take months because the code has become hard to change.
  • You’re paying for a backend, database or service that nobody understands.

Step 1: Recover access before anything else

Code without access is useless, and access without code is a rebuild. Before a new developer writes a single line, collect these. Make sure your company owns each account, not the previous developer’s personal email.

What Why it matters
Source code (GitHub, GitLab, Bitbucket, or a zip) The app itself. Ask for the full repository with history, not just the latest files.
Apple Developer account Needed to publish iOS updates. Should be enrolled under your organization.
Google Play Console Needed to publish Android updates.
Android signing / upload key Required to update the existing Play listing.
Backend and cloud accounts (Firebase, AWS, Cloudflare, Supabase, etc.) Where your users’ data and accounts live.
Third-party services (payments, push notifications, analytics, maps, email) API keys and billing for everything the app depends on.
Domain and DNS Website, deep links, email and privacy policy URLs.
Design files (Figma, Sketch) Saves time on every future screen.

If the previous developer still answers, ask for all of this in one written list. If your contract says you own the work, point to that clause.

Lost the Android signing key?

Don’t panic yet. If the app uses Play App Signing (most apps published in recent years do), Google holds the real signing key, and you can request an upload key reset in the Play Console. If the app predates Play App Signing and the key is truly lost, you generally can’t update that listing and may need to publish under a new one. Find out which case you’re in before planning anything else.

Step 2: Audit the code

A good takeover starts with a short, fixed-price audit, not an open-ended invoice. Here’s what I look at:

  • Does it build? On current tooling, for both iOS and Android.
  • How outdated is it? Framework version (for Flutter apps, whether it’s on Dart 3 and null safety), dependencies, and store target levels.
  • Code quality. Structure, duplication, tests (or lack of them), and how risky changes will be.
  • Security. Hard-coded API keys, open databases, outdated authentication.
  • Backend health. Costs, failing jobs, data backups, and whether anyone can deploy it.
  • Store status. Policy warnings, privacy disclosures, crash rates and reviews.

You get a plain-English report: what’s broken, what’s risky, what can wait, and what it costs to fix each part.

Step 3: Stabilise before adding features

It’s tempting to jump straight to the new features you’ve been waiting for. Resist it. The first goal is a build you can ship safely:

  1. Get the app building on current tooling.
  2. Upgrade the framework and critical dependencies.
  3. Meet the current Google Play target API level and Apple Xcode / iOS SDK requirements.
  4. Fix crashes that affect real users.
  5. Add crash reporting so you can see problems before your users email you.
  6. Ship a stable update to both stores.

Once that’s done, every later change is faster and cheaper.

Step 4: Fix, improve, or rebuild?

After the audit there are usually three paths:

  • Maintain. The code is reasonable. Keep it, fix issues and add features on top.
  • Refactor gradually. The core is sound but parts are painful. Improve them screen by screen while shipping updates.
  • Rebuild. The code is unrecoverable, missing, or built on a dead technology. Rebuilding, often in Flutter so iOS and Android share one codebase, can be cheaper than patching. You can usually keep your store listing, reviews and users by publishing the new app under the same app identifier.

I’ll tell you honestly which one makes sense. Rebuilding is never the default.

How to avoid this happening again

  • Keep every account in your company’s name, with at least two people who have admin access.
  • Make sure your contract says you own the code, and get the repository delivered continuously, not at the end.
  • Ask for a short README that explains how to build and release the app.
  • Budget for yearly maintenance. Apps don’t stay finished, because the platforms they run on keep changing.

Need someone to take over your app?

If you have an iOS, Android or Flutter app with no active developer, email me at hi@ngsang.app. Tell me what the app does, what’s going wrong, and what access you still have. I’ll reply with a clear first step, usually a short audit, so you know exactly where you stand.

Planning something new instead? See how hiring a remote app developer works.

FAQ

Can a new developer take over an app someone else built?

Yes, with the source code and access to your store accounts and backend. Expect a short audit first, then stabilisation, then new work.

What if I don’t have the source code?

Request it in writing and check your contract. If it’s truly gone, the app usually needs a rebuild, but you can often keep the same store listing and users.

What if I lost the Android signing key?

With Play App Signing, you can request an upload key reset in the Play Console. Without it, you may need to publish a new listing.

Why are the app stores warning me about my app?

Both stores raise technical requirements yearly (Android target API level, Apple’s Xcode and iOS SDK versions). Apps that aren’t updated can be hidden or blocked from updates.

How much does an app takeover cost?

It usually starts with a fixed-price audit and stabilisation of a few days to two weeks, followed by monthly maintenance or a scoped feature project.