The TomTom Navigation SDK is a toolkit for developers, empowering them to build location-based apps complete with turn by turn navigation.
What does this do for drivers?
The Navigation SDK prioritizes the device experience of drivers, by providing mobile-first support, regardless of whether they choose Android or iOS.
TomTom’s truck routing is also included and helps drivers on their journey, but also during planning. Parameters – such as height and width, axle weight and cargo types – unique to each vehicle within a fleet can be included in a driver’s planning. These key pieces of information can make a huge difference where route planning and adjustment are concerned. For example, HAZMAT loads are restricted on certain roads and tunnels, bridges, and more can make some routes impassable for certain cargos. Factoring this in when routes are planned can be a boon when routes have to be adjusted on the fly.
Real-time traffic information can support drivers by accounting for habitually congested areas. This information helps provide an accurate time-to-leave to plan their day and incident information to avoid accidents along the way.
Using the Navigation SDK allows fleet company back offices to easily keep track of each driver’s route –, the driver then doesn’t need to make as many manual updates and check-ins. Fleet managers also have faster access to tracking their assets in case of an emergency.
What does integrating Navigation SDK look like for developers?
Mobile development with Navigation SDK is supported in Kotlin for Android, and Swift for iOS.
Some libraries are difficult to learn, which creates long adjustment periods and slower ramp-up times for development teams. TomTom’s developer experience for Nav SDK aims to get around that and to do so, it includes modules which focus on existing key mapping components:
Structuring development in this way creates a low learning curve, especially for developers migrating from using TomTom’s APIs to using the Navigation SDK.
Creating a quick integration experience should keep the strain of shifting navigation tools to a minimum. For developers, adopting the SDK with its full UX means a faster, easier transition to a more powerful solution. It also makes debugging far easier, too.
Ramping up a new navigation experience
Solving fleet drivers’ and managers’ problems is key to keeping our world moving, but the challenge certainly doesn’t end there.
The key to continue solving their problems is to keep creating useful, accessible and powerful navigation tools. The Navigation SDK’s flexible component structure means swifter development, making it easier for engineers to make these tools.
We must also keep making it easier for drivers to use and adopt the tech too. In doing so, we can take the load off fleet managers so that they have less to keep track of, instead of more eventualities to plan for.