Google Voice Android APK shows RCS-related code
Android Authority reported on November 11, 2026, that after dissecting Google Voice Android version 2026.11.01.10, it found RCS-related strings in the app code, including an item that could label the send button as “RCS,” as well as an RCS chat preference switch and other RCS-related action prompts.
9to5Google reported at the same time that version 2026.11.01.1014278023 also contains the “message_send_button_rcs” string, pointing to an RCS send button independent of SMS, but this feature has not yet been enabled. Both media outlets pointed out that the appearance of related content in the code does not mean the feature has gone live, and Google has not released an official announcement or timeline.
Google Voice currently only supports standard SMS and MMS, and does not support RCS typing indicators, read receipts, or high-quality media transfer. The teardown results only show traces of code under development, and whether it will eventually go live remains uncertain.
Original sources:
Title: Google Voice shows early signs of RCS messaging support
Publisher: Android Authority
Date of publication: 2026-11-11
URL: androidauthority.com/google-voice-rcs-support-apk-teardown-3733929
Source type: media report
Verification: The full article content was read for this report; verification date 2026-11-12; no access restrictions
Supporting content: RCS-related strings were found in version 2026.11.01.10, including the send button labeled RCS and the RCS chat switch; currently only SMS/MMS are supported; the feature has not gone live and there is no official timeline. This does not prove that the feature has been fully developed or is about to be released.
ABAB AI Insight
Google has long promoted RCS as an upgraded standard for SMS, and has implemented typing indicators, read receipts, and high-quality media sharing in Google Messages, while publicly urging Apple to support RCS. Google Voice, as a VoIP service that provides an independent number and can be used across devices, has long remained limited to SMS/MMS, leaving users excluded from RCS features in group chats and cross-platform communication.
Teardowns by Android Authority and 9to5Google show that related code exists as strings in the latest Android APK, but it is not activated. For years, user feedback and media commentary have pointed out that Voice’s lack of RCS reduces the practical value of a unified number, especially now that other Google products and major carriers have moved to RCS.
Compared with the full RCS implementation in Google Messages, Voice’s code traces stop at interface labels and switches, with no detailed implementation of complete media handling or encryption appearing. Whether Google will connect Voice to its own Jibe RCS infrastructure, or only use it as a limited functional supplement, is not disclosed in the material.
If it eventually goes live, Voice users could gain rich media capabilities close to Google Messages while keeping an independent number, reducing the need to switch between a main number and a secondary number. The appearance of code itself only shows that development work has started; the launch time, support scope, and whether it will cover the web/iOS side still depend on subsequent version updates.
ABAB News · Cognition Law
The appearance of code strings does not mean the feature has gone live; interface labels can be written in before the full implementation.
For products that have long lacked RCS, the cross-device value of a unified number is diluted once the standard becomes widespread.
Support progress for the same standard across different products from the same company can remain out of sync for a long time.