A handover is how a new team can change the product without folklore. If you are leaving a freelancer, changing studios, or inviting Croncode 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. Security before you sign: security questions.

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.

What belongs in the first drop?

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

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

Which questions should the outgoing team answer in writing?

References on the old studio: check references. Istanbul hiring: what to check.

When should you pay for a discovery week first?

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. Process: fixed scope vs agile. Thin mystery apps: too thin.

People who will read the packet: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan. Shipping: how we ship.

How do we prove we can build after handover?

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

What mistakes make handover hostile?

• NDA theater with no repo: we cannot help.
• Leaving a backdoor admin in the consumer target: we will pull it. Will not build.
• Unowned inspiration in the UI: we will not copy a competitor as a deliverable. Teardowns.
• English-only strings while the store is Turkish: onboarding localization.

Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/. Choose us like any studio: choose an iOS studio. Models: studio vs freelancer.

What does a healthy week-one look like?

We can archive a build, read crashes, reply to one support thread, and name the first increment. Consumer examples of jobs we already understand: YourStyle, Numira, Spylie, Luviport. We will not pretend your app is one of these. Catalog: what Croncode builds.

If the “codebase” is only no-code, say what you can export: custom vs no-code. If you cannot export, we are not taking over a repo. We are estimating a rebuild. Say that in the first call so the commercial shape is honest. A surprise rewrite inside a “handover” fixed price is how both sides lose a month.

Schedule a live archive of a TestFlight from the company org in week one. If that archive fails, stop feature talk. Fix signing. A studio that starts redesigning onboarding while it cannot ship a build is entertaining you. We will not.

Frequently asked questions

Can I handover without the old developer?

Yes if you own the repo, the store, and the vault. If you do not, start with account recovery, not with features.

Do you need production customer data?

No. We need a staging path and a schema. Do not send a live export to a personal chat.

How long is a handover increment?

Often one to two weeks to become dangerous in a useful way. A same-day takeover is a myth unless the repo is already clean.

What if the old contractor refuses?

You still have Apple if you are Account Holder. Rotate secrets. Treat the old binary as untrusted until you ship your own.

Will you keep their architecture?

If it is safe and clear. We will not rewrite for taste in week one. We will isolate a shared admin if it sits in the consumer target.