Mobility & AdTech
Mobility Ad Network — Tablet POC
A POC under development for distributing creatives to tablets with a Next.js admin, Android player, and Supabase/Postgres backend.
System screenshots are not available yet.
- Surfaces
- Admin + player
- Stage
- Technical POC
Challenge
Coordinate campaigns, devices, scheduled playback, and verifiable telemetry before a proven operational rollout.
Solution
The schema covers tenants, campaigns, creatives, temporal assignments, QR, proof-of-play, scans, and heartbeat; the Android player consumes schedules.
Available evidence
- Implemented Next.js admin and Android player
- Temporal assignments and playlists
- Proof-of-play, QR scans, and heartbeat
- Source
- Uber_marleting_tablet@2653faa — STATUS.md, Supabase schema, Edge Functions, and Android player
- Period
- Initial structure in November 2025; technical update on 2026-03-01.
- Method
- Schema, functions, admin, player, tests, and deploy-documentation review.
- Context
- Technical creative-display network with temporal and assignment/device/campaign segmentation.
- Verified on
Limitations
- No deployment or operational fleet use was proven.
- The Android player has no recorded unit or integration tests.
Architecture & Stack
The stack reflects the recorded implementation and this project's context; it is not a generic guarantee of resilience, performance, or scale.
- Next.js
- TypeScript
- Android
- Kotlin
- Supabase
- PostgreSQL
- Edge Functions
Core Features
- Campaign and device management
- Scheduled assignments
- Proof-of-play
- QR scans and heartbeat