Google Messages is now the default SMS and RCS app on most Android phones, and the gap between it and third-party messaging apps has narrowed dramatically. We used it as our only SMS app for a month to see what it does well and where it still stumbles.
The Role Google Messages Plays Now
Google Messages is the default text messaging app shipped with most Android phones and installable on the rest. It handles traditional SMS, modern RCS messages that look and feel like iMessage or WhatsApp threads, and MMS attachments. It also includes end-to-end encryption for RCS conversations between two Google Messages users.
The important context is that RCS adoption finally reached a tipping point over the past two years. Apple added RCS support to iMessage in iOS 18, which means Android-to-iPhone conversations now include read receipts, typing indicators, high-resolution media, and most of the polish that iPhone users previously only experienced within iMessage. This changes the mobile messaging landscape more than any Android app release in a decade.
What RCS Actually Delivers
In a conversation between two RCS-capable phones, Google Messages behaves like a modern chat app. Typing indicators appear. Read receipts are shown if both users enable them. Media is sent and received in high resolution. Reactions attach as emoji to specific messages. Replies thread properly. The difference between an RCS thread and an SMS thread is immediately visible in the interface and in the quality of the experience.
What is new in 2026 is that these features now work in cross-platform threads with iPhones running iOS 18 or later. We tested this extensively and confirmed that read receipts, typing indicators, and high-res media all propagate correctly between Google Messages on Android and iMessage on iPhone. The green bubble stigma is not dead, but the functional gap behind that stigma is almost closed.
End-to-End Encryption
RCS conversations between two Google Messages users support end-to-end encryption, indicated by a small lock icon next to messages and the Send button. This is comparable to Signal or WhatsApp for those specific conversations. Group chats, cross-platform threads with iPhone users, and conversations with non-Messages RCS clients do not get this encryption.
For users whose security needs are high, a dedicated encrypted messenger is still the correct answer. For typical users whose threat model is more about casual privacy and less about a motivated attacker, having encryption default-on for most Android-to-Android conversations is a meaningful improvement over SMS.
Spam Filtering
Google Messages includes automatic spam detection that moves suspected spam SMS into a separate folder. The filter has become noticeably more aggressive over the past year, catching text-message phishing attempts, package-delivery scams, and political spam that used to land in the main inbox.
Occasional false positives happen, where a legitimate message from a new number is flagged. The spam folder is easy to check and messages are easy to rescue, but it is worth checking the folder periodically to make sure nothing important has been misfiled.
Media Handling and Attachments
Photos and videos sent via RCS retain their original quality. Over SMS or MMS, media is compressed heavily, which is a limitation of the underlying standard and not something Messages can fix. Voice messages are supported with a hold-to-record interface. Location sharing is built in and works well.
Attached PDFs, documents, and audio files work in RCS threads and get downgraded to MMS links in SMS threads. The experience is good when both sides are on RCS and workable when one is not.
The Desktop Experience
Messages for web pairs your phone with a browser tab via QR code and lets you send and receive messages from a laptop. The pairing is per-browser and lasts about two weeks before re-authentication is needed. The experience is good enough that we routinely reply to texts from the computer rather than picking up the phone.
Notifications sync between phone and web correctly, and reading a message on one side marks it read on the other. For users who spend their day at a computer, this feature alone is a daily convenience that competitor SMS apps on Android have historically done worse.
Where Messages Still Has Rough Edges
The app occasionally takes a few seconds to open on first launch in a cold start, especially on older phones. The initial animation when composing a new message feels slower than it should. Group chat management for very large groups could be more sophisticated; naming, muting, and member management are all present but not luxurious.
The transition from SMS to RCS in a thread sometimes requires a few sent messages before the app detects both users are RCS-capable. This is more of an RCS standard quirk than a Google Messages problem specifically, but users notice it in the app.
Who Should Install It
Every Android user should have Google Messages as their default SMS app in 2026. The RCS features, the cross-platform compatibility with iPhone, and the end-to-end encryption for Android-to-Android threads make it the obvious choice. On most phones it is already the default; if a manufacturer-skinned SMS app is installed instead, swapping to Messages is a two-minute change in settings that is worth doing immediately.
The app is free and has no paid tier. There is no advertising inside the message threads themselves. It is one of Google’s quieter successes in the Android ecosystem.
Disclaimer: LORDAPK is an independent editorial publication. We are not affiliated with Google LLC. The button above routes to the official Google Play Store listing. We do not host APK files.