Apple’s latest point release, iOS 26.5, is doing something users have asked for — for years: when the technical pieces line up, messages between iPhones and Androids can now be end‑to‑end encrypted. It’s not flashy, but it’s the kind of behind‑the‑scenes change that actually improves day‑to‑day privacy for millions.
What changed (and how you’ll know it’s working)
iOS 26.5 introduces end‑to‑end encryption for RCS — the modern replacement for SMS used by many Android phones — and that encrypted conversation will show a small lock icon when everything is set up correctly. The feature is rolling out in beta and depends on a few moving parts: the iPhone must be on iOS 26.5, the carrier must support RCS encryption, and the Android participant needs the latest Google Messages app. If any of those links in the chain aren’t present the chat can still fall back to older, unencrypted standards.
The industry took notice: carriers, Google and Apple coordinated on this one, and GSMA framed it as a milestone for cross‑platform messaging. If you want a deeper look at the mechanics and launch details, there’s dedicated coverage of how iOS 26.5 brings encrypted RCS to iPhone↔Android conversations here. Apple also first let testers poke at these changes in the public beta that rolled out the RCS and Maps tweaks, so some of the behavior you’re seeing now was previewed earlier.
A few practical points: this is encryption for RCS, not legacy SMS. If a message is forced down to SMS/MMS, it won’t be end‑to‑end encrypted. And like all device‑level crypto, it won’t protect you if one of the phones is already compromised, if someone screenshots the conversation, or if insecure backups expose the content.
The small but useful extras that came with 26.5
iOS 26.5 isn’t just about RCS. Apple tucked in a few other quality‑of‑life changes:
- Maps now suggests places when you tap the search field — little nudges based on nearby trends and prior searches that make discovery a touch faster.
- The App Store gained a new subscription format: an annual plan split into 12 monthly payments (a “monthly with 12‑month commitment” option). It’s intended to give developers more pricing flexibility and to make yearly commitments easier on wallets — though Apple has limited availability in some markets for now.
Those additions aren’t headline‑grabbing, but they smooth friction points people complain about: messy cross‑platform chats, clunky discovery in maps, and sticker‑shock on annual app subscriptions.
Rolling out, and why Apple is moving fast behind the scenes
Even as 26.5 arrives, Apple’s engineers are already testing small follow‑ups. Visitor logs picked up ramped‑up testing of iOS 26.5.1 — a likely minor patch for bugs and security fixes — and signs point to early work on iOS 26.6. At the same time Apple is preparing to turn its attention to iOS 27 ahead of WWDC in June.
One consequence of this push: Apple has stopped signing some older builds, which means downgrading becomes harder once you move up. That lock‑in is part practicality (encouraging users to stay on patched releases) and part safety — older versions can have known exploits. If you were thinking about returning to 26.4, Apple’s move to stop signing older releases is already in effect and worth keeping in mind here.
Expect the encrypted RCS rollout to be gradual. Carriers flip switches, Google pushes updates to Messages, and Apple refines edge cases. For many users the change will be invisible until the lock icon appears in a conversation; for others it will solve long‑standing annoyances like low‑quality media or broken group threads across platforms.
This isn’t the end of the story. Apple still favors iMessage between Apple devices, and iMessage remains the most seamless, feature‑rich and heavily encrypted path for iPhones. But by bringing encrypted RCS into the mix, Apple has reduced one of the major cross‑platform friction points — and that matters more often than you’d think.
If you want to track the small updates and betas that led here, the developer and public betas for 26.5 showed the Maps and RCS changes before general release, and those threads are a useful playbook for what Apple prioritizes next in the beta trail.
