1. Regulatory focus
The Commission’s May 11, 2026 DMA factsheet explicitly extends interoperability beyond messaging apps into device transfer and connected-device experience, naming full device data transfer and eSIM transfer alongside notifications, proximity pairing, background execution, and automatic Wi-Fi connection. The April 27, 2026 Android consultation shows the same regulatory direction: enforcement is moving from app-level rivalry to operating-system control over hardware, software, and contextual access. For messaging, authentication, and companion-device services, control of notification surfaces, switching workflows, and default user flows is now being treated as a market compliance issue.
2. Business impact
The practical effect is immediate for businesses that depend on SMS OTPs, OTT login prompts, wearable notification relay, and multi-device session continuity. Historically, users switching between iPhone and Android, or receiving alerts on watches, earbuds, or in-car systems, often faced broken authentication flows, delayed notifications, failed re-provisioning, and higher support volume because OS-level permissions and background access were uneven. As regulators treat those frictions as non-neutral platform control, providers gain a stronger basis to demand equivalent technical access, but they also inherit new implementation work around permissions, consent logging, migration logic, and fallback messaging design.
3. Operating recommendations
Treat switching compliance as part of your messaging and identity stack, not just a UX or retention project. First, map where OTP delivery, security alerts, SIM/eSIM reprovisioning, device pairing, and notification mirroring depend on OS notifications, background execution, or number migration. Second, build Europe-specific migration playbooks for both iOS and Android, including consent capture, fallback SMS when transfer fails, old-device de-registration, and support verification scripts. Third, track DMA consultations, implementation milestones, and platform framework releases so commercial promises on cross-device continuity are backed by compliant technical readiness.