NameDrop App Store Listing in Simplified Chinese — Contact Exchange, 名片投送 & 轻碰传联系人 zh-Hans Copy
Your iOS or iPadOS app markets Apple NameDrop on the product page — Share contact with NameDrop, Exchange contact info, Bring iPhones together, Contact poster, or frames that show two devices glowing as contact cards swap — and the US listing looks polished.
Open the same app on the China storefront and buyers still land on an English product page.
Title, subtitle, description, and screenshot overlays that read "NameDrop", "Share contact with NameDrop", "Exchange contact info", or "Tap iPhones together" in Latin script.
Shipping NameDrop or proximity contact-exchange 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 — not Nearby Interaction code, not MultipeerConnectivity wiring, not Contacts framework engineering.
Operator guidance only — no ranking guarantee, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS and iPadOS developers — US, UK, EU, Canada, Australia — who:
Ship an app that markets NameDrop or proximity contact exchange as a buyer-facing feature — networking apps, business-card scanners, CRM lead capture, team directories, or dating apps that showcase tap-two-phones-to-share contact cards
Finished the en-US listing — name, subtitle, keywords, description, and NameDrop-oriented screenshot captions — and passed US App Review
Already support NameDrop, Contact poster, or complementary contact-exchange flows in the app (not looking for Nearby Interaction or Contacts API engineering help)
Enabled the China storefront but the zh-Hans product page still shows English copy or untranslated NameDrop badge lines on screenshots
Need paste-ready zh-Hans listing fields — not an engineer for proximity sessions, not a designer to re-render screenshot PNGs, not contact-database consulting
NameDrop engineering vs zh-Hans listing copy — two different jobs
Teams assume Apple's NameDrop rollout covers storefront language. iOS, system frameworks, and Connect actually separate proximity contact behavior from product-page copy:
NameDrop & Contact poster — system feature that lets two iPhones or Apple Watches exchange contact cards when brought together. Controls in-device contact sharing — not App Store language.
Nearby Interaction & proximity APIs — frameworks some apps use for device-to-device ranging and tap-to-connect UX. Your listing may mention tap-to-exchange; building proximity sessions is engineering work, not Connect metadata.
MultipeerConnectivity & Bonjour — custom peer-discovery and P2P transfer stacks. Separate from the zh-Hans description paragraph that explains contact exchange to buyers.
CNContactStore & ContactsUI — address-book read and write APIs when a exchanged card lands in Contacts. Configuring contact persistence is engineering — AppLocale does not touch it.
AirDrop settings & Bring Devices Together — system toggle under Settings → General → AirDrop that enables NameDrop. Your listing may reference the feature; toggling portal settings is outside AppLocale scope.
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 NameDrop support in the binary.
A working NameDrop or contact-exchange story and a localized China listing are both required when you sell on the China storefront — neither replaces the other.
NameDrop listing copy vs AirDrop vs Add to Contacts vs SharePlay
US/EU indie teams often conflate four proximity-and-sharing string families. This page covers product-page listing copy that markets NameDrop contact-card exchange as the hero feature — not file transfer, manual contact save, or group media sync:
NameDrop & contact exchange marketing — paragraphs and frame text explaining "NameDrop", "Share contact with NameDrop", "Exchange contact info", "Bring iPhones together", "Contact poster", 名片投送, 轻碰传联系人, and 姓名投送. This page.
AirDrop file-transfer listing copy — Send with AirDrop, wireless file send, 隔空投送, and 附近分享 for documents and media. Covered on our AirDrop guide — nearby file send, not contact-card swap.
Add to Contacts listing copy — Add to Contacts, Save contact, New contact, and address-book import from forms or scans. Covered on our Add to Contacts guide — manual save flows, not proximity NameDrop.
SharePlay listing copy — synchronized FaceTime sessions, group watch-and-listen, and shared playback overlays. Covered on our SharePlay guide — not tap-to-exchange contact cards.
You can localize the app name and still leave every NameDrop screenshot overlay and description paragraph English-only. Buyers then see a Chinese title with English "Share contact with NameDrop" badges — a mismatch that reads like half-finished localization. See also China App Store still shows English when entire rows fall back.
What China buyers see when zh-Hans NameDrop copy is missing
Networking-conscious purchasers browsing the China App Store evaluate contact-exchange trust in the first scroll. Common failure modes when only en-US is filled:
English title and subtitle — app name and tagline still Latin script while competitors show native Chinese networking positioning
Untranslated NameDrop badges on screenshots — overlay lines like "NameDrop", "Share contact with NameDrop", "Exchange contact info", "Bring iPhones together", or "Contact poster" remain English on zh-Hans gallery frames
Contact-exchange value in English — description opens with US NameDrop marketing ("Tap iPhones together to swap contacts") that China readers skim past or misread
Keyword field still en-US — buyers search 名片投送, 轻碰传联系人, 姓名投送, or 交换联系人; an English-only keyword row misses China Search intent
Mixed page — Chinese description pasted once but screenshot captions and subtitle still English — reads unfinished next to localized competitors
Confused with AirDrop file send — description mentions 隔空投送 for documents when screenshots actually show NameDrop contact posters — a vocabulary mismatch that erodes trust
Formal machine translation — stiff 翻译腔 for Apple's NameDrop feature instead of the phrasing Chinese storefront readers expect (名片投送, 轻碰传联系人)
Better zh-Hans listing copy helps networking-aware buyers understand contact-exchange benefits before install. It does not replace NameDrop engineering, proximity API integration, or Apple's review decisions.
NameDrop-specific listing copy — what translates differently
Contact-exchange listings use vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese App Store readers describe Apple's NameDrop feature — not a literal paste of US marketing:
NameDrop phrasing
US pages use "NameDrop", "Share contact with NameDrop", "Exchange contact info", or "Bring iPhones together." Apple's official Simplified Chinese support vocabulary uses 名片投送 for the system feature. Chinese tech coverage and buyer search also use 轻碰传联系人 and 姓名投送 for proximity contact sharing. AppLocale aligns phrasing with Apple's consumer-facing terms while keeping your app's voice — not inventing NameDrop capabilities your app does not support.
Share vs Receive only
Screenshot overlays differ by exchange mode — mutual share-and-receive, receive-only at events, or share a specific phone number or email from your contact poster. Chinese buyers expect concise action labels: 共享联系人 for share, 仅接收 for receive only, 交换名片 for mutual exchange. Mixing English "Receive only" with Chinese body copy on the same frame looks inconsistent.
Contact poster vs contact card
iOS 17+ Contact poster and photo-and-poster UI appear on many NameDrop marketing screenshots. zh-Hans overlays may use 联系人海报 or 我的名片 where it matches your frames — distinct from generic Add to Contacts save flows covered on the Add to Contacts guide.
Do not conflate with AirDrop file send
NameDrop is part of the AirDrop family in Settings, but listing copy for contact exchange should not reuse Send with AirDrop file-transfer paragraphs meant for 隔空投送 document send. If your app does both, scope each screenshot frame accurately — contact poster glow on one frame, file send on another.
Subtitle and keyword packing
The 30-character subtitle and 100-character keyword field need contact-exchange search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 名片投送, 轻碰传联系人, 交换联系人, and 姓名投送 each signal different intent from AirDrop file-transfer or Add to Contacts keywords.
Common mistakes on NameDrop zh-Hans listings
Assuming NameDrop integration localizes automatically — proximity flow shipped; zh-Hans row never added or left blank
Only translating the description — subtitle, keywords, and screenshot caption lines still English
Reusing US NameDrop badges verbatim — Latin "Share contact with NameDrop" badges on zh-Hans screenshots signal an unfinished localization
Cloning AirDrop file-transfer copy — 隔空投送 paragraphs pasted where NameDrop contact-poster marketing belongs; see AirDrop listing (zh-Hans) for file-send scope
Cloning Add to Contacts copy — Save contact and New contact language where the hero story is tap-two-phones NameDrop; see Add to Contacts listing (zh-Hans)
Conflating listing copy with setup instructions — description explains how to enable Bring Devices Together in Settings instead of what the buyer gets; setup instructions belong in support docs, not AppLocale scope
Translating the in-app permission string only — system NameDrop sheet may show Chinese from iOS while the App Store product page stays English
Expecting AppLocale to implement Nearby Interaction or CNContactStore — proximity APIs, MultipeerConnectivity, and address-book write logic are outside listing rewrite
Connect checklist before you order NameDrop listing copy
Confirm China under Pricing and Availability — storefront enabled if you intend to sell there
Confirm NameDrop or contact-exchange features work in your build — note that we do not change proximity APIs, Contacts entitlements, or portal settings for you
Open App Store → Chinese (Simplified) — note whether the zh-Hans row exists and which text fields are empty vs English placeholder
Export English NameDrop marketing copy — current en-US title, subtitle, keywords, description, promotional text, and every screenshot overlay line ("NameDrop", "Share contact with NameDrop", "Exchange contact info", "Bring iPhones together", "Contact poster", "Share my contact card", "Receive only")
Count screenshot frames — note how many iPhone (and iPad or Apple Watch if universal) slots show NameDrop UI, contact posters, or proximity-exchange badges
Separate listing from in-app UI — listing rewrite does not cover storyboard strings or NameDrop prompt labels inside the binary
Note share mode if marketed — mutual exchange, receive-only, or share a specific field — so zh-Hans copy stays accurate
Plan caption re-export if text is burned into PNGs — Connect caption fields help when overlays are editable; English baked into image files needs design rework outside AppLocale
For one NameDrop-marketing app on the zh-Hans row, paste-ready Simplified Chinese copy for the listing fields you specify:
Title (name) — zh-Hans app name within Connect character limits
Subtitle — contact-exchange or NameDrop phrasing within the ~30-character cap
Keywords — comma-separated zh-Hans search terms with rationale notes (名片投送, 轻碰传联系人, 姓名投送 where relevant)
Description — buyer-readable body copy aligned with your English NameDrop listing meaning
Promotional text — when you include the 170-character promo field in scope
Screenshot overlay / caption lines — zh-Hans replacements for "NameDrop", "Share contact with NameDrop", "Exchange contact info", "Bring iPhones together", "Contact poster", 名片投送, 轻碰传联系人, 姓名投送, and similar frame text
English alignment — matching en-US field notes when both storefronts must stay consistent on contact-exchange promises
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite from your current English NameDrop marketing listing — not a machine translation dump. Default $79 scope is Connect listing metadata; bundle IAP display names or promotional-only passes via the AppLocale product page if needed.
What AppLocale does not do
Does not implement NameDrop, Nearby Interaction, or MultipeerConnectivity flows
Does not write CNContactStore, ContactsUI, or address-book sync integration code
Does not configure AirDrop file-transfer or Bonjour peer-sharing SDKs — see AirDrop listing (zh-Hans) for file-send copy scope
Does not engineer Wallet passes, SharePlay, Continuity Camera, Live Text, AirPrint, Clipboard, Split View, or Drag and drop — separate shop guides cover those listing angles
Does not write Spotlight, Genmoji, Writing Tools, Journaling Suggestions, Camera Control, Math Notes, Passkeys, Face ID, Action Button, or broader Apple Intelligence listing copy — dedicated pages cover those scopes
Does not design, compose, or re-export screenshot PNG/JPEG assets — caption line sheets only
Does not localize in-app UI strings, storyboards, or the app binary
Does not manage Apple Search Ads, ad campaigns, or monetization strategy
Does not guarantee App Store rankings, NameDrop adoption, or download growth in China
Does not operate review-reply retainers or respond to App Store reviews on your behalf
Does not click Save or Submit in App Store Connect for you
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — NameDrop app with en-US listing done; identify which zh-Hans fields and screenshot caption lines are still English
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, English NameDrop marketing copy (all fields and caption lines), screenshot frame count, and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans listing fields arrive at your Stripe receipt email
Paste and submit — fill the zh-Hans row in Connect, enter caption lines per screenshot slot, save, and submit the version for review
Does shipping NameDrop support auto-translate my China listing?
No. NameDrop proximity flows, Nearby Interaction hooks, and contact-exchange UI control in-app behavior — they do not create or fill a Simplified Chinese localization row. Empty or English zh-Hans fields mean China buyers see en-US fallback.
What listing fields does AppLocale rewrite for NameDrop 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 — rewritten from your English NameDrop marketing originals.
Can AppLocale implement NameDrop or configure Nearby Interaction?
No. We deliver listing metadata copy only. NameDrop engineering, Nearby Interaction wiring, MultipeerConnectivity setup, CNContactStore integration, and Contact poster UI are outside AppLocale scope.
How is this different from the AirDrop or Add to Contacts pages?
AirDrop copy markets wireless file send — 隔空投送 and Send with AirDrop. Add to Contacts copy markets manual save-to-address-book flows. This page is NameDrop as the product-page theme: tap two iPhones together to exchange contact cards.
Why do screenshot captions still say "Share contact with NameDrop" in English on China?
Caption and overlay fields are managed per localization. If you filled en-US screenshot text but never saved zh-Hans caption lines — or uploaded the same English-overlay PNGs to the Chinese set — China buyers see Latin NameDrop badges on the product page.
Should zh-Hans copy use 名片投送, 轻碰传联系人, or 姓名投送?
Apple's official materials use 名片投送 for NameDrop. Buyers also search 轻碰传联系人 and 姓名投送. AppLocale picks phrasing that matches your English listing claims and screenshot overlays — without inventing capabilities your app does not support.
What do I send after AppLocale payment?
Your live App Store listing URL, current English NameDrop marketing listing (title, subtitle, keywords, description, promo if used, all screenshot caption lines), screenshot frame counts, and target locale (zh-Hans). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Will localized NameDrop listing copy improve Search ranking in China?
We do not guarantee keyword position, chart rank, or install growth. Complete zh-Hans metadata helps networking-aware buyers who already found your page understand contact-exchange benefits in their language.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not NameDrop or Nearby Interaction engineering, not Contacts API implementation, not AirDrop file-transfer engineering, not Wallet passes, SharePlay, Continuity Camera, Live Text, AirPrint, Clipboard, Split View, Drag and drop, Spotlight, Genmoji, Writing Tools, Journaling Suggestions, Camera Control, Math Notes, Passkeys, Face ID, Action Button, or broader Apple Intelligence listing copy, not screenshot design, not binary or in-app localization, not ads management, not ranking guarantees, not review-reply retainers, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans NameDrop listing copy for the China storefront
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English NameDrop listing copy. No ranking guarantees. Sold by Fortune Insight, LLC.