Mobile product discussion: push notification strategy

Context: This write-up is for colleagues progressing mini program or app work. The client is in healthcare, roughly a dozen staff, based around Europe. Editors know the CMS well enough, but WeChat mini program development still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this WeChat mini program development round so next month's retrospective stays concrete.

Background & Goals

Last week we reviewed iOS and Android app delivery 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 React Native, then followed our reproduction steps. Archive screenshots and config change IDs for this iOS and Android app delivery round so next month's retrospective stays concrete. This write-up is for colleagues progressing mini program or app work. The client is in healthcare, roughly a multi-division group, based around historic downtown districts. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on React Native, 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 sports venues, roughly a multi-division group, based around free-trade zones. We hit a case of legacy outbound links broken. Troubleshooting started with logs on a cloud database, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Testing & Acceptance

Last week we reviewed QR code redemption 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 QR code redemption first. Prefer a go-live window outside peak traffic, and prepare the rollback package early. The same requirement can sound different across departments; writing it down helps align decisions on third-party login. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to third-party login first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Operations & Collaboration

Last week we reviewed third-party login 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 third-party login first. Next, we recommend to give editors a one-page publishing guide. If more features are added, scope the blast radius before scheduling. Last week we reviewed privacy consent dialogs 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 privacy consent dialogs. 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 healthcare, roughly a multi-division group, based around high-tech zones. Editors know the CMS well enough, but iOS and Android app delivery still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this iOS and Android app delivery round so next month's retrospective stays concrete.

Takeaways: This write-up is for colleagues progressing mini program or app work. The client is in manufacturing, roughly a multi-division group, based around high-tech zones. QA walked the main path three times on real devices and flagged edge cases around canary release. Add a field dictionary to the docs so new joiners ask fewer repeat questions.