Points of divergence from international platform conventions

What it is

International platform convention treats the OS as the only host: apps install from a store, identity follows an Apple ID or Google account, and navigation follows iOS or Android. Mainland users also live in a second host—WeChat, Alipay, Douyin and other super-apps that supply discovery, identity, relationships, and some of the chrome themselves. The same service therefore has two doors: an icon on the system home screen, and search, official accounts, scan, and chat inside the super-app. The difference is not a few icons drawn differently. It is which layer users treat as the default operating system for “opening a service.”

QR as the primary deep link, completing booking and support inside a chat thread, and searching the super-app instead of the store are surface symptoms of that dual-host structure. Structures trained only on Human Interface Guidelines or Material miss the doors and habits the second host already occupies.

Why it happens

Dual hosting stacks two shells. The system still has a status bar, gestures, and back; the super-app adds its own navigation bar, capsule, tab bar, and message inbox. Back therefore includes an extra expectation: leave the guest, then leave the host. Discovery splits as well. International convention says “not installed → go to the store.” Mainland convention says “search the super-app first; only then consider installing a standalone app.” QR codes turn posters, objects, and table stickers into launchers; universal links are often the second choice.

The chat thread becomes a service desk because the relationship graph and payment already live in the host. International convention puts support in an in-app ticket or email; Mainland convention puts support in a session, with progress as bubbles on a private timeline. Those two timelines—system notifications and chat messages—compete for the same “something changed” channel. An app that only ships system notifications is, for super-app users, a service with no status.

Where it stops holding

Products shipping only outside Mainland China are not in this dual-host world; international discovery and sign-in are the right default, and bolting on QR and official accounts produces empty chrome. Standalone specialist apps (camera, notes, pro tools) that never enter a super-app shrink the difference back to iOS / Android / HarmonyOS at the system layer. Older users and civic services may live inside one super-app and almost never use the system home screen; the international desktop-icon path is not their door. Workplace hosts (WeCom, DingTalk) add a third layer; the consumer super-app entry model must not be copied into work.

Applying it

• Draw an entry map that lists both the system home screen and the super-app (search, scan, official / life accounts, chat cards), and mark which path is primary for the target user, rather than designing only the post-install home.
• Reserve space and back hierarchy for the second host: guest back returns into the host, and does not swipe the user out to the system desktop in one motion.
• Mirror status onto both system notifications and host conversations, so progress is not visible to only one population.
• Verify with people who use the service only through WeChat or Alipay and have never installed the standalone app: note where they enter, where they go back, and where they check progress. Any step that “requires a download to start” or that surfaces progress only in system notifications is an international single-host assumption leaking into a dual-host environment. Then walk someone who only uses the standalone app, and confirm the host door was not made the only door.

Related

• Same group: R4.04.1 Distributed continuation across devices · R4.04.2 Constraints of mini-programs inside super-apps · R4.04.4 Multi-end deployment requires layout by capability, not screen name · R4.04.5 Service cards surface functions at the desktop layer · R4.04.6 System-owned identity and payment change flow boundaries
• Adjacent: R4.01 Apple Platform Conventions · R4.02 Material Design Conventions · R4.06 Platform convention versus brand consistency
• Search terms: super-app · dual host · QR entry · chat as service