Block Caller App Store Listing in Simplified Chinese — Permanently Block a Phone Number & zh-Hans 拦截来电 / 屏蔽来电 Copy for China
Your iOS app already markets Block Caller, block this caller, permanently block a phone number, or stop calls and FaceTime from one contact on the en-US product page — gallery frames show the Block This Caller sheet, Settings → Phone → Blocked Contacts lists, or block-number confirmation flows — and buyers understand the benefit in English.
Open the same app on the China storefront and the product page still shows English name, subtitle, keywords, description, and screenshot captions that repeat untranslated block-caller jargon.
Shipping block-list guidance or companion UX in the binary does not auto-fill a Simplified Chinese (zh-Hans) localization row.
AppLocale writes paste-ready zh-Hans listing copy for those Connect fields — aligned with what your per-number blocking feature actually delivers, without claiming carrier-wide spam blocking or Phone.app replacement.
Supporting search terms include 拦截来电, 屏蔽来电, and 拉黑号码 — woven naturally, not as the only language on the page.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS developers — US, UK, EU, Canada, Australia — who:
Already ship or are launching an app that markets Block Caller, block this caller, block a phone number, or permanently block calls and FaceTime from one contact on the en-US product page
Show Block This Caller confirmation sheets, blocked-contacts lists, block-number wizards, or unblock flows in screenshot galleries and App Previews
Help users block a specific harasser, ex-partner, telemarketer line, or repeat caller — not looking for unknown-number auto-silence or Messages inbox-filter marketing help here
Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on block-caller gallery frames
Need paste-ready Connect text — not an engineer to wire call-directory extensions, not a designer to re-export every screenshot from scratch
Phone block vs zh-Hans listing copy — two different jobs
Teams assume block-list capability in the binary or a companion guide covers storefront language. Xcode, Phone settings, and Connect actually separate per-number blocking from product-page copy:
Block This Caller (Phone, FaceTime, Messages) — system action that permanently blocks one contact or number from calling, FaceTime, and often messaging. Does not generate Chinese listing text.
Blocked Contacts (Settings → Phone) — the system list of numbers and contacts you have blocked. Separate from the zh-Hans description paragraph that explains block-caller value to buyers.
In-app block-list UI — setup wizards, blocked-number lists, unblock flows, and Block This Caller explainers. Your listing may mention block a phone number; implementing block APIs is engineering work, not listing copy.
Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
App Store tab → Chinese (Simplified) — 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 block flags in the binary.
Working per-number blocking in the app or system settings and a localized China listing are both required when you sell on the China storefront — neither replaces the other.
Block Caller listing copy is not Silence Unknown Callers, Filter Unknown Senders, Report Junk, or Hide Alerts
Call and message apps blur five surfaces indie teams conflate. AppLocale covers listing metadata only — layer 1.
1 — App Store listing metadata (zh-Hans row)
Name, subtitle, keywords, description, plus screenshot overlay captions and App Preview text on the Simplified Chinese localization in App Store Connect. This is what buyers see before install. AppLocale's $79 deliverable is paste-ready copy for these fields — including caption lines on frames that show Block This Caller sheets, blocked-contacts lists, or block-number marketing art.
2 — In-app block-list UI (not included)
Text inside setup wizards — block labels, blocked-number lists, unblock confirmations — comes from your app binary, String Catalog, or runtime data. Translating that requires Xcode localization, not a listing rewrite. We do not edit Phone blocked-contacts layouts or block API code.
3 — Silence Unknown Callers (different Phone setting — not this page)
Silence Unknown Callers (静音未知来电) sends calls from numbers not in Contacts, Mail, or Messages straight to voicemail without ringing — a blanket rule for strangers, not a permanent block of one number you choose. Block Caller (拦截来电 / 屏蔽来电 / 拉黑号码) stops a specific contact or line from calling, FaceTime, and related surfaces entirely. Listing copy for Block Caller should not describe unknown-number voicemail behavior — see Silence Unknown Callers listing guide, not here.
Filter Unknown Senders (过滤未知发件人) routes texts from unknown senders into a separate Messages inbox — inbox separation, not blocking a caller from Phone. Report Junk reports spam messages to Apple or carriers — not permanently blocking a phone number from calling. Block Caller listing copy markets per-number stop-calls-and-FaceTime value — see Filter Unknown Senders listing guide and Report Junk listing guide for those distinct buyer stories.
Hide Alerts mutes notification banners for one conversation — the sender can still call and message; you just stop seeing alert pop-ups. Edit Message and Tapback reactions are messaging UX — not blocking callers. Block Caller listing copy should not describe per-thread mute badges or chat edit overlays — see Hide Alerts listing guide when mute-not-block is your hero.
What China buyers still see when the zh-Hans row is incomplete
When Simplified Chinese metadata is missing or falls back to English, the China storefront product page mirrors your US block-caller marketing gaps:
English app name or subtitle — Search results and the product header show Latin script while competitors read native
Untranslated keyword field — wasted 100-character cap; China Search indexes Simplified Chinese characters like 拦截来电, 屏蔽来电, and 拉黑号码, not English "Block Caller" alone
English description — long body text that never mentions 阻止此来电号码, 已阻止的联系人, or how per-number blocking works before install
Block-caller screenshot captions still in English — overlay lines like "Block Caller", "Block this number", "Blocked contacts", or "Stop calls from this contact" on gallery frames targeting China buyers
Spam blocking overclaimed — description promises universal spam-database blocking when your app only guides users to Block This Caller for one harasser line
Conflated with Silence Unknown Callers — zh-Hans copy mentions 静音未知来电 when the product actually markets blocking one saved number — confusing buyers who expect a different Phone setting
Conflated with Hide Alerts — per-conversation mute copy on block-caller frames when the deliverable is permanent stop-calls — see Hide Alerts listing (zh-Hans)
App Preview voiceover or burned-in English — Connect preview text fields can be zh-Hans even when video assets still carry English; redesigning burned-in video text is outside AppLocale scope
Better zh-Hans listing copy reduces product-page bounce for users who already search in Chinese — it does not auto-block numbers in Settings or translate in-app blocked-contact labels after install.
Common mistakes on Block Caller zh-Hans listings
Leaving "Block Caller" untranslated — Apple markets 阻止此来电号码 and 已阻止的联系人 in zh-Hans regions; English-only overlay lines on otherwise Chinese copy looks unfinished
Machine-translated "block this number" as 阻止这个数字 — awkward phrasing; align with buyer-facing terms like 拦截来电, 屏蔽来电, or 拉黑号码 depending on your UX
Conflating Block Caller with Silence Unknown Callers — 拉黑号码 (stop one contact) is not 静音未知来电 (strangers to voicemail) — different Phone settings, different screenshot stories
Conflating Block Caller with Filter Unknown Senders — inbox separation for stranger texts is not permanently blocking a phone number from calling — see Filter Unknown Senders listing (zh-Hans)
Conflating Block Caller with Report Junk — reporting spam to Apple is not the same as blocking a caller from Phone — see Report Junk listing (zh-Hans)
Conflating Block Caller with Hide Alerts — muting notification banners for one thread is not stopping calls — see Hide Alerts listing (zh-Hans)
Claiming universal spam blocking — metadata must match delivery; do not promise carrier-wide spam-database enforcement unless your call-directory extension and data sources support it
Claiming Phone.app or system dialer replacement — companion apps and setup guides should not imply they replace Apple's Phone app or carrier call routing for all users
English-only What's New after a block-caller launch — version notes are a separate field; base $79 focuses on evergreen listing fields unless you bundle What's New in intake
Assuming block APIs localize the store page — engineering and App Store metadata are independent workstreams
What good zh-Hans Block Caller listing copy looks like
Align tone with your en-US listing and name the block-caller surfaces buyers actually see:
Name & subtitle (30 chars each) — lead with the outcome (拦截来电, 屏蔽骚扰号码) not SDK jargon alone
Keywords (100 chars) — Simplified Chinese queries for block caller, block this number, blocked contacts — weave 拦截来电, 屏蔽来电, 拉黑号码, and 已阻止的联系人 naturally; not English API names stuffed into the hidden field
Description — one clear paragraph on where blocking appears (Block This Caller sheet, Settings blocked list, in-app block wizard) and what the buyer gets — no more calls or FaceTime from that contact
Screenshot captions — one line per frame naming the on-screen state: "一键拉黑号码，来电与 FaceTime 将被拦截" not "Block Caller" alone
Honest scope — if blocking requires specific OS versions, Contacts sync, or supported regions, say so in plain zh-Hans without dialer-replacement or universal-spam-blocking language
Block Caller screenshot captions Chinese buyers expect
Privacy, utility, and anti-harassment apps often dedicate one or two gallery frames to the block-caller story — Block This Caller sheets, blocked-contacts lists, or block-number confirmation flows. Overlay lines on those frames should name the feature in plain zh-Hans:
Block This Caller sheet frame — describe the system action: "阻止此来电号码，永久拦截来电" instead of "Block Caller" alone
Blocked contacts list frame — name the outcome honestly: "已阻止的联系人不再来电或 FaceTime" vs vague "Stop spam" when per-number block is the actual deliverable
Setup wizard frame — explain the guided benefit: "几步完成拉黑骚扰号码" — not English-only "Block this number"
Unblock flow frame — state manageability only when shipped: "随时解除屏蔽，恢复来电" when art shows Settings → Blocked Contacts
Match caption to capture — if the screenshot shows a business block-list dashboard, the overlay should describe 商务号码拦截 not consumer Phone.app UI unless art shows that context
AppLocale includes Block Caller-related overlay lines in the screenshot caption deliverable when your gallery uses them. We do not redesign or re-export PNG assets — you paste overlay text into Connect or your design tool.
Connect checklist before you order Block Caller listing copy
Open App Store → Chinese (Simplified) — confirm the zh-Hans localization row exists; adding China under Pricing and Availability alone does not fill it
Audit five text fields — name, subtitle, keywords, description, promotional text (if used) saved in zh-Hans, not placeholder English
List screenshot frames that show block UI — note which gallery images show Block This Caller sheets, blocked-contacts lists, block wizards, or block-number art so caption lines match frame order
Export current English captions — overlay text from Connect or your design spreadsheet, including any "Block Caller", "Block this number", "Blocked contacts", or "Stop calls from this contact" boilerplate
Confirm feature scope honestly — note system Block This Caller guidance vs in-app block list vs companion dashboard so zh-Hans copy does not overclaim carrier or Phone.app replacement; confirm you are marketing Block Caller — not Silence Unknown Callers, Filter Unknown Senders, Report Junk, or Hide Alerts
Confirm in-app UI language separately — plan Xcode string localization if blocked-contact labels are still English after install
Skip engineering tasks here — Call Directory extensions, IdentityLookup data, carrier integration, and block API QA stay with your dev team
Paste-ready Simplified Chinese listing metadata rewritten from your English App Store copy, with Block Caller-aware phrasing:
App name — up to 30 characters on the zh-Hans row
Subtitle — up to 30 characters; visible under the name in Search
Keywords — up to 100 characters in the hidden keyword field
Description — long listing body explaining block-caller and per-number blocking value for China buyers
Screenshot caption lines — overlay text for frames showcasing Block This Caller sheets, blocked-contacts lists, block wizards, or block-number marketing art (send frame count and current English lines)
Listing alignment — voice consistent with your en-US page; we note both sides when English also needs tightening on blocking claims
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite — not a machine translation dump. Character counts verified before delivery.
What AppLocale does not do
Does not implement Call Directory, IdentityLookup, CallKit, or CXCallController extensions
Does not build spam-number databases, carrier PSTN integration, or call-blocking-as-a-service retainers
Does not configure Block This Caller system actions or claim Phone.app replacement in engineering work
Does not write Silence Unknown Callers (静音未知来电) listing copy — a different Phone setting with a different buyer story
Does not write Filter Unknown Senders, Report Junk, Hide Alerts, Edit Message, or Tapback listing copy as lead
Does not localize in-app blocked-contact labels, setup wizard strings, or runtime caller-ID strings
Does not design or re-export screenshots — only Connect caption text you paste or hand to a designer
Does not edit App Preview video files or burn new subtitles into video assets
Does not manage Apple Search Ads, Custom Product Pages, or ad campaigns
Does not write App Review replies or ongoing ASO retainers
Does not guarantee App Store ranking, call-blocking accuracy, or download growth in China or elsewhere
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
Does not maintain twin listing pages for block-call, caller-block, block-number, block-phone, blocked-callers, or blacklist-caller slug variants
How it works
Confirm scope — zh-Hans listing fields plus Block Caller screenshot captions; block-list engineering stays on your side
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English name/subtitle/keywords/description, screenshot caption lines (note which frames show Block Caller or block-number UI), feature scope (system Block This Caller guide vs in-app block list), and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans fields arrive at your Stripe receipt email
Paste in Connect — App Store → Chinese (Simplified) → save → submit with your next version if needed
Does localizing my listing block a phone number inside the Phone app?
No. AppLocale rewrites App Store Connect metadata — name, subtitle, keywords, description, and screenshot caption lines on your zh-Hans product page. The Block This Caller action in Phone, FaceTime, or Messages, Settings → Phone → Blocked Contacts, and in-app block-list logic are system or binary work outside AppLocale scope.
How is Block Caller listing copy different from Silence Unknown Callers?
Block Caller listing copy markets permanently blocking one chosen contact or phone number — calls, FaceTime, and often Messages from that sender stop entirely. Silence Unknown Callers sends unknown numbers straight to voicemail without ringing — it does not permanently block a specific saved number you pick. Screenshot captions should name 拦截来电, 屏蔽来电, or 拉黑号码 for a named contact — not 静音未知来电 for strangers. See our Silence Unknown Callers listing guide for unknown-number auto-silence claims.
How is Block Caller different from Filter Unknown Senders, Report Junk, or Hide Alerts?
Filter Unknown Senders routes stranger texts into a separate Messages inbox — not a permanent Phone block. Report Junk reports spam messages — not blocking a caller from Phone. Hide Alerts mutes notification banners for one conversation — the sender can still call. Block Caller stops a specific contact from calls and FaceTime entirely.
What character limits apply to zh-Hans Block Caller listing fields?
App name and subtitle are each up to 30 characters on the zh-Hans row. The keyword field allows up to 100 characters. Description and screenshot caption lines have longer limits but should stay concise — especially subtitle and overlay lines that must fit on-device mockups showing blocked-contacts lists or Block This Caller confirmation sheets.
Should I claim my app replaces the Phone app or blocks every spam caller in China?
No. Listing copy should describe the per-number block, blocked-contacts list, or Block This Caller guidance your app actually ships — without promising universal spam blocking, carrier-wide enforcement, or that you are the system Phone app. AppLocale rewrites from your English source claims; we do not invent blocking coverage your binary does not support.
What do I send after AppLocale payment?
Your live App Store listing URL, current English (or partial zh-Hans) name, subtitle, keywords, description, screenshot overlay lines with frame order noted, which frames show Block Caller or block-number UI, and feature scope (system Block This Caller guide vs in-app block list). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Does AppLocale sell separate block-call, caller-block, or block-number twin listing pages?
No. AppLocale does not maintain separate twin listing pages for block-call, caller-block, block-number, block-phone, blocked-callers, or blacklist-caller slug variants. Those search intents fold onto this Block Caller page when permanently blocking a chosen phone number dominates your lead gallery.
Does AppLocale implement CallKit, call-blocking APIs, or Phone.app engineering?
No. We rewrite Connect listing copy only. CallKit provider configuration, IdentityLookup call-directory extensions, carrier PSTN integration, and Block This Caller system behavior are engineering tasks we do not perform.
Will zh-Hans copy mentioning Block Caller 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 per-number blocking 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 Silence Unknown Callers or unknown-number auto-silence listing copy, not Call Directory or spam-database listing copy, not Filter Unknown Senders or Report Junk or Hide Alerts listing copy, not general Messages or Tapback listing copy, not CallKit engineering, not screenshot image design, not in-app string localization, not Apple Search Ads management, not ranking guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
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.