Mention Notes App Store Listing in Simplified Chinese — @mention in Notes / 备忘录提及 / 协作备忘录 @提及 zh-Hans Copy

Who this is for

Western indie iOS and iPadOS developers — US, UK, EU, Canada, Australia — who:

• Already ship a note app or team-collaboration product that markets Mention Notes, Mention in Notes, @mention collaborators, or notify teammates when mentioned inside shared or collaborative notes on the en-US product page and in screenshot galleries
• Sell productivity or knowledge apps where buyers @mention people in shared notes, see mention autocomplete, or receive collaborator notifications — not corner-swipe Quick Note capture, pin-to-top sorting, diary prompts, or general chat threads
• Finished @mention UX in the binary — not looking for Notes.framework, CloudKit shared-note sync, or mention-notification engineering help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on Mention Notes and @mention gallery frames
• Need paste-ready Connect text — not an engineer for Notes APIs, not a designer to re-export every screenshot from scratch, not Connect configuration on your account

If your lead feature is notebooks, folders, tags, sticky notes, or locked notes — not @mentions — see Notes listing (zh-Hans). If you market Pin Note or Pinned Notes at the top, see Pinned Notes listing (zh-Hans). If your hero is corner-swipe Quick Note capture, see Quick Note listing (zh-Hans). If Messages-originated Shared with You shelves dominate, see Shared with You 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.

@mention engineering vs zh-Hans listing copy — two different jobs

Teams assume @mention capability covers storefront language. Xcode, entitlements, and Connect actually separate in-app mention features from product-page copy:

• Notes.framework, CloudKit & shared-note sync — in-app code that saves, syncs, and renders shared notes. Controls whether @mention autocomplete works. Does not generate Chinese listing text. AppLocale does not implement this.
• @mention parsing & collaborator notifications — logic that detects @handles, resolves collaborators, and sends mention notifications. Separate from the zh-Hans description paragraph that explains Mention Notes value to China buyers browsing the App Store.
• Shared-note permissions & collaborator lists — access control features in your app. Listing copy should match what screenshots actually show — an @mention autocomplete sheet, not a generic notebook tree unless that is what the frame shows.
• Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
• App Store tab → Chinese (Simplified) localization — 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 @mention features in the binary.

Working Mention in Notes flows in the binary and a localized China listing are both required when you sell on the China storefront — neither replaces the other. AppLocale covers how you describe Mention Notes and @mention workflows on the product page in zh-Hans, not how you implement Notes.framework or mention-notification logic.

Mention Notes listing copy is not Notes hub, Pinned Notes, Quick Note, Journal, Freeform, Shared with You, or Messages

Productivity apps blur several surfaces indie teams conflate. AppLocale covers listing metadata only — @mention marketing on the product page:

• Mention Notes & @mentions (this page) — Mention in Notes, @mention collaborators inside shared or collaborative notes, notify teammates when mentioned, mention someone in a note, 备忘录提及, 协作备忘录 @提及 — collaborator notifications without leaving the note editor.
• Notes hub & notebooks (different) — folders, tags, sticky notes, locked notes, organized note libraries — not @mentions as the lead. See Notes listing guide — not Mention Notes copy.
• Pinned Notes & pin-to-top (different) — Pin Note, Pinned Notes section at the top of a folder or list. See Pinned Notes listing guide — not @mention copy.
• Quick Note & capture-to-note (different) — corner swipe, Add to Quick Note from Share sheet, fleeting capture while staying in another app. See Quick Note listing guide — not Mention in Notes copy.
• Journal & diary (different) — Apple Journal integration, reflective prompts, Save to Journal badges. See Journal listing guide — not 备忘录提及 mention marketing.
• Freeform & whiteboard (different) — infinite canvas boards, collaborative sketches, sticky boards on a spatial canvas. See Freeform listing guide — not @mention-in-notes copy.
• Shared with You (different) — Messages-originated content surfacing in Photos For You, Safari Start Page, and Listen Now shelves. See Shared with You listing guide — not @mention inside a note editor.
• Messages & iMessage hub (different) — chat threads, group chats, tapbacks, RCS texting. See Messages listing guide — 信息, not Mention in Notes when @mention autocomplete is your gallery hero.
• Math Notes & Writing Tools (different) — equation solving and AI writing-assistant marketing. Not covered on this page — separate scopes with different screenshot vocabulary.

Your screenshots may show an @mention autocomplete sheet beside a shared-note header. Listing copy should name the correct claim per frame — a "Mention in Notes" badge is not a Quick Note corner swipe, not a Pinned Notes section, not a Shared with You shelf, and not a Messages chat thread unless that is what the frame shows.

Apple system Mention in Notes vs your app's @mention marketing — listing honesty

Apple ships Mention in Notes on iOS and iPadOS — in a shared note, type @ and pick a collaborator; they receive a notification and can jump to the mention. Third-party note apps often market @mention autocomplete, collaborator notifications, team mention workflows, or shared-note @handles. AppLocale rewrites listing copy from what your US page already claims:

• If your app complements Apple Notes @mentions — zh-Hans copy can describe Mention in Notes, @mention collaborators, or notify-when-mentioned workflows your binary actually supports without claiming to replace Apple Notes or iCloud shared-note sync unless your English listing already states that accurately.
• If your app uses team @handles or mention chips — description and screenshot overlays should name the mention model you ship (备忘录提及, 协作备忘录 @提及, @提及协作者) in commerce-idiomatic Chinese, not generic "replace Apple Notes" overclaims.
• If your US page mentions iCloud or shared-note sync — AppLocale aligns zh-Hans strings to your English source; we do not invent Apple Notes iCloud parity or full shared-note scope beyond what your screenshots and description support.
• If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not broaden mention scope beyond what your listing already claims.

Clear zh-Hans copy helps productivity and team-collaboration buyers understand whether your app @mentions collaborators inside shared notes before install. It does not replace Notes.framework implementation, mention-notification engineering, or Apple's review decisions — and it does not certify system-Notes parity.

What China buyers see when zh-Hans Mention Notes copy is missing

Note apps that lead marketing screenshots with @mention demos — Mention in Notes callouts, @mention autocomplete sheets, collaborator notification badges — often show English marketing text beside mention UI:

• Screenshot overlay badges — "Mention in Notes", "@mention", "Notify collaborators", "Mention someone", "@mentions in shared notes", "Collaborator notified" on gallery frames
• Description paragraphs — English value props about @mentioning teammates or notifying collaborators in shared notes that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 备忘录提及, 协作备忘录 @提及, or @提及 when buyers filter for collaborative note apps
• Promotional text — 170-character field still pitching Mention Notes in English above the description
• Mixed page — Chinese description pasted once but @mention screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 for mention terms (提及 vs @提及 vs 艾特) and wrong phrasing that does not match how Chinese buyers describe collaborative @mention note workflows on store pages

Better zh-Hans listing copy helps productivity and team-work buyers understand your @mention story before install. It does not replace Notes.framework APIs, mention-notification logic, or Apple's review decisions — and it does not guarantee mention behavior on every device model.

What AppLocale delivers for Mention Notes apps on zh-Hans

This SKU is a listing rewrite scoped to Mention Notes and @mention 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 @mention or Mention in Notes value to China searchers
• Subtitle — concise benefit line that can reference 备忘录提及 or @mention collaborators without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for 备忘录提及, 协作备忘录 @提及, @提及, and collaborative note apps in your category
• Description — long listing body with clear zh-Hans paragraphs on @mention workflows you already ship — without English-only "Mention in Notes" 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 @mention autocomplete, Mention in Notes callouts, collaborator notification badges, or mention chips
• English alignment — matching en-US field notes when both storefronts must stay consistent on @mention promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Mention Notes, Mention in Notes, @mention, or notify collaborators — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent Apple Notes clone or iCloud shared-note sync capabilities your app does not ship.

Mention Notes-specific listing vocabulary — what translates differently

@mention marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe collaborative mention workflows — not a literal paste of US marketing:

备忘录提及 vs 协作备忘录 @提及 vs @提及

US pages use "Mention in Notes", "@mention", "Notify collaborators", or "Mention someone in a note". China storefront copy often uses 备忘录提及 for system Mention in Notes parity, 协作备忘录 @提及 when marketing shared-note collaboration, or shorter @提及 / 艾特 in subtitles and keyword rows — depending on whether you mean Apple Notes mention parity, team @handle autocomplete, or generic notify-when-mentioned workflows. AppLocale aligns phrasing with your actual mention scope.

@mention autocomplete vs collaborator notification

Screenshot galleries often label two distinct surfaces: the @mention autocomplete picker (输入 @ 提及协作者) and the collaborator-notified badge after a mention (已通知协作者). These signal Mention Notes collaboration — different from Quick Note corner swipe, Pinned Notes pin icons, Shared with You shelves, or Messages chat threads as the lead. Match the mention model your English listing and screenshots actually show.

@mentions vs notebook organization

Some apps market both folders and @mentions in shared notes. Listing copy on this page should lead with mention benefit — @mention collaborators and notify teammates — not notebook hub vocabulary unless your hero frames show folder trees instead of @mention UI. See Notes listing guide when notebooks and tags are the lead story.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need mention search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 备忘录提及, 协作备忘录, and @提及 each signal different intent from generic 备忘录 or 信息 keywords.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Mention in Notes" headlines on gallery frames — 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.

What good zh-Hans Mention Notes listing copy looks like

@mention copy appears on screenshot galleries and in description skims. Strong Chinese strings lead with the collaboration benefit and state scope plainly — paste-ready examples for Connect fields:

• Subtitle (example) — 共享备忘录 @提及，协作者即时收到通知 — @mention notification benefit within the ~30-character cap
• Keywords (example) — 备忘录提及,协作备忘录,@提及,共享笔记 — only when accurate to your feature set
• Screenshot overlay (example) — 输入 @ 提及协作者，对方立即收到通知 — Mention in Notes frame with clear benefit line
• Description paragraph (example) — plain zh-Hans list of mention workflows you ship — @mention autocomplete in shared notes, collaborator notifications, jump-to-mention deep links, sync mentions across devices — matching what you actually implemented
• Honest scope — do not claim "replace Apple Notes" in Chinese if your app only markets local @mention sorting inside your own shared-note model

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

Why machine-translated Mention Notes copy fails

• Literal "Mention in Notes" → awkward 在笔记中提到 instead of commerce-idiomatic 备忘录提及 or @提及协作者
• Generic "@mention" → untranslated Latin @mention with no Chinese benefit line beside it
• English badge headlines preserved on zh-Hans screenshots — "Mention in Notes" with no 协作备忘录 @提及 context
• Overlay text overflow — long English mention captions pasted into short screenshot callout zones truncate on device
• Conflating 备忘录提及 with 置顶笔记 — buyers searching for @mentions may not match Pinned Notes pin-to-top keywords
• Leading with 与你共享 or Messages chat terms when the screenshot shows @mention autocomplete inside a note — Shared with You or Messages vocabulary for a Mention in Notes workflow
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention @mentions

Machine translation is fine for internal drafts. Finished mention strings need idiomatic zh-Hans that states what @mention workflows you ship — while keeping accurate scope. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

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 @mentions ("Mention in Notes", "@mention", "Notify collaborators", "Mention someone", "@mentions in shared notes", collaborator notification captions)
• Brief note on which mention workflows your app supports today — @mention autocomplete, collaborator notifications, jump-to-mention links, shared-note permissions, cross-device mention sync — so zh-Hans copy stays accurate
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a mention 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 Mention Notes 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 @mention reliability or collaborator notification delivery improves — listing rewrite describes what you already ship
• No Notes.framework, CloudKit shared-note sync, or @mention UI engineering
• No building a Notes clone, iCloud Notes sync implementation, or custom keyboard
• No screenshot design, PNG re-export, binary localization, or Connect configuration on your behalf
• No claim that your app replaces Apple Notes or system Mention in Notes unless your English listing already states that accurately — and even then, AppLocale does not certify system-Notes parity
• No guaranteed App Store ranking, keyword position, download growth, or mention sync certification outcomes
• No fabricated social proof, review quotes, ratings, or traffic numbers
• No Apple Search Ads management or review-reply retainers
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

Does AppLocale implement Notes.framework or @mention notification logic?

No. We deliver Connect listing metadata copy only — name, subtitle, keywords, description, promotional text when included, and screenshot caption lines. Notes.framework, CloudKit shared-note sync, @mention parsing, and collaborator notification engineering are outside scope.

How is Mention Notes listing copy different from Notes hub, Pinned Notes, Quick Note, Shared with You, or Messages?

Mention Notes listing copy covers @mention collaborators inside shared notes, Mention in Notes, notify teammates when mentioned, 备忘录提及, and 协作备忘录 @提及 — @mentions as the lead. Notes hub listing copy covers organized notebooks, folders, tags, sticky notes, and locked notes. Pinned Notes listing copy covers pin-to-top sorting. Quick Note listing copy covers corner-swipe capture. Shared with You listing copy covers Messages-originated For You shelves. Messages listing copy covers chat threads and iMessage. Those are separate scopes with different screenshot vocabulary.

Should my zh-Hans listing claim to replace Apple Notes or system Mention in Notes?

Only if your app actually provides that capability and your English listing already states it accurately. AppLocale rewrites from your source claims — we do not invent system-replacement promises or certify parity with Apple's Notes app.

What do I send after AppLocale payment?

Your live App Store listing URL, current English listing copy, screenshot overlay lines that mention @mentions (with frame order noted), which mention workflows your app supports, and target locale (zh-Hans). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.

Does localizing my listing change in-app @mention or collaborator notification behavior?

No. Mention parsing, shared-note sync, and notification delivery come from your binary — not Connect listing fields. AppLocale covers product-page marketing copy only.

Will zh-Hans Mention Notes copy 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 @mention 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 Notes.framework or CloudKit engineering, not a Notes clone or custom keyboard, not Notes hub notebook listing copy as the lead, not Pinned Notes pin-to-top listing copy, not Quick Note capture listing copy, not Journal or Freeform listing copy, not Shared with You or Messages chat listing copy as the lead, not Math Notes or Writing Tools listing copy, 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 — zh-Hans listing copy for Mention Notes & @mention apps

$79 one-time

Buy on Stripe

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.

AppLocale product page