Pinyin search on Mac, plus romaji and Korean chosung.
Type wx and 微信 comes up. Type wyy and 网易云音乐 comes up. Coco indexes every installed application by how its name sounds as well as how it is spelled, so apps named in Chinese, Japanese or Korean answer to a Latin keyboard. This page sets out exactly how each script is handled, and exactly where the handling stops.
Why pinyin search on Mac decides whether a launcher gets used at all
A launcher only pays for itself once it is automatic, and an automatic habit dies at the first reliable failure. If your Applications folder holds 微信, 网易云音乐, メモ or 카카오톡, that failure arrives on the first day. You press the hotkey mid-sentence in English and the app you want is written in characters your keyboard is not currently producing. Switch input method, type two Han characters, switch back — four actions to replace one, and slower than reaching for the Dock. So you reach for the Dock, and the launcher becomes something you paid for and stopped opening. In China, Japan and Korea this is not an edge case, it is most of the list. A launcher that cannot find 微信 when you type wx is not a launcher with a gap in it; it is a launcher you quietly abandon.
The obvious alternatives do not close this. Spotlight has carried some pinyin handling in system search for years and will often do something sensible with a Chinese app name. Raycast and Alfred, as of August 2026, ship no pinyin, romaji or chosung matching for application names at all. Both let you attach a custom keyword to an app, so you can make weixin open 微信 — after you go and tell them so, by hand, once per app. That is a reasonable workaround for five apps. It is not a way to search Chinese apps on Mac when forty of them are named in Han characters, and it does nothing the first time you install something new.
Coco takes the other approach: derive the sound at index time, for every app, without being asked. When the app list is built, each application contributes its name, its localised name, its bundle name, a condensed pinyin form and any aliases you have added. From those names Coco derives phonetic keys: pinyin for Han, romaji for Japanese kana, romanisation and 초성 initial consonants for Hangul. All of it is computed on the machine with the transliteration data macOS already ships, so pinyin search on Mac here means no dictionary download, no account, no network call, and nothing typed into the panel leaving the Mac. The same index backs the search panel and the full-screen app grid, so a query that works in one works in the other.
What pinyin search on Mac has to get right
Chinese: whole-word readings, and no tones to type
Pinyin is generated by the system word tokenizer under a Chinese locale, so it segments before it transliterates and gets context-dependent readings right: 音乐 becomes yin yue, not the yin le you get from transliterating one character at a time. Tone marks are stripped afterwards, so the index is toneless and so is your query — type weixin, not wēixìn, and note that tone numbers are not understood either, so wei1xin4 will not match. On top of that, 35 common polyphonic characters (乐, 行, 长, 重, 都, 调 and the rest) are enumerated with every reading worth searching, so a name is reachable by either. The variant count per name is capped at 24 so a character-dense name cannot inflate the index.
Chinese: initials, and the point where initials stop
Initials are taken from the word boundaries in the romanised form, not from every character. 网易云音乐 romanises as three words — wangyi yun yinyue — so its initials are wyy, and wyy hits a dedicated acronym tier that scores well above a fuzzy guess. 钉钉 gives dd, 百度网盘 gives bw. Per-character initials are a different thing: bdwp for 百度网盘 is not in the initials tier, and neither is wx for 微信, because 微信 is one word and its initials are just w. Both still match, through the subsequence tier below, which means they find the app but can be outranked by a prefix match on something else. If you type wx constantly, add it as an alias and it becomes an exact match.
Japanese: romaji search on Mac, from kana only
A Japanese romaji key is generated only when the name contains real kana. メモ indexes as memo, カレンダー as karenda, 音楽アプリ as ongakuapuri, and one small override table exists for readings the transliterator gets wrong for app names (日本 → nihon, nippon). Two honest limits. Long vowels collapse, so カレンダー is karenda and the English word calendar does not match it — nor does karendaa. And a kanji-only Japanese name gets no romaji at all: 写真 falls through the Chinese path and indexes as xiezhen, not shashin. That is deliberate — loading the Japanese transliteration data is a process-wide, unreclaimable cost we will not impose on users with no Japanese content — but it is a real gap, and the fix is an alias.
Korean chosung search, computed rather than looked up
Hangul syllables are laid out at U+AC00 as (lead × 21 + vowel) × 28 + tail, so the initial consonant is (code point − 0xAC00) ÷ 588 into a table of 19 leads. 카카오톡 becomes ㅋㅋㅇㅌ with no dictionary and nothing to maintain, and typing ㅋㅋㅇ prefix-matches it. The leads are emitted as compatibility jamo, the same code points a Korean IME produces for a lone consonant, so the index side and the query side agree. A query made only of jamo bypasses transliteration entirely, so it stays intact. Non-Hangul characters pass through, so Safari 사파리 indexes as Safari ㅅㅍㄹ. A romanised key is stored too: 카카오톡 gives kakaotog, which kakao matches.
Where transliteration is wrong, you get the last word
Machine romanisation is a transliteration, not a brand's English name. 네이버 comes out neibeo, not naver; 사파리 comes out sapali; 카카오톡 comes out kakaotog, so kakaotalk misses. Rather than pretend otherwise, Coco lets you attach as many extra names as you like to any app under Settings → App Aliases. An alias goes through the whole indexing path, phonetic keys included, so a Chinese alias gets its own pinyin and initials. Editing one changes a fingerprint over your apps and aliases, which rebuilds the index on the next search. The index is built once and warmed on a background thread, so none of this runs per keystroke.
Pinyin search on Mac: Coco next to Spotlight, Raycast and Alfred
This is the row of the comparison table where Coco is furthest ahead, and it is worth being precise about why. Spotlight does handle Chinese pinyin to some degree in system search, so for Chinese app names it is not nothing. For Japanese romaji and Korean chosung against app names we have not verified Spotlight's behaviour and will not guess, so those cells say so. Raycast and Alfred have no built-in phonetic matching for app names in any of the three scripts; both offer manual per-app keywords instead. Everything in the Coco column below is derived automatically at index time, for every installed app, with no per-app setup.
The rest of the picture is on the launcher page. Raycast has a far deeper extension ecosystem, Alfred has twenty years of workflows, and Spotlight indexes document contents in a way none of the third parties attempt. Coco has no window management and no native text expander. Coco is $99 once for one Mac, $49 at the launch price, with a seven-day trial that needs no card and no account and a 14-day refund with no questions asked. It needs Apple Silicon and macOS 14 or later. If phonetic matching is not the thing costing you time, buy on something else.
| Coco | Spotlight | Raycast | Alfred | |
|---|---|---|---|---|
| Full pinyin finds a Chinese-named app | Partial | |||
| Pinyin initials (wyy → 网易云音乐) | Not verified | |||
| Both readings of a polyphonic character | Not verified | |||
| Romaji for kana names (メモ → memo) | Not verified | |||
| Romaji for kanji-only Japanese names | Not verified | |||
| Korean chosung (ㅋㅋㅇ → 카카오톡) | Not verified | |||
| Hangul romanisation (kakao → 카카오톡) | Not verified | |||
| Derived automatically, no per-app setup | ||||
| Your own aliases get pinyin too | ||||
| Same matching in the full-screen app grid | ||||
| Runs with no network | Mostly | |||
| Price | $49 once | Included | Free or $8/mo | £34 once |
Setting up pinyin search on Mac takes no setup
Install Coco and open it once
Drag it into Applications and launch it. It reads what you have installed and builds the per-app index, phonetic keys included, on a background thread. There is nothing to enable and no language to pick: the scripts present in your app names decide which keys get generated. The panel comes up on Option-Space, which you can change.
Test it against your own five worst apps
Do not take the examples on trust — the point of this page is that you can disprove it in ten seconds. Open the panel and type the pinyin, initials, romaji or chosung for the five apps you open most. Most will land. Note the ones that do not; that list is short and specific, and step three is for it.
Add an alias for anything that missed
Settings → App Aliases. Pick the app, add as many names as you want: kakaotalk for 카카오톡, shashin for a kanji-only Japanese name, wx for 微信 if you want it as an exact match rather than a fuzzy one. Each alias is indexed exactly like the real name, so a Chinese alias picks up its own pinyin and initials. The index rebuilds on your next search.
Use the same queries in the app grid
Coco's full-screen grid is filtered by the same index the search panel uses, so wyy narrows the grid the way it narrows the list. There is nothing separate to configure, and no second place where a name can be missing. If a query works in one, it works in the other.
Questions people actually ask
- Can I search for Chinese apps on my Mac by typing pinyin?
- Yes. When Coco builds its application index it romanises each app name with the transliteration data macOS already ships, using a Chinese locale and word-level segmentation, and stores the result alongside the real name. 微信 indexes as weixin, 支付宝 as zhifubao, 网易云音乐 as wangyiyunyinyue. Typing any prefix of those finds the app. Because segmentation happens before transliteration, context-dependent readings come out right — 音乐 is yin yue rather than yin le. Tone marks are stripped from both the index and your query, so you type plain letters; tone numbers such as wei1xin4 are not understood. Nothing is downloaded and no request leaves your Mac.
- Do pinyin initials work, and which ones?
- Initials are taken from the word boundaries of the romanised name, so 网易云音乐 romanises as wangyi yun yinyue and its initials are wyy, which matches through a dedicated acronym tier that outranks fuzzy guesses. 钉钉 gives dd and 百度网盘 gives bw the same way. Per-character initials are a separate case: bdwp for 百度网盘, or wx for 微信 whose romanisation is the single word weixin, are not in the initials tier. They still find the app through the subsequence tier underneath it, so the result appears but can sit below a prefix match on another app. If you type one of them constantly, add it as an alias and it becomes an exact match.
- How does romaji search on Mac work for Japanese app names?
- Coco generates a Japanese romaji key for an app name when that name contains real kana. メモ indexes as memo, カレンダー as karenda, and a mixed name like 音楽アプリ as ongakuapuri, so typing ongaku finds it. Two limits are worth knowing before you test it. Long vowels collapse in the index, so カレンダー is karenda: neither karendaa nor the English word calendar will match it. And a name written only in kanji gets no romaji key at all — 写真 is indexed by the Chinese path as xiezhen, not shashin. That is a deliberate trade to avoid loading Japanese transliteration data for users who have no Japanese apps. An alias covers both cases.
- How does Korean chosung search work?
- It is arithmetic rather than a dictionary. Modern Hangul syllables occupy U+AC00 to U+D7A3, laid out as (lead × 21 + vowel) × 28 + tail. The leading consonant of any syllable is its code point minus 0xAC00, divided by 588, indexed into a table of 19 leads. 카카오톡 becomes ㅋㅋㅇㅌ, and typing ㅋㅋㅇ prefix-matches it. The leads are written as compatibility jamo — the same code points a Korean IME emits when you type a lone consonant — so what you type and what is indexed are the same characters. Characters that are not Hangul pass through untouched, so Safari 사파리 indexes as Safari ㅅㅍㄹ. Nothing about this needs maintaining or updating.
- Can I find a Korean app by typing its name in Latin letters?
- Usually, but read this before relying on it. Alongside the chosung key, Coco stores a machine romanisation of the Hangul: 카카오톡 becomes kakaotog, so typing kakao finds it. What that romanisation is not is the brand's own English spelling. 카카오톡 gives kakaotog, so kakaotalk does not match. 네이버 gives neibeo, not naver. 사파리 gives sapali. This is transliteration doing exactly what transliteration does, and no launcher can guess a brand name from syllables. The fix takes ten seconds: open Settings → App Aliases, attach kakaotalk or naver to the app, and the alias is indexed like any other name.
- Do Spotlight, Raycast or Alfred do this?
- Partly, and mostly not. Spotlight has carried some Chinese pinyin handling in system search for years, so Chinese app names are not a blank there. We have not verified how it treats Japanese romaji or Korean chosung against app names, so we do not claim either way. Raycast and Alfred, checked in August 2026, have no built-in pinyin, romaji or chosung matching for application names. Both offer manual per-app keywords, which solves it one app at a time if you remember to do it and redo it for anything you install later. Coco derives all of this automatically at index time, for every installed app, with no per-app setup.
- What does Coco cost, and what does it need?
- Seven days free with no card and no account to create, then $99 once for one Mac, currently $49 at the launch price. It is a one-time purchase rather than a subscription: no renewal, updates within this major version included, a 14-day refund with no questions asked, and you can move the licence to another Mac yourself. It requires Apple Silicon and macOS 14 or later. Phonetic matching needs no configuration and no network. What Coco does not have is window management, a native text expander, or document-content search of the kind Spotlight does — if one of those is what you are shopping for, buy the other thing.
Copy the prompt, or send it straight to the AI you already use — it drives Coco through the same commands you would type yourself.
Install the Coco skill (npx skills add butterflydream-ai/Coco --skill coco -g -y), then use coco to help me with Pinyin search on Mac, plus romaji and Korean chosung..