Meet the world's first HTML5 voice-guided, turn-by-turn navigation API for mobile developers and publishers. It's an effortless browser-based service and offers revenue sharing for US addresses.
The award-winning navigation technology that powers Scout for consumers on smartphones, computers and cars is now available to mobile developers and publishers with Scout for Apps. Scout for Apps is the first HTML5 service that allows you to offer users an exceptional, voice-guided turn-by-turn navigation experience with just one click to any address or location - for free. Including a Scout Drive-to button on your mobile content can help create a seamless experience that keeps users engaged, involved and coming back for more.
Need an ad-free version? No problem. Contact us to discuss how we can best help your business.
Third-party mobile applications, websites and emails often contain content with location that can be enhanced with voice-guided turn-by-turn navigation. All you need is a URL wherever you have location based content.
Here's an example of the product experience:
Use these simple steps to integrate Scout for Apps with your location-based mobile content.
Note: Resize the Scout Button to fit your mobile site or app but don't change the aspect ratio or alter the button in any other manner.
|token||Your token||Required. Must be URI encoded to work. E.g., if your token is "AQAAATS1a5IIf//", then the URI-encoded version will be "AQAAATS1a5IIf%2F%2F"|
|dt||Address||Street address. e.g., "950 De Guigne Dr." Street address should be combined with city/state or postalCode. See Example B. Required to display during navigation|
|Lat , lon||DESTINATION COORDINATES: This field describes the
latitude/longitude of the destination address.The latitude/longitude is specified as a String. For example:
37.373846,-121.999036The lat/lon can be provided after the address followed by an "@" with an address (Example B) or without an address (Example C).
|name||Name of the destination||Required to display during navigation. Every point of interest, whether it is a tourist attraction, event venue, or store, typically has a name. Passing this name will help Scout show the name to the user during navigation, upon arrival, and with their friends when shared.|
Note: URI-encode ALL the parameters within this URL. Be sure to pass name and address for the optimal user experience. See best practices below for more detail.
Invoking any of the above actions will result in launching Scout for Apps in a browser screen similar to the following:
When users push the Drive button, they will launch the navigation mode with voice-guided turn-by-turn directions.
If time spent within your app is a key metric for your business, consider embedding navigation to increase it. To maximize user safety, we allow a third party navbar with a maximum height of 44 pts. The remainder of the screen should be reserved for navigation to minimize driver distraction. To display the navigation experience that has been optimized for web view, add the following user agent string: TNS4A/1.0
Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5 TNS4A/1.0
We will also need a unique identifier to provide you with accurate session and unique user reports. This is especially important for developers licensing our ad-free service. Add a custom HTTP header, T-S4AID, with a unique id value generated by the native client, or add it as a parameter on the query string when invoking our API. It must be at least 32 characters long. This is similar to the device ID if you can retrieve the device id using the native client.
To provide the optimal user experience, we recommend the following:
The test key and token you are provided are rate limited and are designed to only work with our testing servers. You will need to submit your application for review by Telenav to obtain your production key.
Additional tips are available on our Forum.
To provide more information to the user during navigation, you will need to send us the name and address of the destination for display in the navigation destination header, especially when using coordinates to generate a route. Here is what the header will look like:
Coordinates Only Name & Coordinates(Better) Name & Address(Best)
Most mobile applications and websites have places of interest in a list and a landing page. The scout button can be used in either place. Here are some examples:
If you send automatically generated emails to your users, consider integrating Scout for Apps with any location based content. This can include travel itineraries, email marketing to local businesses, and real estate notifications. Here is an example of how to use the Scout button in an automatically generated email.
You can also simply hyperlink the address in your email.
Many developers already use Google maps to display custom markers, multiple markers on a map, and marker labels. If you'd like to continue using Google maps, we recommend the following:
Do not place the Scout Button on a Google Map. We recommend not placing the Scout button onto a marker Info Window. If you do not have a landing page for your InfoWindow, you may place a Scout button on the InfoWindow itself, using the following as an example:
Note: This button is slightly different than the buttons provided. Contact us by visiting our support page to obtain the button asset.
Not all code updates require recertification from Apple or Google. Always review the latest guidelines to verify when and if you need to recertify. Here are some examples of how you may be able to mitigate recertification.