Spatial Persona App Store Listing in Simplified Chinese — visionOS & FaceTime for China
You market Spatial Persona on your App Store page — life-size FaceTime presence, shared spatial calls, immersive co-presence on Apple Vision Pro — and your en-US listing repeats "Spatial Persona", "Share with Spatial Persona", "Meet in Spatial Persona", and "Life-size Spatial Persona" across screenshots and description.
Open the same app on the China storefront and the product page still shows English name, subtitle, keywords, description, and screenshot captions that leave those Spatial Persona phrases untranslated.
AppLocale writes paste-ready zh-Hans listing copy for those Connect fields — aligned with how your spatial FaceTime feature actually works, not a generic visionOS template or SharePlay session pitch.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Spatial Persona is not general visionOS metadata, SharePlay, or SDK work
Teams conflate four different layers when localizing a Spatial Persona app for China. AppLocale covers layer 1 only.
1 — App Store listing metadata (zh-Hans row)
Name, subtitle, keywords, description, plus screenshot overlay captions and App Preview text on the Simplified Chinese localization in App Store Connect. This is what buyers see before install. AppLocale's $79 deliverable is paste-ready copy for these fields — including caption lines on frames that show life-size FaceTime personas, spatial call UI, or shared presence marketing art.
2 — In-app Spatial Persona UI (not included)
Text inside FaceTime sessions — participant labels, spatial presence controls, session status — comes from your app binary, String Catalog, or runtime data. Translating that requires Xcode localization or server-side content, not a listing rewrite. We do not edit Spatial Persona presentation layouts or in-call UI.
3 — Spatial Persona SDK / FaceTime engineering (not included)
Spatial Persona API adoption, GroupActivities coordination, visionOS entitlements, FaceTime integration, and spatial session lifecycle are Xcode and server work. AppLocale does not implement life-size persona rendering, custom spatial layouts, or FaceTime eligibility in your build.
4 — General visionOS product page (different guide)
Platform-specific visionOS name, subtitle, promotional text, and spatial screenshot captions on the Apple Vision Pro tab — without Spatial Persona marketing — are covered in our visionOS / Apple Vision Pro listing guide. This page targets listings that explicitly sell Spatial Persona as a buyer-facing feature on the product page.
What China buyers still see when Spatial Persona copy stays English
When Simplified Chinese metadata is missing or falls back to English, the China storefront product page mirrors your US Spatial Persona marketing gaps:
English app name or subtitle — Search results and the product header show Latin script while competitors read native
Untranslated keyword field — wasted 100-character cap; China Search indexes Simplified Chinese characters, not English feature names alone
English description — long body text that never explains life-size FaceTime presence or shared spatial calls in zh-Hans
"Spatial Persona" as the only caption — branded term without a zh-Hans benefit line on gallery frames targeting China buyers
"Share with Spatial Persona" still in English — overlay lines on screenshots showing shared spatial FaceTime with no Chinese context
"Meet in Spatial Persona" or "Life-size Spatial Persona" untranslated — marketing slogans on visionOS or FaceTime gallery art left as en-US boilerplate
App Preview metadata in English — Connect preview text fields can be zh-Hans even when video assets still carry English; redesigning burned-in video text is outside AppLocale scope
Better zh-Hans listing copy reduces product-page bounce for users who already search in Chinese — it does not auto-translate Spatial Persona UI after install or during FaceTime calls.
Common mistakes on Spatial Persona listings for China
Leaving "Spatial Persona" as the only caption — branded term without a zh-Hans benefit line ("与好友以真实比例 FaceTime 通话") looks unfinished
Literal "Life-size Spatial Persona" → 真人大小的空间角色 — awkward; align with Apple's spatial presence framing and your actual UX
Machine-translated "Share with Spatial Persona" as 分享空间角色 — sounds like file sharing; name shared spatial FaceTime, not English marketing labels alone
Conflating Spatial Persona with SharePlay — synchronized movie watching is SharePlay; life-size FaceTime presence is Spatial Persona — different buyer stories on the product page
Conflating Spatial Persona with general visionOS screenshots — spatial gallery metadata without Persona marketing is a different scope; see visionOS listing guide
Caption lines that describe features your build does not ship — metadata must match actual Spatial Persona eligibility and device requirements
Assuming visionOS engineering localizes the store page — SDK integration and App Store metadata are independent workstreams
English-only What's New after a Spatial Persona launch — version notes are a separate field; base $79 focuses on evergreen listing fields unless you bundle What's New in intake
What good zh-Hans Spatial Persona listing copy looks like
Align tone with your en-US listing and name the spatial FaceTime surfaces buyers actually see:
Name & subtitle (30 chars each) — lead with the outcome (与好友真实比例 FaceTime, 空间通话更沉浸) not SDK jargon alone
Keywords (100 chars) — Simplified Chinese queries for spatial FaceTime, life-size calls, visionOS co-presence where relevant — not English API names stuffed into the hidden field
Description — one clear paragraph on what Spatial Persona means for your app: life-size participant tiles, shared spatial context, compatible devices
Screenshot captions — one line per frame naming the on-screen state: "FaceTime 通话中以真实比例呈现" not "Spatial Persona" alone
Honest scope — if Spatial Persona requires visionOS, specific hardware, login, or premium tier, say so in plain zh-Hans
Spatial Persona screenshot captions Chinese buyers expect
visionOS and FaceTime apps often dedicate one or two gallery frames to the Spatial Persona story — life-size participant tiles, shared spatial call UI, or immersive co-presence marketing art. Overlay lines on those frames should name the feature in plain zh-Hans:
Shared spatial call frame — name the shared context: "与好友在空间中共度 FaceTime 通话" vs vague "Share with Spatial Persona"
Meet / join frame — state how users start: "发起空间 FaceTime，邀请好友以真实比例加入" — not English-only "Meet in Spatial Persona"
visionOS immersive frame — explain what the buyer sees in spatial mode: "在 Apple Vision Pro 上体验沉浸式共同通话" when art shows headset context
Match caption to capture — if the screenshot shows two participants, the overlay should describe 双人通话 not 多人同播 unless art shows more
AppLocale includes Spatial Persona-related overlay lines in the screenshot caption deliverable when your gallery uses them. We do not redesign or re-export PNG assets — you paste overlay text into Connect or your design tool.
Connect checklist before you order copy
Open App Store → Chinese (Simplified) — confirm the zh-Hans localization row exists; adding China under Pricing and Availability alone does not fill it
Audit five text fields — name, subtitle, keywords, description, promotional text (if used) saved in zh-Hans, not placeholder English
List screenshot frames that show Spatial Persona — note which gallery images show life-size FaceTime tiles, spatial call UI, or Persona marketing overlays so caption lines match frame order
Export current English captions — overlay text from Connect or your design spreadsheet, including any "Spatial Persona", "Share with Spatial Persona", or "Meet in Spatial Persona" boilerplate
Confirm in-app UI language separately — plan Xcode string localization if Spatial Persona session labels are still English after install
Skip engineering tasks here — Spatial Persona SDK adoption, visionOS entitlements, FaceTime integration, and spatial session QA stay with your dev team
Paste-ready Simplified Chinese listing metadata rewritten from your English App Store copy, with Spatial Persona-aware phrasing:
App name — up to 30 characters on the zh-Hans row
Subtitle — up to 30 characters; visible under the name in Search
Keywords — up to 100 characters in the hidden keyword field
Description — long listing body explaining Spatial Persona value for China buyers
Screenshot caption lines — overlay text for frames showcasing Spatial Persona, life-size FaceTime UI, or shared spatial presence (send frame count and current English lines)
Listing alignment — voice consistent with your en-US page; we note both sides when English also needs tightening
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite — not a machine translation dump. Character counts verified before delivery.
What AppLocale does not do
Does not implement Spatial Persona SDK, GroupActivities, or FaceTime integration
Does not configure visionOS entitlements, spatial session lifecycle, or FaceTime presentation layouts
Does not localize in-app strings, String Catalog entries, or Spatial Persona UI rendered at runtime
Does not design or re-export screenshots — only Connect caption text you paste or hand to a designer
Does not edit App Preview video files or burn new subtitles into video assets
Does not manage Apple Search Ads, Custom Product Pages, or In-App Event scheduling
Does not write App Review replies or ongoing ASO retainers
Does not guarantee App Store ranking, keyword position, or download growth in China or elsewhere
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — zh-Hans listing fields plus Spatial Persona screenshot captions; engineering stays on your side
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English name/subtitle/keywords/description, screenshot caption lines (note which frames show Spatial Persona or life-size FaceTime UI), and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans fields arrive at your Stripe receipt email
Paste in Connect — App Store → Chinese (Simplified) → save → submit with your next version if needed
Does localizing my listing translate Spatial Persona UI inside FaceTime or visionOS?
No. AppLocale rewrites App Store Connect metadata — name, subtitle, keywords, description, and screenshot caption lines on your zh-Hans product page. In-app Spatial Persona controls, FaceTime session UI, and visionOS runtime strings are binary or Xcode localization work outside AppLocale scope.
How is Spatial Persona listing copy different from general visionOS or SharePlay?
Spatial Persona is Apple's life-size FaceTime presence feature on visionOS and compatible FaceTime calls — not general spatial screenshot metadata on the visionOS tab, not SharePlay synchronized watching or listening through GroupActivities. Screenshot captions should name spatial FaceTime presence benefits rather than generic visionOS gallery lines or shared-playback session copy.
What do I send after AppLocale payment?
Your live App Store listing URL, current English (or partial zh-Hans) name, subtitle, keywords, description, screenshot overlay lines with frame order noted, and which frames show Spatial Persona, life-size FaceTime tiles, or shared spatial presence. Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Does AppLocale implement Spatial Persona SDK or FaceTime integration?
No. We rewrite Connect listing copy only. Spatial Persona API adoption, GroupActivities coordination, visionOS entitlements, FaceTime integration, and in-app spatial session UI are engineering tasks we do not perform.
Will zh-Hans copy mentioning Spatial Persona 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 spatial FaceTime features 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 Spatial Persona SDK or GroupActivities engineering, not FaceTime integration work, not visionOS entitlement configuration, not screenshot image design, not in-app string localization, not Apple Search Ads management, not App Review reply retainers, not ranking guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans listing copy for Spatial Persona & spatial FaceTime apps
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.