You're lucky that you can even use that feature. I can't. It ALWAYS tells me that it can't login.
Posts made by Matt Flaming
RE: Android Auto
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
I wouldn't expect that exactly. It's just really disheartening to read that the planned features we have seen won't roll out for another 6 months. On this list includes Apple CarPlay support, so does that mean when Android Auto is worked on, that it will be another year away? When the new features on iOS rollout, resources will be dedicated to squashing bugs so what does that mean for Android? How long do we really have to wait to get matching feature sets?
It seems too disjointed and the development appears (just from an outsider looking in) to be moving very slowly on the Nav app. I simply don't see value in Nav at this time. We can't even seem to get the basics fixed (my ticket regarding complete and utter failure of the app).
RE: Android Auto
If Android comes across as a second class platform, that's likely because it handles like a second class platform.
Android itself is not the issue though. There are plenty of apps that work EXCELLENTLY in Android. The problem tends to come from developers that develop an app in iOS first and then "try to port to Android". If the app is built with Android in mind, it works marvelously. I find Locus to be an amazing map application, that is only available on Android. Look at OsmAnd. It was Android first, and then "ported to iOS" and it's a completely different app. I think it's good on both platforms, but excels on Android. If you're familiar with Scenic on iOS, they have been saying for years that they are working on an Android version...and those of us on the waiting list got an email this year saying "Well, sorry, not this year"..again. I see this with lots of apps that are "cross platform". If the app was designed in iOS first, the Android version tends to suffer horribly. Same goes, in general, the other way too though.
The notice was sent out to developers months ago indicating Android Auto support for 3rd party nav apps was coming soon. It seems that everyone would have jumped on that chance, yet it "APPEARS" that MRA sat on that and waited. Please note that I say it appears because I've searched around and not found any indication of any kind of transparency as to when talks were had about adding Android Auto.
After saying all this, I get the feeling that MRA just outsources its app development? Is this true? If so, does that mean that funds have to be allocated to one project at a time? Because in my mind, that explains the lag that seems to occur between the 2 platforms and why one is chosen focus at a time. When I see plans of a "new version" that seems to cater to iOS specifically, that's how it comes across. I mean, if you have 2 different sets of developers working on the different apps, then they should both be able to work at the same time. Right? In which case, you would have the Android team working on Android Auto, while the iOS team is working on Car Play.
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.
Windows Mobile (The OS) hasn't been supported in years, and the project was killed off. Why would you build ANYTHING for a dead platform? That's like saying that Blackberry OS needs a version too.
Personally, I would just be happy if the bugs were worked out on Nav, and a few key features were added after the fact.