DrivTok · iOS and Android
A living history for every car.
DrivTok brings maintenance, repairs, costs, reminders, modifications, and the stories around a vehicle into one mobile product.
My role
I designed the product and engineered most of the complete system, from mobile experience and backend behavior through release and operation.
The problem
A vehicle's history is usually fragmented across invoices, notes, spreadsheets, service books, and memory. That makes ownership harder and erases the story enthusiasts care about.
Constraints
- One coherent experience across iOS and Android
- Structured records without making entry feel administrative
- Useful private ownership tools alongside optional public stories
Product evidence
The shipped experience.
Key decisions
What shaped the product.
Organize around the vehicle
Maintenance, expenses, reminders, modifications, and posts share one durable vehicle context instead of behaving like disconnected utilities.
Make history visual
Timelines and summaries turn raw records into something an owner can understand quickly and continue updating.
Ship the complete loop
The product includes the operational work around accounts, data, mobile releases, and ongoing maintenance—not only polished screens.
What shipped
- Vehicle profiles and chronological history
- Maintenance, repairs, expenses, and reminders
- Modification tracking and enthusiast posts
- Public releases on Apple's App Store and Google Play
Honest current state
DrivTok is publicly available on both major mobile platforms. It is proof of shipped scope and end-to-end ownership; this page does not claim revenue or product-market fit.
What I learned
Building the product is only half the commercial system. Distribution and repeated user contact need to be designed as deliberately as the software—one reason I now work with clients from product direction through launch and operation.