Chinese vendor browsers

Chinese vendor browsers are the Android browsers that mainland Chinese users run by default, and they are not the browsers compatibility tables are written for. Huawei, Xiaomi and OPPO ship their own Chromium-based browsers, UC Browser and QQ Browser ship their own kernels (U4 and X5), and a large share of web traffic opens inside the WeChat in-app WebView (XWeb). None of them appears in browser-compat-data, so this matrix is built from vendor documentation alone, row by row, for four behaviours: install to home screen, standalone display, service worker, and Web Push.

Browser & ecosystem support

• Legend
• Yes
• Partial
• Flag
• No
• Unknown

Browser / Platform	Support	Versions	Confidence	Source	Notes
HarmonyOS Browser · install to home screen	Unknown	—	low	source	1
HarmonyOS Browser · standalone display	Unknown	—	low	source	2
HarmonyOS Browser · service worker	Unknown	—	low	source	3
HarmonyOS Browser · Web Push	Unknown	—	low	source	4
Mi Browser · install to home screen	Unknown	—	low	source	5
Mi Browser · standalone display	Unknown	—	low	source	6
Mi Browser · service worker	Unknown	—	low	source	7
Mi Browser · Web Push	Unknown	—	low	source	8
ColorOS Browser · install to home screen	Unknown	—	low	source	9
ColorOS Browser · standalone display	Unknown	—	low	source	10
ColorOS Browser · service worker	Unknown	—	low	source	11
ColorOS Browser · Web Push	Unknown	—	low	source	12
UC Browser · install to home screen	Yes	U4 2.0 (Chromium 57)	low	source	13
UC Browser · standalone display	Unknown	—	low	source	14
UC Browser · service worker	Yes	U4 2.0 (Chromium 57)	low	source	15
UC Browser · Web Push	Unknown	—	low	source	16
QQ Browser · install to home screen	Unknown	—	low	source	17
QQ Browser · standalone display	Unknown	—	low	source	18
QQ Browser · service worker	Yes	—	low	source	19
QQ Browser · Web Push	Unknown	—	low	source	20
WeChat WebView (XWeb) · install to home screen	Unknown	—	low	source	21
WeChat WebView (XWeb) · standalone display	Unknown	—	low	source	22
WeChat WebView (XWeb) · service worker	Unknown	—	low	source	23
WeChat WebView (XWeb) · Web Push	Unknown	—	low	source	24

1. No Huawei documentation found (checked 2026-10-03) stating whether Huawei Browser offers a manifest-based install or `beforeinstallprompt`. Huawei's developer documentation covers ArkWeb, the HarmonyOS web component, which it describes as Chromium M114-based; that documents the component, not the browser's install behaviour.
2. No Huawei documentation found (checked 2026-10-03) on whether a home-screen web app launches in `standalone` display mode or as a browser tab.
3. No Huawei documentation found (checked 2026-10-03) stating that Huawei Browser exposes `navigator.serviceWorker` to third-party pages. The ArkWeb component is documented as Chromium M114-based and as supporting standard W3C APIs by default, which is suggestive but is not a statement about the browser.
4. No Huawei documentation found (checked 2026-10-03) for W3C Web Push (`PushManager`, VAPID) in Huawei Browser. Huawei's documented push path for the web is its own Push Kit service, which is not the Push API.
5. No current Xiaomi documentation found (checked 2026-10-03). Xiaomi's MIUI 9 Global Beta 8.6.14 changelog (2018-06) announced Progressive Web Apps support in Mi Browser with an Apps section listing installed PWAs, but the forum thread is no longer online and no HyperOS-era statement replaces it, so the row stays unknown.
6. No Xiaomi documentation found (checked 2026-10-03) on the display mode of a home-screen web app in Mi Browser.
7. No Xiaomi documentation found (checked 2026-10-03) stating service worker availability in Mi Browser. The Xiaomi HyperOS developer documentation covers quick apps and quick games, not the browser's web platform.
8. No Xiaomi documentation found (checked 2026-10-03) for the Push API in Mi Browser.
9. No OPPO documentation found (checked 2026-10-03). The OPPO open platform documents app-store, quick-app and push SDK integration, not the browser (`HeyTapBrowser`) web platform; its user-facing menu offers a web shortcut, which is not a manifest install.
10. No OPPO documentation found (checked 2026-10-03) on display modes for home-screen web apps.
11. No OPPO documentation found (checked 2026-10-03) stating service worker availability in the ColorOS browser.
12. No OPPO documentation found (checked 2026-10-03) for the Push API in the ColorOS browser; OPPO's documented push channel is its native push SDK.
13. UC's U4 kernel blog (2018-10-26) documents launching a PWA from the home screen (`display: fullscreen`) and states U4 2.0 is Chromium 57 and U4 3.0 Chromium 69. UC's kernel team described the add-to-home-screen conditions (HTTPS, manifest, registered service worker, engagement heuristic) in a 2018 InfoQ interview (https://www.infoq.cn/article/2018/05/practice-influence-pwa-uc-ali). No newer UC statement was found.
14. UC documents only `display: fullscreen` for home-screen launches (U4 kernel blog, 2018-10-26); no UC statement on `standalone` or `minimal-ui` was found (checked 2026-10-03).
15. UC's U4 kernel blog (2018-10-26) documents service worker features of the Chromium 58–69 range (navigation preload, `Clear-Site-Data` covering service workers) as part of the U4 2.0 → 3.0 upgrade; the U4 developer platform advertises full PWA support. The kernel team confirmed service worker support in the 2018 InfoQ interview.
16. UC's 2017-10 U4 2.0 launch coverage claimed a standard web push service for mainland users, but the kernel team's 2018 InfoQ interview listed service worker push among features still needing shell adaptation, and the U4 kernel blog does not mention push. With no vendor document stating the behaviour (checked 2026-10-03), the row stays unknown.
17. Tencent's X5/TBS documentation, which covers the kernel QQ Browser ships, has no page on manifest install or `beforeinstallprompt` (checked 2026-10-03).
18. No Tencent documentation found (checked 2026-10-03) on display modes for home-screen web apps in QQ Browser.
19. Tencent's X5/TBS product documentation has a Service Worker page with a registration walkthrough; it requires HTTPS and gives no kernel version, so `version_added` is left empty rather than invented.
20. No Tencent documentation found (checked 2026-10-03) for the Push API in QQ Browser.
21. WeChat's open-community documentation describes XWeb as a Chromium-based in-app kernel (Chromium 78, 86, 107, 111, 116, 122, 138 and a 142 developer build), detectable by `XWEB/` in the user agent, and notes some devices fall back to the system WebView. It documents no install surface for third-party web pages (checked 2026-10-03).
22. No WeChat documentation found (checked 2026-10-03) on display modes; pages opened in WeChat render inside the WeChat title bar, and the documentation describes no standalone launch for web pages.
23. WeChat's XWeb announcements (Chromium 111 rollout; Chromium 142 developer build, production on Chromium 138) say the kernel upgrades affect third-party web page rendering, but no WeChat document states whether `navigator.serviceWorker` is exposed to third-party pages (checked 2026-10-03).
24. No WeChat documentation found (checked 2026-10-03) for the Push API or notification permission in XWeb; WeChat's documented messaging channels for web content are official-account template and subscription messages, not the Push API.

Source data: /compatibility/cn-vendor-browsers.json · Global usage: 1 % (StatCounter 2026-05)

Source: editorial · Last verified 2026-10-03 · Confidence: low (computed from sources)

How to read the unknowns

A row is unknown when no vendor document states the behaviour, and its note says where we looked. That is most of the table on 2026-10-03. Huawei’s developer documentation covers ArkWeb, the HarmonyOS web component (documented as Chromium M114-based), not Huawei Browser’s install or push policy. Xiaomi’s HyperOS documentation covers quick apps, not Mi Browser. OPPO’s open platform covers store, quick-app and push SDK integration, not HeyTapBrowser. Tencent’s X5/TBS documentation has a Service Worker page and nothing on install or push. WeChat documents XWeb’s Chromium lineage (78 → 142) and that kernel upgrades affect third-party pages, but says nothing about service workers, installs or notifications for those pages.

The two yes rows for UC Browser come from UC’s own U4 kernel blog (2018-10-26), which places U4 2.0 on Chromium 57 and U4 3.0 on Chromium 69 and documents home-screen launch and service worker features; the kernel team’s 2018 InfoQ interview states the add-to-home-screen conditions. No newer UC statement was found, so treat the version as the floor, not the current state.

What the vendors do document is a different push path: Huawei Push Kit, OPPO’s push SDK and WeChat’s template and subscription messages, none of which is the W3C Push API. A PWA that needs re-engagement in this market plans for that rather than for PushManager.

See also

• By country / region: reach for mainland China is weighted by StatCounter browser share, where these browsers sit inside the “other” and Chrome-UA buckets.
• Web Push and Service Worker: the BCD-backed matrices for the engines these browsers derive from.
• Tested evidence welcome: a display-mode media query result or a navigator.serviceWorker check from a named browser version turns an unknown into a sourced row. Use the report link in the footer.

← Back to the Compatibility explorer.