Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I prefer buying knock-off Xerox GUI systems. And knock-off Bill Buxton interfaces. And knock-off ARM cpu devices.

You really have no idea of how unoriginal Apple actually is but also completely fail to realize that there is a need for choice within a brand for consumers and standards across brands for consumers. Too bad cheerleading for Apple is more important to you than building better products and services for ALL consumers.

Knock-off ARM? That's kinda ignoring the history of Acorn and why ARM is even named ARM in the first place and who bankrolled the development of ARM, or who owned ARM originally as a joint-venture with Acorn, and why they have a perpetual license to ARM architecture.
 
Is that Google or Facebook, because Facebook is the one that really benefits from this.

That'd be Google, whose entire business model is user data.

As far as WhatsApp, same story as what Google is looking to do with RCS. Farming at-rest data. Facebook stays at-par at minimum, while they are leaking users to Signal.
 
Seems like some people here are misinterpreting the request. This is not a request to replace iMessage.

The Apple Messages app already has 2 protocols (iMessage and SMS, and technically MMS). If you are communicating with someone who has iMessage then it uses iMessage and all it's features. If you happen to communicate with someone without iMessage then it uses SMS/MMS, Google is suggesting this second part be changes, that if you communicate with someone WITHOUT iMessage then it uses RCS. This would be an overall improvement. You keep iMessage for iPhone-to-iPhone and use the newer RCS protocol for anyone else.

I'm no expert, but, I understand that RCS is a bit of a cluster right now (different carriers interfering or not fully implementing etc...) , so not sure if it's worth implementing yet.
I could be wrong, but you'd think if Apple got on board with RCS, it would be a step in getting this all straightened out. And to everything before the part in bold, I still predict a number of responses on this thread that will continue to ignore or misinterpret it despite you laying it out so plainly.
 
  • Like
Reactions: LD517 and ohio.emt
I could be wrong, but you'd think if Apple got on board with RCS, it would be a step in getting this all straightened out. And to everything before the part in bold, I still predict a number of responses on this thread that will continue to ignore or misinterpret it despite you laying it out so plainly.

Google has already straightened it out, in their minds. They took the RCS protocol and launched their own version, running over-the-top of carrier RCS services. It can be turned on simply within their app, and they hold the SMS stack already so they can use fallback services. Google's deployment is just as closed as carrier RCS services though, it's just they are the server of the data, not the carrier, so they can send to anyone.
 
I think he's implying that one company makes it's money by harvesting user data and selling it, and knowing what's in your conversations is a huge hole in that data.
Neither Google nor Apple sell your data that they collect to 3rd party. Both companies collect and uses your personal data for targeted advertising, but it doesn’t sell it to 3rd-party advertisers. Advertisers can pay Google or Apple to be seen on your iPhone or Android device. If they sell your data then that means they don't make any money as the advertisers can target you themselves with the data that both Apple, Google and every 3rd party service you use collect. This website you are on currently, serves targeted ads.

Information We Collect and Use
We may collect and combine information when you interact with the Site including:

  • Information You Provide. We collect information you provide to us, including:
  • When you create an account with us. When your use the Site, we may also recognize you or your devices whether or not you are signed in. We may use device IDs, cookies, and other signals, including information obtained from third parties, to associate accounts and/or devices with you.
  • When you communicate with others via the Site, or when you post, comment, upload or store content.
  • We analyze and store all content, messaging, and posts. This allows us to develop and deliver relevant features, content, and advertising.
  • When you sign up for paid Services, use Services that require your financial information or complete transactions with us or our business partners, we may collect your payment and billing information.
  • Device Information. We collect information from your computers or mobile devices, either directly or via our ad network and analytics partners, including your activity on the Site across devices. This includes data such as IP addresses, cookie information, mobile device, advertising identifiers, browser and spversion, operating system type and version, mobile network information, device settings, and software data. We may recognize your devices to provide you with personalized experiences and advertising across the devices you use.
  • Location. Our ad networks and analytics partners collect location information from sources such as IP addresses and mobile phone network data. You can manage your location preferences and opt out of location tracking by using the location settings on your devices and within your web browser.
  • Data from Tracking and Ad Technologies. We collect information during and after your interaction with the Site. This is done by data collection technologies, such as web beacons and cookies. These data collection technologies allow us and the advertising networks we use on the Site to understand your activity on and off the Site. This information includes the content and ads viewed or clicked on, the frequency and duration of your activity; your navigation of the Site and other sites, and any purchases from affiliate links.
  • Data from Third Parties.We collect information about you from other users, third-parties, and affiliates, including:
    • from connected third-party services or third-party sign ins such as via Facebook, Twitter or Google.
    • from advertisers about your interactions with their ads or their sites.
 
  • Like
Reactions: LD517 and ohio.emt
All my co-workers and my relatives use Android so texting has been a nightmare with them because of that.

C'mon Apple. Give us RCS in Messages.
How is texting a "nightmare"? Obviously caring about the color of messages being different is a childish concern, so that can't be why it's a "nightmare."

The only issue I ever experience is that full size photos and videos don't send well over carriers' message file limits. But it's super easy to drop a link to a message from a photos app or to just send it over something like Messenger or Whatsapp or something, which most people also have.
 
  • Like
Reactions: LD517
I use signal when non-iMessage recipients are involved. Maybe just allow signal threads to show up in iMessage.

I just moved to the UAE and I’m amazed by how much market penetration WhatsApp has here… Ick ~meta~ products make me feel dirty.
 
  • Like
Reactions: threluja
If everyone is onboard with making RCS a standard Apple needs to get on the bandwagon. SMS/MMS are relics from the past and need to go. There needs to be a central standard. It doesn't make sense for Apple to ignore this. One way or the other they are going to have to do it. When the carriers sunset SMS/MMS they will have no choice. The FCC will mandate it as the standard for the carrier and the carrier will tell Apple to do it or get off the network. If not mandated the carrier will sunset SMS forcing Apple to implement RCS to be compliant with text messaging requirements. This has no impact on iMessage so I don't see this as anything but Apple being petty.
 
How is texting a "nightmare"? Obviously caring about the color of messages being different is a childish concern, so that can't be why it's a "nightmare." The only issue I ever experience is that full size photos and videos don't send well over carriers' message file limits. But it's super easy to drop a link to a message from a photos app or to just send it over something like Messenger or Whatsapp or something, which most people also have.

The text bubbles being green isn't the problem. It's what the green means. When the bubble is green that means it was sent through SMS instead of iMessage. When sent through SMS the message lacks read receipts, you don't get writing notifications, group messaging is a lot more difficult (or results in multiple group messages because one of them excludes one person,) messages aren't encrypted, and sending images and videos are compressed like crazy or won't send at all due to size limitations.

These are all things RCS fixes.

 
If everyone is onboard with making RCS a standard Apple needs to get on the bandwagon. SMS/MMS are relics from the past and need to go. There needs to be a central standard. It doesn't make sense for Apple to ignore this. One way or the other they are going to have to do it. When the carriers sunset SMS/MMS they will have no choice. The FCC will mandate it as the standard for the carrier and the carrier will tell Apple to do it or get off the network. If not mandated the carrier will sunset SMS forcing Apple to implement RCS to be compliant with text messaging requirements. This has no impact on iMessage so I don't see this as anything but Apple being petty.
Apple sees iMessage functionality as a major enticement to their platform. They like the blue/green dichotomy. They are not going to hand that over to Google for nothing. For some reason this reminds me of the old thing with Maps. Back in the day Apple paid Google for their map info, and Google gave them the crappiest, bare-bones implementation as possible while Android had full turn-by-turn. Google saw it as a major plus to their platform. Only when Apple dumped Google and made their own app with turn-by-turn, as bad as it was day one, did Google go ahead and add those features to their iOS app.

If carriers sunsetted SMS then I suspect Apple will implement the most barebones RCS functionality possible to comply, while also continuing to upgrade and manage iMessage.
 
The text bubbles being green isn't the problem. It's what the green means. When the bubble is green that means it was sent through SMS instead of iMessage. When sent through SMS the message lacks read receipts, you don't get writing notifications, group messaging is a lot more difficult (or results in multiple group messages because one of them excludes one person,) messages aren't encrypted, and sending images and videos are compressed like crazy or won't send at all due to size limitations.

These are all things RCS fixes.

I'm aware that RCS is superior to SMS.

My point was that those things don't make using SMS a "nightmare." Texting hasn't been a "nightmare" for the past decade despite it lacking widespread RCS during most of that time.

Group convos can be a little annoying but everything else is pretty trivial.

However, I too support Apple adding RCS support instead of trying to block it in order to make iPhone users harass Android users more.
 
If all/most Android phone makers agree to adopt RCS, and if they get it working correctly on all/most Android phones, to the point that Android users are having a smooth, consistent, RCS experience when messaging each other, and the only ones missing out on those RCS messages are iPhone users — then, I'm betting, Apple will suddenly launch support for RCS.

But if the Android people can't get it together like that? Then Apple won't touch it. Why the hell would they? Google wants Apple to adopt it so Apple can provide the magic glue that gets everybody else in line with it. Apple would be a complete chump if it fell for that.

Google told us for a decade or more that Android was surely going to replace iPhone, that it was a big advantage that Android phones are made by fifty different companies. OK, Google, show us your big advantage: Make RCS a success without Apple's help.
 
I'm aware that RCS is superior to SMS.

My point was that those things don't make using SMS a "nightmare." Texting hasn't been a "nightmare" for the past decade despite it lacking widespread RCS during most of that time.

You don't work at a place full of Android users then or you and every Android user you know use WhatsApp. It's especially worse at places where the Android and iPhone users are split 50/50
 
The solution is so simple: just unfriend anyone who doesn't have an iPhone. Seriously, Android users typically all smell of wee and biscuits and spontaneously combust if they set foot in an Apple Store.

On a serious note Apple are hardly going to embrace RCS through pressuring from Google, if anything it'll just strengthen their resolve to stick to what works (for iOS users, at least...)
 
You don't work at a place full of Android users then or you and every Android user you know use WhatsApp. It's especially worse at places where the Android and iPhone users are split 50/50
Or in Europe.

Nobody really uses SMS. SMS only use is for services notifications, PINs and codes sending and stuff like that.

WhatsApp is the default chatting solution and neither Google or Apple get a piece of anything.
 
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!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.