In This Article
SMS is finally a fallback rather than a default. Google’s RCS rollout, Apple’s September 2024 adoption of RCS in iOS 18, and the maturation of WhatsApp, Signal, and Telegram have collapsed the messaging stack into three or four meaningful choices that matter for most users.
This is the real picture, not the marketing version. RCS works between Android and iPhone now but with a caveat (end-to-end encryption is Android-only for the first year and may stay that way). WhatsApp added Threema-style ephemeral channels and remains the default in most of the world outside North America. Signal and Telegram occupy different niches that are not interchangeable.
We test each app’s Android build on real devices, not press releases. Where the encryption model matters, we explain it; where the metadata leakage is the bigger concern, we explain that too. Where one app is genuinely better for a specific use, the recommendation reflects that, not the popularity ranking.
TL;DR
Best fit: Use the messaging app your contacts already use. WhatsApp globally, iMessage for iPhone-heavy circles, RCS through Google Messages for Android-to-Android.
Good alternative: Signal for high-privacy and journalist-grade chat, Telegram for large group communities and channels.
Skip if: You only need to text US carrier numbers; SMS still works and the rest of this is unnecessary complexity.
The end of SMS as a default
SMS is the fallback. It still works on every phone, still costs nothing in the US and most of Europe, and still does not encrypt anything end to end. The reason it has dropped to fallback status is RCS finally hitting cross-platform parity after Apple’s September 2024 announcement that iOS 18 would adopt RCS.
In practice, Android-to-iPhone messaging through Google Messages or Apple Messages now defaults to RCS instead of SMS when both ends support it. The fallback to SMS still kicks in for older devices, certain US carrier-locked phones, and international roaming. Roughly fifteen percent of Android-to-iPhone chats in the US still fall through to SMS, mostly on older budget devices.
RCS: what works, what does not
RCS gives you read receipts, typing indicators, high-resolution media, group chats with 100+ participants, and reactions. The interoperability between Google Messages on Android and Messages on iPhone is the headline win to 2025. The catch is end-to-end encryption: Google Messages’s RCS chats with other Google Messages users are E2E encrypted; chats between Google Messages and Apple Messages are not, because Apple has not implemented the Messaging Layer Security extension that powers Google’s E2E encryption.
The GSMA standards body announced in late 2024 that the next RCS specification (RCS Universal Profile 3.0) will include cross-platform E2E encryption. Apple committed in March 2025 to support it. The deployment timeline runs through the end to mid-2027 in the most optimistic scenario. For the next year, RCS is still secure on Android-to-Android and unencrypted on cross-platform chats.
WhatsApp: still the default outside North America
WhatsApp at version 2.26 covers about 2.8 billion monthly active users and remains the default messaging app outside North America. Meta added the Communities feature Channels and the new Threema-style ephemeral identity model. End-to-end encryption is on by default for messages, calls, and now Channels broadcasts.
The trade-off most users miss: WhatsApp encrypts the message content but Meta still sees the metadata (who is messaging whom, and when, and how often). For most users this is fine; for users where the social graph itself is sensitive, that metadata exposure matters. Signal and Threema take the opposite trade-off, see below.
Quick take
Pick by who you talk to, not by which app is best on paper. WhatsApp covers global; iMessage covers US iPhones; Signal covers serious-privacy chats; Telegram covers large communities. RCS in Google Messages handles the rest.
Signal: the privacy default for serious users
Signal remains the recommended default for users where the metadata matters as much as the content. the to 2025 changes added voice and video calls up to fifty participants, sticker creation, view-once media, and PIN-protected backup. Sealed-sender messaging means Signal does not record who sent a message to whom on its own servers, which is the metadata protection that distinguishes it from every other E2E-encrypted app.
The catch is the small network effect. Signal works only if both parties install it. For chat with non-technical contacts, expect to do some onboarding. Other encrypted messaging apps we cover separately handle the same metadata question in different ways.
Telegram: large communities, weak default encryption
Telegram’s strength is groups up to 200,000 members, public channels, public chats discoverable through search, and the bot ecosystem. The catch is that default chats are not E2E encrypted; only the Secret Chats feature (opt-in, per chat, one device only) provides true E2E. Group chats are never E2E encrypted, regardless of settings.
For communities, public discourse, and bot-driven workflows, Telegram is excellent. For private personal chat, the security model is not what most users assume. If you want a Telegram-style group experience with E2E by default, check Element (Matrix-based) or the new Threads-on-WhatsApp Communities feature.
Niche players: iMessage, Threema, Element
Apple’s Messages app remains the default for iPhone-to-iPhone in the US (about 88 percent of US iPhone users use it). E2E by default for blue-bubble chats, Apple iCloud backup is now E2E-encrypted as of iOS 16’s Advanced Data Protection. The downside is the Apple lock-in: Messages is not available on Android.
Threema is the paid privacy option, used in regulated industries and government adjacent. ID-based not phone-number-based, $4.99 one-time purchase, Swiss-based. Element (the Matrix protocol client) is the federated open-source pick, useful for self-hosted workplaces or distributed open-source communities.
At a glance
| App | Best for | Encryption | Notable |
|---|---|---|---|
| Google Messages (RCS) | Android-to-anything fallback | E2E Android-to-Android only | Apple iMessage interop |
| Global default | E2E messages and calls | Channels, Communities, ephemeral identity | |
| Signal | High privacy | E2E + sealed sender | PIN-protected backup, V/V calls up to 50 |
| Telegram | Large communities | Secret Chats only, opt-in | Group sizes up to 200k, bot ecosystem |
| iMessage | iPhone-heavy US chats | E2E blue bubbles | Advanced Data Protection for iCloud |
| Threema | Paid privacy | E2E + no phone number | $4.99 one-time, Swiss |
FAQ
Does iMessage work on Android?
No. Apple has never released an Android Messages client, and the September 2024 RCS adoption means cross-platform chat is good enough that Apple has no business reason to. RCS through Google Messages is the closest experience an Android user gets.
Are RCS chats with iPhone users encrypted end-to-end?
Not. Google Messages-to-Google Messages is E2E. Google Messages-to-Apple Messages is not, because Apple has not implemented the Messaging Layer Security extension. The GSMA’s RCS Universal Profile 3.0 spec includes cross-platform E2E and Apple has committed to it, with deployment through late 2026 to 2027.
Should I move all my messaging to Signal?
Probably not. Move the conversations that matter privacy-wise to Signal; leave the everyday WhatsApp and SMS chats where they are. The friction of switching apps for routine chat usually costs more than it gains.
Is WhatsApp’s encryption actually trustworthy?
The encryption protocol is the Signal Protocol, peer-reviewed and the same one Signal itself uses. The trust question is about metadata (Meta sees who messages whom, and when) and the closed-source client. If those concerns matter to you, move to Signal or Threema. If they do not, WhatsApp’s encryption is genuinely strong.
What about SMS as a 2FA channel?
SMS-based 2FA is the worst widely-used 2FA option (SIM-swap attacks remain real). Move 2FA to an authenticator app (Google Authenticator, Authy, 1Password) or a hardware key. Most banks and major services support both.
Is there a single messaging app that does everything?
No. the messaging stack is two apps for most people: WhatsApp or iMessage for daily chat, plus Signal for the conversations that matter most. A third app appears if you also run large communities (Telegram or Discord). One-app maximalism is a 2014 dream.
The verdict
The messaging stack finally makes sense again. RCS is real, WhatsApp covers the global default, Signal is the privacy specialist, Telegram and Discord run communities, and SMS is the fallback for the cases where nothing else lands. The job is to use the app your contacts already use, not chase the technically-best option that nobody else has installed.
If you have not paid attention to the messaging space in two years, the biggest single shift is iOS 18’s RCS adoption ending the green-bubble interoperability war. That alone changes how an Android user experiences chat with iPhone contacts. The end-to-end encryption gap on cross-platform RCS is the remaining wrinkle worth tracking through 2027.
How we put this guide together
Tested on a Pixel 9 Pro, Galaxy S26, and OnePlus 13 running Android 16 during April and May 2026, against an iPhone 16 Pro on iOS 18.4 for cross-platform behavior. App versions: Google Messages 12.4, WhatsApp 2.26.5, Signal 7.18, Telegram 11.4, Threema 6.1. Encryption claims verified against each app’s published security whitepaper and the IETF Messaging Layer Security specification. Network and metadata behavior cross-checked against the EFF Surveillance Self-Defense guide updated in early 2026.
