Apple Eye Tracking & Eye-Gaze Control App Store Listing in Simplified Chinese — Dwell Select, Calibration & 眼动追踪 zh-Hans Copy

Who this is for

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

• Already ship an app where users operate the UI with eye gaze — Eye Tracking setup walkthroughs, calibration dot demos, dwell-to-select highlight rings, gaze navigation badges, or works-with-Eye-Tracking callouts on screenshots
• Market Apple Eye Tracking, eye-gaze control, dwell control, gaze calibration, or 眼动追踪 / 眼球追踪 / 注视控制 / 用眼睛操作 on the en-US product page and in screenshot galleries
• Finished eye-gaze or Eye Tracking-compatible UX in the binary — not looking for front-camera gaze firmware, Eye Tracking API integration, or dwell overlay engineering help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on eye-tracking gallery frames
• Need paste-ready Connect text — not an engineer for gaze hardware, not a designer to re-export every screenshot from scratch

If users press an external adaptive switch rather than dwell with their eyes, that is a different listing story — see Switch Control listing (zh-Hans). If users speak numbered overlay commands to tap UI elements, see Voice Control listing. If users rely on VoiceOver screen reader navigation, see VoiceOver listing. If your lead feature is a simplified caregiver Home Screen, see Assistive Access listing. If the entire China page is still English on every field, start with China App Store still shows English or the AppLocale product page.

What Apple Eye Tracking is — for end users on your product page

Apple ships Eye Tracking as a system accessibility feature in iOS and iPadOS. When your listing mentions eye-gaze control, buyers expect this workflow — not Face ID login, not VR lab hardware, not camera photo filters:

• Turn on Eye Tracking — Settings → Accessibility → Eye Tracking toggle. Gallery frames may show the Eye Tracking onboarding sheet or "Turn on Eye Tracking" badge.
• Calibrate gaze — follow on-screen calibration dots so the device maps where the user is looking. Screenshot overlays often show calibration dot sequences, "Follow the dots" walkthroughs, or recalibrate prompts.
• Dwell to select — hold gaze on a UI element for a configurable dwell time to tap, scroll, or activate it without touch. Marketing frames may show dwell highlight rings, dwell timing sliders, or "Dwell to select" benefit lines.
• Control iPhone with your eyes — navigate Home Screen, apps, Control Center, and system UI using front-camera eye gaze. Gallery frames may show gaze cursor movement, eye-gaze navigation demos, or "Operate with your eyes" callouts.

Your zh-Hans listing should describe the eye-gaze workflows your app actually supports — calibration, dwell select, gaze-friendly layouts — in commerce-idiomatic Chinese. AppLocale rewrites from your English source; we do not invent Eye Tracking capabilities your screenshots do not show.

Eye Tracking engineering vs zh-Hans listing copy — two different jobs

Teams assume eye-gaze capability covers storefront language. Xcode, entitlements, and Connect actually separate gaze navigation in the app from product-page copy:

• Gaze hit targets & dwell timing — in-app code or system integration that sizes tap targets and dwell thresholds for eye-gaze users. Controls whether buyers can operate your app without touch. Does not generate Chinese listing text.
• Calibration & gaze cursor UI — engineering work for calibration flows, gaze pointer rendering, and dwell highlight overlays. Separate from the zh-Hans description paragraph that explains eye-tracking value to buyers.
• Works with Eye Tracking vs custom gaze UI — your binary may integrate with iOS Eye Tracking, ship gaze-friendly layouts, or both. Listing copy should match what screenshots actually show — not promise calibration walkthroughs when your gallery only shows a generic accessibility badge.
• 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 Eye Tracking support in the app.

Working eye-gaze 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 Eye Tracking, dwell control, and gaze calibration on the product page in zh-Hans, not how you implement gaze APIs or front-camera eye tracking.

The Eye Tracking family on one product page — four related surfaces

Apple groups several gaze-accessibility features under Eye Tracking. Western indie listings often mention one or more on the same US product page. AppLocale covers all four on this single guide — paste-ready zh-Hans copy for whichever your screenshots and description already claim:

• Eye Tracking setup (眼动追踪) — Settings → Accessibility → Eye Tracking toggle and permission prompts. Gallery frames may show the Eye Tracking onboarding sheet, front-camera permission dialog, or "Turn on Eye Tracking" badge.
• Gaze calibration (校准 / 注视校准) — follow calibration dots so the device maps gaze position. Screenshot overlays often show dot sequences, recalibrate buttons, or "Calibrate your gaze" walkthroughs.
• Dwell to select (注视控制 / 停留选择) — hold gaze on an element for a set time to activate it. Marketing frames may show dwell highlight rings, dwell duration sliders, or "Dwell to tap" demos.
• Eye-gaze navigation (用眼睛操作) — move a gaze cursor across Home Screen, apps, and system UI without touch. Gallery frames may show gaze pointer movement, scroll-with-gaze demos, or "Control with your eyes" benefit lines.

Your gallery may lead with calibration dots on one frame and dwell highlight demos on the next. zh-Hans caption lines should name the correct surface per frame — a dwell ring demo is not a Switch Control scanning highlight, not a Voice Control numbered overlay, and not a Face ID scan animation unless that is what the screenshot shows.

Eye Tracking listing copy is not Face ID, Switch Control, Voice Control, or VoiceOver

Accessibility and biometrics apps blur several surfaces indie teams conflate. AppLocale covers listing metadata only — eye-gaze and Eye Tracking marketing on the product page:

• Eye Tracking & eye-gaze control (this page) — Apple Eye Tracking, eye-gaze control, dwell to select, gaze calibration, control iPhone with your eyes, 眼动追踪, 眼球追踪, 注视控制, and 用眼睛操作 on gallery frames and in description paragraphs.
• Face ID & face authentication (different) — Face ID unlock, facial recognition login, TrueDepth face matching for device unlock. Not Eye Tracking accessibility — Face ID authenticates identity; Eye Tracking lets users operate the UI with gaze. Do not use Face ID vocabulary on eye-gaze accessibility frames.
• ARKit face mesh & camera eye detection (different) — AR face tracking for filters, photo eye-detection effects, or research SDKs. Not Apple Accessibility Eye Tracking — different buyer intent from gaze-based device control.
• VR research eye trackers (different) — Tobii, Varjo, or lab-grade headset eye trackers for UX research or gaming. Not iOS Settings → Accessibility → Eye Tracking — different hardware and screenshot vocabulary.
• Switch Control & external switches (different) — adaptive switches, auto-scanning, switch recipes. See Switch Control listing guide — Switch Control uses physical switch presses; Eye Tracking uses front-camera gaze and dwell.
• Voice Control & spoken commands (different) — hands-free UI operation with spoken tap and swipe commands. See Voice Control listing guide — Voice Control uses voice; Eye Tracking uses gaze and dwell.
• VoiceOver & screen reader (different) — VoiceOver support, Works with VoiceOver, screen reader navigation badges. See VoiceOver listing guide — VoiceOver reads and explores the UI for blind and low-vision users; Eye Tracking lets users with limited mobility operate the touch interface via gaze.
• Assistive Access & simplified Home Screen (different) — simplified iOS Home Screen for cognitive accessibility. See Assistive Access listing guide — not eye-gaze or dwell control marketing.
• AssistiveTouch & floating assistive menu (different) — on-screen floating home button, virtual home button, custom AssistiveTouch actions. See AssistiveTouch listing guide — AssistiveTouch shows a touchable overlay menu; Eye Tracking uses gaze cursor and dwell without direct touch.
• Guided Access & single-app lock (different) — lock the device to one app with a session passcode. See Guided Access listing guide — kiosk lock is not eye-gaze input marketing.
• Accessibility hub multi-feature dump (different) — Settings → Accessibility home grids that list many assistive features as one bullet list. See Accessibility hub listing guide — hub marketing covers several surfaces together; this page covers Eye Tracking and eye-gaze claims in depth.

Your screenshots may show multiple surfaces in one gallery. Listing copy should name the correct one per frame — a dwell highlight ring is not a Face ID scan animation, not an external switch pairing sheet, not a Voice Control numbered overlay, and not a VoiceOver rotor unless that is what the frame shows.

Apple system Eye Tracking vs your app's eye-gaze marketing — listing honesty

Apple ships Eye Tracking in iOS and iPadOS Settings → Accessibility → Eye Tracking that lets users calibrate gaze, dwell to select UI elements, and operate the device with their eyes using the front camera. Third-party apps may offer Eye Tracking-compatible layouts, gaze-friendly UI, dwell-friendly hit targets, or eye-gaze accessibility companions your binary actually ships. AppLocale rewrites listing copy from what your US page already claims:

• If your app complements iOS Eye Tracking — zh-Hans copy can describe works-with-Eye-Tracking badges, gaze-friendly layouts, or dwell-friendly UI your binary actually ships without claiming to replace Settings → Accessibility → Eye Tracking unless your English listing already states that accurately.
• If your app is a dedicated eye-gaze accessibility product — description and screenshot overlays should name the workflows you ship (眼动追踪, 注视控制, 用眼睛操作) in commerce-idiomatic Chinese, not generic "accessibility controls everything" overclaims.
• If your US page shows calibration or dwell demos — zh-Hans copy should distinguish system Eye Tracking calibration from in-app custom gaze modes when your screenshots show each — matching what buyers will see after install.
• If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not invent broader eye-gaze scope than your screenshots and description support.

Clear zh-Hans copy helps buyers understand whether your app supports gaze calibration, dwell to select, gaze-friendly layouts, or Eye Tracking integration — before install. It does not replace gaze API implementation, dwell overlay engineering, or Apple's review decisions — and it does not certify eye-gaze accuracy in the app.

What China buyers see when zh-Hans Eye Tracking copy is missing

Eye-gaze accessibility apps often lead marketing screenshots with calibration dot walkthroughs, dwell highlight rings, gaze cursor demos, or Eye Tracking setup sheets — surfaces where English marketing text appears beside eye-tracking UI:

• Screenshot overlay badges — "Eye Tracking", "Eye-gaze control", "Dwell to select", "Gaze calibration", "Control with your eyes", "Works with Eye Tracking" on gallery frames
• Description paragraphs — English value props about motor accessibility, hands-free gaze control, or eye-gaze productivity that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 眼动追踪, 眼球追踪, 注视控制, or 用眼睛操作 when buyers filter for eye-gaze accessibility apps
• Promotional text — 170-character field still pitching Eye Tracking in English above the description
• Mixed page — Chinese description pasted once but eye-tracking screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 for Eye Tracking (眼动追踪 vs 眼球追踪 vs 视线追踪) and wrong phrasing that conflates Eye Tracking with Face ID or Switch Control on store pages

Better zh-Hans listing copy helps motor-accessibility and eye-gaze buyers understand your Eye Tracking story before install. It does not replace gaze calibration implementation, dwell overlay engineering, or Apple's review decisions — and it does not guarantee eye-gaze accuracy in the app.

What AppLocale delivers for Eye Tracking and eye-gaze apps on zh-Hans

This SKU is a listing rewrite scoped to Eye Tracking and eye-gaze 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 eye-gaze accessibility to China searchers
• Subtitle — concise benefit line that can reference Eye Tracking or gaze control without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for 眼动追踪, 眼球追踪, 注视控制, 用眼睛操作, and eye-gaze accessibility apps in your category
• Description — long listing body with clear zh-Hans paragraphs on eye-gaze workflows you already ship — without English-only "Eye Tracking" 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 Eye Tracking setup, calibration dots, dwell-to-select demos, gaze cursor movement, or eye-gaze navigation walkthroughs
• English alignment — matching en-US field notes when both storefronts must stay consistent on eye-gaze promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Eye Tracking, eye-gaze control, dwell control, or gaze calibration — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent eye-gaze features your app does not ship.

Eye Tracking-specific listing vocabulary — what translates differently

Eye-gaze marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe Eye Tracking workflows — not a literal paste of US marketing:

Eye Tracking vs Face ID vs Switch Control

US pages use "Eye Tracking", "Eye-gaze control", or "Dwell to select." China storefront copy often uses 眼动追踪 for Apple's Accessibility feature name, 注视控制 for dwell-based selection, 眼球追踪 for general eye-gaze benefit lines, or 用眼睛操作 for control-with-your-eyes marketing — depending on whether you mean system Eye Tracking, in-app gaze-friendly layouts, or dwell timing demos. AppLocale aligns phrasing with your actual eye-gaze scope and avoids conflating Eye Tracking with 面容 ID (Face ID authentication) or 切换控制 (Switch Control external switches) when your screenshots show calibration dots and dwell highlights, not face unlock animations or adaptive switch pairing.

Calibration vs recalibrate vs first-time setup

Screenshot galleries may label first-time calibration (校准 / 注视校准) separately from recalibrate prompts (重新校准). Buyers searching for eye-gaze accessibility apps distinguish onboarding calibration from in-session drift correction — match what your English listing and screenshots actually show.

Dwell to select vs tap vs Voice Control overlay

Dwell highlight rings (停留选择 / 注视选择) look different from Voice Control numbered overlays or VoiceOver focus rings. Do not use 旁白 (VoiceOver) or 声音控制 (Voice Control) vocabulary on frames that show gaze dwell highlights unless that is what the screenshot depicts.

Gaze cursor vs AssistiveTouch floating button

Eye-gaze cursor movement (视线光标 / 注视光标) operates the UI without touch. AssistiveTouch shows a floating on-screen menu users tap — different buyer intent and screenshot vocabulary from gaze pointer demos.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need eye-gaze search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 眼动追踪, 注视控制, and 用眼睛操作 each signal different intent from Switch Control, Voice Control, or Face ID keywords.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Eye Tracking" 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

Eye Tracking feature launches and gaze-friendly UI updates 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 eye-gaze pitch lives in promo text rather than the long description.

What good zh-Hans Eye Tracking listing copy looks like

Eye-gaze 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) — 眼动追踪，注视即可选择 — eye-gaze benefit within the ~30-character cap
• Keywords (example) — 眼动追踪,注视控制,用眼睛操作,无障碍 — only when accurate to your feature set
• Screenshot overlay (example) — 校准注视，停留即可点选 — calibration and dwell frame with clear benefit line
• Description paragraph (example) — plain zh-Hans list of eye-gaze workflows you ship — gaze calibration, dwell to select, Eye Tracking integration, gaze-friendly layouts — matching what you actually implemented
• Honest scope — do not claim full Eye Tracking replacement in Chinese if your app only ships a limited gaze-friendly layout

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

Why machine-translated Eye Tracking copy fails

• Literal "Eye Tracking" → awkward 眼睛跟踪 instead of commerce-idiomatic 眼动追踪 or 注视控制
• Generic "Eye-gaze control" → 眼睛凝视控制 (stiff) instead of buyer-friendly 用眼睛操作 or 注视控制
• English badge headlines preserved on zh-Hans screenshots — "Dwell to select" with no Chinese benefit line beside it
• Overlay text overflow — long English eye-gaze captions pasted into short screenshot callout zones truncate on device
• Conflating 眼动追踪 with 面容 ID — Eye Tracking operates the UI with gaze; Face ID unlocks the device with facial recognition — different buyer intent and keywords
• Conflating 注视控制 with 切换控制 — Eye Tracking uses gaze dwell to select; Switch Control uses external switches and scanning — opposite input method from adaptive switch apps
• Conflating 眼动追踪 with ARKit face mesh — accessibility Eye Tracking calibrates gaze for device control; AR face tracking drives filters and effects — different screenshot vocabulary
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention Eye Tracking or eye-gaze control

Machine translation is fine for internal drafts. Finished Eye Tracking strings need idiomatic zh-Hans that states what eye-gaze 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 Eye Tracking, eye-gaze control, dwell to select, gaze calibration, or control with your eyes ("Eye Tracking", "Eye-gaze control", "Dwell to select", "Gaze calibration", "Control with your eyes", "Works with Eye Tracking")
• Brief note on which eye-gaze workflows your app ships today — gaze calibration, dwell to select, Eye Tracking integration, gaze-friendly layouts — so zh-Hans copy stays accurate
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with an Eye Tracking 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 Eye Tracking and eye-gaze 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 gaze calibration accuracy, dwell timing, or eye-gaze hit target reliability improves — listing rewrite describes what you already ship
• No Eye Tracking API, gaze calibration UI, dwell overlay, or front-camera eye-gaze engineering
• No claim that your app replaces Apple Accessibility Eye Tracking 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 eye-gaze 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 Eye Tracking or gaze calibration APIs?

No. We deliver Connect listing metadata copy only — name, subtitle, keywords, description, promotional text when included, and screenshot caption lines. Eye Tracking API integration, gaze calibration UI, and dwell overlay engineering are outside scope.

How is Eye Tracking listing copy different from Switch Control or Voice Control?

Eye Tracking listing copy covers gaze-based device control — calibration, dwell to select, eye-gaze navigation, and 眼动追踪 workflows. Switch Control covers external switch input and scanning. Voice Control covers hands-free UI operation with spoken commands. Those are different buyer stories with different screenshot vocabulary.

How is this different from Face ID, VoiceOver, AssistiveTouch, or the Accessibility hub guide?

Face ID covers facial authentication for device unlock. VoiceOver covers screen reader navigation. AssistiveTouch covers the floating on-screen assistive menu. The Accessibility hub guide covers multi-feature Settings → Accessibility marketing. Eye Tracking covers gaze-based device control — a different buyer story on each surface.

Should my zh-Hans listing claim to replace iOS Eye Tracking in Settings?

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 Accessibility Eye Tracking features.

What do I send after AppLocale payment?

Your live App Store listing URL, current English listing copy, screenshot overlay lines that mention Eye Tracking, eye-gaze control, dwell to select, or gaze calibration (with frame order noted), which eye-gaze workflows your app ships, 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 eye-gaze behavior?

No. Gaze calibration, dwell timing, eye-gaze hit targets, and front-camera routing come from your binary and iOS — not Connect listing fields. AppLocale covers product-page marketing copy only.

Will zh-Hans Eye Tracking 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 eye-gaze accessibility 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 Eye Tracking or gaze calibration engineering, not Face ID or ARKit face mesh listing copy, not Switch Control or Voice Control listing copy, not VoiceOver or Assistive Access listing copy, not AssistiveTouch or Guided Access listing copy, not Accessibility hub multi-feature dump 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 Eye Tracking & eye-gaze 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