Help for owners
My app is live but nobody can find its source code
Short answer
An app in the store is only the finished package, not the project that built it, so without the source code you cannot change it safely. Ask where it was kept: the developer's repository, an agency, a cloud drive, an old laptop. If it cannot be found, a rebuild guided by the working app is the realistic path.
Does this sound like your situation?
- The app works but I cannot get any new feature or fix added.
- The agency that built it has closed or does not reply.
- I know it exists but not where it is stored.
- A new developer says they need the project and I have nothing to give them.
- The only thing I have is the app itself.
Why does this happen?
The code lived on the builder's own computer or account
Many small projects are built and kept in the developer's personal repository or on one laptop. When that person moves on, the only copy goes with them.
The agency kept it as part of its own system
Some agencies keep every client's code in their own private systems and hand over only the store build.
The app was built with a tool that hides the code
Drag-and-drop app builders keep your project inside their service. If you stop paying or the service closes, the project may not leave with you.
Only the finished app was delivered
A delivery that counted as done when the app went live often did not include the project, the keys or the build steps.
What can I do about it today?
- Ask everyone who touched the appDeveloper, agency, a previous employee, a technical friend. Ask one plain question: where is the code kept, and who can open it.
- Search your own email and drivesLook for repository invitations, shared folders, backup archives and hosting notices. A message from a code hosting service can show where the project lives.
- Find the store accounts and the app's identifiersOpen the App Store and Play Console accounts and note the app name and package or bundle ID. A new developer will need them.
- Do not download a copy from a third-party siteUnofficial copies of an app's package are not a source of your project and can be unsafe.
- Keep the app onlineWhile you look, leave the current version published. Removing it loses users and reviews.
When should I bring someone in?
- Nobody can say who holds the code.
- The app needs an update the store requires, such as a newer target level, and you cannot make it.
- The tool or agency that built it is shutting down.
How do I handle it?
- Look for the code before looking at a rebuildI help you trace where it could still be: repositories, hosting accounts, store build records and the people involved.
- Judge what a rebuild would reuseIf the code is gone, the live app, the server it talks to and the store listing give a clear picture of what has to be rebuilt.
- Keep the store listingWhere possible, the new version is released as an update to the same listing so users and reviews stay.
- Put the new code in your hands from day oneRepository, store accounts and keys are in your company's name from the first day, with a short document on how to build and release.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can the code be extracted from the app?
Not in a form you can safely maintain. A published app is compiled, so I would not treat it as your project.
How much does a rebuild cost?
It depends on the scope. I quote after a short discovery call, against a written scope.
Will users keep their accounts after a rebuild?
If the new version uses the same server and the same store listing, they usually do. I check that before any work.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.