RTT & TTY Call Accessibility App Store Listing in Simplified Chinese — Real-Time Text, TTY & 实时文本 zh-Hans Copy
Your iOS or iPadOS app already sells phone call text accessibility — Apple RTT, Real-Time Text, TTY, software TTY, hardware TTY, or typed text relay during carrier phone calls with Settings → Accessibility → RTT/TTY (or Hearing → RTT/TTY on some OS versions) — and your en-US product page shows RTT call panels, TTY mode toggles, Send as Text walkthroughs, or 实时文本 / RTT / TTY / 电话实时文本 callouts on gallery frames.
Open the same app on the China storefront and buyers still land on an English product page: name, subtitle, keywords, description, and screenshot captions that read "RTT", "Real-Time Text", "TTY", or "Send as Text" in Latin script.
Shipping RTT-friendly call UX or TTY companion workflows 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 how your app actually markets RTT and TTY call accessibility, without conflating real-time text on phone calls with Live Caption media subtitles, Live Speech type-to-speak, Voice Control spoken commands, Hearing Devices pairing, Call Recording, Live Voicemail transcription, Silence Unknown Callers, Hold Assist, Dwell Control pointer dwell, or generic Accessibility hub bullet lists.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS and iPadOS developers — US, UK, EU, Canada, Australia — who:
Already ship or market an app whose buyers use RTT or TTY during phone calls — RTT setup walkthroughs, Real-Time Text call panels, TTY mode toggles, software TTY keyboards, hardware TTY connection demos, Send as Text badges, or Settings → Accessibility → RTT/TTY framing on screenshots
Market RTT, Real-Time Text, TTY, software TTY, hardware TTY, or 实时文本 / RTT / TTY / 电话实时文本 / 听障通话辅助 on the en-US product page and in screenshot galleries
Finished RTT/TTY call accessibility or phone text-relay workflows in the binary — not looking for CallKit RTT routing, TTY hardware firmware, or in-call text relay UI engineering help here
Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on RTT/TTY gallery frames
Need paste-ready Connect text — not an engineer for carrier RTT relay, not a designer to re-export every screenshot from scratch
RTT/TTY engineering vs zh-Hans listing copy — two different jobs
Teams assume RTT or TTY capability in the binary covers storefront language. iOS, carriers, and Connect actually separate real-time text on phone calls from product-page copy:
RTT relay & carrier routing — system and carrier integration that routes Real-Time Text during PSTN phone calls. Controls whether buyers can type and read text on an active call. Does not generate Chinese listing text.
TTY mode & hardware TTY pairing — software TTY keyboards, hardware TTY device connection, and TTY relay settings under Settings → Accessibility → RTT/TTY. Separate from the zh-Hans description paragraph that explains RTT/TTY call accessibility value to buyers.
In-call text relay UI — engineering work for Send as Text panels, RTT conversation threads, and TTY character entry during calls. Listing copy should match what your gallery shows — an RTT call panel is not a Live Caption subtitle bar unless that is what the screenshot depicts.
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 RTT/TTY support in the app.
Working RTT/TTY call 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 RTT, Real-Time Text, TTY, and phone call text accessibility on the product page in zh-Hans, not how you implement CallKit RTT routing, TTY hardware pairing, or carrier relay configuration.
The RTT/TTY family on one product page — four related workflows
Hearing and speech accessibility apps often mention one or more RTT/TTY workflows on the same US product page. AppLocale covers all four on this single guide — paste-ready zh-Hans copy for whichever your screenshots and description already claim:
RTT / Real-Time Text during phone calls (实时文本 / RTT) — typed text sent and received in real time on an active carrier phone call. Gallery frames may show RTT call panels, Send as Text buttons, or "Turn on RTT" badges.
Software TTY mode (软件 TTY) — on-screen TTY keyboard and character entry when hardware TTY is not connected. Marketing frames may show software TTY setup, TTY mode toggles, or TTY relay walkthroughs.
Hardware TTY connection (硬件 TTY) — pairing external TTY devices for phone call text relay. Screenshot overlays often show hardware TTY connection demos, TTY device photos, or "Connect your TTY" walkthroughs.
RTT/TTY settings & call accessibility setup (RTT/TTY 设置) — Settings → Accessibility → RTT/TTY (or Hearing → RTT/TTY) onboarding, carrier RTT availability, and Send Message with RTT toggles. Gallery frames may show RTT/TTY settings sheets or works-with-RTT badges when your English listing already claims them.
Your gallery may lead with an RTT call panel on one frame and a TTY settings walkthrough on the next. zh-Hans caption lines should name the correct workflow per frame — an RTT conversation thread is not a Live Caption media subtitle bar, and a TTY mode toggle is not Live Voicemail transcription unless that is what the screenshot shows.
RTT listing copy is not Live Caption, Live Speech, Voice Control, or other accessibility surfaces
Hearing, speech, and call-accessibility apps blur several surfaces indie teams conflate. AppLocale covers listing metadata only — RTT and TTY phone call accessibility marketing on the product page:
RTT & TTY call accessibility (this page) — RTT, Real-Time Text, TTY, software TTY, hardware TTY, Send as Text during phone calls, and 实时文本 / RTT / TTY / 电话实时文本 / 听障通话辅助 on gallery frames and in description paragraphs.
Live Caption & on-device media captions (different) — live captions, real-time subtitles, 实时字幕 for media, apps, or heard audio playback — not carrier RTT on PSTN phone calls. See Live Caption listing guide — Live Caption displays captions for heard audio; RTT sends typed text during an active phone call.
Voice Control & spoken commands (different) — hands-free UI operation with spoken tap and swipe commands. See Voice Control listing guide — Voice Control uses voice; RTT uses typed text on phone calls.
AssistiveTouch & floating assistive menu (different) — on-screen floating home button and virtual pointer. See AssistiveTouch listing guide — not RTT/TTY call panels.
FaceTime-only marketing (different unless your English listing already shows RTT on FaceTime) — this page leads on RTT/TTY phone call accessibility under Settings → Accessibility → RTT/TTY. Do not reframe RTT as a FaceTime-only feature unless your US listing and screenshots already claim RTT on FaceTime calls.
Accessibility hub multi-feature dump (different) — Settings → Accessibility home grids that list many assistive features as one bullet list. See Accessibility hub listing guide — hub marketing covers several surfaces together; this page covers RTT and TTY call accessibility claims in depth.
Your screenshots may show multiple surfaces in one gallery. Listing copy should name the correct one per frame — an RTT call text thread is not a Live Caption subtitle overlay, not a Live Speech speak-aloud panel, not a Live Voicemail transcription line, and not a Voice Control numbered overlay unless that is what the frame shows.
Apple system RTT/TTY vs your app's call text-relay marketing — listing honesty
Apple ships RTT and TTY in iOS and iPadOS under Settings → Accessibility → RTT/TTY (or Hearing → RTT/TTY on some OS versions) — letting users send and receive Real-Time Text during carrier phone calls for hearing or speech accessibility, with software TTY and hardware TTY options. Third-party apps may offer RTT-compatible call workflows, TTY companion tools, or phone text-relay UX your binary actually ships. AppLocale rewrites listing copy from what your US page already claims:
If your app complements iOS RTT/TTY — zh-Hans copy can describe works-with-RTT badges, TTY-friendly call UI, or phone text-relay companion workflows your binary actually ships without claiming to replace Settings → Accessibility → RTT/TTY unless your English listing already states that accurately.
If your app is a dedicated RTT/TTY or call accessibility product — description and screenshot overlays should name the workflows you ship (实时文本, RTT, TTY, 电话实时文本) in commerce-idiomatic Chinese, not generic "accessibility handles every call feature" overclaims.
If your US page shows software TTY and hardware TTY separately — zh-Hans copy should distinguish software TTY keyboards from hardware TTY connection demos when your screenshots show each — matching what buyers will see after install.
If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not invent broader RTT/TTY scope than your screenshots and description support.
Clear zh-Hans copy helps buyers understand whether your app supports RTT, Real-Time Text, TTY, or phone call text relay — before install. It does not replace CallKit RTT implementation, carrier relay configuration, or Apple's review decisions — and it does not certify hearing or speech accessibility outcomes in the app.
What China buyers see when zh-Hans RTT/TTY copy is missing
Call accessibility apps often lead marketing screenshots with RTT call panels, TTY mode toggles, Send as Text walkthroughs, software TTY keyboards, or hardware TTY connection demos — surfaces where English marketing text appears beside RTT/TTY UI:
Screenshot overlay badges — "RTT", "Real-Time Text", "TTY", "Software TTY", "Hardware TTY", "Send as Text", "Turn on RTT", "Works with RTT" on gallery frames
Description paragraphs — English value props about hearing accessibility, speech accessibility during calls, or TTY relay workflows that China readers skim past
Subtitle and keywords — English-only rows miss China Search intent for 实时文本, RTT, TTY, 电话实时文本, or 听障通话辅助 when buyers filter for call accessibility apps
Promotional text — 170-character field still pitching RTT or TTY in English above the description
Mixed page — Chinese description pasted once but RTT/TTY screenshot captions and subtitle still English — reads unfinished next to localized competitors
Formal machine translation — stiff 翻译腔 that conflates RTT (实时文本 on phone calls) with Live Caption (实时字幕 for media), or uses wrong TTY phrasing on store pages
Better zh-Hans listing copy helps hearing and speech accessibility buyers understand your RTT/TTY story before install. It does not replace CallKit RTT routing, TTY hardware integration, or Apple's review decisions — and it does not make medical or hearing-loss treatment claims.
What AppLocale delivers for RTT and TTY apps on zh-Hans
This SKU is a listing rewrite scoped to RTT and TTY call accessibility 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 RTT/TTY call accessibility to China searchers
Subtitle — concise benefit line that can reference RTT, Real-Time Text, or TTY without stuffing raw English badge text
Keywords — zh-Hans search terms buyers use for 实时文本, RTT, TTY, 电话实时文本, 听障通话辅助, and call accessibility apps in your category — within the 100-character keyword field cap
Description — long listing body with clear zh-Hans paragraphs on RTT/TTY workflows you already ship — without English-only "Real-Time Text" 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 RTT setup, Real-Time Text call panels, TTY mode toggles, software TTY keyboards, hardware TTY connection demos, or Send as Text walkthroughs
English alignment — matching en-US field notes when both storefronts must stay consistent on RTT/TTY promises
We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions RTT, Real-Time Text, TTY, software TTY, hardware TTY, or phone call text accessibility — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent RTT/TTY features your app does not ship.
RTT-specific listing vocabulary — what translates differently
RTT and TTY call accessibility marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe RTT/TTY workflows — not a literal paste of US marketing:
RTT vs Live Caption vs Live Speech
US pages use "RTT", "Real-Time Text", or "TTY." China storefront copy often uses 实时文本 for Real-Time Text on phone calls, keeps RTT and TTY as recognized acronyms when buyers search for them, or uses 电话实时文本 and 听障通话辅助 when your English listing already frames hearing/speech call accessibility that way — depending on whether you mean system RTT during carrier calls, in-app TTY companions, or call text-relay demos. AppLocale aligns phrasing with your actual scope and avoids conflating RTT with 实时字幕 (Live Caption media subtitles) or 实时语音 / 键入朗读 (Live Speech type-to-speak) when your screenshots show RTT call panels, not caption bars or speak-aloud keyboards.
Software TTY vs hardware TTY
Screenshot galleries may label software TTY keyboards separately from hardware TTY device pairing. Buyers searching for call accessibility apps distinguish on-screen TTY entry from external TTY hardware — match what your English listing and screenshots actually show.
RTT on phone calls vs Live Voicemail transcription
RTT sends typed text during an active phone call. Live Voicemail transcribes a message while the caller leaves voicemail — different buyer intent and screenshot vocabulary. Do not reuse Live Voicemail framing on RTT call thread frames unless that is what the screenshot depicts.
RTT vs Call Recording
Call Recording saves audio from answered calls. RTT relays typed characters in real time for accessibility — opposite marketing story from recording badges unless your English gallery explicitly shows both on separate frames.
Subtitle and keyword packing
The 30-character subtitle and 100-character keyword field need RTT/TTY search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 实时文本, RTT, TTY, and 电话实时文本 each signal different intent from Live Caption, Live Speech, or Hearing Devices keywords.
Caption lines vs burned-in badges
Marketing screenshot overlays you control — "RTT" or "Real-Time Text" 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.
Promotional text refreshes
RTT/TTY feature launches and carrier RTT availability 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 RTT/TTY pitch lives in promo text rather than the long description.
What good zh-Hans RTT/TTY listing copy looks like
Call accessibility copy appears on screenshot galleries and in description skims. Strong Chinese strings lead with the benefit and state scope plainly — paste-ready examples for Connect fields:
Subtitle (example) — 电话实时文本，听障通话更顺畅 — RTT call accessibility benefit within the ~30-character cap when accurate to your feature set
Keywords (example) — 实时文本,RTT,TTY,电话实时文本 — only when accurate to your feature set
Screenshot overlay (example) — 通话中发送实时文本 — RTT call panel frame with clear benefit line
Description paragraph (example) — plain zh-Hans list of RTT/TTY workflows you ship — Real-Time Text on phone calls, software TTY, hardware TTY connection, Send as Text during calls — matching what you actually implemented
Honest scope — do not claim full iOS RTT/TTY replacement in Chinese if your app only ships a limited TTY companion workflow
zh-Hans and en-US strings can differ in length and structure when the underlying RTT/TTY story is the same — avoid mirroring English comma-heavy promo lines character-for-character.
Why machine-translated RTT/TTY copy fails
Literal "Real-Time Text" → awkward phrasing instead of commerce-idiomatic 实时文本 or 电话实时文本
Conflating RTT with Live Caption — 实时文本 on phone calls is not 实时字幕 for media captions
Conflating RTT with Live Speech — typed text relay on PSTN calls is not 键入朗读 speak-aloud workflows
English badge headlines preserved on zh-Hans screenshots — "Real-Time Text" with no Chinese benefit line beside it
Overlay text overflow — long English RTT/TTY captions pasted into short screenshot callout zones truncate on device
Conflating TTY with generic "text messaging" — TTY is a teletype relay standard for phone call accessibility, not iMessage or SMS marketing
Conflating RTT call panels with Live Voicemail transcription lines — different screenshot vocabulary and buyer intent
Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention RTT, Real-Time Text, or TTY
Machine translation is fine for internal drafts. Finished RTT/TTY strings need idiomatic zh-Hans that states what call text-relay workflows you ship — while keeping accurate scope and not upgrading to Live Caption, Live Speech, or Call Recording claims. 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 RTT, Real-Time Text, TTY, software TTY, hardware TTY, Send as Text, or phone call text accessibility ("RTT", "Real-Time Text", "TTY", "Software TTY", "Hardware TTY", "Send as Text", "Turn on RTT")
Brief note on which RTT/TTY workflows your app ships today — Real-Time Text on phone calls, software TTY, hardware TTY, Send as Text during calls — so zh-Hans copy stays accurate
Target locales (e.g. zh-Hans for China storefront)
Your deadline if aligning with an RTT/TTY 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 RTT and TTY call accessibility 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 RTT relay reliability, TTY pairing, or call text delivery improves — listing rewrite describes what you already ship
No RTT, TTY, CallKit, or carrier relay engineering
No claim that your app replaces iOS Settings → Accessibility → RTT/TTY unless your English listing already states that accurately — and even then, AppLocale does not certify system parity
No guaranteed App Store ranking, keyword position, download growth, or hearing/speech accessibility 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 AppLocale implement RTT, TTY, or CallKit telephony APIs?
No. We deliver Connect listing metadata copy only — name, subtitle, keywords, description, promotional text when included, and screenshot caption lines. RTT/TTY OS integration, CallKit RTT routing, TTY hardware pairing, and in-call text relay UI engineering are outside scope.
How is RTT listing copy different from Live Caption or Live Speech?
RTT listing copy covers Real-Time Text and TTY during carrier phone calls — typed text relay for hearing and speech accessibility. Live Caption covers on-device captions for media and heard audio. Live Speech covers type-to-speak aloud in conversations. Those are different buyer stories with different screenshot vocabulary.
How is this different from Live Voicemail, Call Recording, or Silence Unknown Callers?
Live Voicemail covers voicemail transcription while a caller leaves a message. Call Recording covers recording answered calls. Silence Unknown Callers covers silencing unknown numbers. Hold Assist covers wait-on-hold automation. RTT covers typed text during an active phone call — a different framing on the product page.
How is RTT different from Hearing Devices, Voice Control, or Dwell Control?
Hearing Devices covers hearing-aid pairing and audio routing. Voice Control covers spoken UI commands. Dwell Control covers pointer-rest dwell-to-click timing. RTT covers real-time text on phone calls — different accessibility surface and keywords.
What do I send after AppLocale payment?
Your live App Store listing URL, current English listing copy, screenshot overlay lines that mention RTT, Real-Time Text, TTY, software TTY, or hardware TTY (with frame order noted), which RTT/TTY workflows your app ships, 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 RTT or TTY behavior on phone calls?
No. RTT relay routing, TTY mode toggles, and call text delivery come from iOS, your carrier, and your binary — not Connect listing fields. AppLocale covers product-page marketing copy only.
Will zh-Hans RTT/TTY 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 RTT and TTY call accessibility 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 RTT or TTY engineering, not Live Caption or Live Speech listing copy, not Voice Control or Hearing Devices listing copy, not Dwell Control, Pointer Control, or Switch Control listing copy, not Call Recording, Live Voicemail, Silence Unknown Callers, or Hold Assist listing copy, not FaceTime-only RTT marketing unless your English listing already shows that, not Accessibility hub multi-feature dump listing copy when that is the lead story, 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.
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.