Onboarding is the first argument that the app will not waste a person. Localization is not swapping words in a spreadsheet. It is choosing examples, permission reasons, and a tone that fits the market. Croncode ships consumer iOS with English and Turkish as a default pair. This page is about onboarding as a product, not about file formats. Broader market work lives in scalability and localization.

Onboarding localization is meaning, examples, and legal tone, not a string catalog dump. If Turkish and English share one joke and one legal hedge, you translated words and missed the user.

What has to change besides the catalog?

The first job example. The photo or case you show. The reason you ask for notifications or camera. The paywall’s three honest lines. The support sentence that says how fast a human replies. Trust patterns: trust onboarding. Push: earn the permission. Paywalls: honest paywalls.

A closet in Istanbul weather is not a closet in a US office campus. A decision example that cites a US school calendar may confuse a Turkish user. A chauffeur window that assumes one airport code set will look careless. Products: YourStyle, Numira, Luviport. A narrative game needs spoiler-safe language in both tongues: Spylie.

Which onboarding steps should you cut per locale?

1. A cultural joke that only one language can carry.
2. A legal claim you cannot defend in that market.
3. A permission you do not need for the first job.
4. A tour of tabs that do not exist in that build.

Thin but complete still applies: MVP too thin. Feature creep in two languages is twice the debt: feature creep.

When is a translator not enough?

Design QA must run in both languages on a small phone: design QA. Accessibility labels need locale too: accessibility.

How does an Istanbul studio work the two files?

English and Turkish move in the same increment. We do not “add TR later” if the listing is in Turkey. Overlap hours: Istanbul hiring. Shipping: how we ship. People: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan.

Naming must be speakable in both markets: naming. Week two copy is onboarding’s cousin: week two.

What mistakes look like being global?

• Machine-translated legal text: you will eat the screenshot.
• Mixed language tickets: a missed review note. Write the working language.
• English screenshots on a Turkish listing: users feel baited.
• AI examples that assume one culture’s wardrobe or holidays: AI brief.

Studio: Croncode. Quote languages in the packet: what to send. Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/.

What should you send for an onboarding localization pass?

The first job, the not-now list, who writes legal, and three examples that are allowed in each market. If you already have users, send the support phrases that repeat: support email. Seasonal lines need their own calendar: seasonal content. Catalog: what Croncode builds.

We will not claim a rank in either language. ASO: positioning. A keyword pile in the subtitle is not localized onboarding. The first job sentence must still be a sentence a tired person can use. If the English line is “Build a look from clothes you own” and the Turkish line is a list of nouns, you translated for search and missed the user. Put the job first. Put keywords second, and only if they are true.

Frequently asked questions

Can I ship English first and Turkish in 1.1?

Yes if the first market is English-only. If you already live in Turkey and sell there, treat Turkish as version one.

Do I need a native speaker on the team?

You need a native reviewer for user-facing meaning. A catalog tool is not a reviewer.

Should onboarding length match in both languages?

No. Turkish lines often run longer. Design for the longer locale or you will clip.

Is the store subtitle part of onboarding?

Yes. It is the sentence before install. Localize the job, not a pile of keywords.

Who owns locale QA at Croncode?

Design owns meaning. Engineering owns that the string is not hardcoded. Both sign the build note.