Name Recognition & Called-Name Alerts App Store Listing in Simplified Chinese — 姓名识别 & 叫到名字时通知 zh-Hans Copy

Who this is for

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

• Already ship or market an app whose buyers use Name Recognition — notify when someone says my name, called-name alerts, or name-called notifications under Settings → Accessibility → Sound & Name Recognition → Name Recognition
• Market Name Recognition, called-name alerts, notify when someone says my name, or 姓名识别 / 名字识别 / 叫到名字时通知 on the en-US product page and in screenshot galleries
• Finished called-name alert UX or Name Recognition-compatible workflows in the binary — not looking for Speech framework plumbing or on-device name-detection engineering help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on Name Recognition gallery frames
• Need paste-ready Connect text — not an engineer for microphone listening pipelines, not a designer to re-export every notification demo from scratch

If your lead feature is Sound Recognition — ambient alerts for alarms, doorbells, animals, and similar environmental sounds — that is a sibling setting under Sound & Name Recognition but a different buyer story. See Sound Recognition listing (zh-Hans). If users rely on Speak Screen to read on-screen text aloud — not name-called notifications — see Speak Screen listing (zh-Hans). If your lead feature is Live Listen microphone streaming to AirPods — not name detection — see Live Listen 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.

Name Recognition listing copy vs name-detection engineering — two different jobs

Teams assume called-name alert capability covers storefront language. iOS, Speech APIs, and Connect actually separate in-app name listening from product-page copy:

• Name Recognition in the app — on-device listening for the user's name or nicknames, notification routing when a name is detected, integration with system Name Recognition settings, and microphone permission flows. Engineering inside the binary — outside AppLocale scope.
• Speech and audio pipeline implementation — distinguishing name detection from ambient sound classifiers, ensuring alerts fire reliably in headphones-on scenarios, and testing notification UX when someone nearby says the user's name. Engineering — not listing rewrite.
• Called-name marketing on the product page — description paragraphs, subtitle positioning, keywords, promotional text, and screenshot overlays that tell buyers your app supports Name Recognition or called-name alerts. Connect text fields — this page.
• Pricing and Availability → China — makes the app downloadable on the China storefront. Separate from language rows.
• App Store tab → Chinese (Simplified) localization — independent row for title, subtitle, keywords, description, promotional text, and screenshot caption lines. Empty or English here means China buyers see English fallback regardless of Name Recognition support in the app.

A Name Recognition-compatible app and a localized China listing are both valuable — neither replaces the other. AppLocale covers how you describe called-name notification value on the store page, not whether name detection runs inside the app.

Name Recognition vs Sound Recognition, Speak Screen, Live Speech, Live Listen, and Voice Control — disambiguation

Apple groups several hearing and speech features under Accessibility. Indie teams conflate them on one product page. AppLocale covers Name Recognition and called-name alert marketing on listing metadata — not the other toggles:

• Name Recognition (this page) — iOS listens for the user's name or nicknames spoken nearby and sends a notification. Useful with headphones on or for hearing accessibility. Gallery frames may show Settings → Sound & Name Recognition → Name Recognition toggles, called-name notification previews, or "Notify when someone says my name" badges. zh-Hans terms: 姓名识别, 名字识别, 叫到名字时通知. Apple documents English-name listening; listing copy must stay honest to that scope.
• Sound Recognition (different) — alerts for alarms, doorbells, animals, smoke alarms, and other environmental sounds — 声音识别. Same parent pane (Sound & Name Recognition / 声音与姓名识别) but a different listener. See Sound Recognition listing guide — environmental sound alerts are not called-name notifications.
• Spoken Content / Speak Screen (different) — the device reads on-screen text aloud — 说出内容 / 朗读屏幕. See Speak Screen listing guide — text-to-speech reading is not listening for your name.
• Live Speech / Personal Voice (different) — the user types or speaks as their own synthesized voice for FaceTime and communication — not listening for names nearby. See Live Speech listing guide and Personal Voice listing guide — outbound voice output is not inbound name detection.
• Live Listen / Hearing Devices (different) — microphone streaming to AirPods or Made for iPhone hearing aids for conversation amplification — 实时收听 / 助听设备. See Live Listen listing guide and Hearing Devices listing guide — hearing-aid streaming is not name-called alert marketing.
• Voice Control / Vocal Shortcuts (different) — speech commands to control the device or trigger custom spoken phrases — not passive name detection notifications. See Voice Control listing guide and Vocal Shortcuts listing guide — command-and-control speech is not notify-when-someone-says-my-name listening.
• Headphone Accommodations / Background Sounds (different) — headphone EQ tuning and ambient focus loops under Hearing — not name recognition. See Headphone Accommodations listing guide and Background Sounds listing guide when those are your lead claims.
• VoiceOver (different) — screen reader navigation — not called-name alerts. See VoiceOver listing guide.

Your gallery may show a Name Recognition toggle on one frame and a Sound Recognition sound-type picker on the next — but listing copy should name each claim accurately per frame. A called-name notification demo is not a baby-cry alert, not a Speak Screen read-aloud panel, not a Live Listen AirPods walkthrough, and not a Voice Control command sheet unless that is what the screenshot shows.

What Name Recognition actually does — listing honesty

Apple ships Name Recognition in iOS and iPadOS Settings → Accessibility → Sound & Name Recognition. When enabled, the device listens for the user's name or nicknames spoken nearby and sends a notification — helpful when wearing headphones or for hearing accessibility. Apple notes that Name Recognition listens for English names and is not intended for emergency reliance. Third-party apps may complement this with called-name alert workflows your binary actually ships. AppLocale rewrites listing copy from what your US page already claims:

• If your app complements system Name Recognition — zh-Hans copy can describe called-name notifications, nickname support, or headphones-on name alerts your binary actually ships — without claiming to replace the system setting or detect every language unless your English listing already states that accurately.
• If your app ships custom called-name alert UX — description and screenshot overlays should name the notification benefits you deliver (姓名识别, 叫到名字时通知, 有人叫名字时提醒) in commerce-idiomatic Chinese, not generic "always hears your name" overclaims.
• Separate Name Recognition from Sound Recognition in copy — Sound Recognition alerts for environmental sounds like doorbells and smoke alarms; Name Recognition alerts when someone says your name. Listing vocabulary must follow your English lead feature and gallery frames.
• No medical or emergency claims — do not imply Name Recognition replaces hearing aids, medical monitoring, or emergency alerting in zh-Hans copy unless your English listing already makes that claim — and AppLocale does not certify safety outcomes.
• If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not invent broader Name Recognition scope than your screenshots and description support.

Clear zh-Hans copy helps buyers who rely on called-name notifications understand your feature story before install. It does not replace Speech framework implementation, microphone permissions, or Apple's review decisions — and it does not promise the device will always hear every name in every environment.

Where English Name Recognition copy shows on the China product page

Hearing-accessibility apps often lead marketing screenshots with Name Recognition toggles, called-name notification previews, or headphones-on alert demos — surfaces where English marketing text appears beside notification UI:

• Screenshot overlay badges — "Notify when someone says my name", "Name Recognition support", "Called-name alerts", "Hear your name with headphones on", "Nickname alerts" on gallery frames
• Description paragraphs — English value props ("Works with Name Recognition", "Get notified when someone calls your name") that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 姓名识别, 名字识别, or 叫到名字时通知 when buyers filter for called-name alert apps
• Promotional text — 170-character field still pitching Name Recognition in English above the description
• Mixed page — Chinese description pasted once but Name Recognition screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 that conflates 姓名识别 (Name Recognition) with 声音识别 (Sound Recognition) or 语音识别 (speech recognition for commands) on store pages

Better zh-Hans listing copy helps called-name alert buyers understand your notification story before install. It does not replace name-detection code, microphone entitlements, or Apple's review decisions.

Common mistakes on Name Recognition zh-Hans listings

• Leaving "Name Recognition" untranslated — Apple and buyers expect 姓名识别 or 叫到名字时通知 in zh-Hans regions; English-only overlay lines on otherwise Chinese copy looks unfinished
• Machine-translated "Name Recognition" as 名字识别 alone — may miss the accessibility setting sense; align with buyer-facing terms like 姓名识别 or 叫到名字时通知 depending on your UX
• Conflating Name Recognition with Sound Recognition — 声音识别 environmental sound alerts are not 姓名识别 called-name notifications; both live under Sound & Name Recognition but serve different buyers
• Conflating Name Recognition with Speak Screen — 朗读屏幕 read-aloud is not passive name listening; TTS output is not called-name alert input
• Conflating Name Recognition with Live Speech or Personal Voice — synthesized user voice for communication is not listening for names spoken nearby
• Conflating Name Recognition with Live Listen or Hearing Devices — 实时收听 microphone streaming and MFi hearing-aid pairing are not name-called notification marketing
• Conflating Name Recognition with Voice Control or Vocal Shortcuts — speech commands to control the device are not notify-when-someone-says-my-name alerts
• Overclaiming emergency or medical reliability — Apple notes Name Recognition is not for emergency reliance; zh-Hans copy should not promise life-safety outcomes
• Assuming called-name alert integration localizes the store page — engineering and App Store metadata are independent workstreams

What AppLocale delivers for Name Recognition apps on zh-Hans

This SKU is a listing rewrite scoped to Name Recognition and called-name alert 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 姓名识别 to China searchers
• Subtitle — concise benefit line that can reference called-name alerts or Name Recognition support without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for 姓名识别, 名字识别, 叫到名字时通知, and hearing-accessibility notification claims in your category
• Description — long listing body with clear zh-Hans paragraphs on Name Recognition and called-name alert features you already ship — without English-only notification 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 Name Recognition UI ("叫到名字时通知", "支持姓名识别", "戴耳机也能听到叫名")
• English alignment — matching en-US field notes when both storefronts must stay consistent on Name Recognition promises

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

Name Recognition-specific listing vocabulary — what translates differently

Called-name marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe Name Recognition — not a literal paste of US marketing:

Name Recognition vs generic "name alerts"

US pages use "Notify when someone says my name", "Name Recognition support", or "Called-name alerts." China storefront copy often uses 姓名识别, 叫到名字时通知, or 有人叫名字时提醒 — depending on whether you mean Apple's Name Recognition setting specifically, custom in-app called-name workflows, or general notification UX. AppLocale aligns phrasing with your actual scope, not inventing Name Recognition support your app does not ship.

Name Recognition vs Sound Recognition — same pane, different feature

Both settings live under Sound & Name Recognition (声音与姓名识别). Name Recognition listens for the user's name — 姓名识别. Sound Recognition listens for environmental sounds like doorbells and smoke alarms — 声音识别. zh-Hans listing copy should not imply 声音识别 when your English source only markets called-name notifications. See the Sound Recognition listing guide only if ambient sound alerts are your lead marketing claim.

Name Recognition vs Speak Screen and Live Speech

Speak Screen reads on-screen text aloud — 朗读屏幕. Live Speech lets the user type and speak as their own voice — outbound communication, not inbound name listening. Name Recognition passively listens for names spoken nearby — 叫到名字时通知. Each surface has distinct buyer vocabulary and should not appear interchangeably in one keyword field unless your English listing genuinely markets all three.

Name Recognition vs Live Listen and Hearing Devices

Live Listen streams live microphone audio to AirPods for conversation amplification — 实时收听. Hearing Devices covers MFi hearing-aid pairing and audiology hardware — 助听设备. Name Recognition sends a notification when someone says your name — different buyer intent from streaming or hardware pairing. zh-Hans copy should not imply 实时收听 when your gallery only shows called-name notification demos.

English-name listening scope

Apple documents that Name Recognition listens for English names. zh-Hans listing copy can describe the called-name notification benefit honestly — 有人叫名字时提醒 — without over-specifying language coverage or claiming detection in every acoustic environment unless your English gallery shows that consistently.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need called-name search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 姓名识别, 叫到名字时通知, and 名字识别 each signal different intent from 声音识别 Sound Recognition keywords.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Notify when someone says my name" headlines on gallery frames showing Settings → Accessibility → Sound & Name Recognition → Name Recognition — 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.

Before / after — Name Recognition listing phrases (en-US → zh-Hans)

Concrete examples AppLocale rewrites from your English source — not Sound Recognition, Speak Screen, or Live Listen copy:

• Screenshot caption — Before: Notify when someone says my name → After: 有人叫名字时通知你
• Description line — Before: Get alerted when someone calls your name nearby → After: 附近有人叫你的名字时会收到提醒
• Subtitle (30 chars) — Before: Called-name alerts → After: 叫到名字时通知
• Screenshot caption — Before: Name Recognition support → After: 支持姓名识别
• Keyword field — Before: Name Recognition,called name,notify me,accessibility → After: 姓名识别,叫到名字,名字提醒,无障碍
• Promotional text — Before: Now supports Apple Name Recognition → After: 现已支持 Apple 姓名识别

Final phrasing depends on your English claims, Name Recognition surfaces on gallery frames, and Connect character caps. See Promotional text in Simplified Chinese when your called-name pitch lives in promo text rather than the long description.

Why English-only Name Recognition copy hurts China storefront conversion

Hearing-accessibility purchasers browsing the China App Store evaluate called-name notification claims in the first scroll. Common failure modes when only en-US is filled:

• Trust gap — Chinese word-of-mouth recommends a "name-alert app"; buyer taps through and sees English "Notify when someone says my name" with no zh-Hans context
• Localized listing, English badges — description promises Chinese called-name support; screenshot overlays still "Name Recognition support" at the worst moment
• Search intent miss — buyers search 姓名识别 or 叫到名字时通知; English-only keywords miss intent even when Name Recognition works in the app
• Competitor contrast — rivals with native zh-Hans called-name copy look more serious about China hearing-accessibility buyers
• Sibling-setting confusion in translation — machine-translated copy that says 声音识别 when you mean 姓名识别, or 朗读屏幕 when you mean name alerts — buyers misread your actual feature scope

Clearer zh-Hans called-name marketing reduces confusion on the product page. It does not replace name-detection implementation, microphone permissions, or in-app accessibility settings.

Why machine-translated Name Recognition copy fails

• Literal "Name Recognition" → awkward 名字识别 as a product name instead of commerce-idiomatic 姓名识别 (matches iOS Settings → 辅助功能 → 声音与姓名识别 → 姓名识别 vocabulary)
• Generic "name alerts" → 名字提醒 without the accessibility-setting sense buyers expect from 叫到名字时通知
• English badge headlines preserved on zh-Hans screenshots — "Notify when someone says my name" with no Chinese benefit line beside it
• Overlay text overflow — long English called-name captions pasted into short screenshot callout zones truncate on device
• Sound Recognition vocabulary bleed — 声音识别 appearing in zh-Hans copy when English source only mentioned name-called notifications
• Speak Screen or Live Speech phrasing drift — 朗读屏幕 or 个人声音 language when English only described Name Recognition alerts
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention Name Recognition

Machine translation is fine for internal drafts. Finished Name Recognition strings need idiomatic zh-Hans that states what called-name behavior you ship — while keeping accurate scope, honest English-name listening limits, and clear separation from Sound Recognition, Speak Screen, Live Speech, Live Listen, and Voice Control marketing. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans Name Recognition listing copy looks like

Called-name 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) — 叫到名字时通知 — called-name benefit within the ~30-character cap
• Keywords (example) — 姓名识别,叫到名字,名字提醒 — only when accurate to your feature set
• Screenshot overlay (example) — 支持姓名识别，戴耳机也能收到提醒 — Name Recognition frame with clear benefit line
• Description paragraph (example) — plain zh-Hans list of called-name notification workflows you ship — nickname support, headphones-on alerts, integration with system Name Recognition — matching what you actually implemented
• Honest scope — do not claim "detects every name in every language" in Chinese if your English listing and Apple docs scope English-name listening

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

Connect checklist before you order Name Recognition listing copy

1. Open App Store → Chinese (Simplified) — confirm the zh-Hans localization row exists; adding China under Pricing and Availability alone does not fill it
2. Audit five text fields — name, subtitle, keywords, description, promotional text (if used) saved in zh-Hans, not placeholder English
3. List screenshot frames that show called-name UI — note which gallery images show Name Recognition toggles, notification previews, or headphones-on alert demos so caption lines match frame order
4. Export current English captions — overlay text from Connect or your design spreadsheet, including any "Notify when someone says my name", "Name Recognition support", or "Called-name alerts" boilerplate
5. Confirm feature scope honestly — note which called-name workflows you ship so zh-Hans copy does not overclaim system-wide Name Recognition parity or emergency reliability
6. Confirm in-app UI language separately — plan Xcode string localization if notification copy and settings labels are still English after install
7. Skip engineering tasks here — Speech framework setup, name-detection models, and called-name alert QA stay with your dev team

First-time China localization? Start with China App Store localization checklist or AppLocale product page.

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 Name Recognition, called-name alerts, notify when someone says my name, or nickname notifications
• Brief note on which called-name alert workflows your app ships today — so zh-Hans copy stays accurate and honest about English-name listening scope
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a Name Recognition feature launch or App Store 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 Name Recognition and called-name alert 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 name detection works in every environment or for every nickname — listing rewrite describes what you already ship
• No claim that Name Recognition replaces hearing aids, medical monitoring, or emergency alerting — Apple notes it is not for emergency reliance
• No Speech framework, name-detection model, or on-device listening engineering
• No Sound Recognition, Speak Screen, Live Speech, Live Listen, or Voice Control listing copy — each accessibility surface has its own guide when that is your marketing scope
• No accessibility audits, medical marketing, or WCAG consulting
• No screenshot set production, notification-demo PNG re-export, or gallery design
• No guaranteed App Store ranking, keyword position, download growth, or badge 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 Apple Search Ads or review-reply retainers
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

What is Apple Name Recognition and why does listing copy matter?

Name Recognition is under Settings → Accessibility → Sound & Name Recognition → Name Recognition. When enabled, iOS listens for the user's name or nicknames spoken nearby and sends a notification — useful with headphones on or for hearing accessibility. Apple documents English-name listening and that it is not for emergency reliance. Marketing that feature on your en-US page does not auto-fill zh-Hans Connect fields.

Does shipping called-name alerts auto-translate my China listing?

No. Called-name alert workflows in the binary do not create or fill a Simplified Chinese localization row. Empty or English zh-Hans fields mean China buyers see en-US fallback on the product page.

What listing fields does AppLocale rewrite for Name Recognition apps?

Paste-ready Simplified Chinese (zh-Hans) copy for App Store Connect listing fields you specify: title, subtitle, keywords, description, promotional text when included, and screenshot overlay or caption lines that mention Name Recognition, called-name alerts, or notify when someone says my name — rewritten from your English originals with terms like 姓名识别 and 叫到名字时通知 where accurate.

How is this different from Sound Recognition or Speak Screen?

Name Recognition listing copy markets notify-when-someone-says-my-name listener workflows — 姓名识别. Sound Recognition covers ambient sound alerts for alarms, doorbells, and animals — 声音识别. Speak Screen covers the device reading on-screen text aloud — 朗读屏幕. Each is a separate accessibility feature — do not reuse boilerplate across them.

How is this different from Live Speech, Live Listen, or Voice Control?

Live Speech and Personal Voice cover the user typing or speaking as their own synthesized voice. Live Listen streams microphone audio to AirPods for conversation amplification. Voice Control and Vocal Shortcuts cover speech commands. Name Recognition passively listens for names spoken nearby and sends notifications — different buyer intent and screenshot vocabulary.

Does AppLocale implement Name Recognition in my app?

No. We deliver listing metadata copy only. Speech framework pipelines, name-detection models, and in-app notification UX are outside AppLocale scope. We rewrite how you describe existing called-name features on the store page — we do not implement them in the app.

Can zh-Hans copy claim emergency or medical reliability?

No. Apple notes Name Recognition is not for emergency reliance. AppLocale aligns zh-Hans strings to your English source — we do not invent medical, safety, or always-hears-your-name promises.

What character limits apply to zh-Hans Name Recognition fields?

App name and subtitle are each up to 30 characters. Keywords allow up to 100 characters. Description and screenshot caption lines have longer limits but should stay concise — especially overlays that must fit on-device mockups.

What do I send after payment?

Your live App Store listing URL, current English listing copy, screenshot overlay lines mentioning Name Recognition or called-name alerts, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.

Is this machine translation?

No. We rewrite Name Recognition and called-name alert listing copy by hand. We do not paste Google Translate or ChatGPT output into deliverables.

How fast is delivery?

Within 24 hours after your Stripe receipt. Send your App Store URL, English listing and overlay copy, target locales, and deadline from the email on your receipt.

Do you guarantee conversion lift or App Store rankings?

No. We improve clarity from your existing copy. We do not promise keyword position, search rank, or download growth.

How much does AppLocale cost?

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

What is AppLocale not?

Not name-detection or Speech framework engineering, not Sound Recognition or Speak Screen listing copy, not Live Speech or Personal Voice listing copy, not Live Listen or Hearing Devices listing copy, not Voice Control or Vocal Shortcuts listing copy, not accessibility audits, not screenshot set production, 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 — Name Recognition & called-name alert listing copy in Simplified Chinese

$79 one-time

Buy on Stripe

After checkout, reply from your Stripe receipt email with your App Store URL, English listing and Name Recognition overlay copy, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. AppLocale does not implement Name Recognition in your app. Sold by Fortune Insight, LLC.