Third Party Mode for Real-Time Car Monitoring in Adrenox
A handover mode for connected cars, built for the moment the keys go to someone else
✳The problem they went after
Handing a car to a valet, cleaner or service executive means losing all visibility. Owners have no reliable way to monitor usage, enforce boundaries, or act quickly when something goes wrong. The write-up names the resulting behaviour plainly: repeated calls to check the car is still fine. Connected car apps carry plenty of features and none aimed at this handover scenario.
✳What they actually did
Third Party Mode is the top-priority solution. Switching it on sets a 60 kilometre per hour speed lock, draws a user-defined geofence with alerts if the car crosses it, activates ADAS features like automatic braking and lane keep assist, and pushes notifications whenever the car moves or exceeds the speed threshold. When the handover ends, the owner gets a trip summary. A companion updates feature notifies on engine start, movement and overspeed, and an AI layer flags proximity changes between car and phone plus unauthorised ignition.
✳What you can take from it
Worth stealing
- Feature scoped to a moment, not a persona
- 60 km/h speed lock plus user-defined geofence
- Trip summary closes out every handover
- Phone-to-car proximity checks flag unauthorised ignition
Read this if
Designing a temporary mode for a high-anxiety handover moment
The transferable bitA good example of scoping a feature to a moment rather than a user type. The mode runs only during handover, ends after, and closes with a summary, which keeps the surveillance framing contained. The chosen success metrics, subscription retention and dashboard engagement time, tie a safety feature back to the business it sits inside.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
