Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It’s not a standard, it’s a protocol Google advocates, why would you expect Apple to help with making its competitor’s technology a standard? Apple has its own technology that it wants to make an industry standard, Google doesn’t help with any of those, either.
It's a standard, just like the GSM, 3G, 4G, 5G radio standards and SMS are. The standard is owned by the GSMA, not Google.

Anyone can develop an RCS client or service, although getting it qualified for interconnection and being permitted to use their marks involves money and talking to the GSMA.

End to end encryption is layered over the top of the standard and is not yet part of it, but the details of implementation are published and theoretically could be implemented by anyone.
 
  • Like
Reactions: RigSatMe
RCS is a protocol, but Google Messages is a service that utilizes Google servers.
Nope.

Google *do* provide a fall back to their own RCS service when using Google messages (Samsung also use the same fallback in Samsung messages) if your service provider does not provide an RCS service.
 
Definitely think Apple should add it to the messaging app. This would silence the “iMessages for Android” drumbeat for a while and probably be a goodwill gesture for regulators. While RCS will be feature rich, I’m sure Apple will still make sure iMessage is a more pleasant experience all around. If Google and Apple really push for RCS implementation, I feel carriers worldwide will have no choice to comply, which is when WhatsApp should start worrying.
 
Why Apple should? iMessage has it all. RCS is another piece of crap.
RCS is a vendor neutral standard.

If your phone's voice system was implemented the same way as iMessage you would only be able to talk to other people who were also using iPhones and you would have to buy your telephone service from Apple.
 
Definitely think Apple should add it to the messaging app.
Don't think there's a technical problem for Apple to implement RCS support into the Messages app. The only hard part would be to decide on the colour bubble :p.

I vote yellow ... heh heh, to keep with the existing theme.
 
Wow, that's a lot of Android fans here on MR, now that's a surprising development /s

I've had two back and forth previous posting reply enjoyments with Android fans regarding data privacy security. I really enjoyed it. It's easy to enjoy a conversation when the facts, that are publicly known, are on my side. :)
RCS is a GSMA standard. Not specific to Android.

These are publically known facts (actually heavily advertised ones in the telecoms industry).
 
Between individuals. Group messages not yet supported. There's no switch to turn it on or off: if both devices support it then you get E2E encryption.

It's implemented over the top of the RCS standard (it's not currently part of the standard).

So when you send a message there’s no way to know ahead of time if it will be e2e encrypted? Or does it indicate somehow?
 
And here it goes again with 'it doesn't matter, they all do it, it is all the same' misinformation. You putting it in a new way "our stuff isn't really private with either" was mildly clever though. A good sugar coating of the same verifiably bogus claim.

1. Yes, total privacy is not currently possible. So why bother, they're all the same. The huge degree and breadth of difference in data privacy compilation doesn't matter at all. They'll get something, you can never be private -- "our stuff isn't really private with either".
2. Yes, an app you choose to install and open almost certainly will collect a category or another of privacy data. So "our stuff isn't really private with either". Sure, the ability of the app on one platform to then track you very widely across all other apps -messaging, maps, call log, contacts etc etc doesn't matter.
3. "It's not like Google is hiding it"? They certainly don't hide in their P/L the huge data monetization as an advertising revenue line item. The more privacy data they collect the bigger that line item, their by far biggest line item. Certainly their consistent terming of privacy data collection as "user experience" as well as fighting one's ability to see and delete the massive data collected(see EU for that) -- yes, Google certainly is honest and open. I'm sure every average user knows how much private data Google collects. Honest as it comes.
4. The general point of Apple just started doing it, Well there you go, it's only been a year or whatever. I think it was early 2019 when they let Facebook know and Facebook then wanted to make Apple feel pain". Sure, it is odd you noted Google's honesty virtue while questioning Apple's motives because it was only recent -- especially when your point is they're all the same. Maybe Apple will one day be honest about it like Google, right.

Here's some shade for you all. iPhones are not superior to Android phones in every way. Android based have advantages. Up front cost clearly one of them. Far more models to choose from. If you like to do internet based App installation, there is another markedly clear advantage. But on privacy data security, Apple walks away in this category. The two aren't even in the same ballpark, period. You can dress your responses up all you want (and based the history of replies from 'they're all the same' posters, I expect any from you should be interesting). What it factually and indisputably won't contain is evidence that privacy data security 'is the same'. Apple runs away with the victory in this category. Those arguing otherwise just do not like that indisputable fact.
1. You have too much time on your hands.

2. I never said privacy wasn’t better on iOS vs Android all I said is that it’s still not totally private and was whole lot less private with how much data third party apps could collect until recently with iOS 14. Is it more private than Android known for tracking you for ad purposes? Especially since iOS 14? I would think so? My point was it’s not totally private and was less private not that long ago so a lot of your info has already been collected so your privacy is already compromised. Does that make sense?
 
So when you send a message there’s no way to know ahead of time if it will be e2e encrypted? Or does it indicate somehow?
In Google messages there's a little lock icon that appears in the conversation and on the send button and a small banner appears in the conversation to tell you if you are chatting securely (or not, if that changes).

Other implementations (if there are any) may present differently.
 
One of the reasons it’s a great product is iMessage. Why should Apple abandon that? If you want to communicate with Android users you can, people are free to pick right now. Apple not porting iMessage to Android does nothing to prevent anyone from buying an Android device. It’s a choice based on preference and weighing the pros and cons, not a gun to someone’s head.
At this point it is Apple who are forcing fallback to a very insecure communication protocol (SMS) if someone chooses to hold a conversation between an iPhone and an RCS supporting device (not necessarily Android).

They don't need to abandon iMessage to fix that.
 
Definitely think Apple should add it to the messaging app. This would silence the “iMessages for Android” drumbeat for a while and probably be a goodwill gesture for regulators. While RCS will be feature rich, I’m sure Apple will still make sure iMessage is a more pleasant experience all around. If Google and Apple really push for RCS implementation, I feel carriers worldwide will have no choice to comply, which is when WhatsApp should start worrying.
That would be good for end customers, and solve a serious security issue forced on people when an iPhone becomes involved in a conversation between RCS supporting devices.
 
it’s still your voice clear as day and people were listening to these interactions. Sorry that’s not totally anonymous to me anyway.

Its still not the same as what Google was doing either. You may have objected, but that doesn't mean its the same thing.
 
At this point it is Apple who are forcing fallback to a very insecure communication protocol (SMS) if someone chooses to hold a conversation between an iPhone and an RCS supporting device (not necessarily Android).

They don't need to abandon iMessage to fix that.
If customers are concerned about message security they have options other than RCS. Nor is Apple the only ones not supporting RCS, its not even available in many countries. And if security was a concern, why did it take so long for Google to include E2E encryption in RCS?
 
  • Like
Reactions: ian87w
That’s because it is not a standard and Apple hasn’t positioned it as one. It’s a feature of the iPhone (and now macOS). Why should Apple just give away a competitive advantage it has over Android/Google?
Because the alternative, fall back to SMS, has serious unfixable security flaws that affect everyone (including iPhone users) as soon as an iPhone becomes involved in a conversation with non-iPhone devices.

Those green bubbles don't just mean non-iMessage, they mean insecure message.

Right now the RCS standard only improves that by requiring encryption between your phone and the RCS message store of your service provider, but that is still a huge improvement, but E2E encryption can be (and is, if using Google messages) layered over the top of that. The expectation is that this will be adopted into the standard, but even if not the method used in Google messages is publically published and implementable by others.
 
Wake me up when RCS is internationally supported by 100% of all operators around the world, and that it is supported by every OEM's default SMS app. Right now, there's no point in complaining about Apple not supporting it when majority of Android users around the world don't even use it.
 
The RCS standard includes multi device support.

It seems Google's implementation does not support this capability, but when using Google messages there is a web client that talks direcly to the phone (similar to WhatsApp for web) that you can use on other devices (desktop pc, iPad, other phone, etc)
What a seamless and easy to use experience, Apple should get right on that...


Between individuals. Group messages not yet supported. There's no switch to turn it on or off: if both devices support it then you get E2E encryption.

It's implemented over the top of the RCS standard (it's not currently part of the standard).
So the "standard" doesn't even ACTUALLY enhance user security. But Apple is the one holding it back?
 
What a seamless and easy to use experience, Apple should get right on that...

So the "standard" doesn't even ACTUALLY enhance user security. But Apple is the one holding it back?
It's not seamless experience. First, not all carriers around the world support it, and not all OEM's support it either on their default SMS app. So the first thing a user have to do is change their default SMS app to Google's messenger. That alone is already a huge barrier for normal folks.

Why bother with Apple when majority of Android OEMs don't even support it? Google doesn't even care if Android OEMs use it.
 
If customers are concerned about message security they have options other than RCS. Nor is Apple the only ones not supporting RCS, its not even available in many countries. And if security was a concern, why did it take so long for Google to include E2E encryption in RCS?
Customers have other options (such as Signal) if they are aware of them. However many people just stick with the default apps.

RCS is still a significant security improvement over SMS even without E2E encryption layered over the top.

My suspicion is that Google only provided an E2EE solution due to market pressure (simply to avoid the accusation of not having it), but have made sure it can be implemented by anyone to exert the same market pressure on Apple (because now it becomes Apple making conversations insecure).

And yes, this is still rolling out around the world (but note, it is not limited to Android, there are implementions for other operating systems- there are even RCS clients that run on iOS devices, although none available in the Apple app store)
 
Wake me up when RCS is internationally supported by 100% of all operators around the world, and that it is supported by every OEM's default SMS app. Right now, there's no point in complaining about Apple not supporting it when majority of Android users around the world don't even use it.
Do you speak to everyone around the world, on every operator?

Thought not.

Maybe not everyone can have security because this is not fully adopted world wide, but at least some people can have some security.

Apple can choose to participate in that. Or not.
 
Do you speak to everyone around the world, on every operator?

Thought not.

Maybe not everyone can have security because this is not fully adopted world wide, but at least some people can have some security.

Apple can choose to participate in that. Or not.
Do you ignore other e2e encrypted services that is platform agnostic like Whatsapp and Signal? The problems that RCS is trying to solve have been solved already, thus there's little interests on RCS from operators and OEMs.

I don't mind people or Google promoting RCS. But pointing a finger at Apple is silly as majority of Android users around the world don't even use it. If Google wanted RCS to be successful, Google should be making it a requirement for GMS certification. That way all Android devices will have to support it by default.
 
  • Like
Reactions: Jakuta
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.