Understanding Mobile Dynamic Solutions: Hybrid, React Native, and Web Approaches

Lin Yang is a senior engineer at YMFE, responsible for Qunar.com’s Hybrid (Hy) and React Native (QRN) mobile solutions, as well as a suite of Node‑based open‑source platforms and development tools, focusing on mobile front‑end engineering and process automation.

In recent years, the mobile internet has grown rapidly, bringing a flood of new technologies and ideas. Although mobile dynamic solutions have existed for many years, the landscape changes daily, prompting a fresh discussion of these approaches.

Foreword

Dynamic solutions in mobile development have sparked ongoing debate, especially after companies like Airbnb and Udacity abandoned React Native. Proponents praise rapid iteration and cross‑platform capabilities, while critics point to performance overhead and the challenges of smoothing platform differences. This article evaluates dynamic solutions from technical, architectural, and cost perspectives.

The Origin of Mobile Dynamic Solutions

The term “dynamic” dates back to the early days of the Internet, describing websites whose content and appearance change with server‑side updates. This dynamism became a hallmark of the web.

With the rise of mobile internet, native apps dominate, but they require users to download updates for any content change, incurring user cost and slowing iteration. Consequently, dynamic solutions that allow server‑driven updates without full app upgrades gained attention.

From early WebView‑based hybrids like PhoneGap and Titanium to modern React Native, Weex, and Flutter, many companies—including Qunar—have adopted these technologies. Over 90% of Qunar’s flight‑booking projects and many hotel‑booking flows now use React Native, with dozens of hybrid projects released daily.

Native Android supports dynamic delivery (e.g., Android App Bundles), while iOS is more restrictive, limiting the availability of universal dynamic frameworks.

Android App Bundles illustration:

Apple’s cautious stance protects users from malicious content changes, contributing to higher app‑store quality.

From Web to Mobile

Although dynamic concepts originated on the web, pure web apps face challenges on mobile devices due to historically low browser performance, fragmented kernels, and limited native APIs (e.g., payment, biometrics). These constraints make pure Web solutions less attractive for many business scenarios.

Efforts like AMP and PWA aim to bridge the gap, but adoption varies across platforms, and short‑term Web‑App environments remain difficult to achieve.

The Hybrid Path

Hybrid development combines WebView‑based UI with native capabilities, reducing the cost of maintaining separate codebases for each platform. The term “Hybrid” draws an analogy to hybrid‑electric vehicles, merging the strengths of both worlds.

Hybrid solutions fall into three categories:

Web‑based hybrids (e.g., Cordova, WeChat WebView, vendor‑specific hybrids).

Non‑Web UI but JavaScript‑driven logic (e.g., React Native, Weex, Flutter).

Web UI with separated logic layers, exemplified by mini‑programs that run UI in a dedicated WebView while business code executes in isolated JavaScript contexts.

The first type offers the lowest implementation cost but suffers from browser‑dependent performance. The second type, represented by React Native, delivers near‑native performance but incurs communication overhead between JavaScript and native modules. The third type provides dynamic UI updates but still faces the performance ceiling of Web rendering.

JSCore as the Core

Both Web‑UI and Native‑UI approaches rely on a single‑threaded JavaScript engine (JSCore) to run business logic. Isolating UI from business code improves performance and enables more aggressive dynamic updates.

JSCore functions like a headless browser without DOM/BOM, similar to a WebWorker, providing network, storage, and other native APIs.

Optimizations such as pre‑initializing JSCore or pre‑loading framework code can trade memory for faster startup.

Web Is Not Dead, PWA Moves Forward

Despite challenges, Web remains the most flexible, cross‑platform technology. Mini‑apps like rn‑web demonstrate that Web can coexist with native solutions, offering lower cost for short‑term projects and superior SEO.

Google’s PWA initiatives, along with growing support from Apple Safari and Microsoft Edge, are revitalizing Web‑App capabilities, making them viable alternatives for many use cases.

Looking Ahead

Dynamic solutions are popular but still face unresolved issues. Continuous experimentation will likely yield new approaches, and the goal remains to deliver better user experiences while enabling faster business iteration.

“The road ahead is long, but we will keep seeking.”