Built in the driver's seat.
DriveLens wasn't created in a boardroom. It started because I drive rideshare too, and I wanted a better way to understand the offers hitting my screen before they disappeared.
I still use DriveLens during my own shifts, so the same bugs, bad data, and frustrating workflows that affect other drivers affect me too.
I was tired of doing the math in my head.
Driving Uber means making decisions in seconds.
- How much does the ride pay?
- How many miles is it really?
- How long will it take?
- Where will it leave me?
- Is the trip actually worth taking?
I got tired of trying to calculate all of that mentally while watching the offer timer disappear.
So I started building the tool I wanted on my own screen.
It started as a tool for my own shifts.
DriveLens originally existed for one reason: help me make faster, more consistent ride decisions.
The first versions were rough. I used them while driving, found what worked, found what was annoying, fixed it, and repeated the process. Over time, that turned into the app DriveLens is becoming today.
It now helps track and understand things like:
Tested on real shifts, not just test screens.
DriveLens gets used in the same environment it was built for.
That matters because rideshare tools can look great in a demo and still become frustrating once you actually rely on them while driving. If something is slow, inaccurate, distracting, or confusing, I want to find out the same way every other driver would.
By actually using it.
Useful data without getting in your way.
DriveLens is not supposed to make driving more complicated. The goal is simple:
Show the information that matters, make it easy to understand, and let the driver make the decision.
That means prioritizing reliability and clarity over stuffing the app with features just because we can. If a feature does not help make driving easier, more informed, or more understandable, it probably does not belong in the app.
Other drivers shape the app too.
My own driving experience is only one market, one phone, and one way of working. That is why feedback from other drivers matters.
Different cities, different ride types, different Android devices, and different driving strategies expose things I may never see myself. DriveLens will continue evolving based on both real-world use and feedback from the people actually using it behind the wheel.
Want to help test DriveLens?
Become a TesterBuilt by a driver. Improved by drivers.
DriveLens exists because rideshare drivers deserve tools built around how the job actually works.