First safe move
Start here: Make mobile data work before the first airport-to-hotel transfer.
Phone and apps
In short
Prepare maps, translation, messaging, wallet/payment, and mobile data first. Add ride-hailing or rail tools only after the basics work.
Behind this answer
Official source: People's Bank of China — Guide to Payment Services in China (2024 edition, page updated May 25, 2024; read July 24, 2026)
Operator source: Airalo
Operator source: Apple — Use eSIM while traveling internationally with your iPhone (read July 24, 2026)
Editorial check
Phone, eSIM, maps, and app answers were reviewed with the current connectivity comparison and setup guidance.
Current app availability, phone number requirements, language support, and account verification flows. Provider plans, device compatibility, app availability, roaming behavior, and network routing can change before departure.
Recovery template
Start with the immediate move, keep a human or offline fallback, and only rely on live rules after checking the official operator, provider, or source.
Use app setup checklistFirst safe move
Start here: Make mobile data work before the first airport-to-hotel transfer.
Fallback path
Use saved offline hotel details, home-SIM SMS or roaming, hotel Wi-Fi, provider support, and screenshots until mobile data is stable again.
Do not assume
Do not treat this answer as final live proof. Do not use as proof of current network access, app availability, provider routing, or device compatibility without checking the live provider and device state.
Source boundary
Current app availability, phone number requirements, language support, and account verification flows.
Action path
A practical answer should leave the traveler with a few moves they can actually make before the trip or at the point of friction.
Make mobile data work before the first airport-to-hotel transfer.
Save hotel, route, and support details offline.
Treat map, message, and translation apps as dependencies, not decorations.
Official source
These facts are read straight from the operator's own page, so you can check each one at the source rather than take it on our word.
The phone number or ID number an app asks for at sign-up is a duty the regulator puts on the app, not a product choice
Where an app provides users with information-publishing, instant-messaging and similar services, its provider is required to authenticate the real identity of each registering user by mobile phone number, identity-document number, unified social credit code or a comparable method — and where a user does not provide real identity information, or registers falsely using another person's or organisation's identity, the provider must not provide the relevant service. That is the sourced answer to the question this page's readers actually hit at the door: the identity gate is a legal authentication duty on that class of service, so expecting to skip it is not an option any individual app controls. Note the qualifier — the clause names providers of information-publishing and instant-messaging and similar services, and does not itemise where maps or translation fall.
Where in the source: Article 6 (第六条): “应用程序提供者为用户提供信息发布、即时通讯等服务的,应当对申请注册的用户进行基于移动电话号码、身份证件号码或者统一社会信用代码等方式的真实身份信息认证。用户不提供真实身份信息,或者冒用组织机构、他人身份信息进行虚假注册的,不得为其提供相关服务。”
“Agree to everything or you cannot use it” has a stated legal limit
App providers must handle personal information lawfully, properly, only as necessary and in good faith, for an explicit and reasonable purpose with published handling rules, within the rules on the scope of necessary personal information; they must not compel a user by any reason to agree to personal-information handling, and must not refuse a user the app's basic functions and services because the user declines to provide personal information that is not necessary. For a traveller doing a pre-departure pass over app setup, this is the most usable line in the instrument: declining information that is not necessary is not supposed to cost you the basic service.
Where in the source: Article 12 (第十二条): “应用程序提供者处理个人信息应当遵循合法、正当、必要和诚信原则,具有明确、合理的目的并公开处理规则,遵守必要个人信息范围的有关规定,规范个人信息处理活动,采取必要措施保障个人信息安全,不得以任何理由强制要求用户同意个人信息处理行为,不得因用户不同意提供非必要个人信息,而拒绝用户使用其基本功能服务。”
App stores verify the developer, not you — and that is why the provider's name is published on the listing
An app distribution platform is required to use composite verification to authenticate the real identity of each provider applying to list an app, again by mobile phone number, identity-document number or unified social credit code in combination, and to publish the provider's name and unified social credit code according to the provider's type of legal entity so the public can look it up. The platform itself must file with the provincial-level cyberspace authority where it is located within thirty days of going live, and the national authority publishes the list of platforms that have filed. So the publisher name shown on a listing is a checkable artefact of a verification duty — which is the one thing a reader can actually verify before installing. This clause authenticates the app's provider (the developer); authenticating the user is the separate duty in Article 6 above, and the two are not the same check.
Where in the source: Article 19 (第十九条): “应用程序分发平台应当采取复合验证等措施,对申请上架的应用程序提供者进行基于移动电话号码、身份证件号码或者统一社会信用代码等多种方式相结合的真实身份信息认证。根据应用程序提供者的不同主体性质,公示提供者名称、统一社会信用代码等信息,方便社会监督查询。” Article 17 (第十七条): “应用程序分发平台应当在上线运营三十日内向所在地省、自治区、直辖市网信部门备案……国家网信部门及时公布已经履行备案手续的应用程序分发平台名单。”
The instrument defines which apps and which services it covers — mini-programs included
“Mobile internet application” is defined as application software running on a mobile smart terminal that provides information services to users. Application information services are listed by type as instant messaging, news and information, knowledge Q&A, forums and communities, live streaming, e-commerce, online audio and video, and daily-life services; distribution services are listed as app stores, quick-app centres, internet mini-program platforms and browser plug-in platforms. For a page about what to have ready before arrival, the material part is that mini-program platforms sit inside the same regime as app stores. Whether maps or translation tools fall inside Article 6's “and similar services” is not itemised anywhere in the instrument, so this layer does not sort them either way.
Where in the source: Article 26 (第二十六条): “本规定所称移动互联网应用程序,是指运行在移动智能终端上向用户提供信息服务的应用软件。” Article 2, second and third paragraphs (第二条): “即时通讯、新闻资讯、知识问答、论坛社区、网络直播、电子商务、网络音视频、生活服务等类型” / “应用商店、快应用中心、互联网小程序平台、浏览器插件平台等类型”
Source: Cyberspace Administration of China (国家互联网信息办公室), official full text on its own site (www.cac.gov.cn) — 移动互联网应用程序信息服务管理规定 (Provisions on the Administration of Mobile Internet Application Information Services) (source the page carries no decree number and no publication-date field; the two checkable time points are Article 27, which puts the provisions in force from 2022-08-01 and repeals the same-named 2016 provisions, and the page path dated 2022-06/14; read October 17, 2026)
What this source does not settle: This layer publishes only what the Cyberspace Administration's own provisions say about the registration gate: that providers of information-publishing, instant-messaging and similar services owe a real-identity authentication duty and must refuse service where real identity is not given, that a user who declines personal information which is not necessary must not be denied the app's basic functions, that distribution platforms authenticate the provider and publish its name, and how the instrument defines the apps, service types and distribution platforms it governs. Four things it deliberately does not do. First, reachability: nothing here states which apps work, load or connect from inside China — no official page publishes such a list, so this page's existing statement that reachability has no source and should be read as field notes stands exactly as written, and the silence here is not evidence either way. Second, it records no workaround for an app that does not load, the same boundary the Google Maps and WhatsApp pages hold. Third, Article 6's duty is not all apps: the clause is limited to providers of information-publishing, instant-messaging and similar services, the instrument does not itemise what else falls inside “and similar services”, and nothing here may be read as “every app in China requires real-name registration”. Fourth, the provider authentication in Article 19 is a check on the developer, not on you, and must not be blended with the user authentication in Article 6. SIM-card real-name registration is a different instrument on a different subject and belongs to the pages that source it; the municipal QR-payment guidance belongs to the page that sources it; neither clause number is republished here. The page's ordering advice — which apps to set up first, and which ones to leave until the basics work — remains this desk's operational judgement, not cited fact. No penalty provision is published, and nothing here predicts whether any individual registration, verification or install will succeed.
Answer hub
Cluster pages help travelers move through related questions without losing the thread.
Related guides
Use these pages when the traveler needs the longer context, product path, or supporting decision.
Related questions
These questions share the same travel problem and help you move sideways without restarting.
Next move
Read enough to make the decision smaller, then open the checklist, search a specific question, choose a setup tool, or share the page with the person planning with you.
Use the checklist when the question has shifted from research to preparation.
Search by the actual problem: Alipay, eSIM, transit visa, first transfer, vegetarian food, or a city name.
Open recommendations when the task is clear enough for a short list to be useful.