Apple gets nothing from CarPlay that they would need anyone for anything. It's a feature, like Android Auto, that makes their users happier. The manufacturers needed Apple and still do.Because Apple needed them, then. Not now. I mean it is pretty clear the difference to most people.
So the difference between what people think 2.0 does and what it actually does is that it skins the UI, not takes it over. The manufacturer still builds that skin themselves, it could even look identical to the screen without the skin. The only reason this is done is because that skin can interact in sync with the phone, so CarPlay elements aren't limited to a window but can be put anywhere on the screen. Like, an app could come along that adds a widget to the dashboard...and that app could be made by the manufacturer. And the manufacturer could even charge for that app. And mine data from it.It seems like it's taking over the interface including the instrument display. Maybe I don't understand what's different about CarPlay 2.0. They aren't taking over the car, just a lot of the user's interaction with it, which is where they hope to mine the data.
The EV's own maps do a poor job of looking for charging spots across all the different networks. Apple Maps does it a lot better, Google Maps in Android Automotive only grabs a couple of networks unless you install more apps - and the manufacturer needs to make those apps available. It's a pain in the butt, and I'm experiencing it right now since my new car doesn't have CarPlay available yet. Even plain old CarPlay can do this, so I'll be happy when just that comes along.But what exactly is Apple Maps providing that isn’t already in the built-in navigation? Last I checked, prioritizing looking for charging spots is already handled by the EVs.
Such as? Any assets beyond “mobile device centric” functions? I gather manufacturers would design assets in order to have a UI that does not clash with their own aesthetic. If these assets are simply "CarPlay" versions of built-in vehicle functions, why have more than the built-in one if the reason for designing an iOS version of it is to fit in with the vehicle? If the assets are mobile device functions, how far do manufacturers need to go? Does "messaging" stop with an asset for iOS Messages? What about other messaging apps?
The whole thing just sounds like extra, sometimes possibly redundant (as in built-in vehicle functions) work for the manufacturer for little end-user benefit and even less benefit to the manufacturer.
So the difference between what people think 2.0 does and what it actually does is that it skins the UI, not takes it over. The manufacturer still builds that skin themselves, it could even look identical to the screen without the skin. The only reason this is done is because that skin can interact in sync with the phone, so CarPlay elements aren't limited to a window but can be put anywhere on the screen. Like, an app could come along that adds a widget to the dashboard...and that app could be made by the manufacturer. And the manufacturer could even charge for that app. And mine data from it.
The only thing that would hold up manufacturers, from what I can see, is that they need to do work to make it happen. And it is likely a little overwhelming for their developers to understand from a high level. And that is likely why Apple released the training style videos at WWDC, they make it much more clear what this is and how it works.
I was my company's contact to Microsoft for our app's inclusion on the Windows desktop. They definitely felt like they could tell us how our application looked under normal use, messaging, etc. I went in thinking this was going to be a cakewalk and sort our icon color, style, text, but MS had to be beaten back with a stick with their "suggestions" of how to make our app fit their design motif.Maybe if Apple was not so arrogant can manufacturers would be more receptive?
This always seemed like a weird push for me.
So the difference between what people think 2.0 does and what it actually does is that it skins the UI, not takes it over. The manufacturer still builds that skin themselves, it could even look identical to the screen without the skin. The only reason this is done is because that skin can interact in sync with the phone, so CarPlay elements aren't limited to a window but can be put anywhere on the screen. Like, an app could come along that adds a widget to the dashboard...and that app could be made by the manufacturer. And the manufacturer could even charge for that app. And mine data from it.
The only thing that would hold up manufacturers, from what I can see, is that they need to do work to make it happen. And it is likely a little overwhelming for their developers to understand from a high level. And that is likely why Apple released the training style videos at WWDC, they make it much more clear what this is and how it works.
Take a page out of Apple's playbook and own the whole widget, that's what Tesla and Rivian do. I wouldn't want to rely on Apple for CarPlay fixes and enhancements given their lousy track record with carplay and some of their first party software.Honestly, and I have no great love for the car makers, they are smart to not buddy up with Apple on this
Apple are bullies who are famously hard to work with and dictatorial and arrogant
If one does not "need them", I'd not work with Apple on anything given their track record
CarPlay does not compete with Android Automotive. In fact, Android Automotive makes CarPlay 2.0 possible - makes it even easier to accomplish.
AAOS does not provide what CarPlay does, it's extremely bare bones.
What happens if you forget your phone? What comes up on all those screens? Does your car still work? I often leave the house without my phone.
What are you even talking about? Android Auto is phone projection, like carplay, what you’re thinking of is Android Automotive, which is a full on OS running on the car’s hardware. Carplay 2 is still phone projection, “Apple OS” isnt a thing to be “completely locked down”, Apple doesnt make an equivalent to Android Automotive. No one is shutting Apple out from that, they arent trying to enter that part of the market to begin withFunny, because Apple currently controls ZERO cars.
AAOS controls a bunch. My Volvo runs fully off AAOS... GM is using a forked version of AAOS and shut Apple out all together. Several others on that list and more adopting.
What's intresting is NO ONE wants Apple at that party, which is telling. Android Auto is still somewhat open where any Apple OS is completely locked down.
What are you even talking about? Android Auto is phone projection, like carplay, what you’re thinking of is Android Automotive, which is a full on OS running on the car’s hardware. Carplay 2 is still phone projection, “Apple OS” isnt a thing to be “completely locked down”, Apple doesnt make an equivalent to Android Automotive. No one is shutting Apple out from that, they arent trying to enter that part of the market to begin with
That and. Cutting out a large swathe of people who don't own an iPhone probably also figures prominently in. Why would someone pay for what will likely be part of a feature package including CarPlay 2 if they do not have iPhone? Where's the incentive? Reducing car functionality for someone that doesn't have an iPhone seems like a poor business decision too. I'm not sure where Apple can reasonably go here.What happens if you forget your phone? What comes up on all those screens? Does your car still work? I often leave the house without my phone.
None of this is "for the consumer" -- they all just want to control the information, the tracking and the money
Funny, because Apple currently controls ZERO cars.
AAOS controls a bunch. My Volvo runs fully off AAOS... GM is using a forked version of AAOS and shut Apple out all together. Several others on that list and more adopting.
What's intresting is NO ONE wants Apple at that party, which is telling. Android Auto is still somewhat open where any Apple OS is completely locked down. Google and Car makers can play nice - car makers can form and customize AAOS however they like, and Google is much easier to collaborate with.
Did you even read my reply?
Did you even read my reply?