Because the dawn of time, it seems, Tesla has remained steadfast in its decision to not support Apple CarPlay and Android Auto. That could be about to vary, as Bloomberg reports that Tesla is now actively developing Apple CarPlay support. The identical can’t be said for Android Auto, as Tesla is barely working on CarPlay right now.
In response to Bloomberg’s unnamed “individuals with knowledge of the matter,” Tesla’s implementation of CarPlay would run in its own window inside Tesla’s broader interface, slightly than replacing the complete system because it does on many vehicles. This is sensible, as Tesla’s operating system controls the complete automobile, not only infotainment, and CarPlay cannot try this. CarPlay Ultra might, but many manufacturers are shying away from it to maintain their very own systems on top of things, and it’s no surprise that Tesla would, too. While CarPlay support is currently in the event and testing phase, no rollout date has been determined yet.
Cratering sales are likely the rationale why Tesla has modified its mind. In response to Carscoops, a McKinsey & Co. study reveals that 25% of EV buyers and 38% of combustion automobile buyers will refuse to buy a vehicle that doesn’t support smartphone mirroring. It is also one in every of the optional features our readers said they cannot do without. Perhaps Tesla and its potential trillionaire CEO, Elon Musk, realized that they cannot afford to lose 1 / 4 of their potential buyers over this. If it’s desperate enough to start out renting cars off the showroom floor, adding CarPlay support doesn’t seem to be as much of a stretch.
Bucking the trend it set
Tesla just isn’t the one EV manufacturer that has refused to support smartphone mirroring, but it surely set the trend for others to follow. Competitor Rivian also doesn’t offer Apple CarPlay or Android Auto, though it recently added Google Maps integration in hopes you will stop caring. GM has jumped on this bandwagon hard, first dropping smartphone mirroring for its EVs, after which banishing it from all future models.
The explanation (or excuse, depending in your standpoint) for this has generally been that generic navigation apps cannot offer the mixing that native systems provide for true interoperability. Google and Apple Maps do not know the battery’s state of charge or estimated range, in order that they cannot route you to the perfect charging station along your route. From GM’s try to win us over:
…when the owner of a Chevy Blazer EV routes to an EV charging station, the vehicle’s native software can begin warming up the battery in order that it’s primed for a faster charge. That is a level of “holistic integration” that is unavailable through CarPlay and Android Auto.
Nevertheless, Rivian provides all this with its Google Maps integration. It is not mirroring, but it surely shows that it is feasible. So does Porsche, whose Macan now supports Apple Maps EV routing inside CarPlay.
Apple® Maps EV routing uses real-time vehicle information to assist customers navigate to their destination, recommending charging stops when needed. By analyzing elevation changes along the route and other aspects, Apple® Maps identifies appropriate charging stations along the best way. If a customer drives until the charge gets too low, they’re offered a path to the closest compatible charging station.
We do not know if Tesla intends to supply any EV-specific functionality like this in its integration, or if it’s going to simply provide basic CarPlay functionality to appease the offended villagers. What is evident, though, is that the corporate that set the trend, standing against smartphone mirroring at a time when everybody else embraced it, is now determining how one can integrate it. The excuse of “Tesla doesn’t, so we haven’t got to” isn’t any longer valid.
This Article First Appeared At www.jalopnik.com
