An internal build of Google Messages 6.2 shows end-to-end encryption could be coming soon to RCS messages
Today, the folks at APKMirror got ahold of an internal “dogfood” build of Google Messages version 6.2. Here, “dogfood” is used in the sense of the phrase “eat your own dog food,” …
Context & Ripple Effects
This May 2020 APK teardown caught the earliest visible code for a project Google spent the next three years shipping in stages. Months after this internal 6.2 build surfaced via APKMirror, Google announced it had finished rolling out RCS globally and would begin encryption testing in Messages — the first official confirmation of what the dogfood build implied.
From there the roadmap unfolded exactly along the lines the leak suggested: one-to-one RCS chats gained encryption at Google I/O 2021, Google confirmed group-chat encryption in mid-2022, and open testing followed that December. The reason this matters: encryption was the main functional gap between RCS and established secure messengers, and closing it was a precondition for making Messages a serious default texting client rather than an SMS app with extras.
First-order effects
- Dogfooding puts encrypted RCS traffic on real devices inside Google, the validation stage immediately before public beta — meaning the feature had moved past prototyping into internal use at the time of this build.
- For Messages users, the change lands only when both parties are on upgraded RCS clients, so adoption depends on Google pushing the feature through its own app rather than waiting on carrier software.
Second-order effects
- Carriers stay gatekeepers even as Google adds the privacy layer: later rollout coverage shows RCS activation still routed through carrier terms of service, so Google's encryption push advances only as fast as those agreements allow.
- With encryption covering RCS chats inside Messages, the differentiation between Google's client and whatever messaging apps ship preloaded on rival Android phones narrows to features, pressuring OEMs to keep Google Messages front and center.
Third-order effects
- If the staged pattern holds — protocol rollout, one-to-one encryption, group encryption, then default-on — RCS becomes a carrier-backed protocol that absorbs the privacy features consumers previously had to switch apps to get, shifting secure texting from a per-app choice to a network capability.
The trend: Carrier-grade messaging is incrementally absorbing consumer messenger privacy features, with Google's Messages client acting as the delivery vehicle for end-to-end encryption on RCS.