If you’ve ever received a text from an iPhone user that reads “Laughed at ‘hey are you coming tonight?’” instead of just showing a laughing emoji — you know the pain. That little text description of a reaction is one of the most annoying artifacts of the Android-iPhone messaging divide.

Google just fixed it.

Yesterday, Google announced a set of updates to Google Messages that target exactly this kind of friction. They’re not flashy. They won’t make headlines the way a new Pixel launch would. But they’re the kind of quality-of-life improvements that make cross-platform texting — something most of us do dozens of times daily — significantly less awful.

Emoji Reactions That Actually Look Like Reactions #

The biggest change: when an iPhone user reacts to your message with an emoji, Google Messages now translates that reaction into an actual emoji on the message bubble. No more “Loved an image” or “Emphasized ‘sounds good.’” Just the reaction, rendered the way it was intended.

This sounds trivial. Honestly, it kind of is.

But it’s also something that affected millions of conversations every day. The old behavior wasn’t just ugly — it broke conversational flow. You’d get a notification, open the thread, and spend a second parsing what “Laughed at…” even meant in context. Now? It just works.

The engineering here is interesting if you stop to think about it. Apple’s iMessage sends these reactions as a specific protocol extension. When those reactions hit an SMS/MMS recipient, they get downgraded to plain text because SMS has no concept of message reactions. Google’s solution: build a translation layer inside Messages that pattern-matches these text descriptions and converts them back into visual reactions.

It’s a hack. But it’s a clever hack.

Google Photos Integration for Video Sharing #

The second big update: Google Photos integration for sharing videos. If you’ve tried sending a video over MMS to an iPhone user, you know the result — a compressed, pixelated mess that barely resembles what you recorded. MMS caps file sizes at somewhere around 1-3.5MB depending on the carrier, and modern phone videos blow past that in seconds.

The workaround Google built: when you try to send a video in Messages, it now offers to share via a Google Photos link instead. The recipient gets a high-quality version they can view directly from the link. No compression, no quality loss, no app install required.

This is one of those features where the implementation reveals the underlying problem. RCS handles media sharing natively — high-resolution photos and videos, no file size caps, no compression artifacts. Between two Android phones running Messages with RCS, none of this is an issue.

But the moment you text someone on an iPhone? You’re back to SMS/MMS with all its 1990s-era limitations.

The Broader Picture: Band-Aids on a Protocol Gap #

I don’t want to be cynical about these updates. They’re genuinely useful, and the teams that built them clearly thought hard about the UX.

But let’s be honest about what they are: workarounds for a fundamental interoperability gap.

Android-to-Android messaging over RCS is excellent. End-to-end encrypted (for 1:1 chats, since June 2021), high-quality media, typing indicators, read receipts, reactions — all the stuff you’d expect from a modern messaging platform. The experience falls apart the moment an iPhone enters the conversation because Apple hasn’t adopted RCS. Everything degrades to SMS/MMS.

Google’s been vocal about this. The “Get The Message” campaign is essentially a public pressure play aimed at Apple — support RCS so cross-platform messaging doesn’t feel like stepping back in time. Whether that pressure works is anyone’s guess. Apple has strong incentives to keep iMessage as a differentiator; the blue bubble vs. green bubble distinction isn’t accidental.

In the meantime, Google’s strategy seems clear: make Messages as good as possible even when the other side won’t cooperate. The emoji reaction translation and Google Photos integration are textbook examples. Can’t get Apple to adopt RCS? Fine. Build clever bridges over the protocol gap.

What I’d Like to See Next #

A few things I’m watching for.

Group messaging between Android and iPhone users is still a disaster — MMS group threads are unreliable, messages arrive out of order, and there’s no way to name the group or manage participants. Any improvement there would be massive.

I’d also like to see the Google Photos integration go both ways. Right now it helps when you’re sending video out, but receiving compressed video from iPhone users is still painful. That’s harder to solve since it requires something on the sender’s side, but worth thinking about.

The reaction translation could expand too. Right now it handles the standard set of iMessage reactions — love, like, dislike, laugh, exclamation, question — but there’s room for more edge cases. Especially as Apple adds new reaction types in future iOS versions.

Why This Matters Beyond Messaging #

These updates are small individually, but they tell a bigger story about how the messaging landscape is evolving. Google’s betting hard on RCS as the successor to SMS, and they’re willing to invest in making the transition smooth even when key players (read: Apple) aren’t on board.

For developers building on messaging platforms, the takeaway is that the interoperability layer between protocols is where a lot of innovation happens. It’s not glamorous work — translating emoji reactions and generating shareable photo links won’t win any architecture awards. But it’s the kind of pragmatic engineering that actually improves people’s daily experience with their phones.

And honestly? That’s what good product engineering looks like. Not waiting for the perfect world where everyone’s on the same protocol, but shipping meaningful improvements within the constraints you actually have.