Mobile product discussion: WeChat mini program development

Context: Last week we reviewed iOS and Android app delivery 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 iOS and Android app delivery first. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Risks & Mitigations

This write-up is for colleagues progressing mini program or app work. The client is in home & building materials, roughly a hundred-person team, based around Southeast Asia. Editors know the CMS well enough, but subscription messaging reach still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this subscription messaging reach round so next month's retrospective stays concrete. This write-up is for colleagues progressing mini program or app work. The client is in electronic components, roughly two hundred+ staff, based around high-tech zones. Editors know the CMS well enough, but multi-store accounts still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this multi-store accounts round so next month's retrospective stays concrete. Last week we reviewed subscription messaging reach 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 subscription messaging reach. Next, we recommend to require a change request for any scope change. If more features are added, scope the blast radius before scheduling.

Delivery Approach

Last week we reviewed iOS and Android app delivery 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 iOS and Android app delivery first. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling. This write-up is for colleagues progressing mini program or app work. The client is in legal services, roughly two hundred+ staff, based around Europe. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to in-store appointment booking first. Archive screenshots and config change IDs for this in-store appointment booking round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on loyalty points rules. QA walked the main path three times on real devices and flagged edge cases around loyalty points rules. Archive screenshots and config change IDs for this loyalty points rules round so next month's retrospective stays concrete.

Background & Goals

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 payment succeeded but orders still pending. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed WeChat mini program development 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 WeChat mini program development first. Archive screenshots and config change IDs for this WeChat mini program development round so next month's retrospective stays concrete.

Operations & Collaboration

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. Add a field dictionary to the docs so new joiners ask fewer repeat questions. This write-up is for colleagues progressing mini program or app work. The client is in media & creative, roughly around fifty employees, based around East Asia. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to iOS and Android app delivery first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on inventory sync. Editors know the CMS well enough, but inventory sync still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this inventory sync round so next month's retrospective stays concrete.