Operations back office
Operational web backoffice engineered with Next.js, TanStack Table, and Leaflet Heatmaps, providing operators and advertisers with real-time inventory management, vehicle verification, and urban impression density heatmaps.
Case study · Urban mobility & vehicle OOH media
Complete vehicular Out-Of-Home (OOH) media ecosystem designed to create supplemental income for rideshare and delivery drivers based on kilometers driven with sponsored ads on vehicle rear windows. It works as both B2B and B2C: companies buy the out-of-home service; the system checks the campaign’s available budget, proposes partner drivers and, once the proposal is approved, the campaign starts running. The solution is architected around two core pillars: a robust operational web backoffice for campaign and inventory management, and native mobile applications published on both the Apple App Store and Google Play Store with background GPS telemetry — fully developed and currently awaiting official launch for commercial operation.

Manage a fleet of cars shared among several advertisers. Each campaign has its own group of cars, a rate paid per kilometer driven and a budget; each car carries the campaign’s banner on its rear window; and the advertiser needs proof — reports showing the neighborhoods where the cars circulated most.
Operational web backoffice engineered with Next.js, TanStack Table, and Leaflet Heatmaps, providing operators and advertisers with real-time inventory management, vehicle verification, and urban impression density heatmaps.
Native driver-facing application built with React Native and Expo 53, published on both official stores. Provides transparent earnings tracking per kilometer driven, campaign selection, and immediate digital onboarding.
Robust tracking engine running in background via Expo Location, mapped to roads via Google Maps API and backed by local SQLite queue to guarantee metric integrity even in tunnels and low-connectivity zones.
Technical foundation structured to meet all vehicular advertising specifications, with the system fully tested, approved, and awaiting official launch for commercial expansion.
The bottleneck wasn’t code — it was requirements and change management.