Truckcom Driver

What happens the second you open it

You land on a login screen. That is the first moment. The app does not show you anything until you enter credentials. No demo mode. No guest access. Just a clean white screen with two fields: username and password. Below that, a login button. The design is minimal. No branding. No flashy graphics. Just a functional entry point. Enter your details and tap login. The app authenticates against the Truckcom office system. That is the backend. The office system manages jobs, vehicles, and drivers. The app is the front-end. It pulls data from the office system. It pushes data back. The connection is real-time. Once logged in, the main screen appears. A list of jobs. Each job shows a reference number, a customer name, a delivery address, and a status. The status can be "Assigned," "In Progress," or "Completed." Tap any job to open the details. That is where the real work begins.

The job details screen is divided into sections. Job info, stops, and actions. The job info shows the customer, the collection point, the delivery point, and any special instructions. The stops section shows the route. Each stop has an address, a planned time, and a status. The actions section is where the driver does the work. Tap "Start" to begin the job. Tap "Vehicle Check" to complete the walkaround inspection. Tap "POD" to capture proof of delivery. Tap "Accident" to report an incident. The actions are straightforward. No hidden menus. No confusing icons. The app is designed for drivers who are on the road. They do not have time to figure out a complex interface. The app respects that. It keeps things simple.

How vehicle checks and ePOD work together

Open the Vehicle Check screen and you see a list of questions. The questions are customisable. The office system defines them. They can include anything: tyre pressure, lights, brakes, mirrors, fluid levels. Each question has a yes/no option. Tap "No" and a text box appears. You can describe the defect. You can also take a photo. The photo is attached to the defect report. That is a useful feature. It provides visual evidence. It helps the office team understand the issue. Complete all questions and tap "Submit." The report is sent to the office system instantly. The driver can then proceed to the next stop.

Now consider the ePOD feature. That stands for electronic Proof of Delivery. Open the POD screen and you see the delivery details. The customer name, the address, the delivery reference. Tap "Sign" and a signature pad appears. The customer signs with their finger. The signature is captured. Tap "Photo" and you can take a photo of the delivered goods. Tap "Scan" and you can scan a barcode or document. The app combines all of these into a single delivery record. That record is sent to the office system. The customer receives an email with the POD attached. That is the workflow. Vehicle check first, then delivery, then POD. The app guides the driver through each step. But there is a catch. The app crashes. Users report that the app shuts down unexpectedly. Sometimes it crashes during the vehicle check. Sometimes it crashes during the POD capture. When it crashes, the data is lost. The driver has to start over. That is frustrating. It wastes time. It creates errors.

The real-world performance and the friction points

Speed is one thing. Reliability is another. The app has been updated frequently. The changelog mentions "bug fixes" but does not specify what was fixed. That is a pattern. The app works well most of the time. But when it fails, it fails hard. Users report that the app crashes constantly. One user said: "Since the update in January 2025 the app is absolutely shocking shuts its self down constantly and every time you turn the app back on you have to re do your vehicle checks every time sort it out." That is a specific complaint. It is not vague. It describes a real problem. The app crashes. The vehicle checks reset. The driver has to repeat the work. That is a significant issue. It affects productivity. It affects accuracy. It affects driver morale.

The location tracking is another friction point. The app uses location even when it is not open. That is stated in the privacy policy. It is also mentioned in the App Store description. "This app may use your location even when it isn’t open, which can decrease device battery life." That is a trade-off. The office system needs to track drivers in real-time. That is a legitimate requirement. But the battery drain is real. Drivers have reported that the app drains their phone battery quickly. That is a problem. Drivers rely on their phones for navigation, communication, and entertainment. A dead battery means a dead phone. That is not acceptable. The app could offer an option to reduce location accuracy. It could allow drivers to disable tracking when they are not working. It does not offer those options. The tracking is always on. That is the default. That is a friction point.

One specific bug that changes how you use the app

The app has a white screen bug on iOS 18. That is documented. The changelog mentions it. "Bug fix for iOS 18, where initialising the app was showing a white screen." That bug is significant. When a driver opens the app, they see a white screen. Nothing else. No login screen. No menu. No buttons. Just a white screen. The app is frozen. The driver cannot do anything. They have to force-close the app. They have to restart it. Sometimes the bug reappears. Sometimes it does not. The bug was fixed in a recent update. But the fact that it existed is telling. It suggests that the app is not thoroughly tested. It suggests that the development process is rushed. That is a concern. The app is used by professional drivers. They rely on it to do their jobs. A white screen bug means they cannot work. That is not acceptable. The app has other bugs too. Crash fixes are mentioned in multiple updates. "Crash fix when handling photos." "Fixed an issue where the on-site check triggers late after the device wakes from sleep." These are not minor issues. They are functional problems. They affect the core workflow. The app is a tool. Tools need to work. This tool has cracks. And those cracks are visible to anyone who uses it long enough.