Navigation SDK Demo App

The main screen of the Navigation SDK application contains the SDK Init and Dispose sections along with the current status. The rest of the main screen consists of usage examples.

Information

We recommend analysing the examples along with the source code. Contact Us to Get Access.

The initialized SDK provides information about location and speed, and enables navigation. It is essential for the proper functioning of the rest of the SDK.

The following screens are only available after initializing the SDK. Otherwise, attempting to select the next screen will result in a toast message being displayed with the following information: "SDK not initialized. Proper initialize first".

Important

The initialized SDK is active between activities.

The screenshot below shows a correctly initialized SDK, ready for further work.

If errors occur during SDK operation, they will be visible in the "Errors" section.

Standalone navigation launcher

This navigation activity is available immediately after connecting the SDK. It contains basic information about navigation functionality and non-customizable views for this activity. This is the quickest way to add navigation to your application. The downside is that you cannot customize the appearance to suit your needs.

The views and map displayed in the activity are available outside the SDK. Users can utilise the views displayed in the SDK on their own screens, with the option to customise them according to their preferences. See Embedded map and Building blocks

Embedded map

This activity shows a map without background navigation. Current speed data is available, as well as the option to enable position tracking and control day/night mode. The view is built from compose components (see Jetpack Compose), and the map is embedded in a fragment. The flat key icon opens the debug panel.

The view below shows the debug panel. It contains information about the current SDK status, a list of errors, and the current navigation status.

Embedded navigation

The Embedded Navigation screen shows how to launch navigation and then navigate using the views provided with the SDK. Below is an example of how to select a navigation destination. After clicking "Go", navigation will begin routing to the selected point. The flat key icon opens the debug panel.

After setting the navigation, the application will display a map screen with the route drawn, allowing you to view the data provided by the SDK for that route on the panels. Available navigation data: Retrieving navigation data

The screen also allows you to launch the debug panel. It is divided into two parts.

The first shows the current status of the SDK, navigation, and a list of errors.

The second allows you to quickly change the automatic route recalculation, control the visibility of slowdowns on the route, and force route recalculation. The ‘force’ flag cancels the ongoing event (if it exists) and tries to perform a new one. If false, it tries to perform the event if there is no ongoing one (rejects otherwise).

Building blocks

The components available in the SDK enable customization, including changing the color of individual sections of the panel. See details UI

Example bars with speed, speed limit, maneuvers, distance, lane assistant and ETA.

Custom components

Using components from the SDK is not the only way to display data provided by the SDK. You can create your own component and then use the SDK to feed it with data. The example below shows simple panels displaying speed, distance, and ETA data. Available navigation data: Retrieving navigation data

Send diagnostic report

The screenshot below shows an example of a dialog box created for sending diagnostic logs related to the SDK. Users have the option of adding a description of the problem. Once sent, the report is analyzed on our end and corrected where possible. See: Report sending

Security notice

Reports are automatically deleted after 30 days.

We automatically collect data relating to the SDK ONLY.