But that has nothing to do with implementing RCS in the Messages app. People act like SMS evolving into something better is bad for Apple users.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple to Adopt RCS Messaging Standard for Better Interoperability With Android Devices
- Thread starter MacRumors
- Start date
- Sort by reaction score
It will go through whatever servers provide the end user with their RCS connection. In the US that is now Google as T-Mobile was the only carrier that managed to get their own RCS servers off the ground, and they just announced they're shutting them down and switching to Google Jibe. In other countries it's likely the carrier's servers.
??? How is being compliant with the actual standard for a messaging protocol seen as sabotaging features/projects? On the contrary...
Sure standards can be improved, but let's improve the standard and not just do it and deviate from the standard
This would make sense as soon as RCS covers all the features available in iMessage. When this happens Apple would have to implement features twice.
Same is true for lot of Apples proprietary. Take Metal. Apple wanted to decouple from open standards like OpenGL and Vulkan, hardening the bars of its wallet garden. But now Apple wants to focus on gaming and invests a crazy amount of time to port DirectX/OpenGL/Vulkan Games back to Mac - since no one in the world cares about Metal.
Apple/Cook is completely wrong here. One way would have been to give the users a system that works perfect, like perfect messaging, perfect OpenGL/Vulkan implementation or a perfect CUDA version for machine learning. But Apple took the way to lock its users in, but all of this is starting to fail.
E2EE is not part of the RCS standard. Apple will only implement it if it becomes part of the standard.
As I said, it may be cross-compatible, that's probably going to be up to Google. But yes, if your provider isn't implementing RCS, it won't matter if Apple enables it, you won't "have" it. Your provider has to utilize it on their end and your device has to utilize it on your end both in order to use it.
Like most business decisions, choosing one option over another is rarely due to one fact. It could very well be because both are true. Standard protocol is a safer option and it also has the benefit of maintaining feature superiority for iMessage. As long as Apple makes a serious effort to advance the standard I don't think it's necessarily a problem. If they put their weight behind it, they could get e2e encryption added to the standard in relatively short order. If however they're content to slow walk the situation and let it sit in committee to die, that is a problem.??? How is being compliant with the actual standard for a messaging protocol seen as sabotaging features/projects? On the contrary...
Sure standards can be improved, but let's improve the standard and not just do it and deviate from the standard
No different to SMS in that regard. Someone has to operate the system that drives it.
Exactly. SMS had to be adopted by carriers and devices for it to work. RCS is no different. Right now, for instance, ATT has Google's RCS implemented but not UP. So if Apple drops support tomorrow, it won't do me any good as ATT hasn't implemented it yet.
That’s not going to change. RCS messages are still going to be green.
What “low quality stuff” are you talking about? All this is is a messaging protocol.
This is a weird complaint. You think a platform being better for its users is a sign that it’s dying? There was lot stacked against Windows Phone that had nothing to do with messaging interoperability.
I’m not sure I follow the logic here.
E2E is not part of the standard. But with Apple working directly with the standards group, it will be.
There’s the uphill battle of regulatory interest that doesn’t want E2EE, who will also have input into the standard.
Might not be as easy as that. We already have governments wanting to unravel existing E2EE systems, I can’t think they are going to give their blessing to make RCS E2EE so readily.
The industry doesn't have to have the blessing of the government, at least in the US.
RCS is a standard ultimately controlled by a private organization (GSMA) and implemented by private companies. While some governments are screamed ng about e2e encryption, the reality is that the world has already moved to that position. The GSMA moving the standard there doesn't move them beyond where everyone else already is. It puts them in the same place. If governments do manage to unravel e2e, then everyone would be in the same boat.
They do need to advocate on policy and regulatory decisions made by governments. Plus the GSMA members themselves may wish to advocate against E2EE if it goes against their own interests, so it won’t just be as plain sailing as Apple swooping in and declaring the RCS universal profile will support E2EE; they will likely receive resistance and pushback from other GSMA members. Although Apple’s boot up their arse might make it happen.
Last edited:
The issue is all three wireless carriers in the United States are using the Google standard for RCS messaging not the RCS Universal Profile. This is just another example of Apple intentionally gimping a feature/service they did not want but were forced to.
I used to follow “new tech” content on YouTube or podcasts, but, even though I do follow some tech news still, I mostly stick to retro tech content these days. It’s a lot more chill and less sh(r)ill.
This is precisely the issue. Android phones are far superior in every way. I just use iPhone for the locked down experience.
In this case, it’s less NIH and more CBA (Controlled By Alphabet), which would be a valid reason for many companies to avoid it, let alone Apple.
Surely the problem here is the use of an industry standard with proprietary extensions? Apple can’t gimp features that don’t exist in the standard.
Exactly. If iPhone has such a low overall marketshare, then why is the EU considering any of Apple's services to be an essential service? SMS works and so does Telegram and WhatsApp. There is no market dominance for failure here. It's about Google being unable to break into the premium mobile market. This has NOTHING to do with consumer choice. It's about breaking AMERICAN tech firms' business model because the EU has no tech.
