Revv

Problem

Most trip-tracking software feels built for someone else: insurers, fleet managers, or car companies. Drivers who want useful trip data often get surveillance incentives, speed-bragging surfaces, or bloated enterprise tooling.

Revv is aimed at drivers who care about their trips, vehicles, and habits, but do not want every mile converted into an insurance score or every leaderboard to reward risky behavior.

What I built

I built the React Native app, Supabase/PostGIS backend, GPS buffer and upload pipeline, Mapbox route views, garage system, AutoDrive flow, privacy-zone processing, efficiency surfaces, social drive cards, and the App Store release path through v1.0.9.

• Records signed-in drives with local buffering and batch upload after trip end
• Processes routes with privacy-zone controls before display and review
• Adds share cards, driver handles, and social feed surfaces around completed drives
• Reported reach: 500 users in the first month
• App Store release: Revv: Drive Tracker v1.0.9

Status

Live on the App Store as Revv: Drive Tracker. Reported reach: 500 users in the first month. Apple lists v1.0.9, released June 11, 2026, with AutoDrive reliability work, drive share cards, driver handles, follower/following views, route previews in the feed, and cockpit polish.

The useful product line is helping drivers learn from their trips without rewarding dangerous driving or burying the experience under fleet-software assumptions.