To be fair, on this particular point, you aren't Apple's customer in this scenario. This is like complaining that Tesla has supercharger stations and your non-Tesla has a different charging connector, so your interactions with Supercharging stations is degraded. This really wouldn't be Tesla's problem.
Apple supports the video standards that were available via MMS/SMS when iMessage rolled out, the higher res videos only available in the first place because Apple added it via iMessage. The newer 'standard' was a Google dominated way of trying to make inroads on Apple's superior implementation and in most of the world, Messages isn't even the top Messaging app.
Now that Apple has announced support for RCS incoming, even including messaging in the suit doesn't make sense in the slightest.
> The newer 'standard' was a Google dominated way of trying to make inroads on Apple's superior implementation and in most of the world, Messages isn't even the top Messaging app.
The RCS standard was is just about as old as the iPhone and older than iMessage. Google began supporting and pushing the standard forward in a way that benefits everyone. Apple could have done the same, or made iMessage an open protocal or any of a number of things. Instead Apple has consistently chosen to go the anti-competitive route.
> Apple's superior implementation
It was 'superior' in some ways inferior in other ways, such as communicating with people without an iphone. iMessage isn't particularly better than any other messaging app, but the benefits of user lock-in, and being the default, replaceable sms app. These anti-competitive behaviors do clearly harm users.
> Now that Apple has announced support for RCS incoming
Perhaps once the support actually lands you'll have more of a point. However, I expect half-assed support and the bare minimum given Apple's previous reluctance.
>To be fair, on this particular point, you aren't Apple's customer in this scenario.
Yes, but my mother, who wants to text a video to her sons to share a moment from her day, is, and Apple prevents her from doing that. There is no way to spin this as anything but Apple being openly user hostile to anyone who wants to communicate with an android user.
("She can just-" No, she cannot "just". My mother is in her 60s, and she shouldn't have to learn a workaround to use a basic feature of her phone that just works on android.)
I suppose that really depends on where you are in the world and how phones are used. Sending video works over WhatsApp here, and nobody uses anything telco or native for that (so no iMessage, MMS or RCS). Next one down would be FaceBook Messenger and then apps like LINE, Telegram and finally Signal. iMessage, MMS and RCS don't even make the list, including the entire 12 to 70 age range.
> To be fair, on this particular point, you aren't Apple's customer in this scenario.
But Apple's customer is also affected, in two ways:
1. I then have to text the person back, asking them to re-send the video using another chat app, or emailing a link, or something like that. That's annoying for the iPhone user.
2. In the other direction, if I didn't know better, and I tried to send a video to the iPhone user, it would end up looking like crap for them. That's not a good experience for the Apple customer.
> The newer 'standard' was a Google dominated way of trying to make inroads...
Not sure why "standard" is in scare quotes; it's an actual standard, whereas iMessage is just some proprietary thing Apple made. And it's not newer: RCS is from 2008, which is older than iMessage, and almost as old as the iPhone itself. Likely work on the standard started before the iPhone's release.
> ... on Apple's superior implementation
This is of course a matter of opinion, but to me, any protocol that is locked down, with the owners refusing to enable interoperability, is by definition inferior, regardless of its other merits.
> Apple has announced support for RCS incoming
And we'll see how that goes. If Apple works with Google to enable full interoperability, including E2EE, I'll be pleased. Anything less, though, and it'll feel like Apple is just doing the bare minimum to try to avoid regulatory action. It also remains to be seen as to how much Google cooperates in the other direction. The RCS E2EE stuff is a proprietary Google extension; hopefully that gets made into a public standard as well.
The bottom line, though, is that Apple doesn't interoperate until they believe that they're going to be legally forced to. At least if they get in ahead of the regulatory action, they can do their implementation more or less on their own terms. It's a smart move, but IMO is also scummy.
The thing that has always baffled me about Apple keeping iMessage iOS-only, and not supporting RCS, is that they've been hurting their own customers with this stance too. Plenty of iPhone users live with a degraded, less-private experience wen communicating with non-iPhone users, or have to remember to use a different chat app when conversing with certain contacts. This makes a lot of Apple's rhetoric (in general, not just regarding messaging) about protecting user privacy feel a bit hollow at times. Clearly their primary motivation for the privacy stance isn't to protect users, it's because they believe it gives them a competitive advantage.
Google's RCS isn't the standard-RCS. You can't use Google's RCS without using Google's RCS servers and you can't run your own. You can run your own standard RCS, but it's not compatible and does not do the same things either.
Apple supports the video standards that were available via MMS/SMS when iMessage rolled out, the higher res videos only available in the first place because Apple added it via iMessage. The newer 'standard' was a Google dominated way of trying to make inroads on Apple's superior implementation and in most of the world, Messages isn't even the top Messaging app.
Now that Apple has announced support for RCS incoming, even including messaging in the suit doesn't make sense in the slightest.