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.
| Field | Details |
|---|---|
| Task code | MOB-14 |
| Phase | P1 — V1 build & integration |
| Product scope | V1 |
| Status | Planned |
| Start | Mon 21 Dec 2026 |
| Due | Tue 22 Dec 2026 |
| Responsible | Imad — Mobile developer (Flutter) |
| Co-responsible | — |
| Effort | 1 person-day(s) planned · 3 from scratch · size S |
| Area · app | Mobile quality · mobile |
| Depends on | MOB-13, DQA-01 |
| Unblocks | QA-01, MOB-15 |
| Milestones | Staging integration complete |
Summary
Play Console apps, internal and closed tracks, data-safety form, background/foreground location declaration and video, privacy policy URL, release signing.
Description
Both apps must pass Google Play review before the pilot, and the delegate app's location use is the review risk: Play requires a prominent disclosure, a foreground-service declaration with a demo video, an accurate data-safety form and a privacy policy (NFR-04, SEC-07, SEC-08, OPS-02). Scope: Play Console apps for dz.hoco.reseller and dz.hoco.delegate (on HOCO's developer account), internal and closed tracks, Play App Signing and versioning, store listings in French with Akram's DQA-01 assets, data-safety forms, location/foreground-service declarations and video, content rating, reviewer access instructions with test accounts, privacy-policy URL. iOS is MOB-16. It needs from Anis the privacy policy page and retention durations validated with HOCO (Law 18-07) and reviewer test accounts on pre-production; from Akram the icons, screenshots and feature graphics. LCH-03B and QA-01 install from the closed track set up here.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Play Console: confirm the developer account owner (HOCO) and Imad's access; create both apps, internal and closed testing tracks, tester lists for the pilot | Imad |
| 2 | Play App Signing enrolment, upload keys from MOB-01, versionName semver and versionCode from the CI build number; release AAB built by CI | Imad |
| 3 | Store listings in French (titles, short and full descriptions) with DQA-01 icons, feature graphics and screenshots | Imad |
| 4 | Data-safety forms: location (delegate only), photos, phone number, name, device ID, crash logs, purposes, encryption in transit, deletion on request | Imad |
| 5 | Foreground-service (location) declaration and demo video showing DA-04 disclosure, starting a tour, the persistent notification and stopping at closing; no ACCESS_BACKGROUND_LOCATION requested | Imad |
| 6 | Privacy policy page and retention durations (positions 90 days, photos, documents) validated with HOCO and published on the HOCO domain | Anis |
| 7 | Content rating, target audience (adults, business use), app access instructions with reviewer accounts for both apps | Imad |
| 8 | Final store visuals and listing review | Akram |
Deliverables
- Play Console apps with internal and closed tracks for both apps
- Approved data-safety forms and foreground-service declaration with the demo video
- Release AABs 1.0.0 (prod flavor) on the closed track
- Privacy policy URL referenced in both listings and in-app settings
Acceptance criteria
- Both apps are approved on the closed track and installable by pilot testers from the opt-in link
- The delegate app's location declaration is approved and the disclosure screen (DA-04) appears before any location permission prompt (SEC-07)
- Data-safety answers match what the apps actually collect (checked against the SDK list: Firebase, Sentry, Maps)
- The privacy policy URL is live and states retention durations validated by HOCO (SEC-08)
- Release builds are signed through Play App Signing and versionCodes increase monotonically from CI
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| NFR-04 | Android first on mid-range phones; iOS on client decision | V1 |
| SEC-07 | Geolocation consent and transparency for delegates | V1 |
| SEC-08 | Privacy policy, data ownership and retention durations validated with the client (Law 18-07) | V1 |
| OPS-02 | Deployment: server, database, storage, backups, domains, certificates, external services, store publication | V1 |
Test measures
- Pre-launch report in Play Console reviewed (crashes, accessibility, security warnings) for both apps
- Install from the closed track on three devices and verify app links (MRA-09) with the Play signing fingerprint
- Checklist review of permissions in the merged AndroidManifest against the data-safety form
Risks
- Play review rejects the location foreground service — tie it strictly to the visible tour, record a clear video and keep a fallback of foreground-only sampling while the app is open
- The Play developer account is not ready (identity verification takes days) — ask HOCO to create and verify it at the start of P1
KPI
- Delivered by Tue 22 Dec 2026 within 1 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-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.
MOB-15 — Mobile test automation & hardening
Integration tests for the ordering and visit flows, golden tests for the design-system widgets, crash-free and cold-start checks in CI.