How Weex Revolutionized OTT Front‑End Performance at Alibaba Entertainment
This article examines Alibaba Entertainment's three‑stage evolution of OTT front‑end technology—from early WebView implementations through a custom Blitz engine to the current Weex (RAX) solution—detailing implementation steps, performance‑boosting techniques, and measurable results that cut page load times by over 50%.
Development History
Alibaba Entertainment pursued ever‑better user experiences across PC, mobile, and OTT platforms. On OTT, they progressed through three phases:
WebView period : Activities were rendered with native WebView. Performance was barely acceptable, and weak OTT hardware plus limited video playback extensions constrained capabilities.
Custom engine (Blitz) period : Blitz acted like a WebView‑style rendering engine. Although heavy on early manpower, development stalled after business shifts, leaving key performance needs—such as local caching and zcache integration—unmet. Various optimizations (delayed page display, 1%‑resolution blur background, async JS, lazy image loading, pre‑loading) were tried but yielded minimal gains.
Weex period : Leveraging Alibaba’s broader Weex rollout, the OTT front‑end adopted Weex (RAX) as its main technology stack, delivering client‑like fluidity and significantly improving page smoothness compared with pure HTML5.
Weex Implementation Plan
1. Implementation Steps
Enable visual construction of Weex output (the existing ARK platform only supported H5). Package Weex components, converting over 40 H5 components to Weex, covering roughly 80% of business scenarios.
Develop custom Weex source code for the remaining 20% of specialized cases (e.g., large‑scale events like Double‑11), shifting development from H5 to the Weex stack.
2. Technical Details
Address OTT‑specific differences: remove JScore (OTT only runs Android), integrate a focus engine for remote‑control navigation, and create custom components.
Visual construction transformation plan (see image).
3. Related Data
Key metrics: page load improvement, smoother rendering, overall user‑experience enhancement.
4. Effect Demonstration
Full‑screen Weex pages
Half‑screen interactive sections
App‑like page experiences
Co‑creation
Through collaborative effort, the upgraded Weex stack became the primary front‑end technology for Alibaba Entertainment’s OTT products. Compared with the previous HTML5 stack, Weex delivers markedly higher stability and performance; average page load time decreased by more than 50% after migration.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.