People Detection App Store Listing in Simplified Chinese — People Detection / Magnifier People Detection / 人物检测 / 检测人 / 行人检测 zh-Hans Copy
Your iOS or iPadOS app already sells people-nearby recognition — People Detection, Magnifier Detection Mode, detect people nearby, low-vision spatial awareness, or 人物检测 / 检测人 / 行人检测 — and your en-US product page shows the user holding the iPhone camera toward a room, sidewalk, or hallway while spoken person distance, position, or appearance cues play on gallery frames.
Open the same app on the China storefront and buyers still land on an English product page: name, subtitle, keywords, description, and screenshot captions that read "People Detection", "Detection Mode", "Detect people", or "Person nearby" in Latin script.
Shipping People Detection or people-nearby UX in the binary does not auto-fill a Simplified Chinese (zh-Hans) localization row.
AppLocale writes paste-ready zh-Hans listing copy for those Connect fields — aligned with how your app actually detects people nearby for low-vision spatial awareness, without conflating People Detection marketing with Magnifier close-up zoom, Door Detection door and exit recognition, Point and Speak camera-point text reading, Live Text OCR, or Visual Look Up image search.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS and iPadOS developers — US, UK, EU, Canada, Australia — who:
Already ship an app with People Detection or Magnifier Detection Mode person recognition — detect people nearby with the iPhone camera, spoken distance and position cues, or appearance descriptions for low-vision users
Market People Detection, Detection Mode, detect people nearby, person recognition, or 人物检测 / 检测人 / 行人检测 / 检测模式 on the en-US product page and in screenshot galleries
Finished person-recognition and spatial-awareness UX in the binary — not looking for computer-vision model training, LiDAR pipeline, or accessibility navigation engineering help here
Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on People Detection gallery frames
Need paste-ready Connect text — not an engineer for Vision or depth APIs, not a designer to re-export every screenshot from scratch
People Detection engineering vs zh-Hans listing copy — two different jobs
Teams assume person-recognition capability covers storefront language. Xcode, camera APIs, and Connect actually separate Detection Mode behavior in the app from product-page copy:
People-nearby recognition — on-device person detection, human bounding boxes, distance estimation, and position cues in the camera viewfinder. Engineering inside the binary — outside AppLocale scope.
Spoken person announcements — converting detected people to spoken distance cues, position feedback, or appearance descriptions for low-vision spatial awareness. Controls voice quality and speaking rate — does not generate Chinese listing text.
Magnifier Detection Mode UI — Detection Mode toggle, People Detection control, and person-targeting reticle in Magnifier-style interfaces. Listing copy should match what screenshots actually show.
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 People Detection features in the app.
Working People Detection 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 People Detection, Detection Mode, and people-nearby spatial awareness on the product page in zh-Hans, not how you implement person recognition or spoken feedback pipelines.
People Detection listing copy is not Magnifier zoom, Door Detection, Point and Speak, Live Text, or Visual Look Up
Accessibility and camera apps blur several surfaces indie teams conflate. AppLocale covers listing metadata only — People Detection and Magnifier Detection Mode marketing on the product page:
People Detection & person recognition (this page) — detect people nearby with the iPhone camera, spoken distance and position cues, appearance descriptions, People Detection, Detection Mode, 人物检测, 检测人, 行人检测, and 检测模式 on gallery frames and in description paragraphs.
Magnifier & close-up zoom (different — already live) — Magnifier, magnifying glass, reading glass zoom, near-distance camera magnification, flashlight magnifier, and color filters for low vision. See Magnifier listing guide — sustained zoom for reading fine print is not people-nearby detection.
Door Detection & exit recognition (different — already live) — find doors and exits with the iPhone camera, spoken door labels, distance cues, exit-direction feedback; 门检测, 检测门, and 门识别. See Door Detection listing guide — door proximity detection is not people-nearby alerts.
Point and Speak & camera-point text reading (different — already live) — point the iPhone camera at physical text on signs, menus, or labels and hear that text spoken aloud; 指着说, 指向朗读, and 指读文字. See Point and Speak listing guide — reading printed text is not detecting people nearby.
Live Text & OCR (different — already live) — extract, copy, or translate text from photos and camera frames; Live Text recognition badges. See Live Text listing guide — text extraction is not low-vision people-nearby awareness.
Visual Look Up & Visual Intelligence (different — already live) — look up objects, plants, landmarks, or products in photos. See Visual Look Up listing guide — image lookup is not Magnifier Detection Mode person alerts.
Speak Screen & VoiceOver (different — already live) — read on-screen content aloud or navigate UI with a screen reader. See Speak Screen listing guide and VoiceOver listing guide — spoken-content accessibility is not camera-based people detection.
Your screenshots may show multiple Magnifier Detection Mode surfaces in one gallery. Listing copy should name the correct one per frame — a People Detection reticle on a hallway with a person nearby is not a magnifier zoom slider, not a Door Detection doorway demo, not a Point and Speak menu-reading demo, not a Live Text copy button, and not a Visual Look Up info card unless that is what the frame shows.
Apple system People Detection vs your app — listing honesty
Apple ships People Detection under Magnifier → Detection Mode on iPhone and iPad — recognize people nearby and hear spoken distance, position, or appearance cues for low-vision spatial awareness. Third-party apps may offer overlapping people-nearby, pedestrian-awareness, or indoor spatial-navigation workflows. AppLocale rewrites listing copy from what your US page already claims:
Do not overclaim system replacement — unless your English listing already states accurate parity, zh-Hans copy should not promise you replace Apple's Magnifier People Detection in Settings
Match gallery frames — if screenshots show pointing at a person in a room or on a sidewalk, subtitle and overlay lines should mention 人物检测 or 检测人 only when those people-nearby demos actually appear on the frames you send
Separate People Detection from Magnifier zoom — "magnify fine print" marketing differs from "detect people nearby" positioning; listing copy should follow your English lead feature
Honest spatial-awareness scope — People Detection helps locate people nearby; AppLocale does not certify indoor navigation accuracy, facial recognition identity claims, or clinical low-vision outcomes; we rewrite marketing claims you already make
Where English People Detection copy shows on the China product page
Western indie teams often ship People Detection UX in the app but leave storefront Detection Mode marketing English-only because the feature works without zh-Hans rows. On the China storefront, English surfaces in places buyers actually read:
Description paragraphs — English value props ("Detect people nearby with your camera") that China readers skim past
Subtitle and keywords — English-only rows miss China Search intent for 人物检测, 检测人, 行人检测, 检测模式, or 放大镜检测模式 when buyers filter for low-vision spatial awareness apps
Promotional text — 170-character field still pitching People Detection in English above the description
Mixed page — Chinese description pasted once but People Detection screenshot captions and subtitle still English — reads unfinished next to localized competitors
Formal machine translation — stiff 翻译腔 for People Detection (人发现 vs 人物检测) and wrong Detection Mode phrasing that does not match how Chinese buyers read store pages
Better zh-Hans listing copy helps low-vision and senior buyers understand your People Detection story before install. It does not replace person-recognition implementation, camera pipelines, or Apple's review decisions.
What AppLocale delivers for People Detection apps on zh-Hans
This SKU is a listing rewrite scoped to People Detection and Magnifier Detection Mode 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 人物检测 or 检测人 to China searchers
Subtitle — concise benefit line that can reference People Detection or people-nearby spatial awareness without stuffing raw English badge text
Keywords — zh-Hans search terms buyers use for 人物检测, 检测人, 行人检测, 检测模式, and 放大镜检测模式 in your category
Description — long listing body with clear zh-Hans paragraphs on People Detection, Detection Mode, and people-nearby features you already ship
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 People Detection UI ("人物检测", "检测人", "行人检测", "检测模式")
English alignment — matching en-US field notes when both storefronts must stay consistent on people-nearby promises
We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions People Detection, Detection Mode, or people-nearby spatial awareness — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent People Detection features your app does not ship.
People Detection-specific listing vocabulary — what translates differently
People Detection marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe people-nearby and low-vision spatial awareness — not a literal paste of US marketing:
People Detection vs Magnifier zoom
US pages use "People Detection", "Detect people nearby", or "Person recognition." China storefront copy often uses 人物检测, 检测人, or 行人检测 — depending on whether you mean Apple's Magnifier Detection Mode People Detection or a third-party spatial-awareness app. Magnifier zoom copy uses 放大镜 or 阅读放大 — a different buyer story. AppLocale aligns phrasing with your actual feature scope.
Detection Mode vs generic camera apps
Screenshot galleries may label Magnifier Detection Mode: "Detection Mode", "People nearby", or camera reticle demos over a person in a room or on a sidewalk. zh-Hans overlay lines may use 检测模式, 人物检测, or 检测人 — matching what your English gallery actually shows, not generic "best camera app" vocabulary.
People nearby vs Door Detection exit finding
People Detection recognizes people nearby for spatial awareness — spoken distance and position cues. Door Detection finds doors and exits for navigation — spoken door labels and exit direction. Listing copy must not conflate 人物检测 (people detection) with 门检测 (door detection) unless your app genuinely ships both and your English listing already claims both accurately.
People nearby vs Point and Speak text reading
People Detection announces person distance, position, or appearance cues. Point and Speak reads printed text on physical objects the camera sees. Listing copy must not conflate 人物检测 (people detection) with 指着说 (point at physical text) unless your app genuinely ships both and your English listing already claims both accurately.
Subtitle and keyword packing
The 30-character subtitle and 100-character keyword field need People Detection–relevant search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 人物检测, 检测人, and 行人检测 each signal different intent from magnifier zoom, door detection, or Live Text OCR keywords.
Before / after — People Detection listing phrases (en-US → zh-Hans)
Concrete examples AppLocale rewrites from your English source — not Magnifier zoom, Door Detection, Point and Speak, or Live Text copy:
Screenshot caption — Before: People Detection → After: 人物检测
Description line — Before: Detect people nearby with your camera → After: 用相机检测附近的人，了解距离和位置
Subtitle (30 chars) — Before: Detect people for low vision → After: 人物检测，低视力感知
Keyword field — Before: People Detection,detect people,person nearby,low vision → After: 人物检测,检测人,行人检测,检测模式,低视力
Promotional text — Before: New — hear when someone is nearby → After: 新功能：附近有人时语音提示
Final phrasing depends on your English claims, People Detection surfaces on gallery frames, and Connect character caps. See Promotional text in Simplified Chinese when your people-nearby pitch lives in promo text rather than the long description.
Why English-only People Detection copy hurts China storefront conversion
Low-vision and senior purchasers browsing the China App Store evaluate people-nearby claims in the first scroll. Common failure modes when only en-US is filled:
Trust gap — Chinese word-of-mouth recommends a "people detection app"; buyer taps through and sees English "People Detection" with no zh-Hans context
Localized listing, English badges — description promises Chinese people-nearby spatial awareness; screenshot overlays still "Detection Mode" at the worst moment
Search intent miss — buyers search 人物检测 or 检测人; English-only keywords miss intent even when People Detection works in the app
Competitor contrast — rivals with native zh-Hans People Detection copy look more serious about China buyers who need spatial-awareness help
Conflation with Magnifier zoom — machine-translated 放大镜 copy on a People Detection gallery frame misleads buyers expecting zoom, not people-nearby alerts
Conflation with Door Detection — 门检测 copy on a People Detection gallery frame misleads buyers expecting door-finding, not person distance cues
Clearer zh-Hans People Detection marketing reduces confusion on the product page. It does not replace person-recognition code, camera APIs, or in-app Detection Mode settings.
Why machine-translated People Detection copy fails
Literal "People Detection" → awkward 人发现 instead of commerce-idiomatic 人物检测 or 检测人
Generic "Detection Mode" → 检测方式 (detection method sense) instead of 检测模式 (Magnifier Detection Mode sense buyers expect)
English badge headlines preserved on zh-Hans screenshots — "Detect people" with no Chinese benefit line beside it
Conflating 人物检测 with 门检测 — people-nearby detection vs Door Detection exit navigation are different Accessibility stories
Conflating 人物检测 with 指着说 — people proximity alerts vs Point and Speak camera-point text reading are different Magnifier Detection Mode surfaces
Conflating 人物检测 with 放大镜 — People Detection spatial awareness vs magnifier zoom for reading fine print
Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention People Detection features
Machine translation is fine for internal drafts. Finished People Detection strings need idiomatic zh-Hans that states what people-nearby support you ship — while keeping accurate scope. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.
What good zh-Hans People Detection listing copy looks like
People Detection 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) — 相机检测附近的人 — People Detection benefit within the ~30-character cap
Keywords (example) — 人物检测,检测人,行人检测,检测模式 — plus 低视力 or 空间感知 when low-vision spatial awareness is an accurate claim
Screenshot overlay (example) — 人物检测，感知附近的人 — People Detection frame with clear benefit line
Description paragraph (example) — plain zh-Hans list of People Detection features you ship — person recognition, spoken distance cues, position feedback, Detection Mode toggle — matching what you actually implemented
Honest scope — do not claim "identify anyone instantly indoors" in Chinese if your app only supports certain environments or requires LiDAR hardware
zh-Hans and en-US strings can differ in length and structure when the underlying People Detection story is the same — avoid mirroring English comma-heavy promo lines character-for-character.
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 People Detection, Detection Mode, detect people nearby, person distance cues, or people-nearby spatial awareness ("People Detection", "Detection Mode", "Detect people", "Person nearby", room or sidewalk demos)
Brief note on which People Detection features your app ships today — person recognition, spoken distance cues, position feedback, Detection Mode UI — so zh-Hans copy stays accurate
Target locales (e.g. zh-Hans for China storefront)
Your deadline if aligning with a People Detection 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 People Detection and Magnifier Detection Mode 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 person-recognition accuracy, speaking voice quality, or Detection Mode reliability improves — listing rewrite describes what you already ship
No person-recognition computer vision, LiDAR, depth sensing, or spoken spatial-awareness engineering
No claim that your app replaces Apple Magnifier People Detection 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 accessibility 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 shipping People Detection auto-translate my China listing?
No. Person recognition and Detection Mode UI in the app does 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 People Detection 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 People Detection, Detection Mode, detect people nearby, person distance cues, or 人物检测 / 检测人 / 行人检测 — rewritten from your English originals.
How is this different from Magnifier zoom, Door Detection, Point and Speak, Live Text, or Visual Look Up guides?
People Detection listing copy covers recognizing people nearby for low-vision spatial awareness — Magnifier Detection Mode marketing on the product page. Magnifier zoom covers close-up magnification for reading. Door Detection covers doors and exits for navigation. Point and Speak covers camera-point physical text reading. Live Text covers OCR text extraction. Visual Look Up covers object and image lookup. Those are separate scopes with different screenshot vocabulary.
Is People Detection the same as Door Detection or Point and Speak?
No. People Detection detects people nearby for spatial awareness. Door Detection finds doors and exits for navigation. Point and Speak reads printed text the camera detects. Each Magnifier Detection Mode surface has a different buyer story. AppLocale rewrites People Detection claims when that is what your English listing markets.
Does AppLocale implement People Detection or computer-vision code?
No. We deliver Connect listing metadata copy only. Person recognition models, Detection Mode APIs, and spoken people-announcement pipelines are outside AppLocale scope. We rewrite how you describe existing People Detection features on the store page — we do not implement them in the app.
What do I send after payment?
Your live App Store listing URL, current English listing copy, screenshot overlay lines mentioning People Detection or Detection Mode (with frame order noted), which people-nearby features you ship, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.
Is this machine translation?
No. We rewrite People Detection and Magnifier Detection Mode 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 Magnifier close-up zoom hub listing copy, not Door Detection listing copy, not Point and Speak listing copy, not Live Text or OCR listing copy, not Visual Look Up listing copy, not Speak Screen or VoiceOver listing copy, not person-recognition engineering, not screenshot design, not binary localization, not Connect configuration, not ranking guarantees, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — People Detection & Magnifier Detection Mode listing copy in Simplified Chinese
After checkout, reply from your Stripe receipt email with your App Store URL, English listing and People Detection overlay copy, target locales, and deadline. Delivery within 24 hours. No ranking guarantees. Sold by Fortune Insight, LLC.