Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Roles and delivery

Handover documentation for agent-built apps: what a client or a new team member needs on day one

An app is handed over properly when someone who was not there can change it, build it and release it without calling the person who left. With agent-built apps there is a second reader to think of: the next agent, which knows nothing about the project except what is written down.

Free 15-minute call with our team, or call +49 761 519 751 50 (24/7, English + German)

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

Two readers: a person and an agent

Classic handover documents are written for people and age quickly. For an agent-built app, the most valuable document is the project memory file (CLAUDE.md or AGENTS.md): the next agent reads it at the start of every task, and the next engineer reads it to see how the project works. If it is accurate, a new person can make a first change on the first day.

The rest of the package is less about code and more about access. In our experience a handover gets stuck less often on unreadable code than on a store console nobody can log in to, or a signing key nobody can find.

The six parts of the package

Repository

The full history, owned by the client's organization, with a README that says how to run, test and deploy. For builder projects: ownership of the Lovable or Base44 project itself.

Project memory file

Stack, commands, conventions, known pitfalls and the rules for agents. Before a change of tools, check which file each agent reads.

Accounts

A list of every service the app depends on: hosting, database, push provider, payments, email, domain registrar. For each one: who owns it and who has access.

Signing keys

The Android keystore with its passwords, and the Apple certificates and profiles or a note that signing is managed automatically. Kept in a password manager, not in the repository.

Store access

Admin roles in App Store Connect and the Play Console for the new owner, plus the demo account the reviewers use.

Runbook

Short, tested instructions for the recurring jobs: deploy the web app, build and submit a store release, rotate a key, restore a backup.

What goes missing

  • The Android keystore or its password. Recovering from a lost key is slow at best.
  • Accounts registered to the private email address of a developer or an agency.
  • Two-factor authentication tied to one person's phone.
  • Environment variables that exist only on one laptop or in one hosting dashboard.
  • The reason behind a workaround. The code shows what was done, not why.
  • Store declarations: what was answered in the privacy questions and the Data safety form, and on what basis.

Let the agent draft the document

Prompt for Claude Code or Codex
Write a handover document for this project as HANDOVER.md. Use only what you can verify in the repository, and say so where information is missing.

Include:
1. What the app does, in three sentences.
2. Stack and architecture: front end, back end, database, hosting, third-party services.
3. Setup: the commands to install, run, test and build, each verified by running it.
4. Configuration: every environment variable by name, what it is for and where its value is stored. Never include the values.
5. Release: how the web app is deployed, and which changes need a new native build.
6. Known problems and open tasks you can find in the code.
7. Questions for the previous owner about things you could not find out.

Keep it under two pages.

Hand it over in a session, not by email

Schedule one working session in which the new owner does the three core jobs while the previous owner watches: change something in the web app with an agent and deploy it, build the native apps, upload a build to a testing track. Every point where the new owner gets stuck is a gap in the documents, and it gets closed on the spot.

A handover is easiest when accounts, keys and listings were in the client's name from the start. If you are taking over an app and are unsure what you are missing, book a free call and go through the list with our team.

Frequently asked questions

Who should own the developer accounts?

The business that owns the app, from the first day. Developers and agencies are given access and can be removed again without affecting the app.

Is the project memory file enough as documentation?

It covers how to work in the code. It does not cover accounts, keys, store access and operational steps, so the handover package needs those as well.

What if the previous developer is no longer available?

Start with access: domain, hosting, store consoles and signing keys. Then let an agent map the repository and write down open questions. Code can be read again; lost accounts and keys are the harder problem.

Three ways to get your app into the stores

Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.

Do it yourself

$109 per platform, one-time

The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.

See plans on the main page

Cloud Builder

$349 per license, one-time add-on

No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.

How the Cloud Builder works Try the free demo

Full Service

$698 per platform $798

Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.

Full Service details Powered by WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Talk it through with our team

Free 15-minute call: your app, your tools, your next step

Rather start right away? See plans and pricing or hand it over with Full Service.