Is there a specific reason why Tesla refuses to integrate CarPlay or Android Auto?
But really be careful how much Android you're talking about. There are some brands really using Google's automotive services; this is not our strategy. When you do this, you get a great package of function and services, no doubt. But you also have to open up all the car's sensor data [to Google], and when I say all, it really is all sensor data," Senger told me.
(statement from Christian Senger, mentioned by Ars as being VW Group's Digital Car and Services division)
Car manufacturers of luxury cars shy away from Android Auto partially because they believe it turns one of their main selling points and silos (advanced technology) into yet another commodity.
> which requires minimal integration with the vehicle
My guess: maybe VW is scared of a potential "which CURRENTLY requires minimal integration with the vehicle" (I imagine that the push for more and more integration will increase in the future) and therefore decided to give it a try now and not to become passively dependent on Google.
BMW allows carplay with a monthly subscription to the rest of their services, largely because they believe that as long as you're getting the full benefit of a connected car, you'll be attached to the value - strategically, it makes no sense for them to give it away from free.
The other thing? These companies are starting to change their mind as consumers demand it as a feature.
Although to be honest, if not for the unconscionable amount of money they (or Navteq, I guess) asks for map updates, I'd be even happier just using the built-in navigation all the time.
I don't even care that it requires USB.
Beyond just the normal controls (which can sometimes be hit or miss once you're in CarPlay/AndroidAuto mode) the extra little functionalities you notice are amazing. A good example is when using Google Maps I can zoom in/out by just pinching the touchscreen in the car, or I can use the physical dial (normally for changing radio stations) to control the zoom level, or scroll through selections. If you change contexts, what the physical dial control change along with them, and its really slick once you get used to it.
I didn't know until I saw it in my ex-sister-in-law's Alfa, but apparently there ARE CarPlay implementations that don't have touchscreens. That makes it much less easy, though still better than any automaker's.
What Tesla does is kind of irrelevant to us, though, since we're a 1-car family, and need to retain the ability to take long trips in areas with poor charger concentration. IOW, if we had 2 cars, one could definitely be a Tesla, but we don't need 2 cars.
But I get what you're saying.
Simple examples:
1) If you accidentally tell the car or the phone not to use CarPlay for a particular phone, there is no obvious way to get it to ask again
2) If you are connected to the same phone via Bluetooth AND CarPlay’s USB connection (...why does it even permit this to begin with??)... Wonkiness results
3) My S.O. refuses to use Waze on it because Waze’s own notifications overlay/BLOCK important elements of its own nav and are not trivially dismissed (do they even test these things??)
These are just off the top of my head in an Audi, hardly a run-of-the-mill car.
Try a Tesla’s UI for a while, and CarPlay will seem like garbage. It becomes very clear why they didn’t go with it. I only wish it had Waze on it, and then I could get rid of my phone mount.
part of the linux foundation
But yeah no nothing to do with data rights on Apple’s end, google does want more data though.
It was very pricey but I got a ProClip mount for my phone. Phone slots right in, automatically starts charging and Android Auto loads right up.
AA/Carplay will win in the long term, simply due to the fact that there's a larger market and app makers can publish their own apps. In other words, I can use Pocket Casts in my Chevy Volt, but need to use a phone screen + bluetooth audio in my Tesla.
I guess I would end up using my phone over Bluetooth, negating much of the benefit the large touchscreen in the Tesla provides, ending up fiddling with my phone to change songs etc.
People are going to point out the privacy issues inherent in using Android, and I understand the complaint, but Google already knows my speed and location at all times anyway just by virtue of having my phone on me. I don't think Android Auto would have any interaction with the cameras or sensors, since most other cars do not have them, but perhaps others can speak to this.
Regardless, this has really diminished my interest in getting a Tesla.
I have a long commute, the only thing that makes it bearable is choosing the content I listen to. The app makes a difference here - PocketCasts and Spotify have features that others don't - so I do want to use their native interfaces. The apps I use in the car have great Android Auto interfaces which simplify content selection. Using Android Auto also integrates with the other features on the phone, such as phone calls, calendar reminders, "OK Google", and maps. This essentially defines my entire driving experience at the moment.
If Tesla's interface doesn't support an app that I want to use (eg. Spotify) then I would have to resort to using the phone over Bluetooth. I wouldn't just say "oh well, I spent $50k on this car but it doesn't support PocketCasts so I guess I'll listen to something else for the next hour" every day. This makes the big touchscreen rather useless, and is going to be more dangerous than my current car because I will be fiddling with the phone.
Maybe I'll just get a big suction cup and mount my phone right on top of the touchscreen, using Android Auto on the phone itself over Bluetooth.