Justice Department officials are in the late stages of investigating the iPhone maker, focusing on how Apple has used its other products and services to defend against threats to its core business.
The thing is, there are versions of all of these (Cast, any number of messaging clients) that have broader compatibility already. They just tend to be locked out of Apple’s ecosystem and Apple has its own versions that lock everyone else out of there’s.
These systems would be so much more friendly for the consumer if everyone just worked together but this insistence on keeping these things siloed just makes it worse for literally everyone.
Wanna share your video on the TV at my house? Oh you have an iPhone? Oh,
Yeah your gallery can’t Cast. I want to share a video at yours? Oh, you have an Apple TV so I can’t Cast to it and Airplay doesn’t exist in my gallery or OS.
This only hurts consumers. And the only people it’s helping is the manufacturers selling you Google TV/AppleTV via suckers that buy both.
Meh. Airplay is like CarPlay. Modern TVs support both Android and iOS casting. Just like most modern cars support both Android Auto and CarPlay.
There are apps you can get for devices that allow you to AirPlay to them as well if they don’t already support it. I got one to AirPlay to my Xbox for example.
I wouldn’t mind an open standard for casting. But both Google Cast and Airplay are currently proprietary. Maybe something will come out of the Matter standards board that everyone can adopt.
Meh. Airplay is like CarPlay. Modern TVs support both Android and iOS casting. Just like most modern cars support both Android Auto and CarPlay.
The key is, most. Not all. And there are still two standards. It is taking more development time and complexity to support this, and therefore, not all car manufacturers nor all TV manufacturers are doing this. It’s still a problem, you’re just arguing semantics of whether it’s the consumers problem or the middle-man’s problem who will end up thrusting the cost upon the consumer anyway.
Either way, it’s extra dev time, complexity, room for things to go wrong, things to think about, different interfaces on different devices, etc. This just doesn’t need to exist and provides no benefit to the end consumer.
There are apps you can get for devices that allow you to AirPlay to them as well if they don’t already support it. I got one to AirPlay to my Xbox for example.
Of course there are. There have been for years. But again, see above. This is just more complexity and shit for you to deal with. And another app for someone to manage. And another thing to go wrong. And something else that needs to be updated when Apple devices to change something.
It’s not beneficial to you. At all. It’s another stumbling block. You can argue about it’s size, but it literally gives zero benefit to the consumer and has no need to exist.
It is, but it’s still an extra device that covers one of the options. It’d be obviously better if one device just supported a shared protocol either phone could use.
Absolutely agree. At least in chromecasts case, it’s an open protocol, and Apple apps can choose to integrate with it. But of course, none of the 1st party apps do
The thing is, there are versions of all of these (Cast, any number of messaging clients) that have broader compatibility already. They just tend to be locked out of Apple’s ecosystem and Apple has its own versions that lock everyone else out of there’s.
These systems would be so much more friendly for the consumer if everyone just worked together but this insistence on keeping these things siloed just makes it worse for literally everyone.
Wanna share your video on the TV at my house? Oh you have an iPhone? Oh, Yeah your gallery can’t Cast. I want to share a video at yours? Oh, you have an Apple TV so I can’t Cast to it and Airplay doesn’t exist in my gallery or OS.
This only hurts consumers. And the only people it’s helping is the manufacturers selling you Google TV/AppleTV via suckers that buy both.
Meh. Airplay is like CarPlay. Modern TVs support both Android and iOS casting. Just like most modern cars support both Android Auto and CarPlay.
There are apps you can get for devices that allow you to AirPlay to them as well if they don’t already support it. I got one to AirPlay to my Xbox for example.
I wouldn’t mind an open standard for casting. But both Google Cast and Airplay are currently proprietary. Maybe something will come out of the Matter standards board that everyone can adopt.
The key is, most. Not all. And there are still two standards. It is taking more development time and complexity to support this, and therefore, not all car manufacturers nor all TV manufacturers are doing this. It’s still a problem, you’re just arguing semantics of whether it’s the consumers problem or the middle-man’s problem who will end up thrusting the cost upon the consumer anyway.
Either way, it’s extra dev time, complexity, room for things to go wrong, things to think about, different interfaces on different devices, etc. This just doesn’t need to exist and provides no benefit to the end consumer.
Of course there are. There have been for years. But again, see above. This is just more complexity and shit for you to deal with. And another app for someone to manage. And another thing to go wrong. And something else that needs to be updated when Apple devices to change something.
It’s not beneficial to you. At all. It’s another stumbling block. You can argue about it’s size, but it literally gives zero benefit to the consumer and has no need to exist.
And here comes Matter.
https://www.macrumors.com/2024/01/09/amazon-unveils-matter-casting/
At least in Google case, chromecasts are super cheap. I have bought several for relatives to make the above scenarios easy
It is, but it’s still an extra device that covers one of the options. It’d be obviously better if one device just supported a shared protocol either phone could use.
Absolutely agree. At least in chromecasts case, it’s an open protocol, and Apple apps can choose to integrate with it. But of course, none of the 1st party apps do