The review and release process of the mini program

The review and release process for WeChat Mini Programs involves multiple stages, requiring strict review mechanisms from code submission to final launch. Developers must familiarize themselves with the details of each step to ensure compliance with platform standards and avoid review failures or delays due to violations.

Pre-Submission Preparation

Before submitting for review, developers must complete the following key steps:

1. Code Integrity Check: Ensure all functional modules are fully developed, with no missing pages or features. For example:

   // Verify all pages are registered in app.json
   {
     "pages": [
       "pages/index/index",
       "pages/detail/detail",
       "pages/user/user"
     ]
   }
   

2. Testing Phase:

   • Test all core functionalities on real devices
   • Cover mainstream device models (iOS/Android)
   • Network environment testing (2G/4G/WiFi)

3. Sensitive Content Handling:

   • Remove test data
   • Check for prohibited content
   • Ensure sensitive features like payments and social interactions comply with guidelines

Detailed Submission Steps

Submit via the WeChat Developer Tools:

1. Click the "Upload" button in the toolbar
2. Fill in version information (recommended to use semantic versioning, e.g., 1.0.0)
3. Add project notes (specify changes made in this update)

# Example: Submission via CLI tool
$ miniprogram-ci upload --pp ./demo --pkp ./private.key -v 1.1.0 -d "Fixed payment API bug"

Key points for review information:

• Functional descriptions must be specific (avoid vague terms like "optimized experience")
• Special permissions require usage scenarios
• Test accounts must be valid (include test data)

Review Stage Details

The WeChat team typically completes reviews within 1-7 working days, focusing on:

Content Review

• Presence of politically sensitive content
• Filtering mechanisms for user-generated content (UGC)
• Compliance with "WeChat Advertising Guidelines"

Functional Review

• Payment features must use WeChat Pay
• Social categories require special qualifications
• Live streaming requires "Information Network Audiovisual Program Transmission License"

Technical Review

• Detection of malicious code
• API call frequency limits
• Performance metrics (launch time should not exceed 2 seconds)

Common rejection reasons:

1. "Actual functionality does not match description" (32%)
2. "User experience issues" (28%)
3. "Incorrect category selection" (19%)

Handling Review Results

After receiving the review outcome:

Approval:

• Immediate release: Visible to all users
• Phased release: Gradual rollout (20%/50%/100%)
• Delayed release: Set a specific launch time

Rejection:

1. Review specific rejection reasons
2. Resubmit after modifications (expedited processing available)
3. Prepare supplementary materials for appeals if needed

// Example: Handling review callback
wx.onAuditDone(res => {
  if(res.success) {
    console.log('Review passed, version:', res.version) 
  } else {
    console.error('Rejection reason:', res.reason)
  }
})

Version Release and Management

Post-release management strategies:

1. Phased Rollout:

   • Release in batches based on user attributes
   • Can be terminated at any time

2. Hotfixes:

   • Use wx.getUpdateManager for silent updates

   const updateManager = wx.getUpdateManager()
   updateManager.onCheckForUpdate(res => {
     if (res.hasUpdate) {
       updateManager.applyUpdate()
     }
   })
   

3. Version Rollback:

   • Maintain at least two stable versions
   • Rollback takes effect immediately (within 5 minutes)

Long-Term Maintenance Recommendations

Establish version control mechanisms:

• Use Git for code versioning
• Each submission corresponds to a review version
• Preserve review history records

Monitoring metrics:

• Crash rate (should be <0.5%)
• API success rate (should be >99.5%)
• User complaint rate (industry average: 0.3%)

| Metric         | Alert Threshold | Check Frequency |
|----------------|-----------------|------------------|
| Crash Rate     | >1%             | Real-time        |
| API Failure Rate| >5%             | Hourly           |
| Payment Success Rate| <85%      | Daily            |