Per-App Settings App Store Listing in Simplified Chinese — 每款 App 的设置 & 针对 App 的设置 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 Per-App Settings — per-app accessibility overrides under Settings → Accessibility → Per-App Settings
• Market Per-App Settings, per-app accessibility overrides, app-specific Bold Text or Larger Text, or 每款 App 的设置 / 针对 App 的设置 / 单个 App 设置 on the en-US product page and in screenshot galleries
• Finished per-app accessibility override support in the binary — not looking for UIAccessibility per-app detection plumbing help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on Per-App Settings gallery frames
• Need paste-ready Connect text — not an engineer for per-app override code, not a designer to re-export every Settings walkthrough from scratch

If your lead feature is a single system-wide Display & Text Size toggle — Bold Text, Larger Text, Increase Contrast, On/Off Labels, or Reduce Transparency applied globally — each has its own shop guide. See Bold Text listing (zh-Hans), Larger Text listing (zh-Hans), or Increase Contrast listing (zh-Hans). If you market Display Accommodations color filters, see Display Accommodations 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.

Per-App Settings listing copy vs per-app override engineering — two different jobs

Teams assume Per-App Settings compatibility covers storefront language. iOS, UIAccessibility, and Connect actually separate in-app override behavior from product-page copy:

• Per-App Settings on the device — Settings → Accessibility → Per-App Settings list where buyers pick an app and assign custom Bold Text, Larger Text, Increase Contrast, Reduce Transparency, Smart Invert, and related accessibility settings for that app only. System configuration UI — outside AppLocale scope.
• Per-app override implementation — respecting per-app accessibility settings at runtime, Dynamic Type scaling when a buyer assigns Larger Text only to your app, layout adaptation when Increase Contrast is per-app, and testing UI under per-app Bold Text. Engineering inside the binary — outside AppLocale scope.
• Per-app accessibility marketing on the product page — description paragraphs, subtitle positioning, keywords, promotional text, and screenshot overlays that tell buyers your app respects Per-App Settings or works with app-specific accessibility overrides. 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 Per-App Settings support in the app.

A Per-App Settings–aware app and a localized China listing are both valuable — neither replaces the other. AppLocale covers how you describe per-app accessibility override support on the store page, not whether your code reads per-app settings at runtime.

Per-App Settings vs system-wide Display & Text Size toggles and Display Accommodations — disambiguation

Apple groups several accessibility controls under Settings → Accessibility. Indie teams conflate the per-app override pane with individual system-wide toggles. AppLocale covers Per-App Settings and per-app override marketing on listing metadata — not the single-toggle guides:

• Per-App Settings (this page) — the per-app override pane where buyers assign custom accessibility settings to individual apps. Gallery frames may show Settings → Accessibility → Per-App Settings lists, app picker rows, or "Respects Per-App Settings" badges. zh-Hans terms: 每款 App 的设置, 针对 App 的设置, 单个 App 设置. This is a configuration list — not one visual toggle.
• Bold Text (different) — system-wide heavier font weight under Display & Text Size → Bold Text. See Bold Text listing guide — 粗体文本 global weight is not the Per-App Settings pane.
• Larger Text (different) — system-wide text size slider under Display & Text Size → Larger Text. See Larger Text listing guide — 更大字体 slider marketing is not per-app override list copy.
• Increase Contrast (different) — system-wide stronger UI contrast under Display & Text Size → Increase Contrast. See Increase Contrast listing guide — 增强对比度 global toggle is not Per-App Settings.
• On/Off Labels (different) — I/O or 1/0 labels on switches under Display & Text Size → On/Off Labels. See On/Off Labels listing guide — 开关标签 switch labels are not the per-app override pane.
• Reduce Transparency (different) — system-wide blur and vibrancy reduction. See Reduce Transparency listing guide — 降低透明度 frosted-glass opacity is not Per-App Settings list marketing.
• Display Accommodations (different) — color filters, invert colors, smart invert, reduce white point, differentiate without color. See Display Accommodations listing guide — color and contrast presets applied system-wide or per-app through a different path, not the Per-App Settings override list UI unless your gallery shows that pane specifically.
• Dynamic Type (different) — scalable typography APIs and UIFontMetrics support. See Dynamic Type listing guide — not Per-App Settings pane copy.
• Accessibility hub (different) — multi-feature Settings → Accessibility home marketing when Per-App Settings is one bullet among many. See Accessibility hub listing guide — not Per-App Settings–first copy.

Your gallery may show the Per-App Settings list on one frame and a Bold Text comparison on the next — but listing copy should name each claim accurately per frame. A Per-App Settings walkthrough is not a system-wide Bold Text toggle demo, not an Increase Contrast slider alone, and not a Display Accommodations color-filter picker unless that is what the screenshot shows.

What Per-App Settings actually does — listing honesty

Apple ships Per-App Settings in iOS and iPadOS under Settings → Accessibility → Per-App Settings. Buyers pick an installed app and assign custom accessibility settings — Bold Text, Larger Text, Increase Contrast, Reduce Transparency, Smart Invert, and related toggles — for that app only, without changing system-wide defaults. Third-party apps may complement this by respecting per-app overrides at runtime. AppLocale rewrites listing copy from what your US page already claims:

• If your app respects per-app overrides — zh-Hans copy can describe Per-App Settings support, app-specific text size, or per-app contrast behavior your binary actually ships — without claiming to replace the system pane unless your English listing already states that accurately.
• If your app ships Dynamic Type under per-app Larger Text — description and screenshot overlays should name the per-app accessibility benefits you deliver (每款 App 的设置, 针对 App 的设置, 单个 App 设置) in commerce-idiomatic Chinese, not generic "accessibility does everything" overclaims.
• Separate Per-App Settings from system-wide toggles in copy — Bold Text under Per-App Settings applies only when a buyer configures your app; Bold Text under Display & Text Size applies globally. Listing vocabulary must follow your English lead feature and gallery frames.
• Separate Per-App Settings from Display Accommodations — Display Accommodations color filters are a different settings path; Per-App Settings is the app-specific override list. Do not conflate 颜色滤镜 with 每款 App 的设置 unless your English listing markets both accurately.
• If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not invent broader Per-App Settings scope than your screenshots and description support.

Clear zh-Hans copy helps buyers who configure per-app accessibility understand your override story before install. It does not replace UIAccessibility checks in the binary, per-app override engineering, or Apple's review decisions.

Where English Per-App Settings copy shows on the China product page

Accessibility apps often lead marketing screenshots with Per-App Settings lists, app-picker rows, or per-app Bold Text demos — surfaces where English marketing text appears beside override UI:

• Screenshot overlay badges — "Respects Per-App Settings", "Per-app accessibility overrides", "Works with app-specific text size", "Customize accessibility per app" on gallery frames
• Description paragraphs — English value props ("Works with Per-App Settings", "Respects per-app Bold Text and Larger Text", "Adapts when buyers assign custom accessibility to your app") that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 每款 App 的设置, 针对 App 的设置, or 单个 App 设置 when buyers filter for per-app accessibility apps
• Promotional text — 170-character field still pitching Per-App Settings in English above the description
• Mixed page — Chinese description pasted once but Per-App Settings screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 that conflates 每款 App 的设置 (Per-App Settings pane) with 粗体文本 (Bold Text) or 增强对比度 (Increase Contrast) system-wide toggles on store pages

Better zh-Hans listing copy helps per-app accessibility buyers understand your override story before install. It does not replace per-app override code, UIAccessibility engineering, or Apple's review decisions.

Common mistakes on Per-App Settings zh-Hans listings

• Leaving "Per-App Settings" untranslated — Apple and buyers expect 每款 App 的设置, 针对 App 的设置, or 单个 App 设置 in zh-Hans regions; English-only overlay lines on otherwise Chinese copy looks unfinished
• Machine-translated "Per-App Settings" as 每个应用设置 alone — misses the Settings pane sense; align with buyer-facing terms like 每款 App 的设置 or 针对 App 的设置 depending on your UX
• Conflating Per-App Settings with Bold Text or Larger Text — 粗体文本 and 更大字体 are individual toggles buyers can assign per app; Per-App Settings is the pane that hosts those per-app assignments — different listing vocabulary
• Conflating Per-App Settings with Increase Contrast — 增强对比度 system-wide contrast is not the per-app override list; separate vocabulary per claim
• Conflating Per-App Settings with Display Accommodations — 颜色滤镜 and 反色 are display-adjustment stories under a different path; Per-App Settings is the app-specific override list under Accessibility
• Conflating Per-App Settings with On/Off Labels — 开关标签 switch-label toggle is one setting buyers may assign per app; Per-App Settings marketing covers the override pane, not switch-label chrome alone
• Describing Per-App Settings as a single visual toggle — it is a configuration list and app picker, not one on/off switch; zh-Hans copy should reflect list-and-override framing
• Claiming UIAccessibility API behavior in listing copy — product-page copy should describe user-facing per-app accessibility benefits, not runtime override detection documentation
• Assuming Per-App Settings integration localizes the store page — engineering and App Store metadata are independent workstreams

What AppLocale delivers for Per-App Settings apps on zh-Hans

This SKU is a listing rewrite scoped to Per-App Settings and per-app accessibility 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 每款 App 的设置 to China searchers
• Subtitle — concise benefit line that can reference per-app accessibility overrides or Per-App Settings support without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for 每款 App 的设置, 针对 App 的设置, 单个 App 设置, and per-app accessibility claims in your category
• Description — long listing body with clear zh-Hans paragraphs on Per-App Settings and per-app override features you already ship — without English-only accessibility 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 Per-App Settings UI ("每款 App 的设置", "针对 App 的设置", "支持单 App 无障碍覆盖")
• English alignment — matching en-US field notes when both storefronts must stay consistent on Per-App Settings promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Per-App Settings or per-app accessibility overrides — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent per-app override features your app does not ship.

Per-App Settings–specific listing vocabulary — what translates differently

Per-app accessibility marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe Per-App Settings — not a literal paste of US marketing:

Per-App Settings vs generic "accessibility options"

US pages use "Respects Per-App Settings", "Per-app accessibility overrides", or "Works with app-specific text size." China storefront copy often uses 每款 App 的设置, 针对 App 的设置, or 单个 App 设置 — depending on whether you mean Apple's Per-App Settings pane specifically, per-app Bold Text or Larger Text behavior, or general accessibility customization. AppLocale aligns phrasing with your actual scope, not inventing Per-App Settings support your app does not ship.

Per-App Settings vs Bold Text, Larger Text, and Increase Contrast — do not conflate

Per-App Settings is the pane where buyers assign Bold Text, Larger Text, Increase Contrast, Reduce Transparency, and related settings to one app. Bold Text, Larger Text, and Increase Contrast each have dedicated system-wide listing guides when that single toggle is your lead marketing claim. zh-Hans listing copy should not imply 粗体文本 or 更大字体 system-wide sliders when your English source only markets the Per-App Settings override list.

Per-App Settings vs Display Accommodations

Display Accommodations covers color filters, invert colors, smart invert, reduce white point, and differentiate without color — often under Display & Text Size or Accessibility paths depending on iOS version. Per-App Settings is the app-specific override list under Settings → Accessibility → Per-App Settings. zh-Hans copy should not imply 颜色滤镜 when your gallery only shows the Per-App Settings app picker.

Per-App Settings vs Accessibility hub marketing

When Per-App Settings appears as one row on a Settings → Accessibility home screenshot alongside AssistiveTouch, Guided Access, and Display & Text Size, the Accessibility hub listing guide covers multi-feature hub copy. This page is for Per-App Settings–first marketing — the override pane, app list, and per-app configuration walkthroughs as your lead story.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need per-app accessibility search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 每款 App 的设置, 针对 App 的设置, and 单个 App 设置 each signal different intent from Bold Text or Increase Contrast keywords.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Respects Per-App Settings" headlines on gallery frames showing Settings → Accessibility → Per-App Settings — 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 — Per-App Settings listing phrases (en-US → zh-Hans)

Concrete examples AppLocale rewrites from your English source — not Bold Text, Larger Text, or Display Accommodations copy:

• Screenshot caption — Before: Respects Per-App Settings → After: 支持每款 App 的设置，单 App 无障碍覆盖
• Description line — Before: Adapts when buyers assign custom accessibility to your app → After: 可在「针对 App 的设置」中为本 App 单独配置无障碍选项
• Subtitle (30 chars) — Before: Per-app accessibility → After: 支持每款 App 的设置
• Screenshot caption — Before: Works with app-specific text size → After: 支持针对本 App 的字号设置
• Keyword field — Before: Per-App Settings,accessibility override,app-specific text size → After: 每款App的设置,针对App的设置,单个App设置,无障碍
• Promotional text — Before: Now respects system Per-App Settings overrides → After: 现已支持系统针对 App 的无障碍设置

Final phrasing depends on your English claims, Per-App Settings surfaces on gallery frames, and Connect character caps. See Promotional text in Simplified Chinese when your per-app accessibility pitch lives in promo text rather than the long description.

Why English-only Per-App Settings copy hurts China storefront conversion

Accessibility purchasers browsing the China App Store evaluate per-app override claims in the first scroll. Common failure modes when only en-US is filled:

• Trust gap — Chinese word-of-mouth recommends a "per-app accessibility app"; buyer taps through and sees English "Respects Per-App Settings" with no zh-Hans context
• Localized listing, English badges — description promises Chinese per-app support; screenshot overlays still "Per-app accessibility overrides" at the worst moment
• Search intent miss — buyers search 每款 App 的设置 or 针对 App 的设置; English-only keywords miss intent even when Per-App Settings works in the app
• Competitor contrast — rivals with native zh-Hans per-app accessibility copy look more serious about China accessibility buyers
• Sibling-setting confusion in translation — machine-translated copy that says 粗体文本 when you mean the Per-App Settings pane, or 增强对比度 when you mean per-app override list — buyers misread your actual feature scope

Clearer zh-Hans per-app accessibility marketing reduces confusion on the product page. It does not replace UIAccessibility checks in the binary, per-app override engineering, or in-app accessibility settings.

Why machine-translated Per-App Settings copy fails

• Literal "Per-App Settings" → awkward 每个应用程序设置 instead of commerce-idiomatic 每款 App 的设置 (matches iOS Settings → 辅助功能 → 针对 App 的设置 vocabulary)
• Generic "accessibility options" → 无障碍选项 instead of buyer-friendly 针对 App 的设置 or 单个 App 设置
• English badge headlines preserved on zh-Hans screenshots — "Respects Per-App Settings" with no Chinese benefit line beside it
• Overlay text overflow — long English per-app captions pasted into short screenshot callout zones truncate on device
• Bold Text or Larger Text vocabulary bleed — 粗体文本 or 更大字体 appearing in zh-Hans copy when English source only mentioned the Per-App Settings override pane
• Display Accommodations phrasing drift — 颜色滤镜 language when English only described Per-App Settings app lists
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention Per-App Settings

Machine translation is fine for internal drafts. Finished Per-App Settings strings need idiomatic zh-Hans that states what per-app override behavior you ship — while keeping accurate scope and clear separation from Bold Text, Larger Text, Increase Contrast, On/Off Labels, and Display Accommodations marketing. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans Per-App Settings listing copy looks like

Per-app accessibility 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) — 支持每款 App 的设置 — per-app benefit within the ~30-character cap
• Keywords (example) — 每款App的设置,针对App的设置,单个App设置 — only when accurate to your feature set
• Screenshot overlay (example) — 针对 App 的设置，单 App 无障碍覆盖 — Per-App Settings frame with clear benefit line
• Description paragraph (example) — plain zh-Hans list of behaviors when buyers assign Bold Text, Larger Text, or Increase Contrast only to your app — matching what you actually implemented
• Honest scope — do not claim "every accessibility toggle per-app everywhere" in Chinese if only part of the app respects per-app overrides

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

Connect checklist before you order Per-App Settings 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 Per-App Settings UI — note which gallery images show Settings → Accessibility → Per-App Settings lists, app picker rows, or per-app override walkthroughs so caption lines match frame order
4. Export current English captions — overlay text from Connect or your design spreadsheet, including any "Respects Per-App Settings", "Per-app accessibility overrides", or "Works with app-specific text size" boilerplate
5. Confirm feature scope honestly — note which per-app overrides your app respects so zh-Hans copy does not overclaim system-wide accessibility support
6. Confirm in-app UI language separately — plan Xcode string localization if accessibility labels and settings chrome are still English after install
7. Skip engineering tasks here — UIAccessibility per-app override detection, Dynamic Type under per-app settings, and per-app override 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 Per-App Settings, per-app accessibility overrides, or app-specific Bold Text, Larger Text, or contrast
• Brief note on which per-app overrides your app respects today — so zh-Hans copy stays accurate
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a Per-App Settings 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 Per-App Settings and per-app accessibility 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 per-app overrides render correctly on every screen — listing rewrite describes what you already ship
• No UIAccessibility per-app override detection, Dynamic Type under per-app settings, or in-app accessibility engineering
• No Bold Text, Larger Text, Increase Contrast, or On/Off Labels system-wide listing copy — each Display & Text Size toggle has its own guide when that is your marketing scope
• No Display Accommodations, Dynamic Type, Reduce Motion, Dark Mode, or Auto Brightness listing copy unless separately scoped
• No accessibility audits, WCAG consulting, or medical marketing
• No screenshot set production, Per-App Settings 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 Per-App Settings and why does listing copy matter?

Per-App Settings is under Settings → Accessibility → Per-App Settings. Buyers pick an app and assign custom Bold Text, Larger Text, Increase Contrast, Reduce Transparency, Smart Invert, and related accessibility settings for that app only. Marketing that feature on your en-US page does not auto-fill zh-Hans Connect fields.

Does shipping Per-App Settings support auto-translate my China listing?

No. Per-App Settings compatibility is in-app behavior — it 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 Per-App Settings 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 Per-App Settings, per-app accessibility overrides, or 每款 App 的设置 / 针对 App 的设置 — rewritten from your English originals.

How is this different from Bold Text, Larger Text, or Increase Contrast?

Per-App Settings listing copy markets the per-app override pane — not a single system-wide toggle. Bold Text covers heavier system-wide text weight. Larger Text covers the text size slider system-wide. Increase Contrast covers stronger UI contrast system-wide. Each is a separate claim — do not reuse boilerplate across them.

How is this different from Display Accommodations or On/Off Labels?

Display Accommodations covers color filters, invert colors, and reduce white point. On/Off Labels covers switch and toggle label chrome. Per-App Settings covers the app-specific override list under Accessibility — different buyer intent and screenshot vocabulary.

Does AppLocale implement Per-App Settings handling in my app?

No. We deliver listing metadata copy only. UIAccessibility per-app override checks, Dynamic Type scaling under per-app settings, and in-app UI work are outside AppLocale scope. We rewrite how you describe existing per-app accessibility features on the store page — we do not implement them in the app.

What character limits apply to zh-Hans Per-App Settings 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 Per-App Settings or per-app accessibility overrides, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.

Is this machine translation?

No. We rewrite Per-App Settings and per-app accessibility 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 UIAccessibility per-app override engineering, not Bold Text or Larger Text system-wide listing copy, not Increase Contrast or On/Off Labels listing copy, not Display Accommodations or Dynamic Type listing copy, not Reduce Motion or Dark Mode 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 — Per-App Settings & per-app accessibility 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 Per-App Settings overlay copy, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. AppLocale does not implement Per-App Settings in your app. Sold by Fortune Insight, LLC.