Competition Law and Autonomous Ecosystem Market Power

1. Introduction

Autonomous ecosystem market power refers to the ability of an undertaking to exercise substantial competitive influence because it controls an interconnected ecosystem of products, services, infrastructure, data, software, interfaces, users, or distribution channels.

An ecosystem may include:

• an operating system;
• hardware or connected devices;
• application stores;
• cloud infrastructure;
• payment systems;
• data and analytics;
• APIs and interoperability standards;
• autonomous or connected vehicles;
• charging or service networks;
• AI assistants;
• digital identity;
• advertising infrastructure; and
• complementary applications and services.

The important competition-law issue is that market power may arise not merely from a high market share in one product market, but from control over several interconnected layers of an ecosystem.

The European Union's Google Android litigation is particularly important because the General Court expressly dealt with the concepts of a multi-sided platform and an “ecosystem”, while examining Google's operating system, app store, search and browser services together.

2. Meaning of an Autonomous Ecosystem

An autonomous ecosystem is a system in which one undertaking controls, or substantially influences, several complementary components that function together.

Example

Consider an autonomous-mobility ecosystem:

Vehicle OS → Autonomous-driving software → Mapping → Cloud → Data → Charging → Payments → Repairs → App marketplace

A company controlling several of these layers may be able to:

1. restrict interoperability;
2. favour its own complementary services;
3. make rivals dependent upon access to infrastructure;
4. impose exclusive contracts;
5. bundle products;
6. use data obtained from one market to strengthen another;
7. make switching expensive; and
8. prevent competing ecosystems from achieving sufficient scale.

Therefore, traditional market-share analysis may not completely capture the competitive significance of ecosystem control.

3. Relevant Competition-Law Framework

A. Dominance or substantial market power

The first question is whether the undertaking possesses substantial market power.

Relevant factors include:

• market share;
• duration of market power;
• barriers to entry;
• network effects;
• switching costs;
• access to data;
• interoperability;
• control over essential technical interfaces;
• economies of scale and scope;
• consumer dependence;
• multi-homing;
• countervailing buyer power; and
• the ability of competitors to replicate the ecosystem.

In the Google Android case, the European Commission relied on factors including market shares, barriers to entry, lack of countervailing buyer power and the limited competitive constraint from alternative operating systems.

4. Ecosystem Market Definition

A major legal difficulty is deciding whether the ecosystem should be treated as:

Approach 1 — Separate markets

Each component may constitute a separate relevant market:

• operating systems;
• app stores;
• search engines;
• cloud services;
• payment services;
• autonomous-driving software.

Approach 2 — Interconnected markets

The authority may examine the competitive relationship between several adjacent markets.

Approach 3 — Ecosystem as a competitive structure

The authority may consider the ecosystem itself as an important competitive parameter, particularly where components reinforce each other through network effects and data advantages.

The Google Android litigation demonstrates the importance of this third perspective: the EU courts considered Google's Android operating system, Play Store, search and browser services in their interconnected competitive context.

5. Network Effects and Ecosystem Power

Autonomous ecosystems often exhibit direct and indirect network effects.

For example:

More users → more data → better service → more developers → more applications → more users.

This creates a feedback loop.

A dominant ecosystem can therefore become increasingly difficult for competitors to challenge even if the initial product itself is technically replicable.

6. Switching Costs and Lock-In

An ecosystem can generate market power through:

• proprietary data formats;
• incompatible APIs;
• account dependency;
• loss of accumulated data;
• loyalty benefits;
• hardware-software integration;
• application incompatibility;
• contractual restrictions;
• proprietary accessories;
• charging infrastructure;
• proprietary autonomous-driving interfaces.

The relevant question is not simply:

“Can the customer theoretically switch?”

It is:

“Can customers switch at sufficient scale and reasonable cost to impose an effective competitive constraint?”

7. Self-Preferencing

An ecosystem controller may favour its own downstream products.

Examples include:

• ranking its own applications above rivals;
• giving its own autonomous-driving service preferential access to vehicle data;
• favouring its own payment service;
• prioritising its own cloud service;
• giving its own products superior API functionality.

This can be particularly problematic when the ecosystem operator simultaneously acts as:

infrastructure provider + platform operator + downstream competitor.

The EU's recent Digital Markets Act enforcement against Google illustrates the continuing regulatory concern with self-preferencing and steering restrictions in digital ecosystems.

8. Tying and Bundling

An ecosystem owner may require customers to obtain Product B together with Product A.

For example:

Autonomous-driving software + proprietary cloud service

or:

Operating system + app store + search service.

Tying becomes particularly significant where the undertaking is dominant in the tying product and uses that position to reinforce its position in another market.

9. Exclusive Dealing

Ecosystem power may also be reinforced through:

• exclusive distribution;
• exclusive pre-installation;
• exclusive API access;
• exclusivity payments;
• preferred-provider agreements;
• contractual restrictions on rival ecosystems.

Such arrangements can prevent competitors from obtaining the scale necessary to challenge the incumbent.

10. Refusal of Interoperability

A particularly important ecosystem issue is access to interoperability.

A dominant undertaking may control:

• APIs;
• technical standards;
• operating-system functionality;
• vehicle data;
• cloud interfaces;
• payment interfaces;
• authentication systems.

Refusing access can disadvantage competitors where the controlled interface is commercially or technically indispensable.

The Google Android proceedings considered the competitive significance of restrictions affecting Android forks and access to proprietary APIs.

11. Data as a Source of Ecosystem Market Power

Data can reinforce ecosystem dominance.

For example:

Users → vehicle data → AI training → better autonomous service → more users → more vehicle data

The same phenomenon can occur with:

• search data;
• location data;
• purchasing data;
• payment data;
• health data;
• mobility data;
• advertising data.

Competition authorities may therefore consider whether an ecosystem possesses a data advantage that competitors cannot reasonably reproduce.

12. Six Major Case Laws

1. Google LLC and Alphabet Inc. v European Commission — Google Android

Case T-604/18; subsequently C-738/22 P

This is one of the most directly relevant authorities.

The European Commission found Google dominant in relevant markets involving Android operating systems and Android app stores and identified several practices, including:

• tying Google Search to Play Store;
• tying Chrome;
• exclusivity arrangements;
• anti-fragmentation obligations.

The General Court expressly referred to the concepts of a multi-sided platform and ecosystem.

The Court of Justice subsequently considered the appeal in 2026, including tying, exclusionary effects, exclusive pre-installation payments and restrictions affecting Android forks.

Principle

An ecosystem can allow dominance in one layer to reinforce market power in interconnected markets.

2. United States v. Microsoft Corp.

253 F.3d 34 (D.C. Cir. 2001)

Microsoft concerned the relationship between:

• operating systems;
• browsers;
• software developers; and
• distribution channels.

Microsoft's control over Windows created significant strategic advantages in adjacent software markets.

The case is important for ecosystem analysis because it demonstrates how a dominant platform can use control over a foundational layer to influence competition in complementary markets.

Principle

Control over an important platform or technological bottleneck can provide the ability to disadvantage competing complementary products.

3. FTC v. Qualcomm Inc.

969 F.3d 974 (9th Cir. 2020)

The Qualcomm litigation concerned Qualcomm's position in cellular modem-chip technology and its licensing practices.

The FTC alleged that Qualcomm used practices associated with its position in key semiconductor technology to maintain its competitive position.

The Ninth Circuit ultimately rejected the FTC's monopolization theory on the record before it.

The case nevertheless remains significant because it demonstrates the importance of distinguishing:

• possession of technological power;
• contractual leverage;
• legitimate intellectual-property licensing;
• exclusionary conduct; and
• harm to competition.

The FTC's case materials describe the underlying allegation as an attempt to maintain Qualcomm's monopoly in key semiconductor technology.

Principle

Possessing an important technological position does not automatically establish unlawful monopolization; the competitive effect of the challenged conduct must still be established.

4. Apple Inc. v. Pepper

587 U.S. 273 (2019)

The U.S. Supreme Court considered whether consumers could sue Apple over alleged monopolistic conduct concerning the App Store.

The case is important to ecosystem competition because Apple's ecosystem involves:

iOS → App Store → developers → consumers → payment mechanisms.

The case illustrates how platform architecture can place an ecosystem operator between suppliers and consumers.

Principle

A platform can occupy a strategically important position between complementary suppliers and final consumers, making platform governance relevant to competition law.

5. Epic Games, Inc. v. Apple Inc.

9th Cir. litigation following the 2021 district court judgment

Epic challenged Apple's App Store policies, including restrictions concerning payment systems and distribution of applications.

The dispute concerned Apple's integrated ecosystem:

iOS → App Store → developers → payments → consumers.

The litigation illustrates competition concerns involving:

• platform access;
• payment restrictions;
• steering;
• commissions;
• alternative distribution;
• switching;
• ecosystem control.

Principle

Control over an application-distribution ecosystem can create significant competitive leverage over downstream developers and complementary services.

6. Google LLC v. United States / Google Search Monopolization Litigation

The U.S. Google search litigation concerns Google's position in general search and related distribution arrangements.

The case is relevant to ecosystem power because Google's search position interacts with:

• browsers;
• mobile operating systems;
• default settings;
• devices;
• advertising;
• data collection.

Principle

Market power may be reinforced through distribution arrangements and default positioning across interconnected technological layers.

13. Additional Important Authorities

7. Google Shopping — European Commission

Google Search (Shopping), Case AT.39740

The European Commission found Google had abused its dominant position in general search by favouring its own comparison-shopping service in search results.

Relevance

This is a classic example of:

platform control + self-preferencing + downstream competition.

8. Google Search (AdSense)

Case AT.40411

The Commission examined Google's contractual restrictions concerning search advertising intermediation.

Relevance

It demonstrates how control over an ecosystem layer can affect adjacent advertising markets.

14. Autonomous Vehicle Ecosystems

The concept becomes particularly important in autonomous mobility.

A modern autonomous vehicle ecosystem may contain:

1. vehicle hardware;
2. sensors;
3. LiDAR;
4. cameras;
5. autonomous-driving algorithms;
6. mapping;
7. cloud computing;
8. telecommunications;
9. charging;
10. payment;
11. maintenance;
12. vehicle operating systems;
13. app marketplaces; and
14. mobility platforms.

A company controlling several layers may obtain ecosystem leverage.

Example

Suppose Company A controls:

vehicle OS + autonomous-driving software + vehicle data + charging network.

It could potentially disadvantage Company B by:

• restricting API access;
• withholding vehicle data;
• preventing interoperability;
• making charging functionality incompatible;
• tying autonomous-driving services to its cloud;
• favouring its own mobility applications.

Each practice would require separate competition-law analysis.

15. Autonomous Ecosystem and Essential-Facility Concerns

An ecosystem component can potentially become an essential facility-type bottleneck where competitors cannot realistically compete without access.

Examples may include:

• proprietary vehicle data;
• critical APIs;
• operating-system functionality;
• charging interfaces;
• autonomous-driving infrastructure;
• mapping infrastructure.

However, mere commercial importance is not automatically enough to establish an essential-facility obligation. The precise legal test varies by jurisdiction.

16. Foreclosure Effects

The central economic question is often:

Does the ecosystem conduct foreclose rivals sufficiently to weaken competition?

Possible foreclosure mechanisms include:

A. Input foreclosure

The ecosystem owner denies competitors access to an important input.

B. Customer foreclosure

The ecosystem owner prevents customers from dealing with competing suppliers.

C. Platform foreclosure

The ecosystem owner restricts rival applications or services from reaching users.

D. Data foreclosure

The ecosystem owner prevents competitors from obtaining data necessary to compete effectively.

E. Innovation foreclosure

The ecosystem owner restricts technologies that could develop into competing ecosystems.

17. Competition Between Ecosystems

Competition may occur not only within an ecosystem but between ecosystems.

For example:

Competition authorities may therefore ask whether conduct prevents consumers and businesses from choosing between competing ecosystems.

18. Multi-Homing

Multi-homing is an important constraint.

If users can easily use several ecosystems simultaneously, ecosystem power may be weaker.

For example:

A consumer can use several cloud providers.

But if switching requires:

• purchasing new hardware;
• losing accumulated data;
• changing accounts;
• retraining employees;
• abandoning applications;
• replacing infrastructure,

then multi-homing may be substantially weaker.

19. Network Effects and Tipping

A major concern is market tipping.

The cycle can be:

Large user base
↓
More data
↓
Better service
↓
More developers
↓
More complementary products
↓
More users
↓
Higher entry barriers

Once an ecosystem reaches this stage, competitors may find it difficult to achieve minimum efficient scale.

20. Interoperability as a Competition Remedy

Possible remedies include:

• mandatory interoperability;
• API access;
• data portability;
• prohibition of discriminatory access;
• neutral ranking;
• restrictions on self-preferencing;
• prohibition of tying;
• removal of exclusivity;
• alternative payment mechanisms;
• access to technical documentation;
• switching tools.

The EU's 2026 DMA measures concerning Android illustrate how interoperability can be used to address ecosystem advantages: the Commission required measures concerning access to Android functionality for competing AI services and access to certain search data.

21. Autonomous Ecosystem Market Power — Legal Test

A useful analytical framework is:

Step 1 — Identify the ecosystem

What products, services, infrastructure and data are interconnected?

Step 2 — Define relevant markets

Identify:

• product markets;
• geographic markets;
• upstream/downstream markets;
• complementary markets.

Step 3 — Establish market power

Examine:

• shares;
• barriers;
• network effects;
• switching costs;
• data;
• interoperability;
• entry.

Step 4 — Identify the bottleneck

Determine what ecosystem component competitors depend upon.

Step 5 — Identify the conduct

Examples:

• tying;
• bundling;
• exclusivity;
• self-preferencing;
• discriminatory access;
• refusal to interoperate;
• data restrictions;
• predatory strategies;
• loyalty mechanisms.

Step 6 — Analyse foreclosure

Ask whether the conduct materially restricts rivals' ability to compete.

Step 7 — Examine efficiencies

Consider:

• security;
• privacy;
• technical integration;
• innovation;
• quality;
• cybersecurity;
• consumer benefits.

Step 8 — Consider remedies

Possible remedies include:

• interoperability;
• data portability;
• non-discrimination;
• access obligations;
• structural separation in exceptional cases.

22. Key Competition Concerns

23. Key Doctrinal Insight

The principal lesson from ecosystem cases is that competition law should not examine each product in isolation where the products are technologically and commercially interconnected.

The Google Android litigation is especially significant because the EU courts examined Google's conduct across operating-system, app-store, search and browser layers rather than treating those relationships as completely independent.

At the same time, ecosystem size itself is not unlawful. Competition law generally focuses on whether market power exists and whether the undertaking has engaged in conduct that produces legally relevant exclusionary, exploitative or coordination effects.

24. Conclusion

Autonomous ecosystem market power represents an important evolution in competition-law analysis.

Traditional analysis asks:

“How much market power does the firm have in Market X?”

Ecosystem analysis additionally asks:

“How does control over Market X allow the firm to influence Markets Y and Z through technological, contractual, data, network and interoperability relationships?”

The principal competition risks are therefore:

ecosystem control → network effects → switching costs → data advantages → interoperability control → self-preferencing/tying/exclusivity → rival foreclosure → ecosystem entrenchment.