Music Recognition & Song Identification App Store Listing in Simplified Chinese — 听歌识曲 & 歌曲识别 zh-Hans Copy

Who this is for

Western indie iOS and macOS developers — US, UK, EU, Canada, Australia — who:

• Already ship an app that identifies songs playing nearby — listen-and-identify buttons, song match results, artist and title cards, or Now Playing song ID on screenshots
• Market Music Recognition, Identify Song, Shazam-style song identification, or recognize what's playing on the en-US product page and in screenshot galleries
• Finished song-ID UX in the binary — not looking for ShazamKit, audio fingerprinting SDKs, or MusicKit playlist API engineering help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on song-identification gallery frames
• Need paste-ready Connect text — not an engineer for fingerprint matching, not a designer to re-export every screenshot from scratch

If your lead feature is Apple Music library browsing — playlists, Crossfade, Apple Music Sing, Replay — not song identification, see Apple Music hub listing (zh-Hans). If you market ambient sound alerts — baby crying, smoke alarm, door knock — not music or song ID, see Sound Recognition listing (zh-Hans). If you market Music Haptics rhythm vibration — not recognition — see Music Haptics listing (zh-Hans). If the entire China page is still English on every field, start with China App Store still shows English or the AppLocale product page.

Song-identification engineering vs zh-Hans listing copy — two different jobs

Teams assume song-ID capability covers storefront language. Xcode, entitlements, and Connect actually separate music recognition in the app from product-page copy:

• ShazamKit & audio fingerprinting pipelines — in-app code that captures ambient audio, matches fingerprints, and returns artist and title metadata. Controls identification accuracy and latency. Does not generate Chinese listing text.
• Microphone permissions & catalog APIs — engineering work for listen-and-identify sessions, offline vs online matching, and result UI. Separate from the zh-Hans description paragraph that explains song-ID value to buyers.
• MusicKit vs identification scope — your binary may identify songs without exposing playlist APIs, or vice versa. Listing copy should match what screenshots actually show — not promise MusicKit playlist browsing when your gallery only shows a listen-and-identify button.
• Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
• App Store tab → Chinese (Simplified) localization — independent row for title, subtitle, keywords, description, promotional text, screenshots, and caption lines. Empty or English here means China buyers see English fallback regardless of song identification in the app.

Working song-ID flows in the binary and a localized China listing are both required when you sell on the China storefront — neither replaces the other. AppLocale covers how you describe Identify Song and listen-and-identify workflows on the product page in zh-Hans, not how you implement ShazamKit or audio fingerprinting models.

Music Recognition listing copy is not Apple Music hub, Sound Recognition, or Music Haptics

Music and audio apps blur several surfaces indie teams conflate. AppLocale covers listing metadata only — song identification and listen-and-identify marketing on the product page:

• Music Recognition & song identification (this page) — Music Recognition, Identify Song, Shazam-style listen-and-identify, Now Playing song ID, 听歌识曲, 歌曲识别, 识别正在播放的歌曲, song match result cards, artist and title reveals, and description copy about identifying songs playing nearby.
• Apple Music hub & playlists (different) — Music app home, playlists, Crossfade, Apple Music Sing, Listening History, and Replay on gallery frames. See Apple Music hub listing guide — catalog browsing and playlist marketing is not song identification.
• Sound Recognition & ambient alerts (different) — Recognize sounds, baby crying detection, door knock, smoke alarm, glass break, and environmental sound alerts. See Sound Recognition listing guide — ambient alert workflows are not music or song ID.
• Music Haptics & feel the music (different) — Music Haptics, feel the music, haptic vibration synced to song rhythm, 音乐触感. See Music Haptics listing guide — rhythm haptic feedback is not song identification.
• Dictation & voice typing (different) — Dictate text, Speech-to-text keyboard, Voice typing. See Dictation listing guide — turning speech into typed text is not identifying which song is playing.
• Voice Memos (different) — personal voice recording, memo playback, and transcription of your own recordings — not catalog song matching from ambient audio.

Your screenshots may show multiple surfaces in one gallery. Listing copy should name the correct one per frame — a song match result card is not a playlist row, not a baby cry alert dashboard, not a Music Haptics waveform, and not a dictation mic button unless that is what the frame shows.

Apple system Music Recognition vs your app's song-ID story — listing honesty

Apple ships Music Recognition in Control Center and Shazam integration that listens to ambient audio and identifies songs playing nearby. Third-party apps may offer overlapping identification, custom match history, lyrics after ID, or companion workflows for Now Playing song ID. AppLocale rewrites listing copy from what your US page already claims:

• If your app complements iOS — zh-Hans copy can describe listen-and-identify demos, match history, or integrations your binary actually ships without claiming to replace Control Center Music Recognition unless your English listing already states that accurately.
• If your app is a dedicated song-ID product — description and screenshot overlays should name the identification benefit in commerce-idiomatic Chinese — 听歌识曲, 歌曲识别, 识别正在播放的歌曲 — not generic "AI knows every song" overclaims.
• If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not invent broader catalog coverage than your screenshots and description support.

Clear zh-Hans copy helps buyers understand whether your app identifies songs from ambient audio before install. It does not replace ShazamKit implementation, microphone entitlements, or Apple's review decisions — and it does not certify match accuracy in the app.

What China buyers see when zh-Hans song-ID copy is missing

Song identification apps often lead marketing screenshots with listen buttons, waveform listening animations, song match cards, or Now Playing song ID badges — surfaces where English marketing text appears beside identification UI:

• Screenshot overlay badges — "Identify Song", "Music Recognition", "What's this song?", "Listening…", "Song found", or artist/title reveal headlines on gallery frames
• Description paragraphs — English value props about discovering music, naming unknown tracks, or Shazam-style workflows that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 听歌识曲, 歌曲识别, 识曲, or 音乐识别 when buyers filter for song-ID apps
• Promotional text — 170-character field still pitching song identification in English above the description
• Mixed page — Chinese description pasted once but song-ID screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 for song ID (识别歌曲 vs 听歌识曲 vs 歌曲识别) and wrong phrasing that does not match how Chinese buyers describe music recognition apps on store pages

Better zh-Hans listing copy helps music-discovery buyers understand your song-identification story before install. It does not replace ShazamKit implementation, microphone permissions, or Apple's review decisions — and it does not guarantee match accuracy in the app.

What AppLocale delivers for Music Recognition and song-ID apps on zh-Hans

This SKU is a listing rewrite scoped to music recognition and song-identification marketing — paste-ready fields you copy into App Store Connect:

• Name (title) — zh-Hans app name within Connect character limits when your English title does not signal song identification to China searchers
• Subtitle — concise benefit line that can reference 听歌识曲 or 歌曲识别 without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for 听歌识曲, 歌曲识别, 识曲, and song-ID apps in your category
• Description — long listing body with clear zh-Hans paragraphs on listen-and-identify workflows you already ship — without English-only "Identify Song" jargon
• Promotional text — when you include the 170-character promo field in scope
• Screenshot overlay / caption lines — short zh-Hans text on gallery images that show listen buttons, song match results, or Now Playing song ID badges
• English alignment — matching en-US field notes when both storefronts must stay consistent on song-ID promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Music Recognition or song identification — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent identification features your app does not ship.

Music Recognition-specific listing vocabulary — en-US → zh-Hans

Song-identification marketing on App Store pages uses vocabulary general music or accessibility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe music recognition — not a literal paste of US marketing:

Identify Song vs 听歌识曲 vs 歌曲识别

US pages use "Identify Song", "Music Recognition", "What's this song?", or "Shazam-style song ID." China storefront copy often uses 听歌识曲 (listen and identify songs — the commerce-idiomatic term buyers recognize from system UI and competitor apps), 歌曲识别 (song identification), or 识别正在播放的歌曲 (identify the song currently playing) — depending on whether you mean Control Center Music Recognition branding, your app's listen button, or Now Playing song ID. AppLocale aligns phrasing with your actual identification scope, not inventing catalog coverage your app does not ship.

Now Playing song ID vs playlist marketing

Screenshot galleries may show a Now Playing bar with a "Identify this song" action — that is song-ID marketing (识别正在播放的歌曲), not Apple Music playlist rows (歌单) or library browsing (曲库). Match the workflow each frame actually shows; do not reuse Music hub vocabulary on identification screenshots.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need song-ID search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 听歌识曲, 歌曲识别, and 识曲 each signal different intent from generic 音乐 or playlist keywords.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Identify Song" headlines on gallery frames — are separate caption fields or burned-in PNG text. See Screenshot captions in Simplified Chinese for caption-field mechanics when overlays are editable in Connect.

Promotional text refreshes

New catalog integrations and song-ID feature launches often land in the 170-character promotional text field above the description — updatable without a new binary. See Promotional text in Simplified Chinese when your identification pitch lives in promo text rather than the long description.

What good zh-Hans song-ID listing copy looks like

Music recognition copy appears on screenshot galleries and in description skims. Strong Chinese strings lead with the benefit and state scope plainly — paste-ready examples for Connect fields:

• Subtitle (example) — 听歌识曲，识别附近播放的歌曲 — song-ID benefit within the ~30-character cap
• Keywords (example) — 听歌识曲,歌曲识别,识曲,音乐识别 — only when accurate to your feature set
• Screenshot overlay (example) — 点击识别正在播放的歌曲 — listen-and-identify frame with clear benefit line
• Song match result (example) — 已识别：歌手与歌名 — match card frame showing identification success
• Description paragraph (example) — plain zh-Hans list of identification workflows you ship — listen from microphone, show artist and title, save match history, open in Apple Music — matching what you actually implemented
• Honest scope — do not claim "identifies every song worldwide" in Chinese if your app only matches a regional catalog

zh-Hans and en-US strings can differ in length and structure when the underlying song-ID story is the same — avoid mirroring English comma-heavy promo lines character-for-character.

Why machine-translated song-ID copy fails

• Literal "Identify Song" → awkward 识别歌曲 as a product name instead of commerce-idiomatic 听歌识曲
• Generic "Music Recognition" → 音乐识别 without 识曲 context — buyers may match speech-recognition or ambient-sound keywords instead of song ID
• English badge headlines preserved on zh-Hans screenshots — "What's this song?" with no Chinese benefit line beside it
• Overlay text overflow — long English Shazam-style captions pasted into short screenshot callout zones truncate on device
• Conflating 听歌识曲 with 声音识别 — buyers searching for song identification may not match Sound Recognition ambient-alert keywords meant for baby cry or smoke alarm apps
• Conflating song ID with Apple Music 歌单 vocabulary — playlist marketing copy on an identification screenshot confuses buyers
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention song identification

Machine translation is fine for internal drafts. Finished song-ID strings need idiomatic zh-Hans that states what identification workflows you ship — while keeping accurate scope. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What you send

• Your live App Store listing URL
• Current English listing copy — name, subtitle, keywords, description, promotional text if used
• Screenshot overlay text that mentions song identification ("Identify Song", "Music Recognition", "What's this song?", "Listening…", "Song found", match result captions)
• Brief note on how identification works in your app today — ambient listen, Now Playing song ID, offline vs online catalog, match history — so zh-Hans copy stays accurate
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a song-ID launch or App Store feature update
• Reply from the email address on your Stripe receipt after checkout

What you get

• Simplified Chinese (zh-Hans) — listing fields and screenshot overlay lines scoped to Music Recognition and song-identification marketing, paste-ready for Connect
• English (en-US) — aligned listing strings when both locales need the same promise in native phrasing
• Character-count notes — which strings fit Connect limits and what to trim
• Paste-ready delivery — formatted copy mapped to each field you sent
• 24-hour turnaround — delivered to the email on your Stripe receipt

What we do not promise

• No guarantee that song identification accuracy or match latency improves — listing rewrite describes what you already ship
• No ShazamKit, audio fingerprinting, AVAudioEngine, catalog-matching, or song-ID engineering
• No MusicKit, playlist API, or Apple Music catalog integration engineering
• No claim that your app replaces Apple Control Center Music Recognition unless your English listing already states that accurately — and even then, AppLocale does not certify system parity
• No guaranteed App Store ranking, keyword position, download growth, or identification accuracy certification outcomes
• No fabricated social proof, review quotes, ratings, or traffic numbers
• No binary localization, in-app string translation, or Connect configuration on your behalf
• No screenshot design, PNG re-export, Apple Search Ads, or review-reply retainers
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

Does AppLocale implement ShazamKit or audio fingerprinting?

No. We deliver Connect listing metadata copy only — name, subtitle, keywords, description, promotional text when included, and screenshot caption lines. ShazamKit integration, audio fingerprinting pipelines, catalog-matching APIs, and microphone capture engineering are outside scope.

How is Music Recognition listing copy different from Apple Music hub, Sound Recognition, or Music Haptics?

Music Recognition listing copy covers Identify Song, Shazam-style listen-and-identify, Now Playing song ID, 听歌识曲, and 歌曲识别 — identifying which song is playing from ambient audio. Apple Music hub listing copy covers playlists, Crossfade, Apple Music Sing, and Replay — catalog browsing, not song ID. Sound Recognition listing copy covers baby crying, smoke alarm, and ambient sound alerts — not music identification. Music Haptics listing copy covers feel-the-music haptic vibration synced to song rhythm — not recognition. Those are separate scopes with different screenshot vocabulary.

Should my zh-Hans listing claim to replace iOS Music Recognition in Control Center?

Only if your app actually provides that capability and your English listing already states it accurately. AppLocale rewrites from your source claims — we do not invent system-replacement promises or certify parity with Apple's Music Recognition feature.

What do I send after AppLocale payment?

Your live App Store listing URL, current English listing copy, screenshot overlay lines that mention song identification (with frame order noted), how identification works in your app, and target locale (zh-Hans). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.

Does localizing my listing change in-app song identification?

No. Audio capture, fingerprint matching, catalog APIs, and match-result UI come from your binary and iOS — not Connect listing fields. AppLocale covers product-page marketing copy only.

Will zh-Hans song-ID copy improve China rankings?

We do not guarantee ranking, browse placement, or download lift. Complete zh-Hans metadata helps users who already find your page understand song-identification value in their language — it is not a placement hack.

How much does AppLocale cost?

$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.

What is AppLocale not?

Not ShazamKit or song-ID engineering, not MusicKit or playlist API work, not Apple Music hub listing copy, not Sound Recognition or Music Haptics listing copy, not Dictation or Voice Memos listing copy, not screenshot design, not binary localization, not Connect configuration, not ranking guarantees, not review-reply retainers, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.

AppLocale — zh-Hans listing copy for Music Recognition & song identification apps

$79 one-time

Buy on Stripe

Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English listing copy.
No ranking guarantees. Sold by Fortune Insight, LLC.

AppLocale product page