Google Navigation
Google is currently developing a truck routing navigation service in its beta form. We have partnered with Google to integrate their truck routing APIs into the DRIVE app, enabling in-app navigation for our drivers. J.B. Hunt drivers will be among the first to use Google's Truck Routing services, while still having the familiar design of DRIVE.
The Problem
Truck drivers require specific Department of Transportation (DOT) approved routes when navigating to their destinations. J.B. Hunt previously subscribed to a third-party navigation service provided to drivers on J.B. Hunt-owned devices. However, many third-party navigation services offer limited functionality. One critical feature for drivers is the ability to view satellite imagery on the map. This feature is essential for them to inspect customer locations and safely navigate into the customer's lot. Since third-party apps lack this functionality, drivers resort to using Google Maps for navigation due to its comprehensive features. However, this poses a major issue as it has led to accidents, as drivers sometimes navigate on non-DOT-approved routes when using Google Maps.
The Value
By integrating Google Truck Routing into the DRIVE app, we provide essential functionality that drivers require while navigating to a customer. This integration allows us to offer navigation seamlessly within the DRIVE app, eliminating the need for drivers to switch between different applications. Drivers can access directions on any device with the DRIVE app installed. By ensuring that drivers have access to the necessary navigation features, we can reduce accidents and enhance job completion safety and efficiency. Additionally, partnering with Google enables us to leverage a familiar navigation service for our drivers, facilitating the adoption of the new navigation system.
The Process
Research and Discovery
-
A year before we began this project, we began researching and gathering user sentiments around truck routing and navigation. We started with a survey that was sent to drivers within the DRIVE app. The driver response to this survey was the largest response amount we had ever received. 1,529 drivers completed the survey, which gave us a good amount of data to provide quantitative data for this project. In the results below, you can see that 962 of the 1,529 drivers prefer Google Maps as their go-to navigation app. For the open answers to question 11, the most entered reason for selecting Google Maps as the go-to navigation service was because of being able to see a satellite view of the map, real time traffic updates, and multistop navigation. Ultimately, the driver feedback on their preferred navigation is why we decided to pursue a partnership with Google as they are developing a truck routing application.
Understanding the Requirements
For this step, we worked very closely with the business to understand what we were trying to achieve with this project. The business had a 100+ page PDF breaking down all of the aspects they wanted to consider doing. We had to work as a product team to narrow down the list to what we would try and achieve in the first iteration. We had to work very closely with Google during this step to understand what functionalities their Commercial Navigation APIs we capable of. The image on the left is from the MIRO board I used during one of our meetings with Google. We walked through various Navigation softwares so we could visualize and note the functionalities Google has available.
Google API Breakdown
Before I could start designing, I had to review Google's Navigation API documentation to see what would be possible to do. I had to work closely with a Google developer to gather screenshots of what their APIs visually provided.
Design
For the design of this project, we aimed to maintain parody with Google while also preserving the familiar look and feel of DRIVE. To achieve this, we modeled the overall layout on Google Maps. To ensure design consistency with the rest of DRIVE, we utilized our mobile design system for all components. This enables drivers to quickly recognize and utilize the map without feeling like they've transitioned to another app. It's important to note that the map itself cannot be modified; it is directly provided by Google and must adhere to their design standards. However, there are a few customizable elements, primarily limited to color.
This project resulted in one of my most complex design files. There are numerous nuances that must be accounted for. Failing to address even one of these instances could potentially confuse a driver during navigation and lead to an accident. Due to the paramount importance of safety in this project, we had to collaborate closely with J. B. Hunt's Safety and Legal team to ensure every scenario was thoroughly covered. Below is an image displaying approximately half of the various scenarios that needed to be addressed.
Changing Requirements
Although we established what we would do for the first iteration, the requirements were constantly changing. I knew this would happen going into the project so I did my best to future proof the designs. They were easy to update and shift as sweeping changes were made. One of those changes was the addition of being able to search for loads and managing a trip sheet.
Establishing the Pilot
Working with our Product Owners, Product Managers, Business Analysts, Safety Representatives, Google Developers, and DRIVE Developers, we were able to establish what we would be attempting to build for the initial pilot phase of this integration. The key features we are focusing on for the pilot are Turn-by-turn truck safe navigation to assigned stops, Map type adjustments, Text to speech while in active navigation, Load profile selection, and Hazmat routing. Future features that will be added as Google develops its APIs will be Navigation to points of interest, multistop navigation, Feedback on routes, Seeing approved fuel stops along routes, and Safe routing for radioactive hazmat loads.
Results
This project is currently in development and will undergo extensive testing during a pilot phase. The integration of Google Navigation will be tested with a select group of 10 drivers, all of whom have accumulated over a million miles of safe driving. We have opted for experienced drivers for the initial testing phase because, in the event of any navigation issues, they will be adept at identifying safety flaws promptly. Additionally, their familiarity with other navigation services will enable them to offer valuable feedback for product enhancement. The initial pilot is scheduled to launch in the winter of 2024.