Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I don't think that's even a concern. To explain -- Dumbphones need to roll into LTE at a minimum here, and 5GNR over the next decade. There's no reason a straw sized data connection can't be added to what will be a mobile VOIP device (for lack of a better term, I guess) at the end of the day anyway, as the data will already be there to deliver voice. It's what drove the win for SMS - extra space available on what was already pinging the towers to maintain a connection.
There’s no technical reason. Then again, back before the iPhone, there was no technical reason you couldn’t connect a cable to your phone and load music on it that way (instead of emailing the files to yourself on your phone and being charged data fees). :) As it is, it’s highly unlikely that carriers will support an app based messaging technology on any non-app enabled dumbphone. Especially one that threatens to take away their SMS cash cow.
 
Yeah that's kind of obvious though isn't it? The solution depends on the person, and Whatsapp, a Google app, or even just SMS/MMS may be their valid solution. Of course this is only my personal use case scenario, but those solutions all stink for myself. But at least with Google RCS they can put it as a default Android app and drive adoption fairly quickly.

Another thing I haven't really thought about, but I'm assuming that 3rd party apps like Whatsapp could adopt Google's RCS also, making it more of a universal solution regardless of what app you decide to use. I honestly don't know from a technical perspective if this is possible, just brainstorming.
Almost no third party app can adopt Google RCS as Google doesn’t provide public APIs. The only exception right now is Samsung which struck some kind of deal with Google.
 
  • Like
Reactions: ian87w
As an ex-Android-user these are my observations: #1 I have no issues with Android and iMessage conflicts, although the functionality between them is not equal. It's okay, I can still communicate just fine. And #2 - Have you ever had Google give you a helpful MESSAGE that your Credit Card BALANCE was DUE on a certain day? Did you know they got that information from the email your Credit Card company emailed to your Gmail account? Do you believe that their other technologies are any more considerate of your privacy? #3. Ex-Android user experience: Google apps and Exchange apps very frequently have 'broken' functionality issues between them, which are NEVER resolved. It isn't an Apple issue - welcome to Android-land. Personally, I don't have any need to go back to Android's glitchy technologies!
I’ve never had Google text me, and why would Google text you about a bill that isn’t related to them?
 
I’ve never had Google text me, and why would Google text you about a bill that isn’t related to them?
It shows up as Google services notification, and as part of Google assistant. Google assistant can preemptively remind you of bills due and appointments from emails they scan on your Gmail. In my country, Google even struck a deal with the carriers so Google can notify me how much data quota I have used on my data plan.

If you never experience this, either you don’t use Gmail or you don’t use Google assistant, or you don’t use Android.
 
  • Like
Reactions: Unregistered 4U
It shows up as Google services notification, and as part of Google assistant. Google assistant can preemptively remind you of bills due and appointments from emails they scan on your Gmail. In my country, Google even struck a deal with the carriers so Google can notify me how much data quota I have used on my data plan.

If you never experience this, either you don’t use Gmail or you don’t use Google assistant, or you don’t use Android.
I’ve used Gmail since it was available and no, that’s never happened…..
 
I’ve used Gmail since it was available and no, that’s never happened…..
Are all your emails of bills, appointments etc on that Gmail? If you enabled Google assistant and the notifications in your Android, it would notify you. It's actually part of the feature of Google assistant. Unless of course you disabled it somewhere in the past, or not use Google assistant.
 
There is a simple way to explain this to people. Take an honest look at Google’s messaging “strategy”. Would a reasonable person believe in Google after they screw up, neglect, or cancel their projects? NOPE

I won’t even get into Google blowing their chance to buy WhatsApp. At the time Facebook paid an outrageous amount for WhatsApp, but it doesn’t seem so crazy now. They understood the value and Google didn’t.
 
Leverage against Apple. IMO, Apple would let them walk, painful in the beginning but Apple would then introduce their own search platform (they’ve been building for years) or adopt DuckDuckGo / Bing and never look back. Google needs iOS search $$$$$ much much more than it needs RCS compatibility.
If Apple launches their own search engine, I'll ditch Google in a heartbeat.
 
Actually, this is a good point. This is proof that RCS is nowhere near as widely supported/adopted as HTTP/HTTPS. No matter how much Google would want folks to believe that.

Support does not matter, density does not matter. If there is a better standard to use which increases security it should be used. It is a standard. Adoption or non-adoption of that standard means nothing. With every new standard that is released, there is always initially a 0% adoption rate. So it doesn't matter where the number is.

For example, if my site had only HTTP it would still be viable. The engines being used like Chrome, Firefox only in the last few years displayed warnings about using raw HTTP, but they'll still be functional. But like that technology I expect Apple to use the more secure protocol if it is viable.

Come to think of it, it would be just as viable if Apple displayed a warning when sending to Android (the green bubble). Apple touts that it cares about consumers and is all about privacy and security but does not state that those communications are not secure. Apple needs to use the standards and make them secure where it is applicable.

This argument and precedent has been set over decades. Standards are not there for people to say "but the dominant position should be used despite the standard, because the dominant position is just getting more dominant." If that were true, then IE would've never been dethroned as the dominant browser and it's non-compliance to standards. It took lawsuits for that to happen. The standards existed the whole time and were ignored.

In fairness, we can debate this all day - Apple has yet to issue a statement. They take no position on user security except to state that it's fine as long as it's on Apple. They don't care about the other 70% of the world, nor do they warn that when communicating with that majority, those messages are insecure by Apple's choice. That's what needs to be addressed.

Apple will end up selling 150 million or more iPhones this year. And, will just as likely end up selling 150+ million phones next year. That is, quite literally, how the world works. If, out of the 6+ billion people in the world, 5 billion are customers that are driven away from the iPhone, that STILL leaves plenty enough people for Apple to still sell another 150+ million phones in a year.

I love these arguments because it is pretty myopic. People are born, people die, the world is not simply a static metric of precisely X amount of people that have phones are deciding their phones. There are people who have no phones whatsoever who are choosing their platform.

IOS started as the dominant mobile platform and has lost overall market share over time, now representing less than 30% of the global market. It will continue to lose market until it adopts more open standards like these. Lawsuits arguing the adoption of open markets, predatory behaviors, closed systems, and forced payment systems are not good news, and people listen.

Android sells around a billion units a year, conservatively. As of 2021 the attrition of Android to Apple has slowed to nearly zero. The innovation has really stalled in the Apple space, and Android users are poised to grow in market share. The trends show this, and in some metrics, already do.

But the context of your response was that people will buy 150mil more iphones to solve issues like this thread. You have not proven that one iota. It's reasons like this thread that drive people away from Apple. Apple does not adhere to standards for the most part until they are forced to. This isn't a secret by far. And if your answer is "but more people use apple!" that's also not true.

You DO recognize, though that SMS being a standard that’s understood and accepted on ALL phones is 100% due to the fact that ALL CARRIERS support SMS, right? If all carriers didn’t support it, SMS wouldn’t be understood and accepted. This is the core of why RCS, even though it’s an evolution of SMS, is going nowhere. Because no carriers support it.
My carrier disagrees with you. It's a small startup called AT&T. Maybe you've heard of it?

And if a singular carrier supports RCS (which actually there are lots worldwide) then see the first point of the thread: It doesn't matter the density, it doesn't matter if zero carriers support anything. It's a standard. It doesn't need density. Saying it needs to be prevalent to be adopted is completely missing the point. USB 5.0 would never be adopted. But since there are only two players in this game, it's highly convenient that the 30% market share is being bullish about standards. Apple needs to make a statement, is really all that's being asked here. But they're not even coming to the table. They just don't care about the 70% market. I also posit they also don't really want to protect and secure the 30% trying to talk to the 70% either. That's just wrong. Apple needs to do something.

Apple is religiously and vigorously anti-standard. They will do whatever they can to be proprietary. It's actually served them very well, and I applaud it for the most part, but the truth is in an interconnected world it's getting very old and people are beginning to really see that. It is possible to be innovative on top of standards (reference: the entire logic behind Lightning vs USB-C). But you can't make as much money without proprietary cabling, closed stores, closed payment systems, closed peripherals, closed security, so they won't even address it. You must simply go all-in on Apple, and "people should just buy more Apple to fix this". Pretty insulting. It drives people away from the platform, not toward it.
 
  • Like
Reactions: Ludatyk and LD517
Support does not matter, density does not matter. If there is a better standard to use which increases security it should be used. It is a standard. Adoption or non-adoption of that standard means nothing. With every new standard that is released, there is always initially a 0% adoption rate. So it doesn't matter where the number is.

For example, if my site had only HTTP it would still be viable. The engines being used like Chrome, Firefox only in the last few years displayed warnings about using raw HTTP, but they'll still be functional. But like that technology I expect Apple to use the more secure protocol if it is viable.

Come to think of it, it would be just as viable if Apple displayed a warning when sending to Android (the green bubble). Apple touts that it cares about consumers and is all about privacy and security but does not state that those communications are not secure. Apple needs to use the standards and make them secure where it is applicable.

This argument and precedent has been set over decades. Standards are not there for people to say "but the dominant position should be used despite the standard, because the dominant position is just getting more dominant." If that were true, then IE would've never been dethroned as the dominant browser and it's non-compliance to standards. It took lawsuits for that to happen. The standards existed the whole time and were ignored.

In fairness, we can debate this all day - Apple has yet to issue a statement. They take no position on user security except to state that it's fine as long as it's on Apple. They don't care about the other 70% of the world, nor do they warn that when communicating with that majority, those messages are insecure by Apple's choice. That's what needs to be addressed.



I love these arguments because it is pretty myopic. People are born, people die, the world is not simply a static metric of precisely X amount of people that have phones are deciding their phones. There are people who have no phones whatsoever who are choosing their platform.

IOS started as the dominant mobile platform and has lost overall market share over time, now representing less than 30% of the global market. It will continue to lose market until it adopts more open standards like these. Lawsuits arguing the adoption of open markets, predatory behaviors, closed systems, and forced payment systems are not good news, and people listen.

Android sells around a billion units a year, conservatively. As of 2021 the attrition of Android to Apple has slowed to nearly zero. The innovation has really stalled in the Apple space, and Android users are poised to grow in market share. The trends show this, and in some metrics, already do.

But the context of your response was that people will buy 150mil more iphones to solve issues like this thread. You have not proven that one iota. It's reasons like this thread that drive people away from Apple. Apple does not adhere to standards for the most part until they are forced to. This isn't a secret by far. And if your answer is "but more people use apple!" that's also not true.


My carrier disagrees with you. It's a small startup called AT&T. Maybe you've heard of it?

And if a singular carrier supports RCS (which actually there are lots worldwide) then see the first point of the thread: It doesn't matter the density, it doesn't matter if zero carriers support anything. It's a standard. It doesn't need density. Saying it needs to be prevalent to be adopted is completely missing the point. USB 5.0 would never be adopted. But since there are only two players in this game, it's highly convenient that the 30% market share is being bullish about standards. Apple needs to make a statement, is really all that's being asked here. But they're not even coming to the table. They just don't care about the 70% market. I also posit they also don't really want to protect and secure the 30% trying to talk to the 70% either. That's just wrong. Apple needs to do something.

Apple is religiously and vigorously anti-standard. They will do whatever they can to be proprietary. It's actually served them very well, and I applaud it for the most part, but the truth is in an interconnected world it's getting very old and people are beginning to really see that. It is possible to be innovative on top of standards (reference: the entire logic behind Lightning vs USB-C). But you can't make as much money without proprietary cabling, closed stores, closed payment systems, closed peripherals, closed security, so they won't even address it. You must simply go all-in on Apple, and "people should just buy more Apple to fix this". Pretty insulting. It drives people away from the platform, not toward it.
Weird statement. If zero carriers adopt RCS, (and no Chinese OEMs support RCS on their stock SMS app), then what's the point in harping on Apple? Apple is hardly the key point in the bigger scheme of things.

As for Apple being anti-standard, although there are plenty of examples, there are also plenty of examples on Apple adopting standards better than the rest. Eg. fast charging. Look at Qualcomm, Xiaomi, Oppo, etc having their own proprietary fast charging tech. Instead, Apple adopted the standard USB-Power Delivery. And Apple also uses USB-PD on their laptops.

Back to RCS, Google's implementation is not necessarily the "standard" either. It's Google's interpretation of RCS going through their own Jibe services. Like SMS, for a true interoperability, the carriers are the key, not Apple. Harping on Apple about RCS is akin to harping on Apple for 5G. The ones Google should be harping on are the carriers. Meanwhile, many carriers around the world that did support RCS have decided to drop it many moons ago. Google is simply late at the game, championing RCS simply because they sucked at making their own chat platform. Now they are doing smear campaign on Apple to hide the fact that they couldn't even figure out their own video conferencing solution against Zoom.
 
Weird statement. If zero carriers adopt RCS, (and no Chinese OEMs support RCS on their stock SMS app), then what's the point in harping on Apple? Apple is hardly the key point in the bigger scheme of things.
The argument is that no carriers use RCS which is untrue.

Apple should use RCS where it is viable to do so.
 
  • Like
Reactions: TimFL1 and LD517
The argument is that no carriers use RCS which is untrue.

Apple should use RCS where it is viable to do so.
Did you read that link you gave? Count how many countries actually support RCS with universal profile, and compare that to the total number of carriers around the world. Majority of them around the world don't. Carriers in S.Korea discontinued it, and Japan simply uses Line. RCS is not like what people are making out here to be, as if it's as universal as SMS. In reality, it's not. It's even more niche than iMessage as it's probably only used by US Pixel users. So a "standard" that is only used in one or few countries by few users? Why should Apple be the one to blame when Google doesn't even bother talking with the carriers and various Android OEMs to support it out of the box?
 
  • Like
Reactions: Unregistered 4U
Almost no third party app can adopt Google RCS as Google doesn’t provide public APIs. The only exception right now is Samsung which struck some kind of deal with Google.

Not even Samsung, not in the way you're thinking. The S21 and S22 have Google Messages, Samsung Messages is no more. What happened was Google threw in the towel on wearables, and admitted Samsung won. They merged WearOS into Tizen, now called just plain ol' Wear, and they share development duties. The breadcrumbs of an API marked "dangerous" is for wearables, which Samsung needs access to for performing their duties on development alongside Google.
 
  • Like
Reactions: Unregistered 4U
My carrier disagrees with you. It's a small startup called AT&T. Maybe you've heard of it?

And if a singular carrier supports RCS (which actually there are lots worldwide) then see the first point of the thread: It doesn't matter the density, it doesn't matter if zero carriers support anything. It's a standard. It doesn't need density. Saying it needs to be prevalent to be adopted is completely missing the point. USB 5.0 would never be adopted. But since there are only two players in this game, it's highly convenient that the 30% market share is being bullish about standards. Apple needs to make a statement, is really all that's being asked here. But they're not even coming to the table. They just don't care about the 70% market. I also posit they also don't really want to protect and secure the 30% trying to talk to the 70% either. That's just wrong. Apple needs to do something.

Your carrier disagrees with you, actually. AT&T, just like Verizon and T-Mobile, have dropped support for their own closed RCS systems in favor of Google RCS. And it happened over a year ago. Google RCS does not equal RCS. It uses "RCS" in its name, but it's just like every other instant messenger. An over-the-top network that runs independent from any carrier.


And the highest the adoption rate ever hit was 8%. It's on the march back down to 0% adoption. It's not a standard, it was a proposed standard that never got any traction, which makes it an abandoned standard. Just because you can go buy a vinyl record does not mean it's not abandoned, it doesn't mean that there weren't competing "standards" in that world, and it sure as hell doesn't mean it's good - CDs came along and took that quality crown no matter what any vinyl fanatic will tell you and even CDs are dead. RCS is that far behind.
 
  • Like
Reactions: Unregistered 4U
Let’s be clear, though, it’s not only Apple that refuses RCS. Every carrier also refuses RCS. There’s not a single carrier that supports RCS in the same way that they support SMS.
I’m not surprised. Carriers do the bare minimum (or less) in effort for their own customers’ usage experience. Also, they’re probably holding on to pay-per-text with a death grip, and SMS character limits are part of that.
 
The argument is that no carriers use RCS which is untrue.

Apple should use RCS where it is viable to do so.
But they aren’t using RCS, they’ve outsourced RCS to Google Jibe. There’s only one implementation, and it requires paying licensing fees to Google. (Well, actually, it seems like there are two implementations, as Google Messages’ RCS gateway is incompatible with Jibe. Yes, Google’s own gateway can’t even send “standard” RCS to carriers using Jibe. I don’t think RCS ever got interoperability working. Samsung licenses Google Messenger’s gateway in order to be compatible with Google Messages RCS. This has been covered before in this thread, RCS is not what Google is making it out to be.)
 
  • Like
Reactions: Unregistered 4U
Apple should use RCS where it is viable to do so.
Maybe we can agree on that because, in reality, RCS isn’t viable to be used anywhere. At best, it was a proposed standard that never got off the ground and Google decided to frankenstein a version only compatible with itself that goes OTT. And then Google decided to Frankenstein it again with a version that adds some modern chat features that doesn’t work with the other version they made.
 
Did you read that link you gave? Count how many countries actually support RCS with universal profile, and compare that to the total number of carriers around the world. Majority of them around the world don't. Carriers in S.Korea discontinued it, and Japan simply uses Line. RCS is not like what people are making out here to be, as if it's as universal as SMS. In reality, it's not. It's even more niche than iMessage as it's probably only used by US Pixel users. So a "standard" that is only used in one or few countries by few users? Why should Apple be the one to blame when Google doesn't even bother talking with the carriers and various Android OEMs to support it out of the box?
Plus, that list looks to be about 5 years old. Since active deployments of Universal Profile RCS have been getting dropped by the carriers, that list is stale information. For Pete’s sake, it even mentions Windows Phone as one of the implementing OSes! It would be like a list of 2G GMA or CDMA deployments.
 
  • Haha
Reactions: Unregistered 4U
If Google can make RCS fully encrypted from end to end, THEN Apple might be interested.

Going to jump on this train because I haven’t been able to find solid documentation on the security and privacy of RCS as compared to iMessage. Reading through these didn’t make me feel great…let’s follow an Apple standard and publish the technical white paper with specifications (if someone knows where it is and would link please do).


 
  • Like
Reactions: Unregistered 4U
With every new standard that is released, there is always initially a 0% adoption rate. So it doesn't matter where the number is.
I agree that it takes time for a new standard to take off, RCS is most certainly NOT a new standard. :) Been around for awhile, carriers even kicked around with it a bit. But, no carrier is currently supporting it in the same way they support SMS, that is, a person that sends an SMS message can have that delivered to anyone else with a cellular phone that can receive SMS.
But the context of your response was that people will buy 150mil more iphones to solve issues like this thread. You have not proven that one iota. It's reasons like this thread that drive people away from Apple. Apple does not adhere to standards for the most part until they are forced to. This isn't a secret by far. And if your answer is "but more people use apple!" that's also not true.
Nope, just that, of ALL the billions of people in the world, people with phones, people without phones, old folks buying their last phone, new folks buying their FIRST phone, Apple ONLY has to sell phones to roughly 150 million people in a given year. So, folks getting turned off by Apple? That would have to be close to 7 BILLION turned off by Apple for it to even matter for the FAR less than 1 billion phones they need to sell.

The answer is not “but more people use apple!” it’s “but fewer people use Apple! There are billions that will NEVER use an Apple device. And, that’s fine, because Apple only needs to sell to a very tiny percentage of 6 billion people in order to make a profit. Their products are CLEARLY not meant for everyone, and that’s fine, they’re still profitable. Even if there are 7 million people like you RIGHT NOW turned off by Apple, that still leaves (counting on fingers) OVER 6 BILLION for Apple to sell to.”
My carrier disagrees with you. It's a small startup called AT&T. Maybe you've heard of it?
Your carrier contacted me to let me know that you misunderstood. They don’t support RCS in the same way that they support SMS because their SMS feature can send messages to any user on any network using any phone, while RCS can only send messages to specific other AT&T users using specific Android phones (not all of them). They apologize that you misunderstood.
And if a singular carrier supports RCS (which actually there are lots worldwide)
If a singular carrier supports RCS, then… they can only send messages to other devices on that same carrier (not all, just specific devices). Apparently… which is nothing like the support for SMS. Which is EVERY carrier.
I also posit they also don't really want to protect and secure the 30% trying to talk to the 70% either.
Now, THIS point is interesting. Because, I could have SWORN that, on my iPhone, I was communicating with multiple Android users JUST RECENTLY! See, there’s this technology, called SMS, allows communication from ANY phone to ANY OTHER PHONE that supports SMS. It SHOULD allow a protected and secure iPhone to communicate with Android. One moment… Yeah, just tried it and the Android person responded. And, I, you know, read it. So, I guess the protection isn’t as sound as you believe it to be?
closed stores, closed payment systems, closed peripherals, closed security, so they won't even address it.
Interestingly enough, neither will Nintendo, Sony, or Microsoft with their systems designed from the start to be closed.
It drives people away from the platform, not toward it.
Well, it drives a FEW people to the platform. Percentage wise it’s a small amount of the market, but Apple has never needed a huge percentage of marketshare to make a profit. Some people don’t like Apple products and that’s fine. Some, perhaps most people, will never use an Apple product, and that’s ok, too. They make products that only a small percentage of folks will ever buy anyway.
 
Did you read that link you gave? Count how many countries actually support RCS with universal profile, and compare that to the total number of carriers around the world. Majority of them around the world don't. Carriers in S.Korea discontinued it, and Japan simply uses Line. RCS is not like what people are making out here to be, as if it's as universal as SMS. In reality, it's not. It's even more niche than iMessage as it's probably only used by US Pixel users. So a "standard" that is only used in one or few countries by few users? Why should Apple be the one to blame when Google doesn't even bother talking with the carriers and various Android OEMs to support it out of the box?
There are countless technical protocols in the world where opportunistic security is in play. This is one of them. I've said this before: It doesn't matter that there isn't 100% saturation - it matters that Apple values security except when it comes to anyone else outside of Apple. They should use the opportunistic security made available to them where available. The extra benefits are just icing on the cake.

This benefits apple insofar as any message that is sent outside of Apple to another vendor (Android) is not secure, in current incarnation. If Apple cared about security globally (aka wants customers who believe their schtick) they would use security and the standards where it is available.
 
RCS is not like what people are making out here to be, as if it's as universal as SMS. In reality, it's not. It's even more niche than iMessage as it's probably only used by US Pixel users. So a "standard" that is only used in one or few countries by few users? Why should Apple be the one to blame when Google doesn't even bother talking with the carriers and various Android OEMs to support it out of the box?
That’s the key, even a cursory examination of RCS will show that it’s not anything like what its proponents claim it’s supposed to be. It’s like talking about how CurrentC will challenge Apple Pay long after it’s demise.
 
Maybe we can agree on that because, in reality, RCS isn’t viable to be used anywhere. At best, it was a proposed standard that never got off the ground and Google decided to frankenstein a version only compatible with itself that goes OTT. And then Google decided to Frankenstein it again with a version that adds some modern chat features that doesn’t work with the other version they made.
Yeah, it’s just not viable. The few folks that want this interoperability (because the vast majority is fine just grabbing whatever chat client the person they want to talk to is on) would be better served focusing on the carriers and suggesting changes there that would provide them their “life changing” read receipts and whatever non-actual-text-message-related features are critically important to them.

Update:
Apparently the list of things that are REQUIRED in order to send a text message between Android and iPhone users includes…
read receipts -
typing indicators -
sending over data -
higher-res video and images -
better group chats -

You will note that precisely zero of these have anything to do with sending “Hey how are you doing?” as a text message to a contact. Unless you simply MUST know when they read it and are sitting there waiting to see if you get a typing indicator that they’re replying, perhaps. :) Google’s biggest problem is that anyone that wants this between iOS and Android users have already downloaded “just another app” to do this… it just wasn’t Google’s because Google were too busy going about the hard work of failing at messaging for the last 10-something years!
 
Last edited:
  • Like
Reactions: ian87w and kc9hzn
This benefits apple insofar as any message that is sent outside of Apple to another vendor (Android) is not secure, in current incarnation. If Apple cared about security globally (aka wants customers who believe their schtick) they would use security and the standards where it is available.
That’s why WhatsApp, Telegram, and others are a thing. They’re all available for iOS and anyone that wants to talk to anyone using an encrypted gateway are already doing it, very likely for years now.
 
  • Like
Reactions: ian87w and I7guy
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.