In a surprising move, Apple has announced today that it will adopt the RCS (Rich Communication Services) messaging standard. The...
In a surprising move, Apple has announced today that it will adopt the RCS (Rich Communication Services) messaging standard. The feature will launch via a software update “later next year” and bring a wide range of iMessage-style features to messaging between iPhone and Android users.
Apple’s decision comes amid pressure from regulators and competitors like Google and Samsung. It also comes as RCS has continued to develop and become a more mature platform than it once was.
Ironically, despite Apple's whining to get to this point, between this, and the EU forcing them to adopt USB-C, and, hopefully 3rd party stores and browsers, I may consider an iPhone for my next phone.
It's a pity you almost need to point a gun to their head for them to consider unshittifing their products.
Yeah. My iphone fanatic of a friend was complaining about something on hers the other day, and was like "Why doesn't Apple just do {whatever}?"
My reply was basically that Apple didn't become a trillion dollar company by giving customers what they want. They became a trillion dollar company by telling customers what they want and marketing the crap out of it.
To be fair, Google has been doing the same stuff with RCS E2E encryption. It ain’t open. There is a reason why Android isn’t littered with dope messaging apps that support encrypted RCS.
Let’s be fair, things like RCS E2E encryption are firmly under control by Google. People like to claim RCS is open, but it’s not.
If RCS was a proper open standard, we would have a lot of awesome messaging apps to choose from. We don’t, and the reason is because Google has been gatekeeping.
I’m annoyed that Apple is late to the game, and I hate that they needed to be pressured to get here, BUT I’m glad to see that they’re going to support universal alternatives to the crap you still have to ask Pichai to please let you use.
Also RCS is build that way. It has more features than SMS, but underneath is even worse than it.
Why in the 2023 people massively want to go back tying their chat app with mobile carrier? Like, giving what Internet standards we now have RCS should really be considered deprecated, hope we won't be stuck with it for next 30 years.
I don’t know how much of a gun it was. Apple has definitely been working on RCS support for a year; you don’t add that in a few months. Similarly I’m pretty sure Apple has been considering USB C in iPhone since at least when they started working on the USB C on iPad, which is what 5 years old?
Of course without pressure they would have probably be slower to move forward, and with Apple secrecy it’s always hard to tell how long things have been ready to ship. But let’s not pretend they just woke up this morning with a horse head in their bed and told their direction team to start working on this.
I hear you, but isn't the proverbial horse's head the fact that the EU is looming over them and forcing them to make a move?
RCS and USBC have been available for a while. It seems disingenuous not to acknowledge that Apple has purposely dragged their feet so they could make more profit selling proprietary software and hardware which is probably why you're being downvoted
They just need to stop using slaves and fighting attempts to fight against it and I might actually get to appreciate the cool things their engineers do actually make.
I’m hoping that they also force Google to do the same. Pushing for a universal RCS E2E encryption standard is great. I’m sick of Google saying RCS is the open alternative to iMessage, when key things like their E2EE implementation are not open at all.
AFAIK Apple has said they are only going to use official RCS spec with no extensions and will work on adding encryption to the spec. Google has announced that they will work with Apple and the GSMA to implement official RCS encryption.
You will be shamed and sentenced to isolation from the rest of the US if caught with a disgusting yellow bubble. Have some self respect, buy an iphone, use imessage
I just want to point out that this announcement comes after Nothing phone company announced they partnered with a company that will bridge the two protocols so apple was about to lose their ability to force android images and videos to look like a potato so iPhone users wouldn't want to leave the apple ecosystem.
This just exactly like when apple decided they were going to be champions of privacy by improving the security on their phones, which coincidentally happened right after a company called cellebrite started selling a product that would allow police to bypass passcodes and fingerprints to access a users data which previously could only be unlocked by the police department paying a fee for each time to unlock a phone.
They will always default to being shitty like any other company treating their users like the enemy until they can't and then they spin it in their favor.
Beeper is sick! Would highly recommend. Or if you’re feeling frisky, self hosting the bridge in a docker container is possible. The container is a kvm osx vm.
Nothing is literally nothing, Apple could care less about them.
Nothing's solution is basically getting you to send your messages to them, and they'll send it through a Mac logged into your Apple ID hence achieving the "blue bubble" lol. Hugely insecure, hacky solution and hardly groundbreaking.
Seems more likely to be Apple getting ahead of incoming legislation than a small phone company’s announcement. Companies like Apple don’t make huge changes within a couple days of nearly unknown (to the general market) companies doing something that might slightly affect them.
Regulations work, and in this case, it doesn’t look like competition played any role. Apple only makes changes like this when forced to by regulators or, in the case of privacy, when it’s marketable. Capitalistic self regulating is almost a myth with them— they wouldn’t even stop selling those butterfly keyboards until their self imposed refresh timeline allowed for it.
I've no doubt it's more than one thing that is driving this, but my point was they are only now agreeing because they have to and not because they want to. This company has literally taken away their customers ability to receive quality media from their friends with the sole intent to pressure people into getting their product so they belong. I know it's hyperbolic to say, but it's basically using teens to bully each other into buying something. Someone had to pitch this idea to a room full of people and all those people thought wow this is a great idea, think about how fucked up that is.
Nothing doesn’t have anything real - it’s a Mac in the cloud with some janky scripting puppeting Messages.app. They haven’t figured out how to plug in at a protocol level or anything.
Holy crap. Now my uncle can stop complaining about degraded quality when Android users are in message rooms. When it comes to tech, he really doesn't care about the culprit. He just complains that people aren't playing in Apple's walled garden.
The biggest thing is attachments like photos/videos.
While MMS pretty universally sucks, Apple is very aggressive with the compression they apply to attachments over MMS so the resulting user experience is garbage akin to what we used to have when MMS was new.
Modern phones from other manufacturers will make use of the full MMS attachment size available, typically 100MB or more (depending on your carrier) iPhones will compress that video down to a couple MB regardless of the higher capacity available.
iMessage is a rich communication layer backed by HTTPS and web sockets so think something like WhatsApp or Telegram; you can send 2 gig files, embed maps and other rich content, etc etc. SMS is well… SMS. So the blue versus green bubble is a dumb reductionist view but the practical impact is visible in say video messaging, where an iMessage can attach a 50mb 4K H.265 clip same as a real messaging app, whereas an MMS will be a 256k 3gpp potato.
iPhones don't support multimedia messaging over anything other than SMS. On Android when you send an image to someone you're sending the actual file (the original file with all its bytes intact). If you try to send it to someone over SMS it'll just goes "nope, you shouldn't do that you should send the actual file", and seamlessly intervenes and just does it.
But since IOS can't receive files, instead preferring to use their proprietary AirDrop system which they don't feel like making available to other developers, Android phones are forced to send it as an SMS. Problem with that is there is a max file size and the image has to be heavily compressed in order to fit.
So then iPhone users (who typically know less about technology than my grandmother) start to complain about the terrible quality of Android photos, even though it's actually an issue with transferring the file, and it's not Androids fault. So what's going to happen is that next year the quality of Android photos is massively going to jump really weirdly 🤔.
It looks like Apple is addressing one of the biggest gripes with RCS - Google’s proprietary crap that isn’t opened up to small 3rd parties. Apple wants things like E2EE to be a universal standard that anyone can use, not something Google only dishes out to big phone manufacturers.
I'm not sure that's quite the case. It sounds like it's just a big undertaking where Google and Samsung are the only ones that have done it. There was never anything stopping Apple.
It's really bad that we sill would live in a ancient model when in order to use the protocol app need some specialized system API to the baseband modem. I thought it was all fixed with just the IP (Internet)?
I'd rather they use the open standard. Google should, too. If there are shortcomings with the standard then let's improve the standard, not create a custom implementation of it.
No matter how poorly Apple's implementation works with Google's, this will be a net positive for consumers.
Apple finally giving in allows RCS to become a true standard that works across any mobile devices. That will motivate developers and the industry as a whole to continue to improve upon it.
The initial release may be underwhelming but in the long run this week be good for everyone.
If Google's implementation remained the defacto "RCS" that everyone used there would be no motivation to add things like encryption to the standard as everyone is using Google's anyway
Around 2010 Google, Facebook, MySpace, even OkCupid were all running on the XMPP standard protocol. The corpos were generally bad stewards not following protocol updates, implimenting features in incompatible ways, & eventually realized there was more to gain be defederating forcing folks to use their platforms & let those corporations siphon the (meta)data of messaging.
What gets me is why they saw the need to invent yet another similar protocol with XMPP still being feature rich, battle tested—as well as Matrix to a lesser extent—unless they already have their plans on how to circumvent the system & repeat this same cycle.
Apple: (Finally supports a standard the rest of the world has been using for years) Look at us. So brave, so innovative. Also, we removed another port. Here's a link to a $29 dongle in the Apple store.
In theory anyone can host an RCS endpoint but in practice that means carriers (historically) or OS vendors (in modernity). So in effect yes all RCS messages will pass through Google servers, but mostly because Apple to Apple texts will remain on iMessage. But any texts starting or ending on Android will go through Google. Note that this doesn’t really change much as Google’s privacy policy for Android users already discloses the bulk ingestion, scanning and processing of communications, including text messages.
There can be other servers and apps, for example Samsung has their own app. It's hard for me to track down details about how they interoperate but it appears that the various services need to agree to work with one another, so I don't think just anyone can create an RCS app and infrastructure and have it work with Google's and Samsung's. However, I imagine Apple is fully capable of it and would be surprised if iPhone RCS wasn't going through Apples network.
I don't want to be cynical, but is this part required for Apple to implement RCS?
"and bring a wide range of iMessage-style features to messaging between iPhone and Android users."
I can totally imagine it being limited to the encryption and the bare minimum, as imessages features don't perfectly overlap with the RCS features (e.g. emojis).
I’m glad that they’re finally going to implement it but I can’t help but shake the feeling that there’s still going to be some interoperability issues.
I'm guessing the bubbles will stay the different colors, which is all apple really cares about. They get a /lot/ of sales on bubble color. So keep the regulators who want to open up imessage to others at bay and keep the primary benefit to apple. As a bonus, it's less terrible in general for all of us.
Thats because it’s just not true that people care about bubble color. Or at least no one I’ve ever encountered at least. The way people talk about it on here you’d think kids were killing themselves because they have an android phone and no one with iPhones will talk to them.
Google Messages is a proprietary chat app that connects to proprietary Google Jire servers on phone carrier's site. It does not use barebone RCS protocol, this is why only Google is now able to make such app even if the app does not use any permission that other apps don't have.
Native support for Android was planned for Android 11, soon we'll get Android 14 and still no support in sight.