What is the scope of the two adopted specification decisions?
Under Article 6(7) of the DMA, Apple must provide developers and businesses with free and effective interoperability with hardware and software features controlled by its operating systems iOS and iPadOS.
On 19 September 2024 the Commission opened two specification proceedings: one dealing with the interoperability of iOS with third party connected devices (DMA.100203) and one dealing with the process Apple put in place to handle the interoperability requests (DMA.100204).
Both specification decisions include detailed measures on how to provide interoperability.
The first set of measures concerns 9 iOS connectivity features, predominantly used for and used by connected devices (DMA.100203). The second set of measures aim to increase the transparency and effectiveness of the process that developers need to follow to obtain interoperability with iOS and iPadOS (DMA.100204).
During these proceedings, the Commission held numerous technical meetings and discussions with Apple and interested developers. This constructive dialogue allowed the Commission to identify the measures that developers need to offer innovative products and services while ensuring that end users maintain their known iPhone user experience and enjoy improved interoperability.
What does this mean for me as an iPhone user?
The objective of Article 6(7) DMA is that devices, apps and products from third parties can be used on an iPhone as seamlessly as Apple’s own products. The specification decisions adopted today support Apple in achieving this objective, by detailing how to securely allow third parties to use certain features that are so far only available to Apple devices. For example, the specification decision on connected devices aims to enable, amongst others, the following improvements:
- iPhone users will have enhanced possibilities to receive push notifications including pictures on their non-Apple smartwatch and reply to these notifications.
- iPhone users will also be able to pair their non-Apple connected devices such as headphones and smartwatches more seamlessly and easily with the iPhone.
- Non-Apple devices such as virtual reality headsets will benefit from better and faster data connections with the iPhone.
- Developers will be able to integrate alternative solutions to Apple’s AirDrop and AirPlay services on the iPhone. As a result, iPhone users will be able to choose from different and innovative services to share files with other users and cast media content from their iPhones to TVs.
Thanks to these new possibilities, in the future new and innovative devices may be developed for the iPhone users, something which was until now constrained by the lack of full interoperability.
What does the specification decision on connected devices (case DMA.100203) mean for me as a business user?
The specification decision clarifies which measures Apple must implement to allow effective interoperability between Apple’s iOS operating system and connected devices by other manufactures in relation to and 9 iOS connectivity features.
Business users will have the ability to interoperate with these features, as specified in the Decision.
These features include:
- iOS notifications: this feature allows connected devices, such as smart watches, to show and react to iOS notifications.
- Background execution: iOS apps need to execute certain actions with respect to connected physical devices ‘in the background’, i.e. without the user looking directly at the app. For example, the iPhone can fetch the latest weather information and synchronise it to a smartwatch, without the need for active user interaction.
- Automatic audio switching: this feature allows users to switch between two devices, for example between a smartphone and a computer, when listening to audio with supported headphones.
- High-bandwidth peer-to-peer Wi-Fi connections:this feature provides allows to establish and use a high-bandwidth Wi-Fi connection between an iOS device and connected physical devices. This high-speed connection can be used to share large files between two devices, or to cast on an iPhone what can be seen on virtual reality glasses.
- Close-range wireless file transfers: this feature allows to access the same iOS-controlled features as Apple’s services in third-party file sharing apps, creating, for example, alternatives to AirDrop.
- Media casting: this allows developers to develop an alternative media casting solution to Apple’s AirPlay by granting them access to required software features in a non-discriminatory way to AirPlay.
- NFC Controller in Reader/Writer mode: this allows apps on an iPhone to communicate with connected devices, such as rings or bracelets, to provide them with information such as a user’s payment card details. The end user can then use the ring or bracelet in a shop to perform payment transactions like with a payment card - without the presence of the iPhone. Moreover, physical smart cards can easily be read for instance to activate or secure mobile banking.
- Proximity-triggered pairing: allows connected physical devices to pair with an iOS device through a simplified procedure. For example, when the user brings a new headset near the iPhone it should be able to pair immediately through a simple and streamlined procedure, independently of whether the headset is an Apple product or a third-party brand.
- Automatic Wi-Fi connection: allows to access information about local Wi-Fi networks saved on the iPhone allows connected physical devices to seamlessly join these networks.
- All features on Apple will have to enable interoperability for any type of connected device, free of charge, via complete, accurate and well-documented frameworks and APIs.
- The interoperability solutions for third parties will have to be equally effective to those available to Apple and must not require more cumbersome system settings or additional user friction.
- All features on Apple will have to make available to third parties any new functionalities of the listed features once they become available to Apple.
- Apple will have to provide third parties with the technical assistance and report how it implemented the measures.
What does the specification decision on process (case DMA.100204) mean for me as a business user?
The specification decision on Apple’s request-based process clarifies how Apple must handle requests from businesses and developers seeking interoperability with iOS and iPadOS features under Article 6(7) of the DMA.
This means that business users will enjoy greater transparency, predictability, and fairness when engaging with Apple on interoperability matters. The decision outlines clearer procedures, structured timelines, and a more transparent decision-making process, making it easier for businesses to plan their interoperability with iOS and iPadOS. Concretely, Apple’s request-based process will include:
- Apple must establish a programme allowing developers to submit ‘reference queries’ to obtain a technical reference on how iOS and iPadOS enable hardware and software features used by Apple’s own services and hardware. These references will then be made available to all developers through Apple’s developer portal. Through these measures, business users will get more transparency on iOS and iPadOS features that are only available for Apple’s own services and hardware. This will help business users to identify features for which to request interoperability and help in describing those features in the request form.
- Apple must ensure that its interoperability solutions are effective, transparent, and maintained over time. All solutions must be as effective as those Apple uses for its own services and hardware, with no restrictions on use cases. Apple must provide complete and public developer documentation upon release and maintain solutions over time.
- If Apple deprecates a solution, it must provide prior notice and continue support for at least three major iOS or iPadOS releases. Any improvements Apple makes to its own internal solutions must also be available at the same time in public interoperability solutions so that third parties can start to integrate them in their devices or services.
- Apple must make available a structured and transparent process for developers seeking interoperability with iOS and iPadOS. This includes a public support webpage with clear guidance on how to submit requests, expected timelines, and assessment criteria.
- Developers will have a dedicated contact point for inquiries, with a response time of maximum 5 working days.
- Apple must provide an option for feedback on its proposed interoperability solutions before they are finalised. Apple must take this feedback into account and explain how it was considered in the development. If a developer disagrees with Apple’s approach, they can request an internal review or use the dispute resolution mechanism to seek further clarification.
- Developers can provide feedback on the project plan within 5 working days. Apple must respond within 5–10 working days, depending on complexity.
- Developers will receive immediate notice if their interoperability request is rejected. The notice must include clear reasoning, details on unmet criteria, and guidance on next steps.
- Developers can appeal rejected interoperability requests through an internal review. Appeals must be submitted within 15 working days and will be reviewed by Apple’s Interoperability Request Review Board (IRRB), which will issue a decision within 30 working days.
- If developers disagree with the internal review outcome, they can initiate a conciliation process. An independent expert will assess the case, and if both parties agree, the expert’s recommendation becomes a legally binding settlement. Apple must maintain a pool of independent conciliators, and the process will be confidential and completed within 3 months. Small and medium-sized enterprises (SMEs) will have their conciliation costs covered by Apple.
- Apple must follow a structured timeline for handling interoperability requests. Eligibility assessments must be completed within 20 working days, project plans communicated within 40 working days, and development cycles must be completed within 6, 12, or 18 months, depending on complexity.
- After development, solutions must be released in the next relevant iOS or iPadOS update, with, in any case, a maximum total timeline of 24 months. Solutions requiring minor or mild engineering efforts will be included in the next interim (“dot”) release, while more complex solutions will be part of the next major release.
- Apple will provide to developers a tracker system for interoperability requests. Developers can access a tracker through the developer portal to monitor request status. Developers can choose to make their requests fully visible, partially visible, or confidential, depending on whether they want to share details of their request with other developers.
- Apple is required to take measures to ensure that non-public information it receives from developers requesting interoperability are only used for the purpose of providing interoperability and cannot be accessed by teams responsible for Apple’s own hardware and services.
- Apple must make public annual reports on interoperability requests and compliance. The reports will include key metrics such as the number of requests received, their status, average processing times, and dispute resolution outcomes. Apple must furthermore notify the Commission of any rejected requests and provide justifications.
By when should Apple implement the measures in each decision?
Apple is required to implement the specified measures within the timeframes set out in the specification decisions.
Apple should implement the measures included in the decision on connected devices (DMA.100203) within the following timelines:
- iOS notifications:
- Beta version by the end of 2025, except for (i) the ability to select which iOS notifications are shown on each connected device within the companion app, and (ii) the functionalities described in the Decision.
- All measuresby 1 June 2026.
- High-Bandwidth Peer-to-Peer Wi-Fi Connection:
- Wi-Fi Aware 4.0 in iOS 19.
- Wi-Fi Aware 5.0 in the next iOS release at the latest nine months following the introduction of the Wi-Fi Aware 5.0 specification.
- Proximity-triggering pairing:
- Beta version by the end of 2025.
- For end users by 1 June 2026.
- Background execution:
- For third-party companion apps in relation to force-quitting and Bluetooth/Wi-Fi disabling actions in iOS 19, and in any case by the end of 2025.
- All measures in iOS 20, and in any case by the end of 2026.
- Close-range wireless file transfer:
- Close-range wireless file transfers while the receiving device has the relevant close-range wireless file transfer solution open by 1 June 2026.
- All measures in iOS 20, and in any case by the end of 2026.
- Automatic Wi-Fi connection:
- All measures in iOS 19, and in any case by the end of 2025.
- By the end of 2025, the solution must provide access to the following Wi-Fi Network Information: SSID (network name), an indication if the SSID is broadcasted or not, the network password (if applicable), and the network security configuration.
- Apple should update the solution to provide access to the Wi-Fi Network Information that Apple shares with any of its own connected devices by 1 June 2026.
- Media casting:
- All measures in iOS 20, and in any case by the end of 2026.
- Automatic audio switching:
- 1 June 2026, except for the functionality to present non-connected third-party devices as available audio routes.
- Apple should provide effective interoperability with that functionality by 1 June 2027.
- NFC Controller in Reader/Writer Mode:
- All measures in iOS 19, and in any case by the end of 2025.
Apple should implement the measures in the specification decision on process (DMA.100204), for:
- All measures (except dispute resolutions) within two months after the Decision, i.e. 19 May 2025, and
- Dispute resolution mechanisms: within four months after the Decision, i.e. 19 July 2025.
I have already submitted an interoperability request to Apple. How do the adopted decisions affect my request?
If your request was submitted prior to the adoption of the decision on process (case DMA.100204) and does not relate to a feature covered by the decision on connected devices, the deadlines for the different stages specified in section 5.1 of the Annex to the decision on process will count as of 19 March 2025.
However, if your request was submitted prior to the adoption of the decision on process and does relate to a feature covered by the decision on connected devices, the measures set out in the decision on connected devices, including regarding timelines, apply.
Do the specification decisions mean that Apple is not complying with the DMA?
No. A specification decision is a tool to assist the gatekeeper to achieve effective compliance with the DMA. A specification decision does not conclude non-compliance nor does it seek to punish the gatekeeper.
Will the specification decisions be made publicly available?
Yes, the non-confidential versions of the specification decisions will be made publicly available on the Commission’s website (DMA.100203 and DMA.100204). This ensures transparency regarding the measures a gatekeeper must implement.
Where can I find more information from Apple on interoperability with iOS and iPadOS?
Developers can learn more about interoperability with iOS and iPadOS at https://developer.apple.com/.
More information about requesting interoperability with iOS and iPadOS in the European Union is also available at Apple’s support page for developers.
What is a ‘specification decision’ and how is it different from a non-compliance decision?
In a ‘specification decision’, the Commission does not take a position on whether the gatekeeper complies with its obligations under the Digital Markets Act (DMA). Therefore, there are no fines attached to such a decision.
By contrast, a non-compliance decision concludes, following an investigation, that a gatekeeper has been non-compliant with a DMA obligation. The non-compliance decision orders the gatekeepers to cease and desist the infringement. In a non-compliance decision, the Commission may impose fines.
Specification decisions are taken following specification proceedings. These are tools in which the Commission and a designated gatekeeper engage in a formalised regulatory dialogue in order for the Commission to identify concrete measures the gatekeeper should take to effectively comply with a certain obligation (included in Article 6 or 7 of DMA). Third parties are formally involved in this process through a public consultation on the draft measures.
The legal basis for a specification procedure is Article 8(2) of the DMA. In the case of specification proceedings, the Commission has six months to conclude the specification proceedings and adopt its final decision with binding measures.
Both types of proceedings are subject to the full respect of gatekeepers’ procedural rights.
Why is the Commission providing guidance to Apple on its obligations to improve the interoperability of its systems?
The DMA regulates the actions of so-called gatekeepers. Gatekeepers are large online platforms that have been designated as such because they provide services – so called core platform services – to many European users. These gatekeepers exercise market power which can undermine the contestability of European digital markets through in particular very strong network effects, large economies of scale, the ability to connect business users with many end users, the lock-in of end users and the ensuing dependence of business users, and degree of vertical integration. The DMA lays down rules to ensure contestability and fairness for business users and end users.
This includes an obligation on gatekeepers of operating systems to provide, free of charge, effective interoperability with the same hardware and software features available to services provided by the gatekeeper itself. This obligation is intended to increase the incentives to innovate and improve products and services for the business users and their customers as well as the gatekeeper itself, and thus positively affect the innovation potential of the wider online platform economy in the EU. This obligation also encourages the gatekeepers to innovate its platform and its own products and services.
The gatekeepers may take strictly necessary and proportionate measures to ensure that the interoperability solutions do not compromise the integrity of the operating system, hardware or software features provided by the gatekeeper, provided such measures are duly justified.
How did the Commission come up with these measures?
The specified measures are based on extensive technical discussions between the Commission, Apple and numerous interested stakeholders, in particular developers. The measures take into account feedback received from third parties on the importance of interoperability for certain iOS features and on Apple’s handling of interoperability requests. Throughout the proceedings Apple and third parties were able to provide input and comment on the draft measures, in particular during a public consultation launched in December 2024. This constructive dialogue allowed the Commission to identify the measures that developers need to offer innovative products and services while ensuring that end users maintain their known iPhone user experience and enjoy improved interoperability.