Help for owners
The agency that built my app now wants more money to release it
Short answer
First read your contract: who owns the code, and what was included in the price. Then find out where the source code and the store accounts live. If they sit with the agency, ask in writing for a handover of both and keep paying only what the agreement says while you take stock.
Does this sound like your situation?
- The agency asks for new payments to hand over the source code.
- The app is published under the agency's store account, not mine.
- I do not have a copy of the code.
- I was told hosting and maintenance are separate costs I never saw.
- I feel locked in and unable to move to another developer.
Why does this happen?
The contract never said who owns the code
Some agreements are silent, or give the client only a licence to use the app. Ownership of the source code is a contract question, not a technical one.
The app was published from the agency's accounts
It is the quickest way to launch. The app then sits in an account you cannot control, and moving it needs the agency's cooperation.
The app runs on the agency's servers and keys
A back end, a database, push notification keys or a domain may belong to the agency. The app can look finished while still depending on their accounts.
Hosting and support were priced separately
Some agencies sell the build once and charge monthly for hosting and care. If this was not discussed clearly, the new request feels like a surprise.
What can I do about it today?
- Read the contract and the invoicesLook for the words 'ownership', 'licence', 'source code' and 'maintenance'. If something is unclear, ask a lawyer about the contract itself. I can describe the technical side but I do not give legal advice.
- List everything the app depends onCode repository, Apple and Google accounts, servers, databases, domain, push keys and paid services. Next to each, write who holds it.
- Ask in writing for a handoverA short, polite email requesting a copy of the code and administrator access to the accounts. Keep the replies.
- Do not take the app offline or publish a second copyA new store listing starts without reviews or users, and an angry stop can hurt your customers more than the agency.
- Keep paying only what the agreement saysDo not refuse payment as a pressure move before you have the code. Check each new demand against the contract.
When should I bring someone in?
- The agency refuses to hand over the code or the accounts.
- You are not sure whether a charge is part of your agreement.
- You need a new developer to take over and nobody can say what the app depends on.
How do I handle it?
- Map the dependenciesI produce a one-page list of what the app needs to run and who owns each piece, so you know exactly what must move.
- Plan the handover in orderCode first, then accounts, then servers and keys, with each step checked before the next one starts.
- Keep the app working while it movesI do the changes with a backup first and a tested way back, so customers see no break.
- Prove you can release aloneThe handover is finished when a small update, built and signed from your own accounts, reaches the stores.
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?
Do I own the app I paid for?
That depends on your contract. Ownership is a legal question, so ask a lawyer to read it. I can tell you which technical pieces you would need in either case.
Can I move my app to my own developer account?
Usually yes, with the agency's cooperation. The related page on transferring an app explains how it works in both stores.
Will you work with the agency?
Yes, if they are willing. A calm, written handover plan usually goes better than a dispute.
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.