Building a Mini-Program Operation Tool with Cloud Development: Maoyan's Practice

This article shares how Maoyan Entertainment built a mini-program operation management tool called "Tangtu" using WeChat Mini Program Cloud Development. The background describes their challenge: during the Chinese New Year, operations team needed to reuse a Qixi Festival photo activity, but the one-time development couldn't support reuse, requiring significant modifications for the new holiday.

The traditional approach involves PM, backend, and frontend collaboration to define configurable items, develop backend interfaces, and integrate with frontend templates. However, this approach has problems including unclear responsibilities, complex environment coordination, and significant debugging time.

The team explored two alternatives: frontend using Node.js for self-provided interfaces, and Mini Program Cloud Development (serverless). Cloud Development provides three core features: Storage (with CDN acceleration), Database (MongoDB-based JSON storage), and Cloud Functions (Node.js logic execution without server maintenance).

They developed the "Tangtu" tool enabling operations/PM to independently create, edit, and publish activities through visual editing. The system stores activity templates in the cloud database, allowing new activity types to be added by uploading JSON configuration without code changes. The architecture separates the editing interface (for operations) from the mini-program display, using activity IDs to dynamically render activities from templates.

Key technical solutions include: storing the same data in both development and production environments for testing, using short IDs in mini-program code to bypass the 32-character parameter limit, and setting storage permissions to public for permanent URLs.

Results: The tool launched before Chinese New Year, supporting 8 activity types while reducing manpower from 3 people to 1. Development time and costs were significantly reduced, and operations teams gained autonomy to configure and launch activities independently.

Lessons learned: Always explicitly specify environment variables in cloud functions (database and storage environments may differ), and note that complex transaction operations and migrating existing MySQL-based services to cloud development remain challenging.