{"id":988601,"date":"2026-10-03T08:00:00","date_gmt":"2026-10-03T08:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988601"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"how-we-name-apps-before-the-store","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/how-we-name-apps-before-the-store\/","title":{"rendered":"How We Name Apps Before the Store"},"content":{"rendered":"
\n

An app name is a store field, a home-screen label, and a word you will say on calls. We name products at Croncode<\/a> before we fall in love with a mark. The working title can be ugly. The store name cannot be a poem that hides the job. This page is the studio sequence. It is not a list of \u201cbest app names\u201d and it is not legal advice.<\/p>\n

\n

Name the job first, keep a disposable working title, then check collisions and spoken sound. A poetic word that hides the job will fail search and review conversations.<\/p>\n<\/blockquote>\n

What is the difference between a code name and a store name?<\/h2>\n

A code name lives in the repo and in Slack. It should be hard to confuse with a client project. A store name lives on the listing and should survive a tired parent saying it out loud. You can ship a year of TestFlight under a code name. You cannot treat the store field as a mood board the week of submission.<\/p>\n

Public names we already shipped: YourStyle<\/a> says closet and outfit. Numira<\/a> is a coined word tied to a decision job. Spylie<\/a> is a character-led case name. Luviport<\/a> points at a journey, not a generic taxi. Catalog: what Croncode builds<\/a>.<\/p>\n

Which checks happen before we buy a domain?<\/h2>\n
    \n
  1. Say the name in English and in Turkish. If one market cannot pronounce it, write a spoken hint.<\/li>\n
  2. Search the App Store for exact and near twins. Saturation: ASO positioning<\/a>.<\/li>\n
  3. Check the bundle ID plan and who will own it. account ownership<\/a>.<\/li>\n
  4. Check whether the subtitle, not the name, will carry the job.<\/li>\n<\/ol>\n

    We do not claim a name is \u201cavailable worldwide\u201d from a quick search. Counsel handles marks when the product is real. Founder: Goktug Unver<\/a>. Design and web: Yusufhan Sokur<\/a>.<\/p>\n

    When should you keep a boring name?<\/h2>\n\n\n\n\n\n\n\n\n
    Signal<\/th>\nBoring name<\/th>\nCoined name<\/th>\n<\/tr>\n<\/thead>\n
    The job is new to the user<\/td>\nOften better<\/td>\nOnly with a clear subtitle<\/td>\n<\/tr>\n
    The category is crowded with the same noun<\/td>\nMay vanish<\/td>\nIf you can teach it<\/td>\n<\/tr>\n
    Legal collision on the noun<\/td>\nNo<\/td>\nYes, after a check<\/td>\n<\/tr>\n
    You only like the vibe<\/td>\nNo, rewrite<\/td>\nNo, rewrite<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Landing pages must repeat the same word the store uses. Store landing pages<\/a>. If the marketing site is enough as WordPress, do not invent a second brand system: when Elementor is enough<\/a>.<\/p>\n

    How do we avoid copying a competitor\u2019s mouthfeel?<\/h2>\n

    Teardown the job they fail, not their two-syllable pattern. Teardowns without copying<\/a>. If the only brief is \u201clike X but nicer,\u201d you are naming a clone. We will ask for the object instead. Briefing AI work: brief an AI studio<\/a>.<\/p>\n

    What we will not build includes copycat listings. What Croncode will not build<\/a>.<\/p>\n

    What mistakes lock you into a bad name?<\/h2>\n