Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Honestly, most likely by way of a lacking technical comprehension, I fail to understand why RCS is such a pain in the computerulo and why it has to be turned on in the first place.

If it’s this…”intricate” and dependent on so many factors on both sides of the tin cans, by way of my same lacking technical knowledge, KNOW that a small change on either side will eventually break basic functionality of RCS.

So I can’t see how this is better for humanity and why Google did it this way? Why not just…you know..make a universal app a la WhatsApp that isn’t carrier dependent, but device agnostic.
(paraphrasing) I don't understand how this works, so it can't be complicated for people on different platforms with different codebases implementing a poorly defined standard should be so hard. I mean if Google takes the RCS spec and fills in all the blanks needed to make it operate between a single codebase in their implementation, well people on different codebases that cannot just use Google's implementation (legally and technically because Android & iOS don't use the same languages) should be able to make all these things that I don't understand work (/paraphrasing).
 
Honestly, most likely by way of a lacking technical comprehension, I fail to understand why RCS is such a pain in the computerulo and why it has to be turned on in the first place.

If it’s this…”intricate” and dependent on so many factors on both sides of the tin cans, by way of my same lacking technical knowledge, KNOW that a small change on either side will eventually break basic functionality of RCS.

So I can’t see how this is better for humanity and why Google did it this way? Why not just…you know..make a universal app a la WhatsApp that isn’t carrier dependent, but device agnostic.
That’s already been done, and it’s called WhatsApp.

This is why I don’t understand what problem RCS is trying to solve. Cross platform, device and network agnostic messaging is a solved problem. RCS does not add anything to this.
 
Why are the mobile networks taking so long to provide this configuration? iOS came out months ago now.
You assume that all networks have loads of people competent in configuring and debugging RCS just hanging around idle... It could also be that they need to dialog with Apple's RCS team and that they are already busy debugging with other networks.
 
If that describes your issue, then it's not RCS itself at fault, but Apple's "network fallback" logic not fully handling that situation of a non-working Wi-Fi (LAN/WAN) connection.
Apple's network fallback logic still has legacy baggage from when Apple first designed it (ie, to work well with Airport access points, not so well with third parties).
 
Now you can see why Apple proceeded cautiously with implementing RCS support. The protocol is a mess. Hopefully Apple's involvement will bring improvements.
The protocol works fine on Android phones that have had it for the past few years. It is only Apple's implementation of the protocol that is a mess. It would seem that Apple has forgotten how to implement standards or work in a multi-platform environment, because every time they try, they fail pretty miserably.
 
The protocol works fine on Android phones that have had it for the past few years. It is only Apple's implementation of the protocol that is a mess. It would seem that Apple has forgotten how to implement standards or work in a multi-platform environment, because every time they try, they fail pretty miserably.
The Android implementation uses Google’s version of RCS, not the standard RCS. That’s why it works on Android.

If Android phones used the standard version of RCS they’d have the same problems.
 
The Android implementation uses Google’s version of RCS, not the standard RCS. That’s why it works on Android.

If Android phones used the standard version of RCS they’d have the same problems.

Would they? I suspect they wouldn't be using a six year old implementation of RCS, like Apple is choosing to do. A lot has been fixed and changed since then.
 
Would they? I suspect they wouldn't be using a six year old implementation of RCS, like Apple is choosing to do. A lot has been fixed and changed since then.
The reason RCS works so relatively well on Android is because Google is controlling the technology behind the scenes, the same way Apple controls the technology behind iMessage.

However, this defeats the point of RCS, which is to have a cross-messaging platform that is NOT controlled by one of the technology giants and is instead controlled by the mobile networks, the same way SMS is.
 
The reason RCS works so relatively well on Android is because Google is controlling the technology behind the scenes, the same way Apple controls the technology behind iMessage.
Hmm. TIL that only Google Pixel and Nexus devices support RCS.
 
The reason RCS works so relatively well on Android is because Google is controlling the technology behind the scenes, the same way Apple controls the technology behind iMessage.

However, this defeats the point of RCS, which is to have a cross-messaging platform that is NOT controlled by one of the technology giants and is instead controlled by the mobile networks, the same way SMS is.

Google built their own RCS servers because the carries were dragging their feet. Once everyone is up and going, I suspect Google will offload to the carriers.

Again, it doesn't explain why Apple is using a years-old version of RCS.
 
  • Like
Reactions: gusmula
That’s already been done, and it’s called WhatsApp.

This is why I don’t understand what problem RCS is trying to solve. Cross platform, device and network agnostic messaging is a solved problem. RCS does not add anything to this.
Some don’t want to use the app and don’t feel safe with their data on the app
 
It’s also why RCS can’t really get off the ground; there’s no incentive or need to make it work.

Plenty of people here (US) do care, and there is incentive. Almost all the MVNOs now have support, and the big three carriers have since iOS18 was released. Zero to full carrier support in less than a year isn't too bad, no?

I wish WhatsApp was more popular here (and in Canada), but it's just not. Plenty have never heard of it, or if they have, install it and then see that none of their contacts are using it.
 
Plenty of people here (US) do care, and there is incentive. Almost all the MVNOs now have support, and the big three carriers have since iOS18 was released. One year for full carrier support isn't bad, no?

I wish WhatsApp was more popular here (and in Canada), but it's just not. Plenty have never heard of it, or if they have, install it and then see that none of their contacts are using it. On my phone, of my 192 contacts, 5 are on WhatsApp.
That just means the USA becomes an RCS silo whilst the rest of the world uses something else.
 
Yes I believe the carrier profile is administered by Apple but ultimately controlled by the network themselves. The carrier profile tells the phone what features the network is capable of I believe.
Huh, I don't like the sound of that. I don't think Apple should be able to gatekeeper network carriers.
 
That just means the USA becomes an RCS silo whilst the rest of the world uses something else.

That's fine; it's been that way with iMessage for years and no one really cares.

I'm just happy to have RCS...I text a lot of Android users daily. I checked my WhatsApp, and of my 292 contacts, 5 are using it.
 
  • Like
Reactions: NoGood@Usernames
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.