Skip to content

GuideApp Developer Disappeared? What to Do in the First 48 Hours

Simon Dziak
Simon Dziak
Founder & developer, App369
LinkedIn
October 27, 2026Facts last verified October 27, 20267 min

Key takeaways

  • Don't start by deleting or resetting anything. First gather proof the app is yours: the contract, paid invoices, company documents and the store listing pages. Every vendor's support team will ask for it.
  • Sign in to every account registered to you and check that its recovery email, phone and billing card are yours, not the developer's.
  • Find two dates: when the Apple Developer membership renews and when the domain expires. If either lapses, the app or the site goes dark.
  • Copy out everything you can already open: the database, the user list, stored files and the store listing text and screenshots.
  • Apps, projects and repositories in the developer's own accounts can usually only be moved by the developer. When they won't, the vendor's support team or a republish from your own account is the way through.

Pricing an app? Try the free app cost calculator or get a range for your project in the instant quote.

If your app developer has disappeared, in the first 48 hours gather proof the app is yours, check you can get into every account registered to you, find when the Apple membership and the domain renew, and copy out the data you can already reach. Don't start by deleting or resetting anything. Then sort the remaining accounts by who can move them, because anything in the developer's own name usually needs the developer, or that vendor's support team, to move.

For the exact steps for your app's services (App Store, Google Play, Firebase, Supabase, Stripe, GitHub, Lovable, Bolt, Vercel, Netlify and the domain), pick them in the free app handover checklist and choose "they've stopped replying". It runs in your browser.

The first 48 hours

1. Gather proof the app is yours

When a developer has stopped replying, the vendors' support teams are your route in, and they ask for proof that the app and the business are yours. Put these in one folder:

  • the contract or statement of work, and any message where the developer agreed to build the app for you;
  • the invoices you paid;
  • your company documents;
  • the app's store listing pages and the website.

The contract also answers a question you will be asked later: who owns the code.

2. Check you can get into the accounts in your name

For each account registered to you (often the Apple and Google developer accounts, Firebase or Supabase, Stripe and the domain registrar), sign in and check:

  • that the recovery email and phone number are yours;
  • which card it bills, and which email gets its renewal notices.

If the sign-in codes go to the developer's phone or email, you can't sign in without them. Ask that vendor's support team to help you change it, with proof the account is yours, such as billing receipts.

What not to do yet: don't delete users, API keys or service accounts, don't cancel any plan, and don't change shared passwords. The live app may still depend on them, and you may need the developer to move other accounts. Change a password only where you are the only person who uses that login.

3. Find the two renewal dates that can take the app down

  • The Apple Developer membership. If the membership the app is published from expires, Apple makes its apps and in-app purchases unavailable in every storefront; copies already on people's phones stay installed (Apple). Find the renewal date now, so a silent developer can't let the app disappear from the App Store.
  • The domain. ICANN Lookup shows a domain's public registration data, sometimes including the expiry date. Make sure the renewal doesn't depend on the developer's card. If the domain sits in the developer's own registrar account, ask the registrar what proof they need to help you take control.

4. Copy out everything you can already open

Export the database, the user list and stored files from any account you can sign in to, and save the store listing text and screenshots, before anything is switched off or stops being paid for.

Then: who can move each account

Anything already registered to you is yours to manage. Anything in the developer's own account is different: most vendors only let the current owner start a transfer. This is what each one says, and the route when the developer never replies.

AccountWho has to start the moveIf the developer never replies
App StoreThe Account Holder of the Apple account the app is in (Apple)Publish the app again from your own Apple account as a new listing. If the account itself is your company's, contact Apple Developer Support about the Account Holder role
Google PlaySomeone who can sign in to the original Play account (Play Console Help)Publish the app again from your own Play account as a new app
FirebaseAnyone who can change the project's IAM policy, usually an Owner (Firebase)If the project belongs to a Google Cloud organization, ask its admin; otherwise contact Google Cloud support
SupabaseAn owner of the organization the project is in (Supabase)Contact Supabase support
GitHubSomeone with admin access to the repository (an organization owner for an organization's repositories) (GitHub)Keep any copy you can already clone, and ask the developer in writing. Your contract decides who owns the code
DomainIf it's registered in your name, you can ask the registrar for the transfer code yourself; if it's in the developer's name, the registrar treats them as the holder (ICANN)Ask the registrar how it handles disputed ownership

A republished app starts with no reviews or ratings, and users have to install the new listing, so try the developer once more in writing before you take that route. Send one message that lists each account and what you need them to do, and keep a copy: support teams may ask what you tried. The handover checklist writes that message for you.

If the Firebase project is the one in their name, How to transfer a Firebase project to a new owner covers the parts people miss: the billing account, the Analytics property and the push notification key.

After ownership moves to you

Once each account is yours: remove the old developer's access, then rotate every API key, service account key and password they could have seen. Do it in that order, so nothing the live app needs is switched off before its replacement is in place.

Getting the app working again

You don't have to recover every account before a new developer starts. A review of the code and accounts you can already reach tells you what is missing and what is broken.

If the app was built with Lovable, Bolt or another AI builder, the AI-Built App Rescue is a fixed-price way to get it working and into accounts you own. If one part has stopped working, such as a login, a payment or a build, the App Fix Ticket finds and fixes it. If you need someone to take over the app for good, the Monthly Dev Subscription covers ongoing work. Not sure which fits? Send me a short description of what you have and what you can still get into, and I'll tell you where I'd start.

Frequently asked questions

What do I do if my app developer disappeared?
In the first 48 hours: gather proof the app and business are yours (contract, paid invoices, company documents), sign in to every account registered to you and check the recovery email, phone and billing card are yours, find when the Apple membership and the domain renew, and export the data you can already reach. Don't delete keys, users or plans yet. Then work out which accounts are in the developer's name, because those need the developer or the vendor's support team to move.
Can Apple or Google move my app if the developer won't?
Only the Account Holder of the Apple account the app is in can start an App Transfer, and a Google Play transfer request has to come from someone who can sign in to the original account. If the app is in the developer's own account and they never reply, the usual route is to publish it again from your own account as a new listing, which starts it with no reviews or ratings.
Should I change all the passwords right away?
Only where you are the only person who uses that login. The live app, or the developer, may still depend on shared passwords, API keys and service accounts, and you may still need the developer to move other accounts. Rotate keys after ownership has moved to you.
Who owns the code if the developer disappears?
That depends on your contract, which is why it is the first thing to find. Separately from who owns it legally, check who controls it: whose GitHub account or organization holds the repository. If it sits in the developer's personal account, only they can transfer it, so clone any copy you can already reach.
How long should I wait before finding a new developer?
You don't have to wait to start. A new developer can review what you can already reach and help you recover the rest. Send the developer one clear written request to transfer each account, and keep a copy, because vendor support teams may ask what you tried.

Sources

  1. Apple: resolving access issues (expired membership)
  2. Apple: overview of app transfer
  3. Apple: app transfer criteria
  4. Apple: transfer the Account Holder role
  5. Play Console Help: transfer apps to a different developer account
  6. Firebase: IAM roles and permissions
  7. Google Cloud: IAM roles overview
  8. Supabase: project transfers
  9. GitHub: transferring a repository
  10. ICANN Lookup
  11. ICANN: domain name transfer policy
Tags
#app developer disappeared #developer stopped responding #developer ghosted #take over app from developer #app handover #app store transfer #firebase owner #app rescue
Share:

Related Resources

Related guides