DQA-12 — Design QA — V2 surfaces
Review of the loyalty, packs, credit and analytics V2 screens across the apps.
| Field | Details |
|---|---|
| Task code | DQA-12 |
| Phase | P4 — V2 evolutions |
| Product scope | V2 |
| Status | Planned |
| Start | Sun 21 Feb 2027 |
| Due | Mon 22 Feb 2027 |
| Responsible | Akram — UI/UX designer |
| Co-responsible | — |
| Effort | 1.5 person-day(s) planned · 2 from scratch · size S |
| Area · app | Design QA · design |
| Depends on | WEB-20, MDA-20 |
| Unblocks | — |
| Milestones | V2 delivered |
Summary
Review of the loyalty, packs, credit and analytics V2 screens across the apps.
Description
Akram reviews the V2 surfaces once they are built (after WEB-20 and MDA-20). In scope: loyalty, rewards and packs in the reseller app (RA-37…39) and web (RW-15); the V2 back-office pages for packs, loyalty and rewards (BO-52…54) and detailed credit, reminders and accounting exports (BO-47, BO-48); and the optimised routes and field analytics in the delegate app (MDA-20). Returns are not part of this review: they are V1 and were reviewed in DQA-02, DQA-04 and DQA-05. Inputs: the DES-30 frames, the V2 token release and the staging builds. Scope: visual fidelity, states and copy, and checking that V2 additions fit the V1 screens they extend (home, cart, checkout, account). This task is one of the conditions of the « V2 delivered » milestone.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Review RA-37…RA-39 and the V2 variants of RA-09, RA-17, RA-18 and RA-27 on the staging build | Akram |
| 2 | Review RW-15 at 1440 and 768 | Akram |
| 3 | Review BO-47, BO-48 and BO-52…BO-54 at 1440 and 1280, including permission-gated finance data | Akram |
| 4 | Review the MDA-20 optimised route display and field analytics on a device | Akram |
| 5 | Regression check: V1 flows touched by V2 (cart totals with packs and vouchers, home layout) still match their V1 frames | Akram |
| 6 | File issues labelled design-qa v2 in both repos and triage them | Anis |
Deliverables
- V2 design QA issues in
hoco-mobileandAnisBetehi/hoco - V2 design QA report with accepted deviations
Acceptance criteria
- Every V2 screen designed in DES-30 has been reviewed on its target platform
- Loyalty levels, points and vouchers use the V2 tokens and components, with no one-off styles
- V1 flows extended by V2 show no visual regression
- No blocker or major issue remains without an agreed fix
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| NFR-07 | Accessibility: readable contrast, reachable buttons, consistent text sizes, explicit messages | V1 |
Test measures
- Side-by-side comparison with the DES-30 frames
- Walkthrough: earn points → redeem a voucher at checkout → check totals and copy
KPI
- Delivered by Mon 22 Feb 2027 within 1.5 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.
DQA-08 — Pilot UX observation & feedback synthesis
Ride along with pilot delegates, interview pilot resellers, synthesise UX findings into prioritised improvements.
Ways of working
The operating model of the three-person team and HOCO: who owns what, the weekly rhythm and the golden rules that apply from day one.