XView Popup Framework: Background, Pain Points, Upgrade Solutions, Architecture, and Future Plans

Background: XView is a transparent plastic‑bag‑like container built on a generic WebView framework, used for marketing pop‑ups such as large‑scale promotions.

Pain points: low development efficiency (requires front‑end, client SDK integration, server configuration, and release cycles) and low exposure due to a long loading process.

Upgrade roadmap: three eras – 1) client H5 popup component era (only H5 links, slow loading); 2) configurable popup era (supports images, GIF, video, Lottie, fast 2‑hour delivery, but complex); 3) visual construction era (native rendering, higher exposure, richer trigger scenarios).

Upgrade scheme covers build process, mutual‑exclusion management, pre‑load upgrades, page management, and low‑cost integration.

Build process: four stages – CMS drag‑and‑drop construction generating a JSON schema, conversion to DSL, publishing to OSS, and client rendering via a flexible SDK.

Mutual‑exclusion: defines priority and group rules to prevent simultaneous pop‑ups.

Pre‑load upgrades: from manual pre‑load in the H5 era to automated multi‑type pre‑load in the visual era, improving success rate and startup performance.

Page management: supports native pages, H5 pages, RN pages, Tongtian‑Tower pages, Flutter pages, and dynamic pages.

Integration: low‑cost SDK integration across various technology stacks.

Post‑upgrade framework consists of external dependencies, CMS backend, CMS construction engine, and client side, each handling data processing, low‑code generation, permission management, media asset handling, and rendering.

Data center provides real‑time statistics such as total exposures, close‑clicks, element clicks, click‑through rate, exposure rate, and visual dashboards.

Current status: over ten business lines are powered, production time reduced to under half an hour; future plans focus on technical empowerment and business value by lowering learning cost, expanding native rendering, enabling self‑service deployment, and adding richer interaction triggers.