DMA Interoperability Architecture for Engineers (2026)

Q: What does the Digital Markets Act require for interoperability?

The DMA requires designated gatekeepers to give third parties free and effective interoperability with certain hardware and software features of their operating systems, let end users port their data to third parties, give business users access to data generated by their activity, and open designated messaging services to interoperability on request. Exact scope depends on the designated service, so counsel should confirm what applies.

Q: Which companies are DMA gatekeepers?

The European Commission's gatekeeper list names Alphabet, Amazon, Apple, ByteDance, Meta, Microsoft and Booking. Each is designated for particular core platform services, such as an operating system, a marketplace, an intermediation service or a messaging app, not for everything it runs. Obligations attach to the designated services, which is why engineering impact differs between gatekeepers and products.

Q: What did the European Commission decide about Apple interoperability in March 2025?

On 19 March 2025 the Commission adopted two specification decisions. The first sets measures for nine iOS connectivity features used mainly by connected devices such as smartwatches, headphones and TVs, including notifications, peer-to-peer Wi-Fi, NFC and pairing. The second makes Apple's process for future interoperability requests more transparent and predictable, with better documentation, communication and timelines.

Q: How long does an interoperability request to Apple take?

According to Apple's published process, eligibility is usually decided within 20 working days, a project plan follows within 40 working days, and development takes 6, 12 or 18 months depending on whether the effort is minor, mild or significant. Release comes with an iOS or iPadOS version, and in any event within 24 months of submission. Timelines pause if you do not respond promptly.

Q: What is Google's Data Portability API?

It is a Google developer API that lets apps, with the user's consent, receive the user's data from Google products such as Search, YouTube, Maps, Play, Shopping and Chrome, including time-based transfer. Developers must pass app verification, including brand verification, a use-case description and a demo video, with an extra security review for restricted scopes and annual re-verification.

Q: How should a platform architect for interoperability mandates?

Build one access layer for all external integrations instead of a project per ruling. It needs a developer registry for third-party identity, a consent service with scopes, expiry and revocation, an interop gateway with scoped short-lived tokens and quotas, a policy engine encoding justified integrity rules with reason codes, and an audit store you could show a regulator. Each mandate then becomes policy plus a connector.

Q: How should a third party design a product that depends on DMA access?

Assume access will be slow, partial and revocable. Detect capabilities at runtime instead of checking versions, treat EU-only access as a regional feature flag, put a per-source adapter in front of your canonical schema, handle consent revocation cleanly and protect imported data as its new controller. Never commit a launch date to a gatekeeper delivering a feature by a date you assumed.

Q: What are the penalties for breaching the DMA?

The Commission's DMA overview lists fines of up to 10% of a company's total worldwide annual turnover, rising to 20% for repeated infringements, plus periodic penalty payments of up to 5% of average daily turnover. For systematic infringements, additional remedies can follow a market investigation. That is why gatekeepers engineer mandated interfaces carefully and why third parties should expect conservative designs.

Satyam Kumar

Back to Blog

architecture

Designing for the DMA: Interoperability Is an API Product With a Regulator in the Room, So Build the Access Layer Once (2026)

By Satyam KumarOctober 16, 202612 min read

digital markets act dma interoperability dma compliance architecture data portability api interoperability requests ios eu gatekeepers apple interoperability eu google data portability api business user data access messaging interoperability api access layer consent management architecture platform regulation engineering eu digital regulation third party api access dma 2026

Designing for the DMA: Interoperability Is an API Product With a Regulator in the Room, So Build the Access Layer Once (2026)

Frequently Asked Questions

Share this article

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

AI & Cloud Architect. Helping teams build systems that scale to millions.

LinkedIn GitHub

Designing for the DMA: Interoperability Is an API Product With a Regulator in the Room, So Build the Access Layer Once (2026)

Frequently Asked Questions

Share this article

Comments

Leave a comment