Google Messages Could Finally Add Emoji Reactions on Wear OS

Google Messages Could

Google is developing new features for its Messages app on Wear OS that could change how users interact with text messages on smartwatches. Code removed from the latest app files suggests that users will soon be able to react to texts with emojis and mark messages as read directly from their watch notifications.

At present, Android users can react to messages with emojis and Photomojis from their phones. These reactions show up on both phones and connected Wear OS devices, but the watch app itself does not let users add reactions from the watch. The hidden code now points to a new MessageReactionsActivity screen that would let users choose emoji reactions right from the smartwatch interface.

The code defines strings like “React with %1$s” and “Remove %1$s reaction,” confirming that the emoji picker will be usable on the watch. It is not yet clear whether these options will include the larger Photomojis available on the phone version of Messages, but users will at least be able to see them when others react from phones.

The code contains a new feature which enables users to mark Wear OS notifications as read through the upcoming “Mark as read” button implementation. Users must open the Messages app on Wear OS to read messages because the current system lacks a read function. The button will provide users with the same notification management feature which Android users currently possess, which allows them to delete unread notifications with one button press.

The new update will help users who use their smartwatch to execute instant replies and handle basic message functions. People will find it easier to express themselves during conversations when they can use emoji reactions directly from their smartwatch instead of using their smartphone. The “Mark as read” feature allows users to manage their unread message count because it helps them eliminate unnecessary messages.

Developers use APK teardown to discover these features because it allows them to check app packages before the official release of new code. The existence of these options in the codebase does not guarantee their future implementation for public release. Google will test the features but they will become unavailable because the company has decided to change its focus.