I would like to create a drivers screen where some useful information are displayed. I want to display navigation hints, but I don't want to program a whole navigation system.
Is there a way to access the current navigation hints from google navigation or any other free navigation app?
I prefer access to an android app, because I thought the easiest prototype would be an android app. But I'm thankfull for any information about it and how this could be achieved.
I would suggest checking if your use case is compatible with restrictions exposed in the Terms of Service of Google Maps API. Have a look at section 10.4.c (iii)
No navigation. You will not use the Service or Content for or in connection with (a) real-time navigation or route guidance; or (b) automatic or autonomous vehicle control.
https://developers.google.com/maps/terms#section_10_4
Related
i have create a tracking project using maps from Google on android kotlin, and i want to create more that user can go to somewhere with navigation (so there's two point, a current location point and destination point). i want to implement turn by turn navigation sdk from mapbox? is it possible to do that? have you build it before?
ya turn by turn navigation is tricky.Map box should make it easier though u just have to implement there sdk in your project and they also have docs on how to use the Map box sdk. only downfall is you have to pay for it.
i would advise if you are creating a personal project try creating a location listener and update current position of the device on a google maps intent. you can then just create your own navigation app ( its abit of a longer way around it but you would have more control over the navigation and plus its free)
I currently learning on the new Android Navigation Architecture Component (https://developer.android.com/topic/libraries/architecture/navigation/).
I kind of confuse with its motive and concept, here are my uncertainties:
Is Android Navigation Architecture Component designed to eliminate the need of using multiple Activity in a single apps? Which mean, the whole apps just need a Single Activity and all other page will be Fragment?
Does using Multiple Activities in the apps, but in the same time using the Android Navigation Architecture Component to navigate the Fragment actually violate the purpose of Android Navigation Architecture Component?
Example Scenario for Question 2:
In theory, the Navigation library supports any architecture you might want to use. Out of the box it can handle Activities and Fragments as navigation destinations, but you can plug in your own solution by implementing your own Navigator (as an example, see this article).
However, quoted / paraphrased from the Google I/O talk on Navigation:
What is my Activity actually meant to do?
Right now, some apps are very Activity-heavy, some are Fragment-heavy, or completely in a different system. We're moving towards a model where the Activity is more just an entry point into your app, rather than it being the owner of the content of your app. It's actually just going to store global state, for example global navigation like a navigation drawer or the bottom bar.
So Google does recommend having just a couple Activities for your app, because you only really need them to serve as entry points. For example, you can have one that opens from the launcher, and another that's opened by deep links. After that, when your app is started, you can do everything else inside it with Fragments.
To summarize and directly answer your two questions:
The Navigation Architecture Component isn't "designed to eliminate the need to use multiple Activities" per se, but it's something Google recommends doing when you're using it.
You can absolutely still use multiple Activities and multiple Fragments mixed together. You can even use a single Activity with purely View based navigation if you like. It's all up to you. If you find the Navigation library useful in combination with how you architect your app, use it.
The tooling of the library might not be that great for custom destinations (for example, the visual editor will probably only support Activities and Fragments for the time being), but you can use it however you'd like from code.
I tried navigation with Intents when user click on marker and it's work well. Problem is that I need implement that in my own app. (without opening GoogleMaps app)
How to start implement navigation from current location to markers in my own app without intents? Any help will be appreciated :)
You may use this library. It uses Directions API but in free plan it has limit to 2500 requests/day.
I'm working on a cross platform (iOS & Android) app that requires the user to follow a (possibly closed) path made of several destinations.
So far it seems that my best option is to find a way to open Google Maps with a URL like this: https://www.google.com/maps/dir/San+Jose,+CA/GooglePlex/San+Francisco,+CA
Besides the fact that such url opens the browser first and not the app directly, Google Maps doesn't enter the "navigation" mode.
I analyzed the SDK and there doesn't seem to be a way to instantiate a path with multiple destinations.
Is there a way to achieve navigation on multiple destinations in Google Maps? If not, any alternative with "navigation" mode?
Yes you can achieve navigation in multiple direction
1) in navigation map first it has been showing one direction , there your calling one api, check that api you will get multiple direction data, just you have to parse the all data by using loop and need to do custom implementation.
I recently used Talk back on an Android device. Some apps don't work well with the Talk Back screen reader because the it's not developed according to the accessibility API. Is there any way that I can access the UI of these apps (from OS level) and manipulate them to be compatible with Talk back?
No. Such change should be made in code. There is no way to modify it from OS level.
Those changes have to be made in XML or Java. User cannot access these values from system layer (security policy). You can refer to: Android Developer guidlines for accesibility. Without proper 'contentDescription' set TalkBack is unable to retrive any information about some views: images, imagebuttons etc.