Hy Hybrid Mobile Framework: Architecture, Philosophy, and Evolution at Qunar

With the surge of mobile usage, the demand for iOS and Android apps has grown rapidly, but pure native development incurs high costs and slow iteration; Qunar therefore introduced the Hy hybrid solution to achieve faster, lower‑cost cross‑platform mobile development.

Hybrid development combines the speed of Web apps with the full functionality of native apps, allowing real‑time updates, cross‑platform code reuse, and native API access, thus overcoming the slow development, release, and update cycles of pure native approaches.

After launching the first independent Hy app (CRM) in early 2015, Qunar released Hy 1.0 and later evolved to Hy 2.0, rebuilt on React to provide better tooling, documentation, and statistical support.

Hy’s philosophy is not to replace Web or Native but to fuse their strengths: Web gains native capabilities via APIs (e.g., Cordova), while Native benefits from Web’s rapid publishing and collaborative advantages, creating a harmonious development path.

In practice, Hy offers extensive platform adaptation (iOS, Android, WeChat, Touch), an offline resource update mechanism, and a unified API layer that lets developers choose the most suitable parts for their projects.

The framework addresses platform fragmentation by standardizing UI rendering, handling high‑DPI issues, and providing consistent rich interactions and offline experiences across devices.

Hy 2.0 follows a progressive, component‑and‑plugin architecture divided into five layers: Yo (frontend styles, components, routing), HySDK (adaptation layer for client environments), Hytive (custom WebView with native APIs), offline package & hot‑update system, and Ykit toolset; developers can adopt any subset as needed.

Compared with Qunar’s React‑Native based QRN framework, Hy and QRN are complementary yet competitive: QRN excels in data‑heavy, image‑rich scenarios, while Hy shines in pure presentation cases, and both teams share insights to improve performance and user experience.

Ultimately, Hy is presented as a pragmatic, progressive solution that enables rapid development, high‑frequency iteration, and reduced costs without aiming to be a universal “silver bullet,” but rather to empower teams to choose the best tool for each mobile challenge.