Hubbleads
[Client]
Hubbleads
[Year]
2024
[Project Focus]
- Turn taxi-mounted rooftop LED screens into a measurable out-of-home ad network.
- Replace estimated OOH reach with counted, logged playback and route/time targeting.
Scroll to explore
[Overview]
Hubbleads is an independent product: a rooftop LED ad network with reach that is counted, not estimated.
[What I did]
- Built the platform for campaign scheduling, route and time-of-day targeting across the rooftop screen network
- Implemented verified playback logging and analytics so campaign reach is counted, not estimated
- Added multi-format creative support (MP4, MOV, GIF, PNG, JPG, HEIC) with weather-resistant, auto-brightness display hardware integration
- Established technical direction, product scoping, and execution strategy as founder
[The role]
Software Engineer and Founder
Njay
Project Info
Hubbleads is a mobile out-of-home advertising network I founded, built around taxi-mounted rooftop LED screens that carry campaigns across busy city routes. The product is the platform underneath the screens: scheduling, targeting, and proof that an ad actually played.
I set the technical direction and built the platform — campaign scheduling, route and time-of-day targeting, and playback logging on Next.js, Node.js, Python, MongoDB, and AWS — so advertisers see verified plays instead of a modeled estimate.
Overview
2024
Hubbleads is a mobile out-of-home advertising network I founded, built around taxi-mounted rooftop LED screens that carry campaigns across busy city routes. The product is the platform underneath the screens: scheduling, targeting, and proof that an ad actually played.
I set the technical direction and built the platform — campaign scheduling, route and time-of-day targeting, and playback logging on Next.js, Node.js, Python, MongoDB, and AWS — so advertisers see verified plays instead of a modeled estimate.
The Process
I scoped the product around what fixed billboards cannot offer: a screen that moves through targeted routes and a record of every time it displayed a given campaign. That record became the product’s core differentiator.
Node.js and Next.js expose the advertiser- and driver-facing surfaces. Python and MongoDB handle the heavier processing behind scheduling and playback logging. AWS is the runtime for the network of screens reporting in.
Hardware constraints shaped the software: multi-format creative support (MP4, MOV, GIF, PNG, JPG, HEIC), weather-resistant units, and auto-brightness for daylight visibility all had to be accounted for in how campaigns are packaged and delivered.
The Outcome
Hubbleads delivers campaigns with logged records of every play, not an estimated reach figure — the reporting an advertiser can defend in a meeting.
The company has a platform built around counted impressions and route/time targeting, positioned against fixed outdoor placements on cost and measurability.