To take over a stalled app project in the UAE, secure control before you hire anyone new. Confirm who holds the code repository, App Store and Google Play accounts, domains, hosting, databases and API keys, and bring everything your company is entitled to under its own control. Then commission an independent code audit and let it decide whether a new team carries on, stabilises the app first or rebuilds.
None of this needs to be dramatic: one software firm's takeover guide, updated in November 2026, notes that most takeovers keep the existing code and improve it step by step.
What should you do first when your app developer goes quiet?
List what you already control and ask for the rest while relations are still civil, noting who owns each account, who has admin access and when it renews.
- Source code repository. It should sit in your company's own GitHub, GitLab or Bitbucket organisation, not the developer's account with you as a guest.
- App Store and Google Play accounts. The App Store shows the account's organisation or individual name as the seller; if your listing shows the agency's or freelancer's name, the app sits in their account. On both stores the current account holder must start a transfer, so the app cannot move without their cooperation.
- Domains and DNS, including the registrar login.
- Hosting, cloud and databases. If you have access, take a fresh database backup and keep it somewhere only you control.
- Third-party services and API keys: payment gateway, SMS and WhatsApp providers, maps, email and push notifications.
Ask the vendor, politely and in writing, for credentials, environment variables, third-party accounts and deployment documentation, with a reasonable deadline. What they must hand over, and when, depends on your contract and what has been paid. Once their work has formally ended, change passwords and rotate the old team's keys carefully: replacing a key the live app depends on can take it offline.
Who owns the code, and how do you get it?
General information, not legal advice. This summarises published law and judgments; the DIFC has its own intellectual property law, so the position can differ there. Ask a UAE-qualified lawyer about your own contract.
Start with the contract's clauses on intellectual property, source code, payment and termination. The UAE's copyright law, Federal Decree-Law No. 38 of 2021, in force since 2 January 2022, protects computer programmes and smart applications. Article 28 sets a default for economic rights: unless otherwise agreed in writing, where an author creates a work for another person, the copyright belongs to that person. Article 9 requires any transfer of economic rights to be in writing, specifying the right, its object, duration and place of use; rights not explicitly assigned stay with the author. Law-firm commentary therefore recommends dealing with ownership expressly in every agreement.
Owning the rights is also not the same as holding the files. In [2026] ADGMCFI 0006 (February 2026), the ADGM Court of First Instance held that, under a contract making transfer of the source code subject to payment, the developer was entitled to the full price before handing the code over. Treating the client team's silence after features were deployed for user acceptance testing as acquiescence in the circumstances, it found the code ready to hand over and gave judgment for the developer for the unpaid balance; a counterclaim for a refund and the cost of a replacement provider failed. In DIFC Small Claims Tribunal case SCT 237/2022, a client's refund and damages claim over a software platform failed because the client could not show it had given the written notice its contract required within three days of delivery; the tribunal treated the handover as accepted.
The lessons: do not assume you can insist on the code before paying, since the contract may say otherwise; raise defects in writing, promptly; and read the payment and handover clauses before you stop paying anyone. Take legal advice before withholding payment or terminating, or if the vendor refuses to release code or accounts.
What does an independent code audit check?
Published takeover and audit guides describe much the same scope: architecture, code quality, dependencies, security, test coverage, infrastructure and the deployment pipeline. For an app, add one test: can a new team build it from the repository and release it to the stores without the old vendor? Expect a written report ranking problems by business risk, with the effort to fix each.
Signs the code is worth keeping, according to those guides: sound architecture, a meaningful share of working, trustworthy code, and technical debt that can be paid down gradually. Warning signs: no coherent structure, security flaws running through the core, an unsupported framework, or requirements that have moved so far the build solves the wrong problem.
Take over, rescue or rebuild: how do you choose?
Let the audit decide. The takeover guide mentioned above draws the lines like this:
- Take over when the app works and the problem is the team. A new team learns the code, fixes what the audit flagged and carries on.
- Rescue when the app itself is failing: crashes, security holes, a broken release process. Software project rescue means stabilising first; new features wait.
- Rebuild only when the audit shows the code cannot be repaired at a sensible cost.
Another 2026 audit guide lists, among its conditions for carrying on, a refactoring bill below 30% of the cost of a rebuild — a starting point, not a rule. If a rebuild is the answer, scope it like a first version; our guide to what an MVP costs in Dubai explains how scope drives price.
What do an audit and a takeover cost, and how long do they take?
Published prices mostly come from overseas firms quoting in US dollars: market signals, not our prices. Two 2026 guides put a focused audit of one to three days at roughly USD 500–5,000 and a fuller audit of a larger codebase at USD 3,000–15,000; one quotes USD 15,000–40,000 for a comprehensive audit of one to three weeks. In the UAE, at least one firm advertises audits of AI-built apps from AED 1,500, with results in 48 hours.
The takeover guide cited earlier estimates audit and stabilisation at USD 3,000–8,000 for a small application, USD 5,000–15,000 for a mid-sized product and USD 10,000–30,000 or more for a complex platform, with new features extra. It puts most small and mid-sized takeovers at three to eight weeks to a stable, fully owned state, including three to ten days to transfer access.
What if the vendor will not cooperate?
Negotiate first, in writing: request the repository and accounts specifically, and state clearly what each side says is owed. Law firm Clyde & Co noted in May 2026 that technology disputes are increasingly common in the UAE, and suggested contracts include a mandatory negotiation or mediation stage before court or arbitration.
Beyond that, the forum depends on your contract and where the parties are based:
- Onshore courts. Per the same briefing, proceedings are generally in Arabic, with documents translated by approved translators; there is typically no oral evidence or cross-examination; and courts generally appoint their own experts.
- DIFC Courts in Dubai, an English-language common-law system, can also hear civil and commercial claims the parties agree in writing to bring there, even after a dispute arises. The DIFC Small Claims Tribunal hears claims within DIFC jurisdiction of up to AED 500,000, or AED 1 million if all parties elect in writing, and opens with a private consultation aimed at settlement.
- ADGM Courts in Abu Dhabi hear disputes connected to ADGM, and others the parties agree in writing to bring there. Commercial claims of up to USD 100,000 (excluding interest and costs) go to the Small Claims Division; court-annexed mediation is available.
- Arbitration, if your contract provides for it.
Code access matters in disputes too. In a 2025 account of a DIFC-seated arbitration, the client's law firm said that without the source code, its client could not produce a comprehensive expert report on the alleged coding defects.
How do you stop it happening again?
Put control into the contract. Whether your next app is built by a freelancer, an agency or a mobile app development company, ask for these terms and have a lawyer check the wording:
- Accounts in your name from day one. Repository, developer accounts, domains, hosting and third-party services belong to your company; the developer gets user access. Apple requires organisations to have a D-U-N-S Number to enrol and lists its developer programme at USD 99 per membership year (prices may vary by region), so start early.
- Written IP assignment as each milestone is paid for, worded with Article 9's formalities in mind. A developer may reasonably want ownership to pass only on payment; that is fair, provided the code sits where you can see it.
- Milestone acceptance with a testing window: a realistic period to test, defects reported in writing, and clear words on what silence means.
- A warranty period for defects found after acceptance, fixed at the developer's cost.
- Handover and exit terms: code, documentation, credentials and deployment instructions on completion or termination, once work done is paid for, plus a defined transition period.
- A dispute clause that names the forum and starts with negotiation or mediation.
Day to day, ask for code committed to your repository as work happens and a working build on your phone every week or two: a stall is hard to hide when progress is visible.
Where to start
Know what you control, secure what you are entitled to, and have the code reviewed before spending more. For a second opinion on a stalled app or custom software project, get in touch with a repository link, the store listings and your list of accounts. We can look at what exists and talk through the technical options; contract questions belong with your lawyer.