Back to benri.tech

WristMSG for Google Chat

The missing Wear OS companion to start, manage, and send Google Chat messages from your wrist.

Why WristMSG?

Google Chat on Wear OS is currently limited to receiving notifications. WristMSG bridges the gap, allowing professional users to initiate conversations and send quick pings without reaching for their phone.

Key Features

How WristMSG works

WristMSG does not log into your Google account and does not call the Google Chat API. It reads incoming Google Chat notifications on your phone using Android's standard Notification Listener permission (BIND_NOTIFICATION_LISTENER_SERVICE), the same mechanism every notification-mirroring app on the Play Store uses, and forwards a minimal subset to your paired Wear OS watch. Your reply goes back through the notification's reply intent, the same path Google's own notification reply box uses.

The Notification Listener permission is used strictly inside the app. We do not store, log, or transmit your notification data externally. Only notifications from the official Google Chat package (com.google.android.apps.dynamite) are processed; all others are ignored.

Reply to Google Chat from your wrist: here's what to expect

WristMSG lets you reply to Google Chat from your watch by securely reusing Chat's own reply action. Once someone messages you, that conversation stays ready (green) on your watch so you can fire back instantly, without waiting for a new message to come in.

What to expect

When a conversation might show "not ready" (orange)

A phone restart, an app update, or aggressive memory management on some OEM devices reclaiming the app after a long idle stretch. In every case the fix is automatic: the next message in that conversation re-enables instant reply. Nothing is lost, an old, idle conversation just needs one fresh message to re-arm.

For the most reliable experience

For teams & IT administrators

WristMSG is suitable for deployment to managed device fleets via Managed Google Play. Zero-server architecture, no analytics SDKs, no DPA required (we collect no data). See the Deployment Guide for IT-admin documentation, or the Teams page for volume pricing inquiries.

Frequently asked questions

How long will a conversation stay ready (green)?

With Keep-Alive on and Unrestricted battery for both apps, a ready conversation typically stays repliable for multiple days. We've seen reply windows survive 3 days or more in our own testing. We don't promise an exact number because some Android OEMs manage background apps more aggressively than others, and a phone restart or app update always resets the window.

What does the green/orange indicator mean?

Green means the conversation is ready, so you can reply instantly from your watch. Orange means the reply window has lapsed (after a phone restart, an app update, or aggressive memory management on some OEM devices during a long idle stretch). The next incoming message in that conversation automatically re-arms it; you don't need to do anything.

What is Keep-Alive and where do I turn it on?

Keep-Alive helps the system keep WristMSG resident so reply windows survive longer between messages. Turn it on in Settings → Reliability → Always On. We recommend leaving it on for the most reliable experience.

Why do I need to set Unrestricted battery usage?

This is the single biggest reliability factor. Android's default battery management can force-stop background apps, including WristMSG and Google Chat, which closes the reply window. Setting both apps to Unrestricted (Settings → Apps → [app] → Battery) prevents that.

If a conversation goes orange, do I lose messages?

No. Nothing is lost. Orange just means an old, idle conversation needs one fresh incoming message to re-arm instant reply. You'll still receive that next message normally, and after it arrives the conversation is ready again.

Does WristMSG sign into my Google account?

No. WristMSG never logs into Google and never calls the Google Chat API. It reuses Chat's own notification reply action via Android's standard Notification Listener permission. Your reply takes the same path Google's own notification reply box uses.