Daniel Palm last edited by
So, back in August it was announced that Google opened Android Auto to outside navigation apps like MRA. Is there an expected release date for the Android Auto compatible MRA Navigation?
No not yet
Mr Mark Melbourne last edited by
Any more news on Android Auto, more bikes are getting this feature.
Bert van Es last edited by
In the mean time other routing applications besides the ones that are owned/made by Google work with Android Auto, like TomTom Go (paid), TomTom Amigo (free), Flistmeister(free) and probably others as well.
When will there be a Android Auto compatible version of MRA?
Con Hennekens last edited by
Android is kind of a second class citizen for most products for some reason.
It's more like Google is a second class company when it comes to application support for other applications than there own... As I understand it, they were the ones not coming forward, not MRA.
Con Hennekens last edited by
It's more like Google is a second class company when it comes to application support for other applications than there own...
It's been available for a few months for other applications...this isn't on Google this time. They were told it was coming, they could have been prepared.
Maybe someone from MRA can explain to you how much effort they have put into convincing Google (and Apple) to let them into their car platform. Google (and Apple) have been holding off for years...
Alexander n last edited by
@Hans-van-de-Ven-MRA-Master is hier misschien nu al iets meer over bekend?
Nee, nog niet
I'm not going to reiterate the amount of effort we put in getting access to either platform, that information can be easily found here on the Forum. We're aware of Android Auto now being available for development and will certainly add the feature in the future, but we' re not going to drop everything we've planned so far because Google suddenly decides to open up. That wouldn't be fair to everyone who's waiting for other features.
If Android comes across as a second class platform, that's likely because it handles like a second class platform. I recently switched back from iPhone to Android because I didn't want to sell my soul for a small piece of hardware (which is a whole other ballpark of problems) but so far the experience has been subpar compared to iOS.
From a more philosophical point of view: I think it is absurd that developing for two platforms requires two completely different skill sets, different development capabilities and in the end, different people. I sincerely hope for the convergence of technology to the point where developing apps is no longer the hassle it is today.
To illustrate, a group we're all forgetting is the WinPhone community. The small percentage of users doesn't justify the possible risks. However, that doesn't mean it wouldn't be nice to include those users too.
Android is an operating system designed to run on a lot of devices. There's a reason why developers prefer iOS, and i'ts because the development pipeline is far more streamlined than for Android. To illustrate: Android completely overhauled the way GPS signals are handled by the device in a relatively recent update (I believe Android 10), which can cause app breakage. In addition to this Android gives smartphone manufacturers freedoms in handling how GPS is used per device. Of course, if you have a company that's Android-only and caters to that group alone, they're going to have an advantage over a company developing on both platforms. That still doesn't make it as good as a platform as iOS for development purposes though.
You can't find any transparency about Android Auto because there were no talks. We reached out several times. We ended up talking to two parties. Apple and the European Anti Trust agency to file a complaint against Google for anti-competitive behavior. After that we put it to rest and moved on.
As for outsourcing our app development, we do. We're very happy about that too, because we used to have in-house app development capacity and know the strains and problems from that affair. Funds aren't allocated to "one project at a time" but projects are procured against a Fixed Price invoice. We could simply open up the existing project planning and request that the app developers just drop everything they do and start working on Android Auto (in fact, during a meeting today I mentioned that Android Auto is something we'd be interested to explore after the current batch of projects is completed). However, as you might understand, I can't do that with good conscience.
@Matt-Flaming I understand that, the reason I'm conservative with planned features is because I don't want to create the wrong expectations regarding the MRA Navigation timeline or an Android Auto timeline.
I do think there might be a small misunderstanding here: all of the features (except of course Apple Carplay) are for both platforms. We also don't atlternate resources between development and "bug hunting". Instead they're paralel processes. Each week, at least 12 hours are dedicated to "accute" problems and bug squashing, like the issues you're experiencing in Android. Because, again, we'd rather have those criticisms here on the Community Forum where we can see them and do something about it, rather than in some hidden corner of the internet. To illustrate: your points helped us actively track down several issues, and raised awareness that while our app might be 96% crash free, that doesn't mean it's going to be useable for everyone. A navigation app stuck in demo mode is useless. There's no denying that. The recalculating route and demo-mode bug are now a top priority for the app development team.