The DMA interoperability obligation is the set of duties in the EU Digital Markets Act that requires a designated gatekeeper to let rival products and services work with its core platform services on fair, effective and free terms. In platform regulation, it is one of the most technically demanding rules, because compliance requires engineering changes to operating systems and messaging apps rather than only changes to contracts or policies.
Two provisions carry the obligation. Article 6(7) opens hardware and software features controlled by a gatekeeper operating system or virtual assistant, while Article 7 requires interoperability of designated messaging services. Both aim to lower switching costs and weaken ecosystem lock-in, so that competing devices, apps and messengers can reach users without depending on the gatekeeper’s goodwill.
Legal basis and scope of the obligation
The Digital Markets Act, Regulation (EU) 2022/1925, applies only to companies the European Commission has designated as gatekeepers for specific core platform services. The interoperability duties therefore bind named services, such as a mobile operating system or a messenger, and not the whole company. The first designations took effect in September 2023, with compliance due by 7 March 2024.
The following table separates the two legal sources, which differ in beneficiaries, triggers and technical content.
| Provision | Covered service | Who benefits | Trigger |
|---|---|---|---|
| Article 6(7) | Operating systems and virtual assistants | Service providers and hardware makers | Applies directly, requests handled case by case |
| Article 7 | Number-independent messaging services | Rival messaging providers | Formal request against a reference offer |
The obligation is free of charge under Article 6(7): a gatekeeper may not demand a fee for access to the features themselves. It must also provide the same features available to its own services, which is the core of the equal-treatment test.
How operating system interoperability works
Article 6(7) requires effective interoperability with the same hardware and software features that the gatekeeper’s own products use, for example the near-field communication chip, background execution or notification handling. It covers both horizontal access for competing services and vertical access for connected hardware such as smartwatches and headphones.
Where compliance is disputed, the Commission may open specification proceedings under Article 8 and adopt a binding decision that defines the measures in detail. The first such decisions, adopted for Apple’s iOS in 2025, listed features including notification forwarding to smartwatches, automatic audio switching, proximity pairing and Wi-Fi peer-to-peer connections, together with a transparent process for handling developer requests.
| Feature category | Example use by a rival | Why access matters |
|---|---|---|
| Notifications | Third-party smartwatch shows and answers alerts | Parity with first-party wearables |
| Proximity pairing | Rival earbuds connect with one tap | Removes friction that favors own accessories |
| NFC access | Third-party wallet makes contactless payments | Competition in mobile payments |
| Background execution | Companion app keeps a device synchronized | Reliable operation of connected hardware |
| Default handling | Rival app opens links or files by default | Real user choice between services |
Messaging interoperability under Article 7
Article 7 obliges a gatekeeper messaging service to connect with rival services that request it, using a published reference offer that sets out the technical conditions. The functions become mandatory in three phases, which reflects the growing technical difficulty of preserving security in group and real-time communication.
| Phase | Deadline after designation | Required functions |
|---|---|---|
| Phase one | Immediately on request | One-to-one text, images, voice messages, videos and files |
| Phase two | Within two years | Group text messages and media in groups |
| Phase three | Within four years | One-to-one and group voice and video calls |
Crucially, the gatekeeper must preserve the level of security, including end-to-end encryption, across the interoperable connection. A requesting provider must therefore meet comparable security standards. Interoperability is opt-in for users: nobody is forced to receive messages from other networks.
Integrity safeguards and the limits of the duty
The DMA lets a gatekeeper take measures that are strictly necessary and proportionate to protect the integrity of its operating system, hardware or software. Such measures must be duly justified and cannot become a disguised refusal. The burden is on the gatekeeper to explain why a specific restriction protects security rather than market position.
This creates the central tension of the obligation. Gatekeepers argue that broad access exposes users to privacy and security risks, while rivals and the Commission argue that vague security claims historically served to entrench closed ecosystems. Specification decisions resolve the conflict feature by feature, which makes the process slow and technical.
- A security restriction must address an identified risk, not a hypothetical one.
- The same restriction should apply to the gatekeeper’s own services where the risk is the same.
- Delays in documentation or access can themselves amount to non-compliance.
Comparison with related platform obligations
Interoperability is one of several DMA tools that target lock-in, and it is often confused with neighboring duties. The comparison below shows how it differs from rules on data and self-preferencing.
| Obligation | What it opens | Main beneficiary |
|---|---|---|
| Interoperability (Art. 6(7) and 7) | Technical features and messaging networks | Rival services and device makers |
| Data portability (Art. 6(9)) | User data for transfer | End users and receiving services |
| Ban on self-preferencing (Art. 6(5)) | Fair ranking and display | Competing offers in rankings |
| Sideloading and app stores (Art. 6(4)) | Alternative app distribution | Developers and alternative stores |
Enforcement and practical consequences
The Commission enforces the DMA directly. Non-compliance can lead to fines of up to 10% of worldwide annual turnover, rising to 20% for repeated infringements, plus periodic penalty payments. Gatekeepers must document their measures in annual compliance reports, which allow rivals to assess and challenge them.
In practice, the obligation shifts design decisions toward openness: interfaces once reserved for first-party products must be documented, tested and offered to others. Some gatekeepers have limited or delayed new features in the EU, citing interoperability burdens, which shows that the rule affects product roadmaps as well as competition.
In simple terms
Large tech companies build their phones and apps so that their own products work best together. That makes it hard to switch brands. The DMA interoperability obligation tells the largest companies in the EU to open those doors to competitors.
A smaller maker’s smartwatch should show phone notifications just like the phone maker’s own watch. A user of one messaging app should one day chat with friends on another app. The messages must stay encrypted.
A practical example
A European company that makes fitness smartwatches has long struggled with iPhone owners, because its watch could not reply to notifications or stay reliably connected in the background, while the phone maker’s own watch could. Customers returned the product, and retailers hesitated to stock it.
After the specification decision under Article 6(7), the company requests access to notification interaction and background connectivity through the gatekeeper’s documented process. Its engineers integrate the new interfaces over several months, and the watch gains replies to messages and stable synchronization for EU users.
The outcome is a measurably more competitive product in the EU market and a clear example of how interoperability rules translate into concrete features for consumers.