Chinese vendor browsers
Published Updated
Chinese phone makers and app vendors ship browsers including Huawei Browser, Mi Browser (Xiaomi), ColorOS Browser (OPPO), UC Browser on Alibaba’s U4
kernel, QQ Browser on Tencent’s X5 kernel, and the WeChat in-app WebView (XWeb). The
browser list of browser-compat-data includes none of them, so each row rests
on what the vendor itself has published, for four behaviours: install to home screen,
standalone display, service worker, and Web Push.
22 of the 24 cells in this matrix are unknown, because no vendor document states the behaviour; only 2 rest on a vendor document.
Most of these vendors document their own web components, quick apps and push services rather than these browser behaviours. The exception is UC: its kernel team said in a 2018 InfoQ interview that U4 2.0 (Chromium 57) supports PWA features at the kernel level, and that add to home screen and Web Push notifications need separate adaptation in the browser shell or the system. Tencent’s X5 Service Worker page carries no date, has an archived copy from April 2018 and now redirects to the X5 home page, so the QQ Browser row cites an archived copy from 2023-06-02. Read both as the state of those kernels at the time, not today.
Browser & ecosystem support
Section titled “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# | Unknown | — | 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 |
- No Huawei documentation found (checked 2026-10-03 and 2026-10-20) stating whether Huawei Browser offers a manifest-based install or `beforeinstallprompt`. Huawei's developer documentation covers ArkWeb, the HarmonyOS web component, and maps it to Chromium by system version (M114 for HarmonyOS 4.1 to 5.1, M132 by default for 6.0, M132 for 6.1, M144 by default for 7.0; ArkWeb overview, updated 2026-09-17). That documents the component, not the browser's install behaviour. Huawei's support pages for HarmonyOS 5.0 and later describe adding a page to the desktop from Huawei Browser as a shortcut, with no mention of a manifest.
- No Huawei documentation found (checked 2026-10-03 and 2026-10-20) on whether a home-screen web app launches in `standalone` display mode or as a browser tab.
- No Huawei documentation found (checked 2026-10-03 and 2026-10-20) stating that Huawei Browser exposes `navigator.serviceWorker` to third-party pages. ArkWeb's API reference gives apps that embed the component service worker hooks (`warmupServiceWorker`, `setServiceWorkerWebSchemeHandler`, API 12 and later; updated 2026-10-10), which is suggestive but is not a statement about the browser.
- No Huawei documentation found (checked 2026-10-03 and 2026-10-20) 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.
- 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.
- No Xiaomi documentation found (checked 2026-10-03) on the display mode of a home-screen web app in Mi Browser.
- 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.
- No Xiaomi documentation found (checked 2026-10-03) for the Push API in Mi Browser.
- 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.
- No OPPO documentation found (checked 2026-10-03) on display modes for home-screen web apps.
- No OPPO documentation found (checked 2026-10-03) stating service worker availability in the ColorOS browser.
- 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.
- Not documented as shipped (checked 2026-10-20). UC's U4 kernel blog (2018-10-26) mentions launching a home-screen web app with `display: fullscreen` only in its survey of Chromium 58–69 features, and says U4 3.0 (Chromium 69) was still in testing and staged rollout; it states U4 2.0 is Chromium 57 and U4 3.0 Chromium 69. In a 2018 InfoQ interview (https://www.infoq.cn/article/2018/05/practice-influence-pwa-uc-ali) UC's kernel team said add to home screen and Web Push notifications need separate adaptation in the browser shell or the system. Neither says UC Browser shipped an install path, so the row is unknown.
- 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).
- 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.
- 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.
- Tencent's X5/TBS documentation, which covers the kernel QQ Browser ships, has no page on manifest install or `beforeinstallprompt` (checked 2026-10-03 and 2026-10-20).
- No Tencent documentation found (checked 2026-10-03 and 2026-10-20) on display modes for home-screen web apps in QQ Browser.
- Tencent's X5/TBS product documentation had 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. The page is undated, has archived copies from 2018-04-09 and 2023-06-02, and by 2026-10-20 redirects to the X5 home page, so this rests on an archived copy.
- No Tencent documentation found (checked 2026-10-03 and 2026-10-20) for the Push API in QQ Browser.
- 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).
- 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.
- 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).
- 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.
Vendors checked
Section titled “Vendors checked”Public documentation checks are dated and cover the four behaviours. HarmonyOS NEXT has documentation for some products, as do Quark and Baidu, but Quark and Baidu lack vendor documents that establish a browser support status.
| Vendor | Sourced cells in the matrix | Documented | Not documented | Newest dated evidence | Pages checked |
|---|---|---|---|---|---|
| HarmonyOS NEXT (ArkWeb, Huawei Browser) | 0 / 4 | ArkWeb's Chromium version per system version (M114 for HarmonyOS 4.1 to 5.1, M132 by default for 6.0, M132 for 6.1, M144 by default for 7.0); service worker hooks for apps that embed ArkWeb (API 12 and later); a home-screen shortcut from Huawei Browser on HarmonyOS 5.0 and later. | Manifest install, standalone display and Web Push in Huawei Browser. | 2026-10-10 ArkWeb WebviewController reference | developer.huawei.com developer.huawei.com consumer.huawei.com checked 2026-10-20 |
| Mi Browser (Xiaomi) | 0 / 4 | Nothing current. A MIUI 9 Global Beta changelog announced PWA support in Mi Browser in 2018; that forum thread is offline. | All four behaviours. | 2018-06 MIUI 9 Global Beta 8.6.14 changelog | dev.mi.com checked 2026-10-03 |
| ColorOS Browser (OPPO) | 0 / 4 | Nothing on the browser. The open platform covers app-store, quick-app and push SDK integration. | All four behaviours. | no dated vendor document | open.oppomobile.com checked 2026-10-03 |
| UC Browser (Alibaba) | 1 / 4 | Service worker features of the U4 kernel (U4 2.0 on Chromium 57, U4 3.0 on Chromium 69). Home-screen launch appears only in its survey of Chromium 58–69 features; U4 3.0 (Chromium 69) was then still in testing. | A shipped install path, standalone display and Web Push. | 2018-10-26 U4 kernel blog | developers.uc.cn checked 2026-10-20 |
| QQ Browser (Tencent X5) | 1 / 4 | A Service Worker page in the X5/TBS product documentation. It is undated, has an archived copy from 2018, and now redirects to the X5 home page. | Manifest install, standalone display and Web Push. | 2023-06-02 last archived copy of the X5 Service Worker page (undated; also archived 2018-04-09) | x5.tencent.com web.archive.org checked 2026-10-20 |
| WeChat WebView (XWeb, Tencent) | 0 / 4 | XWeb's Chromium lineage (78 to a 142 developer build) and that kernel upgrades affect third-party pages. | Install, display mode, service worker and Web Push for third-party pages. | no dated vendor document | developers.weixin.qq.com developers.weixin.qq.com checked 2026-10-03 |
| Quark (Alibaba) | no rows (no vendor document) | No public documentation found as of 2026-10. Quark's help centre and release notes (newest entry 2026-09-07) name no engine and no web-app behaviour, and the developer platform requires a login. | All four behaviours. | no dated vendor document | quark.cn quark.cn open.quark.cn checked 2026-10-20 |
| Baidu (Baidu App, Baidu Browser) | no rows (no vendor document) | No public documentation found as of 2026-10. Baidu's developer portal covers no browser or engine, the smart-program web-view documentation covers only mini programs, and the Baidu Browser and Lavas sites did not respond. | All four behaviours. | no dated vendor document | developer.baidu.com smartprogram.baidu.com browser.baidu.com checked 2026-10-20 |
How to read the unknowns
Section titled “How to read the unknowns”A row is unknown when no vendor document states the behaviour, with the searched sources listed in its note. Huawei’s developer documentation covers
ArkWeb,
the HarmonyOS web component, and maps it to Chromium by system version (M114 for
HarmonyOS 4.1 to 5.1, M132 by default for 6.0, M132 for 6.1, M144 by default for 7.0), not Huawei
Browser’s install or push policy. Its support page for HarmonyOS 5.0 and later
describes adding a site to the desktop
from Huawei Browser as a shortcut and does not mention a manifest. Xiaomi’s
HyperOS documentation covers quick
apps, not Mi Browser. OPPO’s open platform
covers store, quick-app and push SDK integration, not HeyTapBrowser. 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 UC Browser service worker row rests on 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 on the kernel team’s statement in the same InfoQ interview that U4 2.0 supports PWA features at the kernel level. The UC install row is unknown: the same post mentions home-screen launch only in its survey of Chromium 58–69 features and says U4 3.0 (Chromium 69) was still in testing, and in the 2018 InfoQ interview the kernel team says add to home screen and Web Push need adaptation outside the kernel. No newer UC statement was found.
Huawei also documents its own push service, Huawei Push Kit, which is not the W3C Push API.
See also
Section titled “See also”- By country / region: reach there is weighted by browser family, and none of these browsers has a family of its own.
- Web Push and Service Worker: the BCD-backed matrices for the engines these browsers derive from.
← Back to the Compatibility explorer.