Google and Apple finally fixed the worst thing about texting an iPhone

In March 2026, we received exciting news. Not only was RCS 4.0 bringing long-awaited features to our messaging apps, but end-to-end encryption was being tested between Android and iOS devices.

Even though it was technically possible since RCS 3.0, it wasn’t as simple as pushing an update to iMessage and calling it a day. But that day has finally come.

End-to-end encryption between iMessage and Android is potentially the biggest milestone in the Apple-Android relationship since the introduction of the first iPhone.

While it might seem like a mere quality-of-life update, this update has exciting ramifications for the future of messaging.

However, Google still has a long way to go.

Related

These hidden Google Messages effects finally made me enjoy texting again

Now I can't go back to normal texts

Posts 4
By  Anu Joy

What end-to-end encryption between Android and iPhone means

The last wall between Android and iOS communication is gone

Sameer Samat, President of the Android ecosystem, posted enthusiastically on X about the feature, stating: “This cross-industry effort replaces outdated SMS with a more secure & private way to chat, no matter what phone you have.”

It’s certainly a success. Google has been pushing for Apple to break down the iMessage walled garden for years (remember the cringy Google ads?), and the result is a bigger success for Google than it is for Apple.

End-to-end encryption has been a staple of iMessage, encouraging users that their chats will always remain private.

This came with a stark visual reminder in the form of the dreaded green bubble (which isn’t going away), that established Android as the “other” messaging service in our minds.

While iMessage support for RCS was a huge step forward for Android/iOS communication, the lack of encryption has held back integration.

Now, Google Messages and iMessage are closer to feature parity than ever.

This update matters more for Google than Apple

But don’t celebrate Google for reaching this milestone

While I’m happy about RCS support for iMessage, Google isn’t the one responsible for the change.

In 2023, the Chinese government began establishing a law that required all new 5G devices to require RCS support to be certified.

The potential of losing this market was a bigger deal for Apple than any fuss Google was kicking up.

The only independent move from Apple is regarding end-to-end encryption.

For obvious reasons, the Chinese government isn’t keen on its citizens encrypting their conversations, so this move is likely Apple saying, “Well, if I have to support this feature, I might as well make it work well.”

For Google, this is yet another piece of evidence that Android is no longer the “other” phone.

New Android phones are just as stylish as iPhones, the software is arguably more advanced, and the ecosystem is rapidly becoming as impressive as Apple’s.

So, how will this update change our messaging going forward?

The green bubble may be the only indication that something is different

But Google still has work to do

Apple keeping the green bubble for Android users is wise from a marketing perspective, but it feels childish at this point.

Apple wants to continue highlighting that someone is using an Android phone (which is different, and therefore bad, and therefore should be avoided), but at this point, it feels ridiculous.

Google Messages is a fantastic messaging app in 2026. While it’s not perfect, it’s packed with powerful features that make it more than a match for iMessage.

If it weren’t for two things, it would be ready to become the number one messaging app on Android.

One of the greatest features of iMessage is that you don’t need a phone number to use it.

I fondly remember the days of texting friends on my iPod Touch with iMessage. Even though I didn’t have a phone number, my Apple ID meant I could text without a problem.

Subscribe for deeper take on RCS, iMessage and privacy

Want clear context on RCS 4.0, cross-platform end-to-end encryption, and what it means for messaging and device ecosystems? Subscribe to the newsletter for concise analysis, practical implications, adoption hurdles, and privacy-focused insight.

Get Updates

By subscribing, you agree to receive newsletter and marketing emails, and accept our Terms of Use and Privacy Policy. You can unsubscribe anytime.

Separating Google Messages and RCS from your phone number would be a huge step towards feature parity.

The second problem is a lack of adoption. RCS does work over Wi-Fi, and if your recipient also uses RCS, you won’t be charged carrier fees for texting. This is mostly relevant for international texting.

But while this is technically feasible, adoption is nowhere near enough to be reliable.

As a European, WhatsApp is my trusty messaging companion. I can text across borders, knowing that I will never be charged international texting fees.

Google Messages has a feature that lets you lock a conversation to RCS-only communication, but a quick scroll through my contacts on Google Messages reveals that most are still using SMS.

To establish true feature parity with iMessage, Google needs to make RCS the default messaging service for Android. It won’t be a smooth changeover, but it’s necessary.

iMessage is struggling to maintain its position

While Google needs to iron out the problems with Google Messages, the app is well on its way to becoming just as effective as iMessage.

Widespread RCS adoption means we’ll have much more choice over the apps we use. There’s plenty of opportunity here, and Google can’t rest after its surprise victory.