There are many different map and navigation apps available for Android devices and we cannot possibly test them all. If you want to check how well apps on your phone or tablet work with Furkot, open this page on your Android device and use intents listed below.

If you want to test Android apps' support of GPX files use these instructions instead.

If you want to test launching Apple iOS map and navigation apps use these instructions instead.

Android apps cooperate with each others by declaring intents. Furkot launches apps by issuing intents and Android system finds apps that match those intents (Common Maps Intents, Google Maps Intents). When there is more than one app you may see a list of matching apps to select from.

Intents below marked america correspond to location of the Boston Public Library (address: 700 Boylston Street, Boston, MA 02116, USA, coordinates: 42°20'58.1"N 71°04'39.9"W). Intents marked europe correspond to location of the Eiffel Tower (address: Champ de Mars, 5 Avenue Anatole France, Paris, France, coordinates: 48°51'30.1"N 2°17'40.1"E). Expected behavior when clicking on each intent in the web browser on Android phone is either automatic opening of map and navigation application or a list of applications capable of showing and/or navigating to the location. Selecting application from the list should result in action described for each intent.

Intents supported in Furkot ¶

Furkot issues a different intent for each combination of its Navigation Apps selection and the navigate button. To test, open this page on your Android device and click the intent links below.

1. Google Maps, next to Coordinates

Expected behavior: an app should display directions and/or start navigation from the current location to the location above. Only coordinates are passed; destination name and address may be different than the name and address above. Works with Google Maps, OsmAnd.

1. Google Maps, next to Stop address

Expected behavior: an app should display directions and/or start navigation from the current location to the address above. Only address is passed; destination name may be different than the name above. The location of the destination is calculated from address by the navigation app and may be different, sometimes drastically so, than the actual stop location set in Furkot trip plan. Works with Google Maps.

3. Google Maps, next to Route

Expected behavior: an app should display directions and/or start navigation from the current location to the location above passing a series of points approximating the route. Works with Google Maps.

1. Default Map App, next to Coordinates

Expected behavior: an app should display the location above on the map. It may also display directions and/or start navigation from the current location to the location above. Only coordinates are passed; destination name and address may be different than the name and address above. Works with Google Maps.

1. Default Map App, next to Stop address

Expected behavior: an app should display the location above on the map. It may also display directions and/or start navigation from the current location to the address above. Only address is passed; destination name may be different than the name above. The location of the destination is calculated from address by the navigation app and may be different, sometimes drastically so, than the actual stop location set in Furkot trip plan. Works with Google Maps.

Intents considered for the future versions of Furkot ¶

You may have a map or navigation app installed on your Android device that doesn't respond to any intent above. There are several more possible intents that may work with it. If that's the case and you let us know, we may consider adding it to the future version of Furkot2Go. To test, open this page on your Android device and click the intent links below.

1. Alternative way of passing coordinates to Google Maps

Expected behavior: an app should display the location above on the map. It may also display directions and/or start navigation from the current location to the location above. Only coordinates are passed; destination name and address may be different than the name and address above. Works with Google Maps, OsmAnd.

2. Alternative way of passing address to Google Maps

Expected behavior: an app should display the location above on the map. It may also display directions and/or start navigation from the current location to the location above. Only address is passed; destination name may be different than the name above. The location of the destination is calculated from address by the navigation app and may by very different than the actual stop location set in Furkot trip plan. Works with Google Maps.

3. Alternative way of passing coordinates to Default Map App (map intent geo:)

Expected behavior: an apps should open map centered on the location. Map center should have coordinates the same as location but may or may not be marked in any specific way.

4. Intent for Google Navigation

Expected behavior: an app should display directions and/or start navigation from the current location to the location above. Only coordinates are passed; destination name and address may be different than the name and address above. Works with Google Maps.

5. Google Maps with coordinates and label

Expected behavior: an app should display directions and/or start navigation from the current location to the location above. Name is passed in addition to coordinates; destination address may be different than the address above.

6. Default Map App (map intent geo:) with coordinates and label

Expected behavior: an app should display the location above on the map. It may also display directions and/or start navigation from the current location to the location above. Name is passed in addition to coordinates; destination address may be different than the address above. Works with Google Maps, OsmAnd.