The only part of this a driver ever touches.
Everything else on this site is for the office. This is the screen in the cab, and if it is not in a language the driver reads comfortably then none of the rest of it works.
Try it in four languages
This is the real interface with real strings, not a mockup with the text swapped. 2 of the 4 mirror the layout.
المحطة التالية
عيادة الشفا
الموعد 09:00 – 11:00
6.4 km · 12 min
The whole layout mirrors — list rows, progress, the tab bar and the icon direction, not only the text.
Who is actually holding the phone
Fleet software in this region is usually sold to an English-speaking office and then handed to a cab where English is the third language in the room. The gap shows up as non-compliance and gets blamed on drivers.
- The default is Arabic, not English
- Most telematics apps ship in English and treat everything else as a translation to be added later. On a Saudi fleet that is backwards: the office may work in English, but the cab does not.
- Urdu and Hindi are not an afterthought
- A large share of drivers here read Urdu or Hindi far more comfortably than either Arabic or English. An app they can only half-follow produces exactly the compliance you would expect.
- The driver picks, not the administrator
- Language is set on the driver's own account and follows them between vehicles. Nobody has to file a request to read their own screen.
- Right-to-left means the layout, not the font
- Arabic and Urdu mirror the whole interface — navigation, progress, icon direction. An app with Arabic text in a left-to-right layout reads as though nobody checked.
It has to work on a bad phone with no signal
Not as a graceful-degradation story. As the normal case, because that is what a shift between Riyadh and the Empty Quarter actually looks like.
An app that needs a connection to show today's jobs is an app that strands a driver at a gate. Everything the driver needs for the shift is on the handset before they leave the yard.
Works with no signal
Jobs, checks and photographs are captured locally and sync when the phone reconnects. A driver in a dead zone is not stuck at a screen asking them to try again.
Built for the phone drivers own
Tested on five-year-old Android handsets on the cheapest data plans. The app is a few megabytes and does not assume a recent device.
Light on data
Photographs compress on the handset before upload, and nothing uploads over a metered connection unless it has to.
Light on battery
Location comes from the vehicle unit, not the phone's GPS, so an eight-hour shift does not flatten a driver's handset.
What the driver can see about themselves
A system drivers experience as surveillance gets worked around. One they can see into gets used. This is the difference, and it is mostly a matter of who sees what first.
How the score is built- Their own score, first
- A driver sees their events and score in the app before a manager raises them. Being told about your driving by a screen is uncomfortable; hearing it in a meeting three weeks later is worse.
- Their own footage
- The clip attached to an event is theirs to watch. Most coaching conversations end there because there is nothing left to explain.
- No live tracking of the person
- The app does not report the driver's phone location. The vehicle is tracked; the person is not followed home.
The rest of the platform
Live tracking
Position, speed and ignition every ten seconds.
Routing and dispatch
Plan the day, send it to the driver's phone.
Asset and trailer tracking
Trailers, generators, plant and containers.
AI dashcam
Road and cabin, clipped to the event.
Driver behaviour
Scored per driver and per trip.
Incident centre
Footage, telemetry and witnesses in one file.