App & mini program delivery: third-party login

Context: 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. Archive screenshots and config change IDs for this subscription messaging reach round so next month's retrospective stays concrete.

Background & Goals

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. This write-up is for colleagues progressing mini program or app work. The client is in maternity & baby products, roughly about thirty people, based around inland growth markets. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on Git, 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.

Risks & Mitigations

The same requirement can sound different across departments; writing it down helps align decisions on crash log collection. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to crash log collection 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 wholesale & retail, roughly a dozen staff, based around Southeast Asia. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to API integration testing first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Operations & Collaboration

Last week we reviewed in-store appointment booking 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 in-store appointment booking first. 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. 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.

Delivery Approach

This write-up is for colleagues progressing mini program or app work. The client is in wholesale & retail, roughly a dozen staff, based around capital business districts. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Next, we recommend to run a real-device smoke check before go-live. 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 finance & tax consulting, roughly two hundred+ staff, based around capital business districts. QA walked the main path three times on real devices and flagged edge cases around loyalty points rules. Next, we recommend to log API status codes and latency. If more features are added, scope the blast radius before scheduling. Last week we reviewed subscription messaging reach with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but subscription messaging reach 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 iOS and Android app delivery. 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.