MRA Nav and Android Auto
Brian Martin last edited by
Will MRA Nav work with android auto at anytime? I understand it works with apple play!
@matt-flaming, That's definitely NOT the case. Both Apple end Google kept their stores closed for competing navigation products. Apple gave the strive up somewhere late last year I believe, Google followed somewhere middle of this year. At a time the roadmap for the coming time had already been established. Therefore development of Android Auto compatibility has to wait. It is definitely not a matter of favors.
(This info is distilled from this communityforum, I do not have any inside knowledge)
PAD 0 last edited by
@matt-flaming As an iOS app user, my experience tells me that there is no particular favour either way on MRA’s part. Rather, the Navigation app is sadly lacking for both it seems. I don’t know what's going on, but much has been promised yet very, very little has been forthcoming in terms of functionality or improved user interface.
It is definitely not a matter of favors.
That's weird, because in another thread the team has said that iOS gets the updates first...
That's literally the definition of prioritization.
I think you did not understand the rest of my message. It is simply not possible to develop an app for a platform that does not allow to develop an app. So if it is anyone prioritizing anything, it is Google in this case.
Delores K Staples last edited by
This post is deleted!
Delores K Staples last edited by
Drabslab last edited by
I guess that it comes down to a huge conflict for a relatively small company like MRA between investing - and putting their resources into - in their own roadmap, and following the unpredictable "wishes" of a diverse user community.
If MRA wants to have navigation software that stands out, it has to ensure that it is 100% compatible and interoperable with its route planning software. Too some extend this may mean that it has to finalise its re-design of a number of core functions of the routeplanner first, before starting on updating the depending functions of the navigation software.
I prefer that they take their time and get a mature product instead of a speedy patchwork leading to difficulties afterwards. Also, I prefer a company that believes in its own product, and goes its own way, above a company that jumps on each and every hype instead of delivering real value.
However, what is missing in this story is a decent communication from MRA itself. Clearly, many people on this forum are stressed out by not receiving any news and that is bad for a company claiming that they take communication with the user base very seriously.
Maybe a blog from the owner on this not so trivial subject is more than due?
Drabslab last edited by Drabslab
My tickets have gone MONTHS without any updates, or confirmation that they have even READ the tickets. All I can do is assume they don't care about NAV at all.
This is an old pain. I have also experienced how a ticket can be unanswered for years ... and then suddenly disappears from the support system.
I guess the ball is in the MRA camp now?
With other words, those with diect access to the staff, or the staff itsefl, could provide an answer.
Hello, this is what i know at this moment.
MRA Navigation is currently under evaluation within the Team, depending on the evaluation decisions are made regarding development.
MRA Navigation doesn't currently work with Android Auto, that is because we had a lot of difficulty getting access to the development environment. Secondly, after this years' improvements to stability and bugs we're currently reevaluating the way forward for our Navigation app in all possible aspects. That means branding, User Interface, connectivity to the core MRA Routeplanner service and the positioning of the not-to-be-forgotten MRA Mobile app.
@Matt-Flaming I'm sad to see that you remain extremely unhappy with the app, especially, since if my memory serves me right, the performance on your end was improved some time ago and we also refunded you for the entire experience.
"My tickets have gone MONTHS without any updates, or confirmation that they have even READ the tickets. All I can do is assume they don't care about NAV at all." I'm forwarding this to the support team, this should not happen. If you don't get an answer from them you can send me a personal message. It might take days for me to respond, as I sadly don't spend as much time on the forum as I used to, but I'll escalate it further.
MRA Navigation is currently the secondary product of MyRoute-app, by far. That's true. It's userbase and resources are a fraction of the planner and from a commercial point of view I understand your belief that we would prioritize the planner over the navigation app. On a day to day basis, that's true. Most of our resources go into MRA Routeplanner, but as I've outlined above, we strongly believe that mobile applications are the future of our positioning as a company in the smart mobility revolution. It is a goal of MyRoute-app to cater to a much larger audience using the Navigation app then we currently do.
PAD 0 last edited by PAD 0
My tickets are labelled ‘In afwachting van uw antwoord’ which, if I’m not mistaken, means ‘pending your reply’. This is incorrect. What is correct is that, after many months, the balls remain very much in MRA’s court, awaiting action from them to rectify issues. This includes one that has considerable potential to give rise to death or serious injury. Apparently, no one within MRA gives a damn? Perhaps being faced with legal consequences might provide some motivation.
Thank you all for your concern and input!
I would like to draw attention to what Timo had said about Android Auto: “MRA Navigation doesn't currently work with Android Auto, that is because we had a lot of difficulty getting access to the development environment. Secondly, after this years' improvements to stability and bugs we're currently reevaluating the way forward for our Navigation app in all possible aspects. That means branding, User Interface, connectivity to the core MRA Routeplanner service and the positioning of the not-to-be-forgotten MRA Mobile app.” *
In addition, I noticed in several messages that there is a lot of uncertainty about the tickets;
We try to respond to a ticket within 48 hours. For some problems/questions we need additional information and ask the user. It is also possible that the user encounters a bug, we will communicate this back and pass this on to the programmers ("Secondly, after … all possible aspects" *). Ofcourse we want to help the user as quickly as possible, but some things take longer than others.
In addition, “pending your reply” means that a message has already been sent to you and that we are waiting for your reply.
Lastly, it can happen that a ticket is closed, this is done automatically by the system when the user has not responded to a ticket for too long.
I hope this has brought some clarity, and for the people who have not yet received a response to their ticket I would like to receive the ticket number (You can also send this in another ticket with the name 'Rosalie' added). I will then see if I can get you up to date. Sorry for the inconvenience.
@pad-0 I would like to receive your ticket number (You can also send this in another ticket with the name 'Rosalie' added). I will then see if I can get you up to date. Sorry for the inconvenience.
@matt-flaming I would like to receive your ticket number (You can also send this in another ticket with the name 'Rosalie' added). I will then see if I can get you up to date. Sorry for the inconvenience.
Matt, I meant what I said. I’m not telling you to shut up. I said that I’m sad that you’re still unhappy because I was under the impression that we fixed your performance AND refunded you for a bad experience. Moving forward from that impression, you can imagine my surprise at hearing about an “extremely unsatisfied customer” on the forums that “absolutely required an elaborate reaction” by me, only to find out it’s you . Sorry if that wasn’t clear to begin with.
Out of thousands of satisfied users using MRA Navigation there is a small percentage that’s experiencing issues. The vast overwhelming majority is able to use MRA Navigation exactly as marketed: as a replacement and/or back-up Navigation app. Look around, there are plenty of people who are essentially saying “I’m having a good experience with MRA Navigation”. Of course that’s less than the amount of voices on a forum going “This is crap”, because that’s what people on forums tend to do. The difference between us and other companies is that we don’t sterilize our communication channels from dissenting voices. For some this makes us look bad, because we don’t remove criticism or force it to go elsewhere where it’s less likely to be seen.
Now I want, and I know you want this too, to have a good conversation about this subject with the people that are least happy in our community. I don’t have a magic wand, but based on your previous dealings with us I hope you at least have the confidence that I take what’s being said seriously and do what I can to give a clearer view of the future of MRA Navigation. To tip that off: in the coming weeks we’ll publish a clear roadmap for MRA Navigation in the same way we have for MRA Routeplanner. Our support team is also going to use your examples to review their answers and the way issues are presented to the management.
MRA is a company nowhere near in size to TomTom, OSM or even Sygic. The fact that we’re being compared with those companies is a compliment in itself, since it’s what we aspire to, but again, we’re nowhere near their capacity at this time.
For those unsatisfied with MRA Navigation or having unresolvable issues at this time our policy remains equitable and clear: we will refund you and hope to welcome you back at a later time.
Anyone with remaining questions or remarks can send them to me or the support team directly. (I usually answer in a few days). For now, the discussion has devolved far from the original topic so I'm locking this thread.