Cross‑Platform Development of JD Mini‑Program for Fast Delivery: Background, Action, Research, Progress, and Planning

This report details JD's mini‑program cross‑platform initiative for the Fast Delivery service, covering background, actions taken, research findings, progress achieved, planning considerations, risk mitigation, and expected benefits such as reduced cost, improved stability, and higher development efficiency.

JD Retail Technology
JD Retail Technology
JD Retail Technology
Cross‑Platform Development of JD Mini‑Program for Fast Delivery: Background, Action, Research, Progress, and Planning

Preface: JD Mini‑Program Open Platform provides rich capabilities for lightweight, personalized applications, enabling developers to develop, debug, preview, and release mini‑programs across multiple channels.

Background: Fast Delivery (Kuaisong) includes 7 mini‑program channels, 2 apps, PC, H5, and an Open Platform, totaling 15 endpoints. Traditional independent development per endpoint leads to high cost and inconsistent experience; cross‑platform aims to improve efficiency and reduce R&D cost.

2019 cross‑platform solution: a self‑developed compilation tool unified 7 mini‑programs into one codebase.

App cross‑platform exploration: evaluated H5 (low cost, poor experience) and Flutter (high cost, full rewrite). Adopted H5 for non‑core pages.

Action: Investigated JD Group’s cross‑platform solutions (Mcube, JDFlutter, JDHybrid, JD Mini‑Program). Determined JD Mini‑Program best fits Kuaisong due to existing platform and map performance.

Research: three parts – usage analysis of JD Mini‑Program across business lines, demo performance testing (including map), and online stability testing via “price detail” page. Results showed sub‑second launch, native‑like map interaction, and degradation rate reduced to 0.3%.

Progress: Completed integration and achieved degradation <1% without affecting conversion rates on order detail page (four core actions).

Planning: Identify modules suitable for mini‑program cross‑platform based on compliance, iteration frequency, and closed‑loop processes. Expected benefits: 80% code reuse across three terminals saving 2 HC, stability improvement (issue resolution from 14 to 1 day), efficiency gain (feature verification time reduced by 58%).

Risks: Compliance changes may affect mini‑program usage; fallback to native app for critical functions.

Attachments: include charts and screenshots.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

risk managementDeploymentJDmini-program
JD Retail Technology
Written by

JD Retail Technology

Official platform of JD Retail Technology, delivering insightful R&D news and a deep look into the lives and work of technologists.

0 followers
Reader feedback

How this landed with the community

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.