{"id":988623,"date":"2026-10-05T11:00:00","date_gmt":"2026-10-05T11:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988623"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"how-to-check-istanbul-studio-references","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/how-to-check-istanbul-studio-references\/","title":{"rendered":"How to Check Istanbul Studio References"},"content":{"rendered":"
\n

A reference is a person who will tell you what it was like to ship. A logo wall is advertising. When you hire in Istanbul you still need the same conversation you would have in any city, plus timezone and entity checks. The hiring checklist is a sibling: what to check when hiring<\/a>. This page is how to run the reference itself. Croncode LLC is in Albuquerque. Engineering is in Istanbul. We are not croncodetech.com.<\/p>\n

\n

Check Istanbul studio references by speaking to a person who shipped, confirming who owned the Apple account, and looking at a live listing. A slide of logos is not a reference.<\/p>\n<\/blockquote>\n

Who should you ask to speak with?<\/h2>\n

The product owner who sat in the demos, not a salesperson who joined after launch. Ask for a name and a year. Ask whether that person still has the App Store listing. Account ownership: who owns the account<\/a>. If they cannot show a listing, ask for a TestFlight story you can verify another way. Live consumer proof we can show is ours: YourStyle<\/a>, Numira<\/a>, Spylie<\/a>, Luviport<\/a>.<\/p>\n

Our names are public: Goktug Unver<\/a>, Yusufhan Sokur<\/a>, Ozgur Ismet Ozkan<\/a>. Do not invent a biography for Ozgur. A short public profile is enough.<\/p>\n

Which questions survive a polite call?<\/h2>\n
    \n
  1. Who submitted the binary, and whose Apple org was it?<\/li>\n
  2. What slipped after version one, and who stayed?<\/li>\n
  3. How did they handle a crash on the first job? Crash questions<\/a>.<\/li>\n
  4. Did the sprint demo show a build or a deck? Sprint demo<\/a>.<\/li>\n
  5. Was the support inbox alive? Support email<\/a>.<\/li>\n<\/ol>\n

    Vendor models: studio vs freelancer vs agency<\/a>. iOS selection: choose an iOS studio<\/a>.<\/p>\n

    When is a reference useless?<\/h2>\n\n\n\n\n\n\n\n\n
    Signal<\/th>\nTreat as weak<\/th>\nTreat as useful<\/th>\n<\/tr>\n<\/thead>\n
    No overlap hour mentioned<\/td>\nYes<\/td>\nThey name a clock<\/td>\n<\/tr>\n
    \u201cThey were cheap\u201d<\/td>\nYes<\/td>\nThey name ownership<\/td>\n<\/tr>\n
    Cannot say who wrote Turkish<\/td>\nYes if you need TR<\/td>\nThey name a reviewer<\/td>\n<\/tr>\n
    NDA blocks every fact<\/td>\nOften<\/td>\nThey can still describe process<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Localization: onboarding localization<\/a>. Commercial shape: fixed price vs retainer<\/a>. Security: security questions<\/a>.<\/p>\n

    How do you verify without being rude?<\/h2>\n

    Open the App Store listing they cited. Read recent reviews as a team habit you will also use on your own app: reviews<\/a>. Check that the legal name on the invoice matches the entity they want you to sign. Identity hygiene: Croncode vs croncodetech<\/a>. Shipping story: how we ship<\/a>.<\/p>\n

    If they only offer a marketing site, that can still be real work. It is not store proof. When a site is enough<\/a>.<\/p>\n

    What mistakes waste the reference week?<\/h2>\n