In development. Follow the journey.
Tripwise is being developed to help drivers understand their habits, learn from their journeys and build safer driving behaviours, without judgement.
Sample journey, 23 min
Concept previewMost driving apps hand you a number and leave you to guess what it means. Tripwise is being built on a different idea: driving data should help people understand and improve their habits, not label them as good or bad drivers.
This interactive demonstration explores how Tripwise might turn driving behaviours into understandable feedback. The scoring model is illustrative and is not a validated assessment of driving safety.
Something to try
Each slider runs from 0 to 100, where higher means smoother or more anticipatory. The score is a weighted sum, rounded and kept between 0 and 100:
score = 0.25 × braking + 0.20 × acceleration + 0.15 × cornering + 0.20 × speed consistency + 0.20 × anticipation
The weights are design choices for this demo. They are not derived from road-safety research.
The app isn't built yet. These are concept screens with sample data, showing the experience we're working towards in three stages.
Tripwise aims to turn supported driving and phone-sensor data into journey summaries a person can actually read: where things went smoothly, and the moments that might be worth a second look.
Tuesday morning, school run
Concept, sample dataThe goal is to explain what a detected event might mean, why it could matter and what might change its interpretation, and to let drivers say when the data got it wrong.
A firmer stop near a junction
Concept, sample dataOver time, the intended product will help drivers recognise patterns across many journeys and work towards better habits at their own pace. One journey never tells the whole story; trends say more.
Braking over eight weeks
Concept, illustrative dataTripwise began after a real road crash. We won't retell it here; it belongs to the people it affected. What it left us with was a plain understanding of how quickly an ordinary journey can change, and how much it matters to notice risky habits early, while there's still time to learn from them.
We don't claim that any app could have changed what happened. Crashes have many causes, and data sees only some of them. But it raised a question we keep coming back to: what if driving data helped people understand their habits, rather than simply judging them?
That question is the whole of Tripwise. Everything we build has to make someone better informed, never just more nervous.
A number on its own can't tell you whether a hard stop was a lapse in attention or the right response to a child chasing a ball. Without that context, a score can punish good decisions and miss the habits that matter.
What was detected, why it might matter, what could change the picture and what you might try next. If we can't explain a piece of feedback in plain words, it shouldn't be shown.
Nobody gets better at something by being told they're bad at it. Useful feedback is specific, fair and points somewhere. It treats the driver as someone capable of improving.
New drivers are building confidence and independence at the same time. Parents want them safe. We think those goals meet in honest conversations, helped by information the driver has chosen to share.
How a score is calculated, what data is used and who can see it should be knowable by the person it's about. That's a design requirement, not a policy page.
A product that people don't trust won't be used, and one that's used reluctantly won't help. Consent, control and minimal data collection are part of making it work at all.
See every phase and task, filter by area or status, and read short notes on what's being explored and why.
Open the development logTripwise aims to support young drivers and their families without becoming a tracking product. The driver stays at the centre.
Try the sharing controls. Everything here is a mock-up.
Concept, not a live featureOnly Sam can change these.
Live location tracking isn't part of this concept. Tripwise is about understanding journeys, not watching them.
We're exploring ways to recognise personal progress. None of these exist yet, and they may change or never ship.
Marking moments of progress against your own starting point, never against other drivers.
Short, optional focuses, like a week of gentler pull-aways, with an explanation of why each one matters.
Recognising steady, settled driving sustained over time, rather than one good trip.
Possibly, one day, rewards funded by partners. No partnerships exist today.
What we won't do: reward people for driving more miles, taking more journeys or spending more time on the road. The safest journey is sometimes the one you don't need to make.
Phone sensors are useful, but they aren't perfect. A product like this has to be upfront about its limits, or it will mislead the people it's meant to help.
Accelerometers and GPS vary between devices and can drop out, drift or misread movement.
A phone in a pocket, a loose mount, potholes and speed bumps can all look like driving events.
A single firm stop explains very little on its own. Patterns across many journeys say far more.
Any number Tripwise shows should come with how it was calculated and what it can't account for.
Who sees what should be the driver's decision, visible at all times and easy to change.
Where the data is uncertain, the product should say so, rather than present a guess as a fact.
Tripwise is in development. Follow the journey as we explore a more thoughtful way to understand driving and encourage safer habits.
The app is not available yet, and there's no download.
A public record of what we're working on, what's finished and what's still only a plan. Statuses reflect where things genuinely stand: most of Tripwise hasn't been built yet.
Short write-ups of what's being explored and why. Filters above apply here too.
This log is published from structured data in the page. New updates are added as entries, with honest statuses; nothing here describes user research, test results or partnerships, because none have happened yet.