The LocationKit API provides a unified library across platforms and devices that can be used to request location information.
VZ Navigator provides a developer interface which allows applications to execute commands such as navigating to a destination. The API requires the following functionality to be added to a caller application:
- Platform-specific discovery code to verify that VZ Navigator is installed
- Code to build the App2App URL needed to control VZ Navigator for navigation
- Platform-specific code to launch VZ Navigator using the App2App URL
NBI provides a much simpler interface to VZ Navigator. The NBI API consists of a discovery function (isNavigationAvailable) that does the job of verifying the presence of VZ Navigator and a navigate function (navigateTo) that builds the App2App URL and launches VZ Navigator to do the navigation session.
There are advantages for using NBI vs. VZ Navigator App2App, which include:
- Turn-Key: A developer using NBI will probably want to use the simplified MapKit API, as it requires very little effort and is guaranteed to work properly
- Sample Code for using the VZ Navigator App2App
Note that the VZ Navigator App2App API provides additional functionality other than navigation. While it is outside the context of NBI, an application may want to use the extended VZ Navigator App2App functionality instead of NBI and take advantage of VZ Navigator’s feature set. For obtaining this information, please contact us directly.
You can leverage either MapKit directly or VZ Navigator navigation App2App using the following:
With NAVBuilder Inside, it is all about choices!