Mobile Development 12 min read

Hybrid App Development: Strategies and Framework Comparisons for Mobile and PC

The article reviews hybrid app development strategies by comparing mobile frameworks such as React Native, Weex and Flutter with PC solutions like Chrome‑based H5, Electron and Qt + CEF, and illustrates a staged migration case study of Taobao Live’s client—from pure Qt to Qt + CEF and finally to Electron + Node—to shorten cycles, simplify third‑party integration, and leverage Chromium’s capabilities.

DaTaobao Tech
DaTaobao Tech
DaTaobao Tech
Hybrid App Development: Strategies and Framework Comparisons for Mobile and PC

Hybrid applications aim to combine the excellent interaction experience of native apps with the cross‑platform development advantages of web apps, enabling efficient business iteration in the current Internet era.

hybrid 英 [ˈhaɪbrɪd] 美 [ˈhaɪbrɪd] adj. 混合的;杂种的 n. 杂种;杂种动物;杂交植物;(不同事物的)混合物,合成物 复数:hybrids 派生词:hybrid adj.

For mobile hybrid development, open‑source frameworks such as React Native, Weex and Flutter are commonly used. A comparison table shows their supported platforms, implementation technologies, engines, programming languages, framework weight, and community activity.

On the PC side, common hybrid solutions include Chrome (H5), Electron (Node + H5) and Qt + CEF/Qt. Their supported platforms, underlying technologies, engines, and community status are compared in a similar table.

The article presents a concrete case: the Taobao Live PC client. Early versions were built with OBS Studio (Qt‑based UI, C‑based audio/video core). The architecture evolved from pure Qt native to Qt + CEF and finally to Electron + Node, aiming to reduce development cycles, improve third‑party integration, and enable rapid feature iteration via web containers.

Key challenges identified are long development cycles with pure C++/Qt, frequent release pressure, and difficulty for third‑party teams lacking C++ expertise. The proposed solution is a staged migration: Qt → Qt + CEF → Electron + Node, providing a containerized front‑end while retaining native performance where needed.

CEF was chosen because it is based on Chromium, has an active community, offers Chrome‑level compatibility, rich APIs (off‑screen rendering, request interception, cookie injection, etc.), and eases cross‑platform updates.

Implementation details include a multi‑layer window hierarchy (browser main window, native C++ rendering windows, and pop‑up windows), handling of dynamic library loading paths, and the directory structure of the Electron + Node client.

Current status: the new framework has been gradually rolled out for the Taobao Live client. Upcoming work includes expanding low‑level capabilities (e.g., clean stream recording), optimizing rendering pipelines, extending business plugins, and strengthening development and testing infrastructure.

The team behind the project consists of engineers from backend, client, multimedia, and XR domains, focusing on large‑scale e‑commerce live streaming and continuous technical innovation.

Fluttercross‑platformHybrid AppElectronCEFQtReact Native
DaTaobao Tech
Written by

DaTaobao Tech

Official account of DaTaobao Technology

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.