App & mini program delivery: WeChat mini program development

Context: This write-up is for colleagues progressing mini program or app work. The client is in beauty & wellness, roughly a hundred-person team, based around capital business districts. QA walked the main path three times on real devices and flagged edge cases around in-store appointment booking. Archive screenshots and config change IDs for this in-store appointment booking round so next month's retrospective stays concrete.

Delivery Approach

Last week we reviewed loyalty points rules with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around loyalty points rules. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed canary release with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around canary release. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling.

Risks & Mitigations

Last week we reviewed mini program order flow with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around mini program order flow. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed WeChat mini program development with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but WeChat mini program development still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions. The same requirement can sound different across departments; writing it down helps align decisions on push notification strategy. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to push notification strategy first. Next, we recommend to log API status codes and latency. If more features are added, scope the blast radius before scheduling.

Testing & Acceptance

Last week we reviewed subscription messaging reach with the client's IT lead. They care more about stability than buzzwords. We hit a case of mini program review rejected. Troubleshooting started with logs on enterprise chat, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed privacy consent dialogs with the client's IT lead. They care more about stability than buzzwords. We hit a case of holiday traffic spikes slowing the site. Troubleshooting started with logs on Git, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed QR code redemption with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but QR code redemption still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on multi-store accounts. Editors know the CMS well enough, but multi-store accounts still needs a one-page rule sheet to cut verbal rework. Prefer a go-live window outside peak traffic, and prepare the rollback package early.