GrapheneOS is building native RCS support into its own Messaging app, a step that will let the privacy-hardened Android fork stop leaning on Google Messages for anything beyond plain SMS.
The project is best known for stripping Google’s default reach out of Android: no Play Services baked in, no telemetry phoning home, no Google apps unless a user sideloads them. That reputation was built around the operating system itself. GrapheneOS RCS support is the clearest sign yet that the project’s ambitions have moved past the OS layer and into the everyday apps people actually open, starting with messaging.
A Messaging app rebuilt in Compose
AndroidAuthority reports that GrapheneOS is preparing a new release of its Messaging app with a completely overhauled interface built on Android Compose, alongside what the developers describe as a massive amount of other improvements and bug fixes. RCS support is part of that same push, and once it lands it will let GrapheneOS users get read receipts, typing indicators and higher-resolution media inside the OS’s own app instead of installing Google Messages to get those features.
The same release adds a secure paste feature that stops other apps from reading clipboard data copied elsewhere. Android’s clipboard has historically been readable by any app with basic permissions, which matters more than it sounds: a verification code or password copied from one app can sit exposed to whatever else is running until something overwrites it. Restricting that access at the OS level closes a leak most people never think to check for.
Why cutting out Google Messages matters here
RCS has never been a neutral protocol on Android. Most carriers route it through Google’s own backend, and for years the only practical way to get RCS features on a Google-free build of Android was to install Google Messages itself, complete with its ties to Google Play Services. For a project whose entire premise is minimising Google’s footprint on the phone, that has always been an awkward exception. Native GrapheneOS RCS support closes that gap: it keeps rich messaging inside an app the project controls and audits, rather than requiring users to bring in the one Google app the whole distribution was built to avoid.
What Google’s own Messages coverage says about it
The two outlets covering this corner of Android this week were not covering the same story. AndroidAuthority published its report on the GrapheneOS overhaul first; by our arithmetic, 9to5Google’s regular roundup of new Google Messages features followed roughly five hours later, and it tracks Google’s own A/B-tested rollouts rather than anything from GrapheneOS. Google Messages routinely trials features for a long stretch before they reach stable, and nothing in that pipeline references ceding any ground to a third-party RCS client. That gap is the story: GrapheneOS is building its way out of Google Messages on its own schedule, not as part of any arrangement with Google.
GrapheneOS hasn’t given a firm release date for the Compose-based Messaging app, and it isn’t yet clear whether RCS ships in that same build or arrives in a follow-up update. That timing, and whether the secure paste feature gets picked up by other privacy-focused Android forks, is worth watching once the release lands.
