People Occlusion App Store Listing in Simplified Chinese — ARKit Real People in Front of Virtual Content, Person Occlusion Rendering & 人物遮挡 zh-Hans Copy
Your AR or spatial app markets Apple People Occlusion on the en-US product page — ARKit person occlusion rendering, real people correctly appearing in front of virtual objects in camera passthrough, People Occlusion Rendering, Person Occlusion, Ultra People Occlusion, or gallery frames with badges like "People Occlusion", "Real people in front of virtual content", "Person occlusion in AR", "People appear in front of virtual objects", "ARKit People Occlusion", or "Ultra People Occlusion".
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 Occlusion" and "Person Occlusion" in Latin script while ARKit on Chinese devices and developer docs label the same compositing behavior 人物遮挡 with 人体遮挡 and 人物遮挡渲染 navigation.
Shipping People Occlusion-friendly AR sessions 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 presents live person occlusion value, without conflating People Occlusion with Object Capture photogrammetry, Subject Lift photo subject cutout, Clean Up object removal, Cinematic Mode or Portrait Mode camera depth-of-field, Hand Tracking visionOS pinch gestures, or general ARKit Place in AR alone.
People Occlusion is live AR depth compositing — real people occlude virtual objects in passthrough — not Object Capture 物体捕捉 photogrammetry, not Subject Lift 主体提取 still cutouts, not Clean Up 清理照片 erase, not Cinematic Mode 电影效果 or Portrait Mode 人像模式 camera bokeh, not Hand Tracking 手部追踪 pinch input.
Operator guidance only — no ranking guarantee, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie AR, iOS, iPadOS, and visionOS developers — US, UK, EU, Canada, Australia — who:
Ship an AR, mixed-reality, retail AR, or spatial computing app whose en-US product page prominently markets Apple People Occlusion — real people in the camera view correctly appearing in front of virtual AR content
Show gallery frames with People Occlusion passthrough demos, person-in-front-of-virtual-object walkthroughs, mixed-reality occlusion hero art, camera passthrough compositing, or Ultra People Occlusion badges — not Object Capture photogrammetry rings, Subject Lift cutout stickers, Portrait Mode bokeh hero, or Hand Tracking pinch rings as the lead story
Reference buyer-facing People Occlusion vocabulary like People Occlusion, Person Occlusion, People Occlusion Rendering, ARKit People Occlusion, or Ultra People Occlusion (人物遮挡, 人体遮挡, 人物遮挡渲染 in zh-Hans developer UI) in screenshot overlays or description bullets
Finished the en-US listing and passed App Review — not looking for ARKit person-segmentation, RealityKit occlusion, or depth-compositing engineering here
Enabled the China storefront but the zh-Hans row is empty, machine-translated, or still English on People Occlusion gallery frames
Need paste-ready zh-Hans listing fields — not an engineer for ARKit occlusion pipelines, not a designer to re-export every passthrough screenshot from scratch
People Occlusion vs zh-Hans listing copy — two different jobs
Teams assume People Occlusion capability in ARKit and RealityKit covers storefront language. Person segmentation, depth compositing, and Connect actually separate live occlusion behavior from product-page copy:
People Occlusion rendering pipeline — ARKit segments people in the camera feed and composites virtual content behind them so real people appear in front of virtual objects. Controls whether buyers see believable mixed-reality occlusion. Does not generate Chinese listing text. AppLocale does not implement this.
Person segmentation & depth compositing — runtime AR session behavior that occludes virtual meshes when a person walks between the camera and a virtual object. Your listing may show passthrough walkthroughs; wiring occlusion in RealityKit is engineering, not listing copy.
Camera passthrough & mixed-reality scenes — gallery frames where a live person blocks a virtual product, furniture piece, or character. Listing copy describes the benefit; segmentation quality lives in the binary.
Ultra People Occlusion — enhanced person occlusion branding on supported gallery frames. Listing copy describes the tier; occlusion fidelity is engineering.
Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
App Store tab → Chinese (Simplified) — 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 Occlusion support in ARKit.
People Occlusion working in buyer AR sessions and a localized China listing are both required when you sell on the China storefront — neither replaces the other. AppLocale covers how you describe person occlusion rendering, real-people-in-front-of-virtual-object value, and 人物遮挡 on the product page in zh-Hans, not how you implement ARKit occlusion in code.
People Occlusion ≠ Object Capture ≠ Subject Lift ≠ Portrait Mode ≠ Hand Tracking — explicit contrast
Apple ships several spatial, camera, and photo surfaces indie teams conflate. AppLocale covers listing metadata only — People Occlusion marketing on the product page:
People Occlusion & person occlusion rendering (this page) — People Occlusion badges, passthrough demos where real people block virtual objects, mixed-reality occlusion walkthroughs, Ultra People Occlusion, 人物遮挡 / 人体遮挡 / 人物遮挡渲染 on gallery frames.
Object Capture & photogrammetry (different — LIVE) — multi-angle photos to 3D models on Mac — 物体捕捉. See Object Capture listing guide — 3D object scanning and USDZ export, not live AR people-in-front-of-virtual occlusion.
Subject Lift photo cutout (different — LIVE) — lift subject, remove background, share as sticker from still photos — 主体提取. See Subject Lift listing guide — static photo cutout, not live AR people occlusion rendering.
Clean Up object removal (different — LIVE) — tap-to-erase photobombers and clutter from still photos — 清理照片. See Clean Up listing guide — photo cleanup, not runtime person occlusion in AR.
Cinematic Mode depth-of-field video (different — LIVE) — shallow-depth video with focus shifts — 电影效果. See Cinematic Mode listing guide — camera portrait look on video, not AR people occlusion.
Portrait Mode depth-of-field stills (different — LIVE) — shallow-depth still portraits — 人像模式. See Portrait Mode listing guide — portrait stills, not AR person occlusion compositing.
Hand Tracking & visionOS hand input (different — LIVE) — pinch to select, tap in air, gesture control without controllers — 手部追踪. See Hand Tracking listing guide — hands and gestures, not full-body person occlusion rendering.
General ARKit Place in AR (different — LIVE) — runtime AR placement and View in your space preview — 增强现实. See ARKit listing guide — general AR preview when People Occlusion is not your lead story.
Motion Capture and body tracking may appear in the same spatial category but are a different lead story — skeletal pose capture for animation and mocap workflows, not person occlusion rendering where real people block virtual content in passthrough. Do not lead with mocap vocabulary on People Occlusion frames unless that frame explicitly shows body-tracking UI. Your screenshots may show multiple spatial surfaces in one gallery. Listing copy should name the correct one per frame — a passthrough person-occlusion demo is not an Object Capture photo ring, not a Subject Lift cutout sheet, and not a Hand Tracking pinch highlight unless that frame explicitly shows those UIs.
What China buyers see when zh-Hans People Occlusion copy is missing
AR commerce, retail try-on, and mixed-reality apps often lead marketing screenshots with passthrough demos where a person walks in front of a virtual object — surfaces where English UI chrome and your marketing blurbs appear together:
English title and subtitle — app name and tagline still Latin script while competitors show native Chinese 人物遮挡 and 人物遮挡渲染 positioning
Untranslated occlusion captions — overlay lines like "People Occlusion", "Real people in front of virtual content", "Person occlusion in AR", and "People Occlusion Rendering" remain English on zh-Hans gallery frames
Mixed-reality value in English — description opens with US occlusion marketing ("Virtual objects hide behind real people in AR") that China readers skim past or misread
Keyword field still en-US — buyers search 人物遮挡, 人体遮挡, or 人物遮挡渲染; an English-only keyword row misses China Search intent
Mixed page — Chinese description pasted once but screenshot captions and subtitle still English — reads unfinished next to localized competitors
Conflating People Occlusion with Subject Lift — machine translation that promises 主体提取 photo cutouts when your app only markets live AR person occlusion — mismatched expectations at install
Conflating People Occlusion with Portrait Mode — 人像模式 depth-of-field language on passthrough occlusion frames — different buyer promises
Better zh-Hans listing copy helps AR buyers understand People Occlusion value before install. It does not replace ARKit person-segmentation implementation, privacy-policy legal text, or Apple's review decisions.
English People Occlusion phrases China buyers still see
Common en-US marketing lines that leak onto the China product page when zh-Hans caption fields are empty or copy-pasted from the US gallery:
People Occlusion — feature name and headline badge on gallery frames showing passthrough occlusion workflows
Person Occlusion — alternate marketing phrasing for single-person occlusion demos
Real people in front of virtual content — buyer workflow hero lines and passthrough walkthrough captions
People appear in front of virtual objects — mixed-reality compositing callouts on hero art
ARKit People Occlusion — developer-facing ARKit integration callouts on gallery frames
Ultra People Occlusion — premium-tier or Ultra-branded occlusion callouts on hero frames
Virtual content hides behind people — hero marketing for believable mixed-reality depth
Chinese buyers searching for 人物遮挡, 人体遮挡, or 人物遮挡渲染 still land on English-only overlays — that reads as an incomplete localization pass, not a bilingual AR occlusion app.
People Occlusion-specific listing copy — what translates differently
Person occlusion listings use vocabulary general AR guides rarely cover. zh-Hans copy should reflect how Chinese App Store readers describe live people-in-front-of-virtual-object workflows — not a literal paste of US marketing:
人物遮挡 vs 人体遮挡 vs 人物遮挡渲染
US pages say "People Occlusion" or "Real people in front of virtual content." China storefront copy often uses 人物遮挡 for Apple's People Occlusion feature name, 人体遮挡 when the hero frame emphasizes full-body segmentation, and 人物遮挡渲染 when the caption describes the rendering pipeline buyers recognize from AR demos. AppLocale aligns phrasing with each screenshot — not one blanket term for every overlay.
人物遮挡 vs Object Capture
People Occlusion composites live camera people in front of virtual AR objects — 人物遮挡 / 人物遮挡渲染 vocabulary. Object Capture reconstructs 3D models from multi-angle photos on Mac — 物体捕捉 / 三维扫描 vocabulary on the Object Capture guide. Do not use photogrammetry phrasing on People Occlusion passthrough frames.
人物遮挡 vs Subject Lift or Clean Up
Subject Lift markets static photo subject cutout and sticker export — 主体提取 on the Subject Lift guide. Clean Up markets tap-to-erase object removal from still photos — 清理照片 on the Clean Up guide. People Occlusion markets live runtime occlusion in AR passthrough — not still-photo editing.
人物遮挡 vs Portrait Mode or Hand Tracking
Portrait Mode and Cinematic Mode need 人像模式 or 电影效果 phrasing aligned to camera depth-of-field frames — not 人物遮挡 from this page unless the frame shows AR passthrough occlusion. Hand Tracking pinch demos need 捏合选择 phrasing from the Hand Tracking guide — not full-body occlusion language unless the frame shows person segmentation compositing.
Why English People Occlusion copy hurts on the China storefront
AR commerce and mixed-reality apps compete on the China App Store. Retail and spatial buyers evaluate product-page clarity before they download:
Occlusion value buried in Latin script — English "People Occlusion" on zh-Hans title/subtitle frames signals the team did not finish China marketing
Mixed-reality badges left untranslated — Real people in front of virtual content callouts appear as raw English on screenshots when caption fields are empty
Description mismatch — zh-Hans body copy mentions 人物遮挡 while screenshot overlays still say "People Occlusion Rendering"
Search intent gap — subtitle and keywords may miss 人物遮挡, 人体遮挡, or 人物遮挡渲染 terms buyers actually type
Competitor contrast — native zh-Hans AR apps in the same category show Chinese overlays; English badges look like an import
Subject Lift confusion — 主体提取 cutout language on frames that show live passthrough occlusion — buyers expect 人物遮挡, not photo sticker copy
Better zh-Hans People Occlusion marketing copy improves product-page clarity for China AR traffic — it does not replace in-app UI localization, ARKit occlusion engineering, or Apple review decisions.
Common mistakes on zh-Hans People Occlusion listings
Only localizing title and description — screenshot overlays still say "People Occlusion" on every passthrough frame
Machine-translating People Occlusion literally — awkward strings instead of idiomatic 人物遮挡 phrasing Chinese buyers recognize from Apple developer docs
Conflating with Object Capture — 物体捕捉 / 三维扫描 copy on passthrough occlusion frames; Object Capture is photogrammetry, People Occlusion is live person compositing
Conflating with Subject Lift or Clean Up — 主体提取 or 清理照片 copy on live AR occlusion frames; still-photo editing is a different buyer workflow
Conflating with Portrait Mode or Cinematic Mode — 人像模式 or 电影效果 depth-of-field language on AR occlusion frames; camera bokeh is not AR people occlusion
Conflating with Hand Tracking — 手部追踪 pinch-and-gesture copy on full-body occlusion frames; hand input is not person segmentation rendering
Leading with general ARKit Place in AR — 增强现实 placement vocabulary on frames that show person occlusion compositing when People Occlusion is your hero
Ignoring Ultra People Occlusion caption lines — English "Ultra People Occlusion" on screenshots for features you ship but never market in Chinese
Assuming ARKit People Occlusion in the binary = localized storefront — system occlusion APIs do not auto-fill Connect overlay fields
Expecting AppLocale to implement person-segmentation pipelines — ARKit occlusion and RealityKit depth compositing are outside listing rewrite
What good zh-Hans People Occlusion listing copy looks like
People Occlusion-centric listings name the live person-in-front-of-virtual-object workflow in plain zh-Hans — not a word-for-word mirror of English brochure lines:
Subtitle — one clause on AR person occlusion or real people blocking virtual content; room for 人物遮挡-adjacent search terms within 30 characters
Keywords — mix category terms (AR 购物, 增强现实, 混合现实) with occlusion intent (人物遮挡, 人体遮挡, 人物遮挡渲染); avoid English-only "People Occlusion" stuffing
Description — lead with the passthrough occlusion workflow; mention Ultra People Occlusion only when your app actually supports that surface
Screenshot overlays — short lines naming what the frame shows: 人物遮挡, 人物遮挡渲染, 真人挡在虚拟物体前 — not "People Occlusion" pasted through machine translation
Voice match — same 你/您 and punctuation habits as your other zh-Hans fields
zh-Hans People Occlusion captions can differ idiomatically from en-US overlays when the on-screen feature is the same — avoid mirroring comma-heavy English marketing onto passthrough art. Do not reuse Object Capture photogrammetry phrasing on person occlusion frames.
No twin slug pages — only app-store-people-occlusion-chinese.html
AppLocale does not maintain separate twin pages for these slugs when People Occlusion dominates your lead gallery:
person-segmentation, occlusion, people-occlusions — alternate People Occlusion slugs fold here — not as duplicate SKUs
arkit-occlusion, person-occlusion — platform or alternate spelling search intents belong here — not as separate twin slug pages
roomplan, lidar-scan, spatial-capture — room or LiDAR scan intents belong on Object Capture scope when photogrammetry is the lead — not as People Occlusion twin pages
Twin slugs: AppLocale does not maintain separate pages for person-segmentation, occlusion, people-occlusions, arkit-occlusion, or person-occlusion URL slugs. Only app-store-people-occlusion-chinese.html covers People Occlusion listing copy.
Connect checklist before you order People Occlusion listing copy
Open App Store → Chinese (Simplified) — confirm the zh-Hans row exists; note which fields are still English
Audit People Occlusion screenshot overlays — export English caption text per frame; list lines mentioning People Occlusion, Person Occlusion, People Occlusion Rendering, Real people in front of virtual content, or Ultra People Occlusion
Verify subtitle and keywords — do they mention 人物遮挡 or person occlusion workflows in Chinese or still mirror en-US?
Check description bullets — People Occlusion feature paragraphs may be English-only even when title is zh-Hans
Separate Object Capture scope — if your gallery also shows photogrammetry capture frames, confirm whether those need the Object Capture guide in addition to People Occlusion copy
Separate Subject Lift or Clean Up scope — if your gallery also shows photo cutout or object-removal frames, confirm whether those need the Subject Lift guide or Clean Up guide in addition to People Occlusion copy
Plan re-export if text is burned in — Connect caption fields help only when overlays are editable text layers, not English baked into PNGs
Verify China in availability — Pricing and Availability includes China if the storefront should show zh-Hans copy
How this differs from Object Capture, Subject Lift, and Hand Tracking guides
Our screenshot captions guide covers overlay copy boundaries for any app gallery. Our Object Capture guide covers Mac photogrammetry — 物体捕捉 — not live AR people occlusion. Our Subject Lift guide covers photo subject cutout — 主体提取 — not runtime person occlusion. Our Hand Tracking guide covers visionOS pinch and gesture control — 手部追踪 — not full-body person occlusion rendering. This page covers People Occlusion–centric marketing on listing metadata — name, subtitle, keywords, description, and overlay lines that sell ARKit person occlusion, real people in front of virtual content, and 人物遮挡:
Feature marketing copy — not ARKit person-segmentation or RealityKit occlusion engineering
人物遮挡 and 人物遮挡渲染 phrasing — not Object Capture photogrammetry or Subject Lift cutouts
Live passthrough person occlusion — not Portrait Mode bokeh, Cinematic Mode video depth, or Hand Tracking pinch input
Screenshot overlay lines when bundled — not in-app UI string localization
For one app on the zh-Hans row, paste-ready Simplified Chinese listing copy for People Occlusion–marketing fields you specify:
Title (name) — zh-Hans app name within Connect character limits
Subtitle — People Occlusion or AR person occlusion positioning within the ~30-character cap
Keywords — comma-separated zh-Hans search terms with rationale notes
Description — buyer-readable body copy aligned with your English People Occlusion listing meaning
Promotional text — when you include the 170-character promo field in scope
Screenshot overlay / caption lines — zh-Hans replacements for "People Occlusion", "Person Occlusion", "People Occlusion Rendering", "Real people in front of virtual content", "People appear in front of virtual objects", "ARKit People Occlusion", "Ultra People Occlusion", and similar passthrough occlusion frame text
English alignment — matching en-US field notes when both storefronts must stay consistent on People Occlusion support promises
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite from your current English People Occlusion listing — not a machine translation dump. Default $79 scope is Connect listing metadata; bundle extra caption lines via the AppLocale product page if needed.
What AppLocale does not do
Does not implement ARKit People Occlusion APIs, person-segmentation pipelines, or RealityKit depth compositing
Does not configure AR session occlusion quality or segmentation tuning in your binary
Does not write Object Capture listing copy when that is the lead story — see the Object Capture guide
Does not write Subject Lift listing copy when that is the lead story — see the Subject Lift guide
Does not write Clean Up listing copy when that is the lead story — see the Clean Up guide
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, English People Occlusion copy (all fields and caption lines), screenshot frame count, and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans listing fields arrive at your Stripe receipt email
Paste and submit — fill the zh-Hans row in Connect, enter caption lines per screenshot slot, save, and submit the version for review
Does People Occlusion auto-translate my China listing?
No. People Occlusion — ARKit person occlusion rendering where real people in the camera view correctly appear in front of virtual AR content — does not fill App Store Connect localization rows. If zh-Hans fields are empty, the China product page falls back to en-US copy.
Why do my People Occlusion screenshot captions still say People Occlusion in English?
Screenshot overlay lines are per localization. English People Occlusion badges on the en-US gallery do not propagate to zh-Hans until you paste Chinese caption text into the Chinese screenshot set.
What do I send after AppLocale payment?
Your live App Store listing URL, current English listing fields, People Occlusion–related screenshot overlay lines, target locale (zh-Hans), and any frame counts. Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
How is People Occlusion different from the Object Capture listing page?
Object Capture marketing covers Mac photogrammetry — multi-angle photos reconstructed into 3D models and USDZ — 物体捕捉 / 三维扫描. People Occlusion marketing covers live AR depth compositing where real people block virtual objects in passthrough — 人物遮挡 / 人物遮挡渲染. Different workflow, different buyer story, different zh-Hans vocabulary.
How is this different from Subject Lift or Clean Up pages?
Subject Lift marketing covers static photo subject cutout and sticker export — 主体提取. Clean Up marketing covers tap-to-erase object removal from still photos — 清理照片. People Occlusion marketing covers runtime person occlusion in live AR passthrough — not still-photo editing.
How is this different from Cinematic Mode, Portrait Mode, or Hand Tracking pages?
Cinematic Mode and Portrait Mode cover camera shallow depth-of-field on video or stills — 电影效果 / 人像模式. Hand Tracking covers visionOS pinch and gesture control without controllers — 手部追踪. People Occlusion covers AR person segmentation compositing where real people appear in front of virtual content — not camera bokeh or hand input marketing.
Will localized People Occlusion copy improve Search ranking in China?
We do not guarantee keyword position or download growth. Complete zh-Hans metadata helps AR buyers who already found your page understand person occlusion value in their language.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not ARKit People Occlusion API or person-segmentation engineering, not Object Capture, Subject Lift, Clean Up, Cinematic Mode, Portrait Mode, or Hand Tracking listing copy when those lead the page, not ranking guarantees, not QuantRadar, and not investment or legal advice. AppLocale does not maintain twin slug pages for person-segmentation, occlusion, people-occlusions, arkit-occlusion, or person-occlusion. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans People Occlusion listing copy aligned with your ARKit person occlusion and mixed-reality product page
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English People Occlusion listing copy. No ranking guarantees. Sold by Fortune Insight, LLC.