Dynamic Type & Larger Text App Store Listing in Simplified Chinese — Adjustable Font Size & zh-Hans Copy

Dynamic Type listing copy vs typography engineering — two different jobs

US/EU indie teams conflate in-app font scaling with storefront language. Connect and Xcode actually separate them:

• Dynamic Type in the app — UIFontMetrics, SwiftUI .dynamicTypeSize, scalable fonts, and layout that reflows at larger content sizes. Engineering inside the binary — outside AppLocale scope.
• Auto Layout and accessibility trait code — constraint updates, minimum touch targets, and trait overrides when text scales. Engineering — not listing rewrite.
• Larger-text marketing on the product page — description paragraphs, subtitle positioning, keywords, promotional text, and screenshot overlays that tell buyers your app supports Dynamic Type or adjustable font size. 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 Dynamic Type support in the app.

A Dynamic Type-compatible app and a localized China listing are both valuable — neither replaces the other. AppLocale covers how you describe larger-text support on the store page, not whether fonts scale inside the app.

Dynamic Type listing copy vs VoiceOver, Dark Mode, Kids, and HealthKit guides

Several shop guides cover adjacent Apple platform features. This page covers adjustable font size and larger-text marketing on listing metadata — not engineering, not unrelated category copy:

• Dynamic Type and larger text on the product page — description, subtitle, keywords, promotional text, and screenshot overlays like "Supports Dynamic Type", "Adjustable font size", "Larger accessibility text", "Scales with system text size", and "Readable at every size". This page.
• VoiceOver and screen reader support — "Works with VoiceOver", screen reader badges, blind and low-vision marketing. Covered on our VoiceOver listing guide — not larger-text typography copy. Do not claim VoiceOver in zh-Hans if your English listing only sells Dynamic Type.
• Dark Mode and appearance themes — light/dark UI marketing on gallery frames. Not covered here — a separate listing topic when your product page leads with appearance, not font scaling.
• Kids category and Made for Kids — age-rating-adjacent listing copy and parental messaging. Covered on our Kids category listing guide — not general typography accessibility marketing.
• HealthKit and Apple Health — workout, sleep, and vitals-adjacent listing copy. Covered on our HealthKit listing guide — not Dynamic Type badges on utility or productivity apps.

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

Where English Dynamic Type copy shows on the China product page

Western indie teams often ship Dynamic Type in the app but leave storefront larger-text marketing English-only because fonts scale without zh-Hans rows. On the China storefront, English surfaces in places buyers actually read:

• Screenshot overlay badges — "Supports Dynamic Type", "Adjustable font size", "Larger accessibility text", "Scales with system text size" on gallery frames comparing small vs large text
• Description paragraphs — English typography value props ("Fully supports Dynamic Type", "Readable at every accessibility text size") that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 动态字体, 更大字号, 可调字体, or 无障碍文字大小 when buyers filter for readable apps
• Promotional text — 170-character field still pitching larger text in English above the description
• Mixed page — Chinese description pasted once but Dynamic Type screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 for Dynamic Type (动态类型 vs 动态字体) and wrong typography phrasing that does not match how Chinese buyers read store pages

Better zh-Hans listing copy helps typography-conscious buyers understand your larger-text story before install. It does not replace UIFontMetrics in the binary, layout engineering, or Apple's review decisions — and it does not certify your app as fully accessible.

What AppLocale delivers for Dynamic Type and larger-text apps on zh-Hans

This SKU is a listing rewrite scoped to Dynamic Type and larger-text 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 larger-text support to China searchers
• Subtitle — concise benefit line that can reference adjustable font size or Dynamic Type without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for readable apps, Dynamic Type support, and typography accessibility in your category
• Description — long listing body with clear zh-Hans paragraphs on Dynamic Type and larger-text features you already ship — without English-only typography 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 larger-text badges ("支持动态字体", "字号随系统设置放大", "更大辅助功能文字")
• English alignment — matching en-US field notes when both storefronts must stay consistent on typography accessibility promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Dynamic Type or larger text — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent typography features your app does not ship.

Dynamic Type-specific listing vocabulary — what translates differently

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

Dynamic Type vs generic "big font"

US pages use "Supports Dynamic Type", "Adjustable font size", or "Larger accessibility text." China storefront copy often uses 支持动态字体, 字号可调, 随系统文字大小缩放, or 更大辅助功能文字 — depending on whether you mean Apple's Dynamic Type specifically or general readability. AppLocale aligns phrasing with your actual typography scope, not inventing Dynamic Type support your app does not ship.

Larger text vs VoiceOver — do not conflate

Dynamic Type is typography scaling — VoiceOver is screen reader support. zh-Hans listing copy should not imply 旁白支持 or 读屏友好 when your English source only mentions adjustable font size. If you ship both, say both accurately; if you ship larger text only, keep VoiceOver vocabulary out of subtitle, keywords, and overlays.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need typography-relevant search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 动态字体, 更大字号, and 无障碍文字 each signal different intent from generic productivity keywords.

Caption lines vs burned-in badges

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

Typography accessibility launches and larger-text milestone 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 larger-text pitch lives in promo text rather than the long description.

Why English-only Dynamic Type copy hurts China storefront conversion

Typography-conscious purchasers browsing the China App Store evaluate 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 "Supports Dynamic Type" with no zh-Hans context
• Localized listing, English badges — description promises Chinese readability; screenshot overlays still "Adjustable font size" at the worst moment
• Search intent miss — buyers search 动态字体 or 更大字号; English-only keywords miss intent even when Dynamic Type works in the app
• Competitor contrast — rivals with native zh-Hans typography copy look more serious about China buyers who need larger text
• Overclaim risk in translation — machine-translated "fully accessible" strings that imply VoiceOver or screen reader support when you only ship font scaling

Clearer zh-Hans typography marketing reduces confusion on the product page. It does not replace UIFontMetrics in the binary, layout engineering, or in-app font settings.

Why machine-translated Dynamic Type copy fails

• Literal "Dynamic Type" → awkward 动态类型 instead of commerce-idiomatic 动态字体 or 系统文字大小
• Generic "accessible text" → vague 可访问文字 instead of 辅助功能文字大小 (Settings vocabulary buyers recognize)
• English badge headlines preserved on zh-Hans screenshots — "Supports Dynamic Type" with no Chinese benefit line beside it
• Overlay text overflow — long English typography captions pasted into short screenshot callout zones truncate on device
• VoiceOver vocabulary bleed — 旁白支持 appearing in zh-Hans copy when English source only mentions larger text
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention Dynamic Type

Machine translation is fine for internal drafts. Finished Dynamic Type strings need idiomatic zh-Hans that states what font scaling you ship — while keeping accurate scope and not upgrading to VoiceOver claims. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans Dynamic Type listing copy looks like

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

• Overlay: "支持动态字体，字号随系统设置放大" — feature + scope in one line
• Description paragraph: plain zh-Hans list of areas that scale with larger text — body copy, navigation labels, settings screens — matching what you actually implemented
• Subtitle: "字号可调，阅读更轻松" or category-specific readability line within the ~30-character cap
• Keywords: include 动态字体 / 更大字号 only when accurate — do not keyword-stuff VoiceOver terms if you only ship font scaling
• Honest scope — do not claim "fully accessible" or 旁白支持 in Chinese if only typography scales with Dynamic Type

zh-Hans and en-US strings can differ in length and structure when the underlying typography 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 Dynamic Type or larger text ("Supports Dynamic Type", "Adjustable font size", "Larger accessibility text", "Scales with system text size")
• Brief note on which app areas support Dynamic Type today — so zh-Hans copy stays accurate to your implementation
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a typography accessibility 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 Dynamic Type and larger-text 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 developers and small teams whose app supports Dynamic Type or larger accessibility text and whose en-US listing markets adjustable font size — but the China App Store product page still shows English "Supports Dynamic Type", "Adjustable font size", or "Larger accessibility 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 typography engineering sprint. If you searched for Dynamic Type App Store Chinese, zh-Hans larger text listing rewrite, or China App Store adjustable font size copy, this is the deliverable.

What we do not promise

• No guarantee that your app supports Dynamic Type everywhere — listing rewrite describes what you already ship
• No UIFontMetrics, SwiftUI font scaling, Auto Layout, or in-app typography engineering
• No VoiceOver audits, screen reader implementation, or WCAG consulting — see our VoiceOver guide only if that is your marketing scope
• No guaranteed App Store ranking, keyword position, download growth, or accessibility 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 screenshot design, PNG re-export, Apple Search Ads, or review-reply retainers
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

Does shipping Dynamic Type support auto-translate my China listing?

No. Dynamic Type compatibility is in-app typography engineering — 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 Dynamic Type 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 Dynamic Type, larger text, or adjustable font size — rewritten from your English originals.

Should I claim VoiceOver in zh-Hans if we only support larger text?

No. Dynamic Type and larger-text support are typography accessibility — not screen reader support. Listing copy should describe adjustable font size accurately without implying VoiceOver unless your app actually ships screen reader features.

Does AppLocale implement Dynamic Type in my app?

No. We deliver listing metadata copy only. UIFontMetrics, font scaling, layout reflow, and in-app UI work are outside AppLocale scope. We rewrite how you describe existing larger-text features on the store page — we do not implement typography in the app.

How is this different from VoiceOver listing guides?

Dynamic Type listing copy markets adjustable font size and larger accessibility text on the product page. VoiceOver copy covers screen reader support — different buyer intent and Connect string families. Do not reuse VoiceOver boilerplate when your gallery only shows font scaling.

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 Dynamic Type or larger text, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.

Is this machine translation?

No. We rewrite Dynamic Type and larger-text 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 UIFontMetrics or Dynamic Type engineering, not VoiceOver or screen reader copy, not Dark Mode listing guides, not Kids or HealthKit listing guides, 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 — Dynamic Type & larger text 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 Dynamic Type overlay copy, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. AppLocale does not implement Dynamic Type in your app. Sold by Fortune Insight, LLC.