better than nothing? —
Update cuts down on the disruptive blocks of text generated by Apple’s Tapbacks.
Putting aside the lack of end-to-end encryption support, one of the most annoying things for Apple iPhone users about communicating with Android users via SMS are all the iOS features that get lost in translation. Having a visual effect translated to a deadpan “(sent with Balloons)” ruins whatever impact you intended the effect to have, and it clutters up your message history with extraneous text.
On that second front, Apple’s Tapback feature is especially annoying. When using iMessage, this short list of half a dozen reactions is a handy way to signal acknowledgement or enjoyment, or just to bump a message thread to the top of someone’s list. On Android phones, each individual Tapback generates an entirely new block of text with a text description of the reaction and the entire original text. As a fallback option for non-smartphones or an accessibility feature, this isn’t necessarily a bad thing. But it can quickly make SMS group-text threads chaotic and unreadable for Android users.
A new update to the Google Messages app, which was spotted over the weekend by 9to5Google and appears to be rolling out to some Android users now, fixes that issue by translating Tapback responses into emoji responses. Android devices using the Messages app have been able to send each other emoji responses for over a year now, but this is Google’s first attempt to map Apple’s response mechanism to its own.
Of course, in an ideal world, the non-stopgap solution to this communication problem would be for Apple to add RCS messaging support to iPhones, or for it to make iMessage an open standard, or for Apple and Google and the world’s phone carriers to get on the same page about a single standard that they can all support. In the meantime, at least a simple “thumbs up” response can be seen and understood regardless of what smartphone ecosystem you’re embedded in.