MRA-22 — Reseller app code screen for WhatsApp
RA-04 words itself from the channel of auth.otp.send and offers the SMS option.
| Field | Details |
|---|---|
| Task code | MRA-22 |
| Phase | P1 — V1 build & integration |
| Product scope | V1 |
| Status | Planned |
| Start | Sun 27 Dec 2026 |
| Due | Mon 28 Dec 2026 |
| Responsible | Imad — Mobile developer (Flutter) |
| Co-responsible | — |
| Effort | 0.5 person-day(s) planned · 1 from scratch · size S |
| Area · app | Reseller app · mobile |
| Depends on | SRV-51, MOB-06 |
| Unblocks | MRA-23 |
| Milestones | — |
Summary
RA-04 words itself from the channel of auth.otp.send and offers the SMS option.
Description
Decision D-64. API: auth.otp.send takes an optional channel (WHATSAPP or SMS) and its answer now says channel WHATSAPP, SMS or EMAIL. Send nothing for the first code, so the server chooses. Word RA-04 from the channel of the answer, never from the request: it says SMS when WhatsApp refused the message. On WHATSAPP, show « Recevoir le code par SMS », which repeats the call with channel SMS and clears the boxes; the old code stops working. It is available at once, because the 60 s cooldown is per channel. auth.otp.verify does not change. Keep sending androidAppHash: SMS auto-fill still applies, but a WhatsApp code has no auto-fill. A client whose enum only knows SMS and EMAIL breaks on the new value once the setting is on, so regenerate hoco_api first. Staging: when the setting is on, simulated codes land in Mailpit in the phone's mailbox, and the test numbers keep 123456. The delegate app does not change.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Regenerate hoco_api | Imad |
| 2 | Wording of RA-04 from channel, in the three languages | Imad |
| 3 | Recevoir le code par SMS | Imad |
Deliverables
- apps/reseller/lib/src/features/auth/ updated
Acceptance criteria
- With WhatsApp on, RA-04 names WhatsApp and offers the SMS option
- An answer of SMS after a WhatsApp refusal shows the SMS wording
- With WhatsApp off, RA-04 is unchanged
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| AUTH-03 | Reseller self sign-up: phone verified by OTP, store details, declared customer type (super-gros, demi-gros, détail), password, optional invitation code | V1 |
| AUTH-04 | Reseller sign-in (phone or email + password, or a one-time code) and password reset by OTP | V1 |
| AUTH-07 | Password policy, hashing, OTP expiry/resend cooldown and attempt limiting | V1 |
Screens
API surface
| Endpoint group | Operations |
|---|---|
| Authentication & sessions | 14 |
Test measures
- Widget test of RA-04 for each channel
Risks
- Must ship before the setting is switched on in production
KPI
- Delivered by Mon 28 Dec 2026 within 0.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.
MOB-17 — Design QA fixes & accessibility pass (both apps)
Apply Akram's design-QA findings, check contrast, touch targets, text scaling and screen-reader labels, verify RTL readiness on key screens.
MRA-23 — Reseller app sign-in options and login email
RA-07 takes a phone or an email and offers a code; RA-35 confirms a login email.