Skip to content
App Doctor

What you get, on an example

The two documents you receive, filled in for an invented app: TableNow, the ordering app of a restaurant chain, built by an agency that has since closed. Names, companies and figures are made up; the structure is the real one.

1. The ownership map

Example with made-up data

After the ownership check: one call, the map within two working days.

You control 1 of the 9 things your app depends on. The app runs, but the agency still holds the Google Play account, the signing key and the code, so nobody at your company can publish a fix today.

WhatWho controls it todayRiskThe step to get it back
Google Play account The agency's developer account red App transfer to your company's account; the agency starts it, we write the request. 1–2 weeks.
Apple account Your company's, but only the former manager can sign in amber A second admin, and two-factor sign-in on a company phone. One hour.
Signing keys Android upload key with the agency; Apple certificates expired red Reset the upload key through Google; new Apple certificates. 2–5 days.
Source code The agency's repository; your latest copy is from 2022 red We ask for access; if it doesn't come, we recover the code from the published app. 1–3 weeks.
Server and hosting Azure in your company's name, paid with the former manager's card amber Billing on the company card and a named admin. One day.
Domain names The server's address is registered by the agency red Transfer the domain to your company's account. One week.
Data and backups The database is yours; a restore has never been tested amber A test restore. One day.
Outside services Notifications (Firebase) in the agency's Google account; payments in yours amber Move the Firebase project to your company. One day.
Contract The code is yours once paid in full; the last invoice is paid green Keep the copies; we ask the agency for a written confirmation.

2. The assessment report

Example with made-up data

After the assessment: 5 working days.

What is now in your company's name

  • The Android app, transferred to your company's Google Play account.
  • The Apple account: two admins, new certificates.
  • The code, in your company's repository; the app builds again, on our machine and automatically.
  • The Firebase project, moved to your company; the domain transfer is under way and completes in 5 days.
  • The documentation: how the app is built and published, the accounts, and who has access.

Risks, in order of urgency

  1. The Android app targets API 33: new users no longer see it, and it can't be updated until it targets API 36.
  2. It's built with Xamarin.Forms, which is no longer supported: it has to move to .NET MAUI.
  3. The payments library reaches end of support in January 2027.
  4. There are no automated tests for ordering and payment.

The fixed-price quote for bringing it up to date

Move to .NET MAUI, API 36 and Xcode 26, the new payments library, tests for ordering and payment, publish to both stores: €7,800, 4 weeks. Ordered within 30 days, the assessment (€1,800) is credited: €6,000. Then the care plan from €450 a month.

The report, the documentation and the accounts stay yours, whatever you decide.

Back to prices