Latest update: The updated backend and tablet player are now live in production (released 7–8 Oct), including the fix that lets the device report show real hardware readings. The handover document for the Android developer is drafted for signing tomorrow (Fri 9 Oct). Still open before signing: the production release of the device-management application, which is still the July version. Overall development holds at 98%.
Executive Summary
Overall Progress
Development scope · EPIC-00–07
98%
Core functional platform is ready (98%). Hardware validation and operational fleet deployment are excluded, pending tablet delivery and partner readiness.
- Core product (100%): Ad playlist, video playback, remote device control, interactive ads, and entertainment features are fully built. The flexible campaign content form was completed on 15 Sep: the advertising team can now configure campaigns for any screen layout, with the system enforcing which slots are mandatory and which media types each slot accepts.
- Testing & QA readiness (100%): Every application runs automated checks before each release build, and internal acceptance testing is complete — all 86 scenarios passed.
- Production deployment (done): The backend went live on 15 Sep and has had two updates since; the latest, on 8 Oct, makes the device report show real hardware readings and makes the ad-delivery list and its summary totals agree. The tablet player application received two production updates on 7–8 Oct with the reliability fixes from the stability test. The device-management application still needs its production update.
- Internal device stability (95%): The repeated 24-hour test passed and was formally closed on 8 Oct for both the player and the device-management application: just over 25 hours on one version, no crashes. Short restarts seen on one tablet were traced to its power supply, and two other tablets ran for more than 24 hours without issue. What remains is recording the setup of the five new tablets.
- Team handover: The Android developer’s contract ends 11 Oct (handover signed 9 Oct) and the CMS developer’s on 1 Nov (handover signed 30 Oct). Knowledge transfer to the internal Android engineer is complete — an app update was published independently on 2 Oct — and the CMS transfer is under way. Each developer signs a handover document; per contract they fix, without extra cost, bugs found before their contract ends for 30 days afterwards. The app-signing keys and cloud accounts have been handed to AMG (confirmed 5 Oct), so the company can keep updating the tablets independently.
- Attention point: The Android handover is signed tomorrow (Fri 9 Oct). Nine of fourteen handover items are verified complete and the handover document is drafted. Still open: the production release of the device-management application, recording the setup of the new tablets, recording one remaining known issue, and moving one technical procedure into the code repository. Unfinished items are listed in the handover document and covered by the developer’s free 30-day bug-fix period. The CMS handover (30 Oct) has no blockers.
- External dependencies: The new tablets and their power adapters have both arrived and all five are installed and running around the clock at head office, working as expected; AMG has six tablets for testing, all at the office. Testing in real cars is not possible for now, so validation runs at head office. Rollout in actual taxis still waits for the taxi partner agreement.
Timeline — Gantt by Epic (Apr–Oct 2026)
Complete
In progress
Planned
Blocked / external dependency
Today (8 Oct)
Swipe horizontally to see the full timeline.
Next management checkpoint: Android handover signed (Fri 9 Oct) with the device-management application released to production, findings from the head-office tablet run, and the CMS handover (Fri 30 Oct).
Go-live to real taxis: pending the taxi-provider partnership decision. Internal development and office-vehicle validation continue independently.