RapTrak

§ 1The starting point

While visiting another city, I wanted to watch a rap battle and could not find where one was happening. That small discovery problem became the starting point for RapTrak.

§ 2The problem to solve

Finding an event is only one part of the scene. Crews need a way to manage their work, and MCs need a public place to show their accomplishments.

§ 3What I built

I built the product across four journeys: finding nearby battles, crew management, MC profiles and accomplishments, and administration and moderation. I owned the product direction, design, mobile app and backend.

§ 4Where it stands

All four journeys are functional. The app has not been publicly released: community preparation and time alongside other work have shaped the launch timing.

Note —Functional does not mean publicly launched. No adoption, app-store availability or community-impact metrics are claimed. Detailed architecture and implementation decisions will be documented after a dedicated source review.