Apple and Google just made phones less sticky. Mobile teams need a new playbook.

On May 12, Apple shipped iOS 26.5 to every supported iPhone. The same day, Google ran The Android Show: I/O Edition 2026, with a co-headline that would have sounded absurd two years ago. Apple and Google are cooperating to let users move between iPhone and Android, wirelessly, taking their passwords, photos, messages, apps, contacts, and eSIM with them. Pixel and Galaxy first, more devices through the rest of 2026.

That is the story for users. For mobile teams the story is different, and it shows up in three quieter places. A new App Store subscription tier. Granular contact permissions on Android. RCS end-to-end encryption between iOS and Android. Together they signal that the lock-in assumptions a lot of mobile product strategy is built on are weakening.

What actually shipped this week

iOS 26.5 enables a Transfer to Android flow in Settings, with options to share message attachments for none, 30 days, 1 year, or all. RCS E2EE rolls out gradually, default-enabled, controlled via Settings, Messages, RCS Messaging. On the App Store side, Apple opened a monthly billing tier with a 12-month commitment, available worldwide except in the US and Singapore. EU users also get Live Activities for third-party accessories and continued work on third-party audio switching, both driven by the Digital Markets Act.

The Android Show added the other half. Wireless iPhone-to-Android transfer launching on Pixel and Samsung first. Quick Share now compatible with AirDrop across Samsung, Oppo, OnePlus, Vivo, Xiaomi, and Honor. Adobe Premiere arriving on Android. For developers, Android 17 introduces granular contact access (request specific contacts instead of the whole list) and Screen Reactions for simultaneous user reaction and screen capture.

Why this matters more than the iOS 27 roadmap

The interesting tension here is that none of these features are individually new news. The combined picture is that switching phones is going to keep getting easier, and the regulator pressure behind it (the EU's DMA) is not going away. Apple and Google are doing this because they have to, and because they have each calculated that user portability is now cheaper to give than to fight.

For app teams, the implication is that you cannot model retention around platform stickiness anymore. We have seen this pattern up close in our travel-platform work, where customers compared mobile and web checkout and we learned that "they're on iOS, they'll stay" is not a strategy. The product has to earn the keep on each side.

Three things mobile teams should do now

Audit how much of your retention is platform-locked. If a meaningful chunk of your users would churn the moment Transfer to Android is a few taps, you have a product problem disguised as a platform advantage. In our native iOS and Android projects for healthcare and IoT clients, we run the same engagement metrics on both stores and treat any large gap as a signal to investigate, not to celebrate.

Revisit your subscription pricing. The new monthly-with-12-month-commitment tier is genuinely useful for products with high lifetime value but a sticker-shock annual price. We have seen subscription apps cut churn by giving users a lower entry point without committing them to month-to-month economics. Worth modelling for your audience before assuming "annual or monthly" is the whole space.

Update your Android contact permission flow. The granular contacts API on Android 17 is the kind of change that is easy to miss in release notes and easy to ship worse than competitors do. Asking for the whole contact book when you only need three people will increasingly get you flagged in privacy reviews and in store rankings. Same lesson we learned shipping the iOS contact picker pattern over full-access requests in our development work for e-commerce clients.

If you handle messaging, RCS E2EE is now your problem

RCS end-to-end encryption between iPhone and Android is a quiet but big change. Carrier rollout is gradual, the protocol is GSMA's, and it changes the assumption that cross-platform messages travel in the clear. If your product involves messaging (customer support, marketplace chat, healthcare patient comms), this is the moment to check whether your fallback paths still leak metadata, whether your retention policy survives E2EE, and whether your compliance story matches what the platforms now do by default. In our security reviews for enterprise clients, the most common finding in messaging-adjacent features is that they assume transport-layer encryption only and quietly downgrade when the user composes outside the app's own channel.

If retention, store policy compliance, or cross-platform messaging strategy for a native iOS or Android app sounds familiar, let's talk.