Tips · Clarity · 4 min read
What a driving score actually measures
A clear look at phone-sensor driving scores: harsh events, local math, what they are not (crash detection, insurance grades), and why Apexmatic keeps trips on the device.
Driving scores sound like a single truth. In practice they are a summary of how often the car (or the phone in it) saw hard accel, hard brake, sharp cornering, or a quick heading flick — weighted into a number that is easy to glance at.
What Apexmatic counts
- Harsh accel, brake, corner, and swerve against thresholds you can retune.
- Optional speeding spans when you set a cap.
- Notes like possible-impact or phone-in-hand that you can review — they do not change the score.
- Road roughness along the path as pavement context, not a driver penalty.
What it is not
It is not verified crash detection, not an emergency call, and not an insurer’s grade of you as a person. Phone sensors miss context a human can see — weather, an ambulance, a pothole dodge that was the safest choice.
Why “local” matters
Apexmatic computes the score on the phone and keeps the trip there unless you export it. That means the feedback loop is yours: improve the next drive because you want to, not because a remote dashboard is waiting.
Apexmatic
Keep the trip on your phone.
Ready to see those habits on a real trip? Apexmatic scores the drive on your phone — Android now, iOS coming soon. Trips stay on the device unless you export them.
