Legal Services mini program notes: WeChat mini program development

Context: This write-up is for colleagues progressing mini program or app work. The client is in automotive services, roughly about thirty people, based around economic development zones. Editors know the CMS well enough, but loyalty points rules 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.

Operations & Collaboration

This write-up is for colleagues progressing mini program or app work. The client is in media & creative, roughly a dozen staff, based around Europe. We hit a case of legacy outbound links broken. Troubleshooting started with logs on Nginx, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. This write-up is for colleagues progressing mini program or app work. The client is in manufacturing, roughly a dozen staff, based around inland growth markets. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on Postman, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed API integration testing 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 API integration testing. Archive screenshots and config change IDs for this API integration testing round so next month's retrospective stays concrete.

Testing & Acceptance

Last week we reviewed push notification strategy with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to push notification strategy first. Archive screenshots and config change IDs for this push notification strategy round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on App and backend field alignment. We hit a case of payment succeeded but orders still pending. Troubleshooting started with logs on object storage, then followed our reproduction steps. 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 privacy consent dialogs. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to privacy consent dialogs first. Next, we recommend to run a real-device smoke check before go-live. If more features are added, scope the blast radius before scheduling.

Risks & Mitigations

Last week we reviewed multi-store accounts with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but multi-store accounts still needs a one-page rule sheet to cut verbal rework. Next, we recommend to store backups in a separate folder with dated labels. If more features are added, scope the blast radius before scheduling. The same requirement can sound different across departments; writing it down helps align decisions on iOS and Android app delivery. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to iOS and Android app delivery first. Next, we recommend to store backups in a separate folder with dated labels. If more features are added, scope the blast radius before scheduling. Last week we reviewed loyalty points rules 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 Git, then followed our reproduction steps. Archive screenshots and config change IDs for this loyalty points rules round so next month's retrospective stays concrete.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on canary release. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on WeChat DevTools, then followed our reproduction steps. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling.