MOB-18 — Pilot improvements — mobile
Prioritised fixes and UX adjustments from the pilot retrospective and Akram's field observations; release to the public track.
| Field | Details |
|---|---|
| Task code | MOB-18 |
| Phase | P3 — Generalisation (after the 3 months) |
| Product scope | V1 |
| Status | Planned |
| Start | Sun 17 Jan 2027 |
| Due | Tue 19 Jan 2027 |
| Responsible | Imad — Mobile developer (Flutter) |
| Co-responsible | — |
| Effort | 3 person-day(s) planned · 8 from scratch · size M |
| Area · app | Mobile quality · mobile |
| Depends on | LCH-03B |
| Unblocks | LCH-05, MOB-16 |
| Milestones | — |
Summary
Prioritised fixes and UX adjustments from the pilot retrospective and Akram's field observations; release to the public track.
Description
The pilot shows what real delegates and resellers struggle with; this task turns the pilot retrospective and Akram's field observations into prioritised fixes and UX adjustments, then releases both apps to production for the generalisation (OPS-04, OPS-06). Scope: the MOB-18 backlog from LCH-03B, agreed priorities with Anis and HOCO, implementation of the top items, store listing updates and a staged rollout to the production track with monitoring; the minimum version is raised so pilot builds update. Large new features go to the V2 backlog. It needs prioritisation with Anis and HOCO, server changes for any item that touches the API, and Akram's design adjustments for UX changes. LCH-05 (generalisation waves and public release) starts from this release.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Pilot retrospective backlog prioritisation (must before generalisation / soon / V2) with Anis and HOCO | Imad |
| 2 | UX adjustments designed or validated by Akram from field observations | Akram |
| 3 | Implement the must-have fixes and adjustments in both apps, each with a regression test | Imad |
| 4 | Server-side changes required by pilot findings (contract additions announced before merge) | Anis |
| 5 | Store listing refresh (screenshots, descriptions) for the public reseller app; distribution decision for the delegate app (closed track or managed Play) | Imad |
| 6 | Staged rollout to production (10 % → 50 % → 100 %) with crash-free and sync-error monitoring, halt criteria defined | Imad |
| 7 | AppVersionPolicy: minimum version raised to the generalisation release once rollout completes | Anis |
Deliverables
- Release 1.1.0 of both apps on the production track
- Closed pilot issues with release notes
- Updated Play Store listings
Acceptance criteria
- All must-have pilot items are fixed, tested and confirmed by a pilot user or Akram
- The staged rollout reaches 100 % with crash-free users at or above 99.5 % and no rise in sync rejections
- Pilot versions are forced to update through the minimum-version policy
- The reseller app is publicly available on Google Play for generalisation (LCH-05)
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| OPS-04 | Maintenance: warranty period, corrective/preventive/evolutive maintenance, support SLAs and priorities, monitoring and security updates | V1 |
| OPS-06 | Pilot with a limited group of delegates and resellers, then progressive generalisation | V1 |
Test measures
- Full MOB-15 suites and the Test Lab matrix on the release candidate
- Regression test for each pilot fix
- Rollout monitoring review at each stage (Sentry release health, Play vitals)
Risks
- Pilot feedback exceeds the 4-day budget — strict must-have cut agreed with Anis; the rest goes to the evolutive maintenance backlog
- Rollout regressions reach many users — halt criteria and the ability to raise the minimum version to a fixed build
KPI
- Delivered by Tue 19 Jan 2027 within 3 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.
LCH-03B — Pilot (2 weeks) — mobile support & hotfixes (Imad)
Two calendar weeks on call for pilot users: crash/ANR triage, hotfix releases on the closed track, field visits with delegates when needed.
MOB-16 — iOS build & App Store release (on client decision)
Apple developer account, signing, iOS permissions strings, TestFlight, App Store review.