{"id":988635,"date":"2026-10-06T14:00:00","date_gmt":"2026-10-06T14:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988635"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"how-to-handover-a-codebase-to-a-studio","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/how-to-handover-a-codebase-to-a-studio\/","title":{"rendered":"How to Handover a Codebase to a Studio"},"content":{"rendered":"
\n

A handover is how a new team can change the product without folklore. If you are leaving a freelancer, changing studios, or inviting Croncode<\/a> onto an existing app, the packet matters more than a kickoff vibe. This is the inbound checklist we ask for. Quote shape: what to send<\/a>. Security before you sign: security questions<\/a>.<\/p>\n

\n

Handover a codebase with repo access, store roles, secrets in a company vault, and a written debt list. A zip in chat is not a handover.<\/p>\n<\/blockquote>\n

What belongs in the first drop?<\/h2>\n
    \n
  1. Git remote the company owns, not a personal laptop path.<\/li>\n
  2. Apple org roles. You stay Account Holder. Account ownership<\/a>.<\/li>\n
  3. Bundle ID, signing, and where dSYMs go. Crashes<\/a>.<\/li>\n
  4. Secrets in a vault, rotated if a past contractor still has them.<\/li>\n
  5. A debt list: known crashes, hardcoded strings, hidden admin. Shared codebase risks<\/a>.<\/li>\n<\/ol>\n

    If a marketing site exists, handover host and DNS separately: cPanel deploys<\/a>. Do not put WordPress admin passwords in the iOS repo.<\/p>\n

    Which questions should the outgoing team answer in writing?<\/h2>\n\n\n\n\n\n\n\n\n
    Topic<\/th>\nAsk<\/th>\nFail signal<\/th>\n<\/tr>\n<\/thead>\n
    Store<\/td>\nWho can upload today<\/td>\n\u201cI use my personal team\u201d<\/td>\n<\/tr>\n
    Privacy<\/td>\nSDK list vs label<\/td>\nShrug. Analytics<\/a><\/td>\n<\/tr>\n
    Deletion<\/td>\nWhere the script lives<\/td>\nFounder laptop. Deletion<\/a><\/td>\n<\/tr>\n
    Support<\/td>\nWhich inbox<\/td>\nDead alias. Support<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    References on the old studio: check references<\/a>. Istanbul hiring: what to check<\/a>.<\/p>\n

    When should you pay for a discovery week first?<\/h2>\n

    When there is no test target, no README, or the binary on the store does not match the default branch. Commercial: a short fixed discovery then a retainer is cleaner than a fake fixed price. Fixed price vs retainer<\/a>. Process: fixed scope vs agile<\/a>. Thin mystery apps: too thin<\/a>.<\/p>\n

    People who will read the packet: Goktug Unver<\/a>, Yusufhan Sokur<\/a>, Ozgur Ismet Ozkan<\/a>. Shipping: how we ship<\/a>.<\/p>\n

    How do we prove we can build after handover?<\/h2>\n

    A sprint demo on a new TestFlight from the company org, not a screenshot of the old Xcode. Sprint demo<\/a>. Design QA on the first job: design QA<\/a>. If AI is in the app, we need the fail-safe and the keys story: fail-safe AI<\/a>.<\/p>\n

    What mistakes make handover hostile?<\/h2>\n