App & mini program delivery: loyalty points rules

Context: This write-up is for colleagues progressing mini program or app work. The client is in restaurant chains, roughly two hundred+ staff, based around the Middle East. 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 lazy-load homepage assets by route. If more features are added, scope the blast radius before scheduling.

Background & Goals

Last week we reviewed WeChat mini program development 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 CDN, 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 automotive services, roughly about thirty people, based around new urban centers. We hit a case of CMS image uploads over-compressed. Troubleshooting started with logs on Nginx, then followed our reproduction steps. Next, we recommend to require a change request for any scope change. 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 inventory sync. Editors know the CMS well enough, but inventory sync 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.

Testing & Acceptance

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. Archive screenshots and config change IDs for this QR code redemption round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on inventory sync. QA walked the main path three times on real devices and flagged edge cases around inventory sync. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Delivery Approach

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 mobile menus nested too deep. Troubleshooting started with logs on Nginx, then followed our reproduction steps. 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 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. Prefer a go-live window outside peak traffic, and prepare the rollback package early. 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 legacy outbound links broken. Troubleshooting started with logs on CDN, then followed our reproduction steps. Archive screenshots and config change IDs for this subscription messaging reach round so next month's retrospective stays concrete.

Takeaways: Last week we reviewed privacy consent dialogs 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 privacy consent dialogs first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.