Bold Text App Store Listing in Simplified Chinese — 粗体文本 & 加粗文本 zh-Hans Copy

Bold Text listing copy vs typography engineering — two different jobs

US/EU indie teams conflate system accessibility features with storefront language. iOS Settings and App Store Connect actually separate them:

• Bold Text on the device — iOS applies heavier system typefaces across UI text when Bold Text is enabled. Toggle under Settings → Accessibility → Display & Text Size → Bold Text. System accessibility behavior — outside AppLocale scope.
• UIFont weight APIs and custom font engineering — code that detects Bold Text traits, ships custom typefaces, or adapts in-app typography when system text weight changes. Engineering inside the binary — not listing rewrite.
• Bold Text marketing on the product page — description paragraphs, subtitle positioning, keywords, promotional text, and screenshot overlays that tell buyers your app works with Bold Text, respects heavier system typefaces, or reads clearly when Bold Text is on. 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 how strongly your US listing markets Bold Text.

An app that references Bold Text in onboarding and a localized China listing are both valuable — neither replaces the other. AppLocale covers how you describe heavier system typefaces and Bold Text compatibility on the store page, not whether Bold Text toggles inside iOS Settings.

Bold Text listing copy vs Increase Contrast, Dynamic Type, Reduce Transparency, Display Accommodations, Zoom, and Screen Distance guides

Several shop guides cover adjacent Apple display and text accessibility features under Settings → Accessibility → Display & Text Size. This page covers heavier system typefaces and Bold Text marketing on listing metadata — not engineering, not unrelated category copy:

• Bold Text and heavier system typefaces on the product page — description, subtitle, keywords, promotional text, and screenshot overlays like "Bold Text", "Heavier system typefaces", "Bolder UI text", "Works with Bold Text", "Clearer labels when Bold Text is on", and Settings → Accessibility → Display & Text Size → Bold Text toggle demos. This page.
• Increase Contrast UI boosts — stronger borders, fills, and separators on buttons, icons, and system UI chrome without changing font weight. Covered on our Increase Contrast listing guide — not heavier typefaces. Increase Contrast sharpens UI element contrast; Bold Text makes text bolder.
• Dynamic Type and Larger Text font scaling — adjustable font size, scalable typography, and 动态字体 / 更大字号 when users move the text-size slider. Covered on our Dynamic Type listing guide — not Bold Text weight. Dynamic Type changes size; Bold Text changes weight without enlarging text.
• Reduce Transparency opaque backgrounds — less see-through blur behind sheets, menus, and controls under Display & Text Size. Not covered on a dedicated shop guide yet — different from Bold Text. Reduce Transparency changes background opacity; Bold Text changes font weight.
• Display Accommodations and color filters — invert colors, smart invert, reduce white point, differentiate without color under Accessibility settings. Covered on our Display Accommodations listing guide — not typeface weight. Color filters tint the display; Bold Text makes system text heavier.
• Accessibility Zoom screen magnification — window zoom, full-screen zoom, zoom controller under Settings → Accessibility → Zoom. Covered on our Accessibility Zoom listing guide — not Bold Text. Zoom enlarges on-screen UI; Bold Text strengthens typeface weight without magnification.
• Screen Distance too-close reminders — Face ID viewing-distance nudges under Display & Text Size. Covered on our Screen Distance listing guide — not heavier typefaces. Screen Distance warns about physical holding distance; Bold Text adjusts system text weight.
• Reduce Motion toned-down animations — fewer parallax and motion effects under Accessibility settings. Covered on our Reduce Motion listing guide — not Bold Text or typography weight claims.

You can localize the title and still leave every Bold Text screenshot overlay and heavier-typeface paragraph English-only. Buyers then see a Chinese name with English "Bold Text" badges — a mismatch that reads like half-finished localization. See also China App Store still shows English when entire rows fall back.

Where English Bold Text copy shows on the China product page

Western indie teams often market readability or Bold Text compatibility on the US page but leave storefront heavier-typeface marketing English-only because the feature lives in iOS Settings. On the China storefront, English surfaces in places buyers actually read:

• Screenshot overlay badges — "Bold Text", "Heavier system typefaces", "Bolder UI text", "Works with Bold Text", "Clearer labels" on gallery frames showing Settings → Accessibility → Display & Text Size → Bold Text toggles or before/after typeface demos
• Description paragraphs — English readability value props ("Text stays readable with Bold Text on", "Respects system Bold Text") that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 粗体文本, 加粗文本, 更粗字体, or 无障碍文字 when buyers filter for Bold Text-friendly or readability apps
• Promotional text — 170-character field still pitching Bold Text compatibility in English above the description
• Mixed page — Chinese description pasted once but Bold Text screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 that uses wrong Settings vocabulary (增强对比度 for Increase Contrast instead of 粗体文本 for Bold Text) or conflates Bold Text with Dynamic Type font scaling, Increase Contrast UI boosts, or Reduce Transparency when your English source only claimed heavier system typefaces

Better zh-Hans listing copy helps Bold Text-conscious buyers understand your heavier-typeface story before install. It does not replace UIFont weight engineering in the binary or Apple's review decisions — and it does not require you to re-shoot an entire typeface-demo screenshot gallery to mention Bold Text in text.

What AppLocale delivers for Bold Text and heavier-typeface apps on zh-Hans

This SKU is a listing rewrite scoped to Bold Text and heavier system typeface 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 Bold Text or readability awareness to China searchers
• Subtitle — concise benefit line that can reference Bold Text compatibility or heavier system text without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for Bold Text-friendly workflows, heavier typeface readability, and Display & Text Size-adjacent claims in your category
• Description — long listing body with clear zh-Hans paragraphs on Bold Text and heavier-typeface features you already claim — without English-only Bold Text 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 Bold Text toggles or typeface demos ("支持粗体文本", "系统文字更粗更清晰", "兼容加粗文本设置")
• English alignment — matching en-US field notes when both storefronts must stay consistent on Bold Text and readability promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Bold Text, heavier system typefaces, or bolder UI text — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent Bold Text integration your app does not describe.

Bold Text-specific listing vocabulary — what translates differently

Heavier-typeface marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe Bold Text in iOS Settings — not a literal paste of US marketing:

Official Settings vocabulary

Apple's zh-Hans Settings UI uses 粗体文本 for Bold Text, with related buyer language around 加粗文本 (bolded text), 更粗字体 (heavier typefaces), 显示与文字大小 (Display & Text Size under 辅助功能 → 无障碍), and 可读性 (readability). Listing copy should mirror that vocabulary — not generic 视力 or medical eye-exam claims that could imply clinical products.

Bold Text vs Increase Contrast — do not conflate

Increase Contrast strengthens button, icon, and separator borders — 增强对比度, 提高对比度. Bold Text makes system text heavier — 粗体文本, 加粗文本. If your English gallery shows an Increase Contrast toggle, do not upgrade zh-Hans copy to 粗体文本 claims. See the Increase Contrast listing guide only if UI contrast boosts are your lead marketing claim.

Bold Text vs Dynamic Type and Larger Text — do not conflate

Dynamic Type and Larger Text scale font size — 动态字体, 更大字号, 字号可调. Bold Text changes typeface weight without enlarging text — 粗体文本. If your English gallery shows a text-size slider or "Supports Dynamic Type" badges, do not upgrade zh-Hans copy to Bold Text claims unless that is what the frame depicts. See the Dynamic Type listing guide only if adjustable font size is your lead marketing claim.

Bold Text vs Reduce Transparency

Reduce Transparency makes sheet and menu backgrounds more opaque — reducing see-through blur. Bold Text makes system text bolder. zh-Hans listing copy should not imply 降低透明度 when your English source only shows a Bold Text toggle. Each Display & Text Size toggle has its own buyer vocabulary.

Bold Text vs Display Accommodations color filters

Color filters, smart invert, and reduce white point live under Accessibility → Display & Text Size alongside Bold Text — but they are different features with different buyer intent. zh-Hans listing copy should not imply 颜色滤镜 or 降低白点 when your English source only shows a Bold Text toggle. See the Display Accommodations listing guide only if color filters are your lead marketing claim.

Bold Text vs third-party font apps

Font marketplace apps sell custom typeface packs, font installation, and designer font browsing — different buyer intent from Apple's system Bold Text toggle. zh-Hans listing copy should describe Bold Text compatibility or heavier system text — not 字体商店 or custom font catalog positioning unless your English source already claims that product category.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need Bold Text and readability search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 粗体文本, 加粗文本, and 更粗字体 each signal different intent from generic productivity keywords or Increase Contrast terms like 增强对比度.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Bold Text" headlines on gallery frames showing Settings → Accessibility → Display & Text Size → Bold Text — 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.

Why English-only Bold Text copy hurts China storefront conversion

Accessibility-conscious purchasers browsing the China App Store evaluate Bold Text and readability claims in the first scroll. Common failure modes when only en-US is filled:

• Trust gap — Chinese social posts or word-of-mouth recommend a "readable app"; buyer taps through and sees English "Bold Text" with no zh-Hans context
• Localized listing, English badges — description promises Chinese accessibility awareness; screenshot overlays still "Bold Text" at the worst moment
• Search intent miss — buyers search 粗体文本 or 加粗文本; English-only keywords miss intent even when your app references Bold Text in onboarding
• Increase Contrast vocabulary bleed — machine-translated 增强对比度 appearing in zh-Hans copy when English source only claimed Bold Text heavier typefaces, confusing buyers who wanted bolder text not UI contrast presets
• Dynamic Type vocabulary bleed — machine-translated 动态字体 or 更大字号 when English source showed Bold Text, not font-size scaling
• Competitor contrast — rivals with native zh-Hans Bold Text and readability copy look more serious about China buyers who care about 无障碍 and heavier system text

Clearer zh-Hans Bold Text marketing reduces confusion on the product page. It does not replace UIFont weight engineering in the binary or in-app typography adaptation work — and it is not a substitute for medical vision positioning your app does not claim.

Why machine-translated Bold Text copy fails

• Literal "Bold Text" → awkward 粗体文字 instead of commerce-idiomatic 粗体文本 (matches iOS Settings → 辅助功能 → 显示与文字大小 → 粗体文本 vocabulary)
• Increase Contrast vocabulary bleed — 增强对比度 or 提高对比度 when English source showed Bold Text, not UI contrast toggles
• Dynamic Type vocabulary bleed — 动态字体, 更大字号, or 字号可调 when English source meant heavier typefaces, not font-size scaling
• Reduce Transparency bleed — 降低透明度 when English source showed Bold Text, not opaque-background toggles
• Color-filter vocabulary bleed — 颜色滤镜 or 智能反色 when English source showed Bold Text, not Display Accommodations toggles
• Third-party font app vocabulary — 字体商店 or 自定义字体 when English source marketed Apple's built-in Bold Text, not a font marketplace
• Over-medicalized 眼科 or 视力检查 claims when English source only described a Settings typeface-weight preset, not clinical eye exams
• English badge headlines preserved on zh-Hans screenshots — "Bold Text" with no Chinese benefit line beside it
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention Bold Text

Machine translation is fine for internal drafts. Finished Bold Text strings need idiomatic zh-Hans that states what typeface-weight scope you claim — while keeping accurate separation from Increase Contrast, Dynamic Type, Reduce Transparency, color filters, and third-party font products. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans Bold Text listing copy looks like

Heavier-typeface copy appears on screenshot galleries and in description skims. Strong Chinese strings lead with the benefit and state scope plainly:

• Overlay: "支持粗体文本，系统文字更粗更清晰" — feature alignment + benefit in one line
• Description paragraph: plain zh-Hans list of how your app respects Bold Text or heavier system typefaces — clearer labels, readable UI text when Bold Text is on — matching what you actually describe on the US page
• Subtitle: "支持粗体文本" or "兼容加粗文本" within the ~30-character cap
• Keywords: include 粗体文本 / 加粗文本 only when accurate — do not keyword-stuff Increase Contrast, Dynamic Type, or color-filter terms if you only market Bold Text compatibility
• Honest scope — do not claim "built-in Bold Text" in Chinese if your app only recommends enabling system Bold Text in Settings

zh-Hans and en-US strings can differ in length and structure when the underlying Bold Text 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 Bold Text or heavier typefaces ("Bold Text", "Heavier system typefaces", "Bolder UI text", "Works with Bold Text", "Clearer labels")
• Brief note on how your app references Bold Text or heavier system typefaces today — so zh-Hans copy stays accurate to your marketing scope
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with an accessibility launch or App Store gallery 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 Bold Text and heavier-typeface 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

Who this is for

US and EU indie iOS and iPadOS developers and small teams whose en-US listing markets Bold Text compatibility, heavier system typefaces, bolder UI text, accessibility readability, or workflows framed under Settings → Accessibility → Display & Text Size → Bold Text — but the China App Store product page still shows English "Bold Text", "Heavier system typefaces", or "Bolder UI text" copy on screenshots and listing fields — and who want paste-ready zh-Hans listing strings without hiring a full-time localization contractor or a custom font engineering sprint. If you searched for Bold Text App Store Chinese, zh-Hans 粗体文本 listing rewrite, or China App Store heavier-typeface copy, this is the deliverable.

What we do not promise

• No guarantee that Bold Text is enabled on a buyer's device — listing rewrite describes what you already claim
• No UIFont weight API, custom font embedding, or Bold Text rendering engineering
• No Increase Contrast, Reduce Transparency, or Display Accommodations listing copy — see those guides only if that is your marketing scope
• No Dynamic Type or Larger Text listing copy alone — font-size scaling is a different claim; see the Dynamic Type guide if that is your lead story
• No Screen Distance, Reduce Motion, Zoom, or Magnifier listing copy — see those guides only if that is your marketing scope
• No third-party font app or font marketplace positioning
• No vision-health medical outcomes, eye-exam positioning, or clinical certification claims
• No screenshot set production, typeface-demo PNG re-export, or gallery design
• No guaranteed App Store ranking, keyword position, download growth, or vision-health 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

Is Bold Text the same as Increase Contrast?

No. Bold Text makes system text heavier — 粗体文本, 加粗文本. Increase Contrast boosts UI element contrast for buttons, icons, and separators — 增强对比度, 提高对比度 — without changing font weight. See our Increase Contrast listing guide for UI contrast marketing copy.

Is Bold Text the same as Dynamic Type or Larger Text?

No. Dynamic Type and Larger Text market adjustable font size and scalable typography — 动态字体, 更大字号. Bold Text markets heavier system typefaces without enlarging text — 粗体文本. See our Dynamic Type listing guide for font-size scaling copy.

Is Bold Text the same as Reduce Transparency?

No. Reduce Transparency makes sheet and menu backgrounds more opaque — less see-through blur. Bold Text makes system text bolder — 粗体文本. Different Display & Text Size toggles with different buyer vocabulary.

Is Bold Text the same as Display Accommodations color filters?

No. Display Accommodations covers color filters, invert colors, and reduce white point — 颜色滤镜, 降低白点. Bold Text covers heavier system typefaces — 粗体文本. See our Display Accommodations listing guide for color-filter marketing copy.

Is Bold Text the same as a third-party font app?

No. Bold Text markets Apple's system-wide accessibility toggle under Settings → Accessibility → Display & Text Size. Third-party font apps and custom typeface marketplaces are different product categories with different buyer intent.

What listing fields does AppLocale rewrite for Bold Text 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 Bold Text, heavier system typefaces, bolder UI text, or readability — rewritten from your English originals.

Does AppLocale implement Bold Text or custom fonts in my app?

No. We deliver listing metadata copy only. UIFont weight APIs, custom font embedding, and Bold Text trait detection are outside AppLocale scope. We rewrite how you describe existing heavier-typeface claims on the store page.

What do I send after payment?

Your live App Store listing URL, current English listing copy (name, subtitle, keywords, description, promo if used), screenshot overlay lines mentioning Bold Text or heavier typefaces, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.

Is this machine translation?

No. We rewrite Bold Text and heavier-typeface 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 Bold Text or custom font engineering, not Increase Contrast or Reduce Transparency listing copy, not Dynamic Type listing copy alone, not Display Accommodations or color-filter listing copy, not Zoom or Magnifier listing copy, not third-party font apps, 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 — Bold Text & heavier system typeface 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 Bold Text overlay copy, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. AppLocale does not implement Bold Text in your app. Sold by Fortune Insight, LLC.