← ShopAppLocale by Fortune Insight, LLC · 2026-08-27
Always-On Display App Store Listing in Simplified Chinese — iPhone & Apple Watch AOD Copy
You market Always-On Display on the product page — iPhone always-on lock screen glances, dimmed AOD UI, or Apple Watch always-on watch face compatibility — and the US gallery looks polished.
Open the same app on the China storefront and the product page still reads English: name, subtitle, keywords, description, and screenshot captions that say Always-On Display, AOD, Always-on lock screen, Works with Always-On Display, or Always-on watch face.
Chinese buyers on supported iPhones and Apple Watch land on a page that looks unfinished.
AppLocale delivers paste-ready zh-Hans listing copy for those Connect fields — not AOD engineering, not always-on rendering implementation, not screenshot design.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS and Apple Watch developers — US, UK, EU, Canada, Australia — whose App Store product page leads with Always-On Display marketing:
iPhone always-on lock screen — dimmed glance UI, persistent clock and widget data, or app content visible on supported iPhones without waking the screen
Apple Watch always-on watch face — complications, metrics, or app data that stay visible when the wrist is lowered and the display dims
English AOD overlay copy — captions like “Always-On Display”, “AOD”, “Always-on lock screen”, “Works with Always-On Display”, “Glance without waking”, or “Always-on watch face” still on zh-Hans frames
Binary already supports AOD — you ship the feature; you need storefront text in Simplified Chinese, not engineering help
China storefront enabled — Pricing and Availability includes China, but the zh-Hans row is empty, machine-translated, or still English
You need paste-ready Connect text — not an engineer to implement always-on rendering, not a designer to re-export every AOD PNG from scratch. If the entire China product page is still English on every frame, start with China App Store still shows English or the AppLocale product page for a full-row pass first.
AOD listing copy vs engineering vs screenshot design
Always-On Display apps blur three workstreams indie teams conflate. AppLocale covers layer 1 only.
App Store Connect listing metadata — name, subtitle, keywords, description, promotional text, screenshot overlay captions on the zh-Hans row. AppLocale scope.
Always-On Display in-app UI — dimmed lock screen layouts, always-on watch face complications, WKApplication rendering, SwiftUI always-on modes, and localized runtime strings inside iOS and watchOS. Engineering scope — not AppLocale.
Screenshot composition — device frames, dimmed-screen mockups, always-on watch face captures, re-exporting PNGs with burned-in headlines. Design scope — AppLocale delivers caption lines you paste or hand to a designer.
This page covers the first bucket for AOD-centric product pages. It is not our StandBy guide (landscape charging nightstand mode), not our Lock Screen widgets guide (portrait accessory slots), not our Live Activities guide (time-bound ActivityKit updates), and not our Watch complications guide (watch face slot marketing without always-on framing).
Always-On Display is not StandBy, Lock Screen widgets, Live Activities, or generic complications
Buyers and reviewers confuse five surfaces when localizing an AOD-marketed app for China. Listing copy should name the surface your screenshots actually show — and not claim iPhone AOD if you only ship Watch always-on faces.
iPhone Always-On Display (this page — when your gallery shows it)
Dimmed always-visible lock screen on supported iPhones — clock, widgets, and app glance data visible without fully waking the display. Your marketing may say “Always-On Display” or “Glance at a dimmed screen”. AppLocale rewrites Connect metadata and AOD frame captions for China buyers.
Apple Watch always-on watch face (this page — when your gallery shows it)
Persistent wrist data when the display dims — complications and app metrics that remain visible on always-on capable Apple Watch models. Distinct from generic complication marketing when your English copy explicitly says “Always-on watch face” or “AOD on your wrist”. See Watch complications guide only when complications — not always-on behavior — are the lead story.
StandBy mode (different guide)
Landscape charging nightstand view — clock, photos, and widget stacks when iPhone charges in landscape. StandBy can appear on an always-on-capable iPhone, but nightstand carousel marketing is covered by the StandBy listing guide, not this page.
Lock Screen widgets (different guide)
Portrait Lock Screen customization — circular, rectangular, and inline accessory slots. Widgets may appear on an always-on lock screen, but accessory-slot gallery marketing is covered by the Lock Screen widgets guide, not AOD-specific copy.
Live Activities & Dynamic Island (different guides)
Time-bound live updates on Lock Screen and Dynamic Island — delivery timers, sports scores, workout status. Persistent always-on glances are not Live Activities. See Live Activities listing guide or Dynamic Island product page copy only if your gallery leads with live update UI.
Why Always-On Display English captions hurt on the China storefront
AOD-first apps often dedicate multiple gallery frames to dimmed lock screen glances or always-on watch face previews — surfaces where English marketing copy appears beside clock and complication chrome:
Untranslated AOD headlines — “Always-On Display”, “AOD”, “Works with Always-On Display” left on zh-Hans frames while the description claims full Chinese support
Always-on lock screen boilerplate — “Glance without waking”, “See it on your always-on lock screen”, “Dimmed display ready” still in Latin script on frames Chinese buyers skim first
Watch always-on face lines in English — “Always-on watch face”, “Stays visible when you lower your wrist”, “AOD on Apple Watch” never rewritten for wrist-aware buyers
English sample data in AOD captures — widget titles, complication labels, or metric names frozen in Latin script on dimmed-screen previews
Searchable fields still English — subtitle and keywords never packed for 全天候显示, 常亮, or always-on-adjacent terms Chinese users type
Claiming iPhone AOD when only Watch ships — description promises always-on lock screen glances but screenshots show watchOS always-on faces only — or the reverse
Better zh-Hans listing copy and AOD screenshot captions reduce product-page bounce for always-on-aware buyers — they do not replace platform always-on configuration inside the binary or guarantee Search rank.
Common mistakes on Always-On Display zh-Hans listings
Leaving “Always-On Display” untranslated everywhere — Apple markets 全天候显示 in zh-Hans regions; mixing English AOD jargon with otherwise Chinese copy looks unfinished
Using Android-style 息屏显示 for iPhone AOD — native App Store copy in China aligns with Apple’s 全天候显示 framing, not generic OLED always-on slang from other platforms
Calling AOD “StandBy” or “widgets” in every field — buyers searching for 待机显示 or 锁屏小组件 expect different surfaces; AOD dimmed glances deserve their own phrasing
Claiming Always-On Display on every iPhone — listing copy should not imply universal iPhone AOD when your app only markets Apple Watch always-on face compatibility
Translating only the description — name, subtitle, and keywords still English while AOD screenshots dominate the gallery
English burned into PNG exports — Connect caption fields are zh-Hans but overlay text on the image file is still Latin script
Assuming AOD engineering localizes the store page — binary always-on support and App Store metadata are independent workstreams
Conflating with Live Activities — persistent always-on glances and ActivityKit live timers are different surfaces; do not reuse Live Activity boilerplate on dimmed lock screen frames
ChatGPT 翻译腔 on always-on jargon — awkward literal translations of “dimmed display” or “low-power always-on” that native readers do not use in App Store copy
What good zh-Hans Always-On Display listing copy looks like
Listing fields should name the always-on surface your screenshots actually show — iPhone lock screen, Apple Watch face, or both — aligned with gallery order:
Subtitle — one concrete promise: “支持 iPhone 全天候显示” or “Apple Watch 表盘常亮可见” — not vague “提升效率”, and not iPhone AOD claims when only Watch ships
Keywords — mix category terms (时钟, 待办, 健身) with AOD intent (全天候显示, 常亮, 表盘) within Connect’s ~100-character zh-Hans budget; see Simplified Chinese keywords guide
Description — short paragraphs for dimmed lock screen glances and/or always-on watch face data — mirror screenshot sequence and match the hardware you actually support
Screenshot captions on AOD frames — name the on-screen action: “息屏也能一眼看到待办” or “抬腕放下,数据仍常亮” — not “Always-On Display” in Latin script
Sample widget or complication titles in caption lines — when your gallery shows example always-on data, caption sheet lists zh-Hans equivalents for designer re-export
Voice consistency — same 你/您 choice as your description across overlay lines and promotional text
Connect checklist for Always-On Display apps targeting China
Open App Store → Chinese (Simplified) — confirm the zh-Hans row exists; empty rows fall back to English on the China storefront
Audit searchable fields — name, subtitle, keywords, description saved in zh-Hans, not placeholder English
Walk the screenshot gallery in order — flag frames showing iPhone dimmed lock screen glances, always-on watch face previews, or English AOD overlay copy
Confirm which surfaces you ship — iPhone AOD, Watch always-on face, or both — before writing subtitle and keyword claims
Export overlay lines — spreadsheet of English caption text per frame beats screenshots of Connect alone
Note burned-in vs Connect captions — if always-on titles are embedded in PNGs, caption deliverables go to your designer for re-export
Verify China in Pricing and Availability — storefront enabled before expecting zh-Hans to appear
Separate engineering tasks — always-on rendering, WKApplication configuration, and in-app dimmed-mode UI stay with your dev team
For one app on the zh-Hans row, paste-ready Simplified Chinese listing copy focused on Always-On Display-centric product pages:
Name, subtitle, keywords, description — rewritten for China Search intent and always-on workflows you market on iPhone, Apple Watch, or both
Promotional text — when you include current English promo copy in your brief
Always-On Display screenshot caption lines — overlay text for frames showing dimmed lock screen glances, always-on watch face data, and English lines like Always-On Display, AOD, Always-on lock screen, Works with Always-On Display, Always-on watch face
English alignment — en-US fields tightened when both storefronts need the same promise in native phrasing
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite from your current English listing — not a machine translation dump. Default $79 scope is listing metadata plus AOD frame captions; ask if you need iPad/Mac device sets or Custom Product Pages bundled separately.
What AppLocale does not do
Does not write Always-On Display, WKApplication, or SwiftUI always-on rendering code
Does not configure dimmed lock screen layouts, always-on watch face complications, or platform AOD entitlements in Xcode
Does not design, compose, or re-export Always-On Display screenshot PNG/JPEG assets
Does not localize in-app widget display names, watch face labels, string catalogs, or the app binary
Does not run Apple Search Ads, paid UA, or review-reply retainers
Does not guarantee App Store rankings, AOD feature discovery, or download growth
Is not QuantRadar, not investment advice, and not legal review
Does not invent reviews, ratings, or traffic numbers
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English listing text, English screenshot overlay lines (especially Always-On Display and always-on watch face frames), which surfaces you ship (iPhone AOD, Watch always-on face, or both), and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans copy arrives at your Stripe receipt email
Paste into Connect — enter metadata on the zh-Hans row; hand caption lines to your designer if text is burned into PNGs
Does AppLocale implement Always-On Display or always-on watch face rendering in my app?
No. We rewrite App Store Connect listing metadata and screenshot caption text only. AOD engineering and in-app always-on UI are separate work.
What Always-On Display listing copy does AppLocale deliver?
Paste-ready zh-Hans name, subtitle, keywords, description, and caption lines on screenshots that show iPhone always-on lock screen glances, dimmed AOD UI, Apple Watch always-on watch face data, or English overlays like Always-On Display, AOD, and Always-on watch face.
Should I claim Always-On Display on iPhone if my app only supports Apple Watch always-on faces?
No. Listing copy should match the surface your gallery actually markets. AppLocale will not write iPhone AOD claims when your screenshots and binary only show watchOS always-on face compatibility.
How is this different from StandBy, Lock Screen widgets, or Live Activities listing copy?
StandBy is landscape charging nightstand mode. Lock Screen widgets are portrait accessory slots. Live Activities are time-bound ActivityKit updates. Always-On Display is the dimmed always-visible lock screen on supported iPhones — or persistent always-on watch face data on Apple Watch.
Does localizing AOD screenshots fix in-app always-on UI text?
No. Listing captions do not change widget content, watch face labels, or dimmed lock screen UI at runtime. In-app string localization requires Xcode and platform-specific always-on configuration outside AppLocale scope.
What do I send after payment?
Your live App Store listing URL, current English listing text, English screenshot overlay lines (especially AOD frames), which surfaces you ship, and target locale (zh-Hans). Reply from the email on your Stripe receipt — we deliver within 24 hours.
Will zh-Hans AOD keywords rank my app for 全天候显示?
We do not guarantee keyword position or download growth. We pack keywords within Connect limits based on your app’s actual always-on use case — not empty rank promises.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not AOD engineering, not always-on rendering implementation, not screenshot design, not binary localization, not ads, not ranking guarantees, not review-reply retainers, not QuantRadar, and not investment advice.
AppLocale — zh-Hans Always-On Display app listing copy for the China App Store
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and current English listing plus Always-On Display screenshot caption lines. No ranking guarantees. Sold by Fortune Insight, LLC.