Implementing a Mobile App Continuous Delivery Platform to Boost Release Efficiency at New Oriental

1 Background

As the New Oriental APP team grew, rapid requirement iteration, many participants, and multiple concurrent versions created challenges for fast continuous integration and quality assurance. The team needed to improve both efficiency and quality control, prompting the development of a new APP continuous‑delivery platform.

2 Problems

Before the platform, releasing a new APP version involved manual steps: confirming version numbers, editing them, triggering Jenkins builds, uploading packages to fir.im or sharing via IM, and performing additional hardening, security scans, and store uploads for Android. This caused chaotic management, excessive manual intervention, difficulty tracing versions, costly external distribution, and low automation in testing.

3 Solution

After researching solutions from companies like Ctrip, Meituan, and ByteDance, the team redesigned the release workflow and built an internal mobile delivery platform. The new process provides online version requests, standardized management, cost‑effective test‑package distribution, traceable build‑version links, and a one‑stop release operation that eliminates cross‑system steps.

4 Implementation Technology

4.1 System Architecture

The project follows a front‑back separation architecture: the front end uses Vue ElementUI, the back end combines Python Flask and Java SpringBoot, builds are driven by shell scripts, MySQL stores data, and Redis provides caching.

4.2 Implementation Process

The platform links version request, compilation, automated testing, security hardening, scanning, release management, and installation into a streamlined pipeline.

4.3 Feature Demonstration

1) When adding a new version, the system automatically generates and maintains the version name after the type is selected.

2) During testing, build history, linked defect records, and requirement tasks are recorded.

3) After a successful test, the platform can directly perform package hardening, security scanning, and publishing.

5 Current Usage

After more than a month of trial, bug fixing, and polishing, the system is now stably used by the DEV, QA, and PM teams for daily APP releases, significantly reducing communication overhead and increasing release efficiency.

6 Future Considerations

The next step is to increase automated testing coverage, integrating stability and UI compatibility tests into the existing version‑management and device‑management system, so that each code commit undergoes full compile, static analysis, testing, packaging, and deployment, embodying true CI/CD.

7 Acknowledgements

The project was co‑developed by QA members of the R&D‑2 and R&D‑1 teams, with contributions from teachers Xinwu, Xiaopeng, and guidance from front‑end experts Yunan and Changzhou, as well as feedback from the APP development team.

8 End‑note

During development, the team also referenced mature APP security solutions, detailed in the article “APP Automated Hardening + Security Scanning” .