Device Ecosystem Interoperability and Fragmentation Issues

1. Introduction

Device ecosystem interoperability refers to the ability of hardware devices, operating systems, applications, accessories, cloud services, communication protocols, and third-party platforms to work effectively with one another. In digital markets, interoperability can determine whether users and developers can move between competing ecosystems or remain dependent on a particular ecosystem.

Fragmentation occurs when an ecosystem is divided into incompatible or partially compatible technical environments—for example, different operating systems, proprietary APIs, device standards, authentication systems, app stores, payment systems, or accessory protocols.

From a competition-law perspective, interoperability problems become significant when a firm with substantial market power can use technical control over an ecosystem to foreclose rivals, disadvantage complementary products, increase switching costs, restrict innovation, or prevent effective multi-homing.

The central legal question is generally not whether interoperability is desirable in the abstract, but whether a firm's conduct concerning interoperability constitutes an exclusionary or exploitative practice under the applicable competition regime.

2. Meaning of Device Ecosystem Interoperability

Interoperability may exist at several levels:

A. Hardware interoperability

Different manufacturers' devices can communicate or operate with each other.

Examples include:

• smartphones and headphones;
• computers and peripherals;
• smartwatches and phones;
• vehicles and charging equipment;
• IoT sensors and hubs.

B. Operating-system interoperability

Third-party hardware and software can interact with an operating system without unjustified technical restrictions.

C. API interoperability

Third-party developers can access APIs necessary to provide competing functionality.

D. Data interoperability

Users can transfer their data between competing services or devices.

E. Identity interoperability

Users can use authentication or identity credentials across different services.

F. Payment interoperability

Different payment providers can interact with a device's payment infrastructure.

G. Accessory interoperability

Third-party accessories can perform functions comparable to first-party accessories.

3. What Is Ecosystem Fragmentation?

Fragmentation occurs where technically similar products operate within isolated technological environments.

For example:

Device A → proprietary OS → proprietary API → proprietary app store → proprietary cloud → proprietary payment system

may create an ecosystem that is technically functional internally but difficult to connect to competing ecosystems.

Fragmentation can therefore be natural, technical, or strategically created.

Natural fragmentation

Different technologies evolve independently and have legitimate compatibility limitations.

Competitive fragmentation

Different firms adopt competing standards to differentiate their products.

Strategic fragmentation

A dominant undertaking deliberately restricts interoperability to make rival products less effective.

The third category raises the most significant competition concerns.

4. Why Interoperability Matters for Competition

Interoperability can reduce the economic importance of ecosystem boundaries.

Suppose:

Ecosystem A

• operating system;
• device;
• cloud;
• payment service;
• wearable.

and

Ecosystem B

• competing operating system;
• competing device;
• competing cloud;
• competing wearable.

If the wearable works equally well with both systems, consumers can choose between them more easily.

If the wearable works fully only with Ecosystem A, switching becomes more costly.

Thus:

Interoperability → lower switching costs → greater contestability

whereas:

Interoperability restrictions → higher switching costs → stronger ecosystem dependence.

5. Principal Competition Concerns

A. Foreclosure of competing devices

A dominant platform may give its own hardware preferential access to important APIs while limiting equivalent access to competing devices.

This can make rival hardware technically inferior even when its underlying technology is comparable.

B. Self-preferencing

A platform may permit its own products to use functionality that is unavailable to competitors.

For example:

• first-party smartwatch receives full messaging functionality;
• competing smartwatch receives limited functionality;
• platform claims the restriction is technically necessary.

The competition question becomes whether the limitation is objectively justified or instead disadvantages competing products.

C. API degradation

Interoperability does not necessarily require complete denial of access.

A platform may technically provide an API while:

• limiting functionality;
• imposing lower rate limits;
• increasing latency;
• removing functionality;
• restricting background operation;
• limiting notifications;
• changing authentication requirements.

This can produce functional non-interoperability despite formal API availability.

D. Accessory certification

Certification programs may be legitimate because they can address:

• security;
• safety;
• electromagnetic compatibility;
• privacy;
• technical reliability.

However, certification can raise competition concerns where it is unnecessarily restrictive or selectively applied to competing accessory manufacturers.

E. Switching costs

Interoperability restrictions may increase:

• learning costs;
• replacement costs;
• data-transfer costs;
• accessory replacement costs;
• application-repurchase costs;
• account migration costs.

These costs can reinforce ecosystem lock-in.

6. Network Effects and Ecosystem Lock-In

Device ecosystems frequently exhibit indirect network effects.

More users attract:

developers → applications → accessories → complementary services → more users.

This can create a reinforcing cycle:

Users ↑ → Developers ↑ → Applications ↑ → Device attractiveness ↑ → Users ↑

Interoperability can weaken this feedback loop by allowing users and complementary products to participate across ecosystems.

Fragmentation can strengthen it by making ecosystem participation exclusive.

7. Multi-Homing

Multi-homing means that a user, developer, or business participates in multiple competing ecosystems.

For example, a developer may support:

• Android;
• iOS;
• Windows;
• macOS.

Interoperability restrictions can increase the cost of multi-homing.

If developers must create separate technical integrations for each ecosystem, the dominant ecosystem may gain bargaining power over developers.

8. Six Important Case Laws

1. United States v. Microsoft Corp. — 253 F.3d 34 (D.C. Cir. 2001)

Facts

Microsoft possessed substantial power in the market for Intel-compatible PC operating systems. The case concerned Microsoft's conduct toward competing technologies, particularly Netscape's browser and Java.

Interoperability relevance

Microsoft's control over Windows gave it the ability to influence the development environment available to competing software.

The court examined conduct involving:

• operating-system APIs;
• middleware;
• default settings;
• technical integration;
• restrictions affecting competing technologies.

Principle

A dominant platform can potentially use control over a technological interface to disadvantage complementary or competing products.

Relevance to device ecosystems

The case is important for understanding how control over an operating system can become a source of competitive leverage over adjacent technologies.

2. European Commission — Microsoft (2004)

The European Commission found that Microsoft had abused its dominant position by refusing to provide interoperability information necessary for competing work-group server operating systems.

Interoperability significance

The Commission treated interoperability information as potentially essential for competitors to compete effectively in an adjacent market.

The case illustrates the importance of:

• technical interfaces;
• communication protocols;
• interoperability information;
• compatibility between competing systems.

Principle

Where a dominant platform controls information necessary for interoperability, refusal or restriction of access can raise Article 102 TFEU concerns under specific circumstances.

Device ecosystem application

The principle can extend conceptually to:

• proprietary device APIs;
• synchronization protocols;
• accessory interfaces;
• operating-system functionality.

3. Bronner v Mediaprint — Case C-7/97

Facts

The case concerned access to a newspaper home-delivery system controlled by another undertaking.

Principle

The Court of Justice established a demanding framework for claims based on refusal to provide access to an infrastructure.

The Court emphasized conditions including whether access was indispensable and whether exclusion would eliminate effective competition.

Interoperability significance

Although not a device case, Bronner provides an important framework for analysing when competition law should require a dominant undertaking to share infrastructure.

Device ecosystem application

A competitor seeking access to a proprietary device ecosystem may need to establish more than the fact that interoperability would be commercially convenient.

4. IMS Health GmbH & Co. OHG v NDC Health — Joined Cases C-418/01 P

Facts

IMS Health controlled a pharmaceutical data structure used for market research.

A competitor sought access to the structure because compatibility with the established system was commercially important.

Principle

The Court examined when refusal to license intellectual property could constitute abuse of dominance.

The exceptional circumstances included considerations concerning:

• indispensability;
• elimination of competition;
• prevention of a new product for which consumer demand existed.

Interoperability relevance

The case is highly relevant where interoperability depends upon access to a protected technical structure or interface.

Device ecosystem application

Potentially analogous situations include proprietary:

• device protocols;
• operating-system interfaces;
• synchronization structures;
• accessory standards.

5. Slovak Telekom a.s. v European Commission — Joined Cases C-165/19 P and C-166/19 P

Facts

The case involved access to telecommunications infrastructure and alleged exclusionary conduct by a dominant undertaking.

Principle

The judgment addressed the relationship between refusal-of-access principles and exclusionary conduct involving infrastructure controlled by a dominant undertaking.

The Court confirmed the importance of analysing the precise nature of the conduct rather than treating every interoperability/access dispute as an ordinary refusal-to-deal case.

Device ecosystem significance

Digital ecosystems increasingly involve infrastructure that is both:

• technically integrated; and
• commercially indispensable to complementary products.

This makes the distinction between ordinary commercial disagreement and exclusionary conduct particularly important.

6. Google Android — European Commission, Case AT.40099

Facts

The European Commission investigated Google's contractual arrangements concerning the Android ecosystem.

The Commission examined arrangements involving:

• Android operating systems;
• Google Play;
• search;
• mobile-device manufacturers;
• app distribution.

Interoperability and fragmentation

The Android ecosystem demonstrated how control over an operating-system ecosystem can affect competition between:

• operating systems;
• application distribution channels;
• search services;
• device manufacturers.

The Commission examined restrictions that could limit the ability of manufacturers to develop or distribute competing Android-compatible versions and thereby affect ecosystem fragmentation.

Principle

Contractual restrictions imposed by a dominant platform can raise competition concerns when they limit competing ecosystems or reinforce an existing position in interconnected markets.

Device ecosystem relevance

The case is particularly useful for analysing ecosystem control, because operating systems, app stores, search, and hardware distribution can operate as mutually reinforcing components.

9. Additional Important Cases

7. Google Shopping — Case AT.39740

Google's treatment of competing comparison-shopping services provides a broader example of how a dominant digital platform can influence access to users through control of a major interface.

The case is relevant to device ecosystems because the competitive importance of a digital interface may depend not merely on formal access but on how the platform designs and presents access.

8. Apple — App Store Practices

Competition authorities in multiple jurisdictions have investigated Apple's control over the iOS ecosystem, including:

• App Store access;
• payment mechanisms;
• restrictions on alternative distribution;
• developer rules;
• interoperability-related functionality.

These proceedings illustrate the broader principle that an ecosystem owner can exercise competitive influence through technical and contractual rules governing participation.

Because different investigations concern different markets, periods, and legal theories, each proceeding must be analysed separately rather than treated as establishing one universal rule.

10. Fragmentation as a Competitive Strategy

A useful analytical model is:

Stage 1 — Control

Dominant firm controls:

OS + API + authentication + app distribution + cloud

Stage 2 — Restriction

It limits:

third-party API access

Stage 3 — Functional degradation

Competitors receive:

fewer features + slower performance + limited background access

Stage 4 — Consumer effect

Users experience:

reduced compatibility + higher switching costs

Stage 5 — Ecosystem reinforcement

More users remain within:

dominant ecosystem

This can produce a feedback loop of technological dependence.

11. Compatibility Versus Differentiation

Competition law does not normally require every product to be identical.

A firm may legitimately differentiate its ecosystem through:

• design;
• security;
• privacy;
• performance;
• technical architecture;
• product integration.

Therefore:

Interoperability ≠ obligation to eliminate all product differentiation.

The important issue is whether a restriction has a legitimate technical or commercial justification and whether its implementation unnecessarily excludes competitors.

12. Security Justifications

Interoperability restrictions may sometimes be justified by:

Cybersecurity

Uncontrolled API access can create security vulnerabilities.

Privacy

Cross-platform access can expose personal information.

Device integrity

Unauthorized accessories can damage hardware.

Authentication

Open access may facilitate identity fraud.

Safety

Medical, automotive, and industrial devices can require controlled interoperability.

These considerations must therefore be distinguished from restrictions whose principal effect is competitive foreclosure.

13. Technical Standards and Standardisation

Standardisation can reduce fragmentation.

Examples include common:

• communication protocols;
• charging standards;
• authentication standards;
• file formats;
• messaging protocols;
• APIs.

But standardisation can itself create competition issues if a dominant firm controls the standard-setting process or uses standards to exclude rivals.

14. Data Portability and Interoperability

Data portability is related but distinct from technical interoperability.

Portability

"Can I take my data elsewhere?"

Interoperability

"Can another system work with my existing device/service?"

A consumer may technically export data but still face ecosystem lock-in because:

• applications cannot migrate;
• accessories do not work;
• APIs are unavailable;
• authentication credentials cannot be transferred.

Consequently, data portability alone may not eliminate ecosystem dependence.

15. Developer Fragmentation

Developers can face several layers of fragmentation:

The resulting development cost can become a significant barrier to entry.

16. Competition Effects

Potential adverse effects include:

Consumer effects

• higher switching costs;
• reduced choice;
• reduced compatibility;
• duplicated purchases.

Developer effects

• increased development costs;
• duplicated integrations;
• dependence on dominant APIs;
• reduced ability to innovate.

Rival effects

• reduced access to users;
• inferior functionality;
• higher distribution costs;
• reduced scale.

Innovation effects

Interoperability restrictions can potentially discourage innovations designed to operate across ecosystems.

However, integration can also produce legitimate innovation and quality improvements. The competitive assessment therefore depends on the particular conduct and market circumstances.

17. Fragmentation and Market Definition

Traditional product-market analysis may become difficult where ecosystems overlap.

For example:

Smartphone
↓
Operating system
↓
App store
↓
Wearables
↓
Cloud
↓
Payment

Each layer can potentially constitute a separate market, while competitive conditions at one layer can influence another.

Consequently, competition authorities may need to analyse:

• primary market power;
• adjacent markets;
• ecosystem-wide effects;
• cross-market leverage;
• network effects.

18. Interoperability and Essential Facilities

The essential-facilities doctrine may become relevant where a dominant infrastructure is indispensable to effective competition.

However, courts generally apply demanding conditions before imposing a mandatory access obligation.

The cases involving Bronner, IMS Health, and later access jurisprudence demonstrate why competition authorities must distinguish:

1. ordinary refusal to cooperate;
2. commercially inconvenient incompatibility;
3. deliberate exclusion;
4. genuinely indispensable infrastructure.

19. Remedies

Where interoperability restrictions are found unlawful, possible remedies can include:

A. API access

Require access to specified technical interfaces.

B. Non-discrimination

Require equivalent access for first-party and third-party products.

C. Data portability

Allow users to transfer relevant information.

D. Interoperability standards

Require compliance with established technical standards.

E. API documentation

Provide sufficient technical information to enable effective integration.

F. Certification reform

Prevent discriminatory certification requirements.

G. Monitoring

Require periodic reporting or independent technical audits.

20. Key Legal Tests

When analysing device ecosystem interoperability, the following questions are useful:

1. Does the undertaking possess substantial market power?
2. What ecosystem component does it control?
3. Is interoperability technically necessary or merely commercially desirable?
4. Are competitors actually dependent upon the interface?
5. Is access available on equivalent terms?
6. Does the restriction disadvantage competing products?
7. Does it increase switching costs?
8. Does it prevent effective multi-homing?
9. Is there a legitimate security, privacy, safety, or technical justification?
10. Is the restriction proportionate to that justification?
11. Does it foreclose an equally efficient competitor?
12. Are consumers or developers harmed through reduced choice or innovation?

21. Case-Law Principles at a Glance

22. Conclusion

Device ecosystem interoperability and fragmentation are increasingly important competition-law issues because modern devices are no longer isolated products. Smartphones, computers, wearables, vehicles, applications, cloud services, payment systems, accessories, and identity systems can operate as interconnected ecosystems.

The principal competition concern arises when a firm with significant ecosystem power uses technical or contractual control to make competing products less compatible, less functional, or more costly to use.

The leading jurisprudence—from Microsoft, Bronner, IMS Health, Slovak Telekom, and Google Android—shows several recurring principles:

• interoperability can be commercially and competitively significant;
• access obligations are not automatic;
• indispensability is important in refusal-of-access cases;
• technical interfaces can become sources of market power;
• contractual and technological restrictions can reinforce ecosystem dominance;
• legitimate security and technical objectives remain relevant;
• the legal assessment depends heavily on the specific market structure and conduct.

Thus, the central competition-law problem is not fragmentation itself, but whether fragmentation is an ordinary consequence of competing technologies or is being used, without adequate justification, as a mechanism for excluding competitors and reinforcing ecosystem dependence.