MOB-13 — Field test with a delegate — GPS, weak network, offline
A real tour in Oran-like conditions: tolerance, airplane-mode visits and sync recovery, photo queue, battery drain measured.
| Field | Details |
|---|---|
| Task code | MOB-13 |
| Phase | P1 — V1 build & integration |
| Product scope | V1 |
| Status | Planned |
| Start | Thu 17 Dec 2026 |
| Due | Mon 21 Dec 2026 |
| Responsible | Imad — Mobile developer (Flutter) |
| Co-responsible | Akram |
| Effort | 1.5 person-day(s) planned · 3 from scratch · size S |
| Area · app | Mobile quality · mobile |
| Depends on | MOB-12 |
| Unblocks | MOB-14 |
| Milestones | — |
Summary
A real tour in Oran-like conditions: tolerance, airplane-mode visits and sync recovery, photo queue, battery drain measured.
Description
Lab tests do not reproduce shops with thick walls, 3G in town centres or a full day on battery; this task runs a real tour with a delegate in Oran-like conditions to validate tolerance, offline behaviour and battery before the stores (SYN-04, SYN-05, FLD-07, FLD-15). Scope: one real tour of 8–12 points of sale on staging or pre-production data, with Imad observing the app and Akram observing usability and outdoor readability: check-in distance and accuracy per stop, airplane-mode visits and sync recovery, the photo queue on weak networks, and battery drain with sampling. Out of scope: building new features; fixes found go into MOB-15/MOB-17 or hot fixes. It needs a pilot delegate and real point-of-sale coordinates arranged with HOCO, a tour planned in the back-office, and the MOB-12 build. The findings tune the tolerance and sampling defaults proposed to Anis and feed MOB-14 and DQA-03.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Plan the field day with HOCO: delegate, 8–12 real points of sale with verified coordinates, tour created in the back-office, test resellers prepared | Imad |
| 2 | Measurement sheet per stop: time to fix, accuracy, distance at check-in, tolerance result, indoor vs outdoor | Imad |
| 3 | Offline scenario: three consecutive visits in airplane mode (with photos and a new prospect), then reconnection and sync timing | Imad |
| 4 | Weak-network scenario: photo queue on 3G/EDGE with progress and retry observed | Imad |
| 5 | Battery and data measurement over the tour with sampling on (batterystats, data usage) | Imad |
| 6 | Usability and outdoor readability observation (sunlight, one-handed use, gloves/fast taps), notes with photos | Akram |
| 7 | Debrief with the delegate and written findings, prioritised as blocker / fix before pilot / later | Akram |
| 8 | Proposals to Anis for tolerance, accuracy and sampling defaults based on the measurements | Imad |
Deliverables
- Field test report (metrics per stop, offline and battery results, findings) shared with Anis and Akram
- GitHub issues for each finding labelled field-test with priority
- Proposed field settings values (tolerance, accuracy, interval, distance)
Acceptance criteria
- All visits of the day are on the server after sync with zero duplicates and zero lost photos (SYN-05)
- At least 90 % of check-ins at correctly located stores pass the 150 m tolerance; every failure is explained (wrong coordinates, indoor accuracy) (FLD-07)
- Offline visits replay within 1 minute of reconnection (SYN-04)
- Battery drain over the tour is measured and within the agreed target, or a mitigation is planned (FLD-15)
- No crash or ANR during the tour (Sentry clean for the session)
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| SYN-04 | Delegate app keeps the tour, visits, notes and photos locally under weak network | V1 |
| SYN-05 | Sync queue handling retries, duplicates (idempotency), errors and conflicts | V1 |
| FLD-07 | Map and navigation: position, next destination with ETA and distance, external GPS navigation, arrival confirmation within tolerance | V1 |
| FLD-15 | Location policy: consent, frequency, tolerance and retention configurable and transparent | V1 |
Test measures
- Real tour with a delegate following the measurement sheet
- Post-tour server audit: visits, photos, pings and prospects compared with the app's local logs
- Sentry and battery stats review of the field devices
Risks
- Bad weather, delegate unavailability or wrong store coordinates waste the day — book a backup date and verify coordinates the day before
- Testing on staging with real shop owners may confuse them — use test resellers or brief the visited shops in advance with HOCO
KPI
- Delivered by Mon 21 Dec 2026 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.
MOB-12 — Staging integration — real API, edge states, performance
Switch both apps from the mock to staging, walk every flow, fix contract mismatches, cold-start and list performance on a mid-range Android.
MOB-14 — Store readiness — Play Console tracks, data safety, location declaration
Play Console apps, internal and closed tracks, data-safety form, background/foreground location declaration and video, privacy policy URL, release signing.