My developer disappeared. What should I do first?+
Secure what you can before changing anything. List every account the product uses, note which ones are in your name, and take a fresh backup of the database and files. Change passwords you control and rotate keys the developer could use. Then collect the contract, invoices, and any code or access you already have.
Can you take over a software project from another developer or agency?+
Yes. A takeover starts with access and an audit, not new features. Diffwise.app reads the code, hosting, and release process first, then recommends what to fix, what to rebuild, and in what order. The recommendation comes after reading the code, not before.
What if I do not have access to the source code?+
Check where copies might exist: a hosting provider, a build service, an old repository invite, or the previous vendor's records. Ask the vendor in writing, and review what your contract says about delivery. If the code cannot be recovered, a rebuild may be the only path. The live product and its data can still guide what to build.
What is a code audit before a takeover?+
It is a written review of whether a new team can change and release the product safely. It covers the build, release path, secrets, access control, data and backups, dependencies, integrations, monitoring, and tests. Each finding is ranked by risk and comes with a suggested fix.
Should we rebuild the app from scratch?+
No, a full rebuild is not the first step by default. A rebuild restarts much of what the product has already learned, and the old version has to keep running in the meantime. Rebuild the areas no one can test or explain, or that sit on unsupported platforms. Fix the rest where the structure is sound.
How long does a software project rescue take?+
It depends on what is missing. Recovering accounts can depend on registrars, app stores, or the previous vendor, and some transfers have waiting periods. The audit gives you a ranked list of work, so you can decide what must happen before the next release and what can follow.
How much does a software project rescue cost?+
Cost depends on codebase size, access status, the number of integrations, production incidents, and the state of documentation. Missing accounts and a broken build add work, as does a product that is live and failing. Diffwise.app does not publish fixed prices. The audit gives you a scoped list of work, so you can compare options on the same basis.
What is software project rescue?+
Software project rescue means taking over a stalled, failing, or abandoned software project and getting it back under your control. It starts with access, backups, and an audit, then moves to stabilizing the product and agreeing a plan to fix or rebuild what needs it.
What are the signs a software project needs rescue?+
Common signs are repeated missed dates, a developer who stopped responding, unclear ownership of the code and accounts, bugs that keep returning, releases nobody can repeat, and rising spend with little finished. Several together mean it is time for an independent review.
What are the first steps of a software project rescue?+
Assess what exists and who controls each account, recover access and ownership of the code and key accounts, stabilize the build and release, then agree a written plan. Feature work waits until the product can be built and released from code you hold.
Can you recover a domain or app store account held by the previous developer?+
No, we cannot promise recovery of an account you do not control. The provider and account ownership determine the available path. A domain registrant can request a transfer code from the registrar and can complain to ICANN if a transfer is denied improperly. Apple and Google Play transfers must be started by the current account owner, so they usually need the previous developer's cooperation.