Global Digital Operating System Dominance Issues

Introduction

Digital operating-system dominance refers to a situation in which a company controls an operating system (OS) that functions as a foundational layer for smartphones, computers, connected devices, vehicles, cloud environments, or other digital ecosystems. An operating system is not merely software; it can determine which applications can reach users, which payment systems can operate, which browsers or search engines are accessible, what data can be collected, which hardware is compatible, and what technical standards developers must follow.

The competition-law concern arises when an OS provider uses this foundational position to extend, protect, or exploit market power in adjacent markets. The most important mechanisms include self-preferencing, tying, default settings, app-store restrictions, technical interoperability restrictions, exclusionary licensing, data advantages, switching costs, and discriminatory access.

Because digital operating systems frequently operate globally, their dominance raises a particularly important question: should competition law treat the OS as an ordinary product market, or as critical digital infrastructure whose control can confer structural power across an entire ecosystem?

1. Meaning of Digital Operating System Dominance

An operating system can perform several strategically important functions:

• controls access between hardware and applications;
• determines application-installation rules;
• controls APIs and technical interfaces;
• manages permissions and security;
• determines default applications;
• controls access to app stores;
• facilitates payments and subscriptions;
• generates valuable behavioural and technical data;
• influences advertising and discovery;
• imposes contractual conditions on developers;
• determines interoperability with competing devices and services.

Consequently, OS dominance can produce ecosystem-wide leverage.

For example:

OS → App Store → Apps → Payments → Advertising → Data → Cloud services → Devices

Control at the first layer can therefore influence competition at all subsequent layers.

2. Relevant Markets

Competition authorities may define several different markets rather than treating the OS as one universal market.

A. Mobile operating systems

The relevant market may include operating systems for smartphones and tablets.

The principal competitive variables include:

• installed user base;
• developer ecosystem;
• app availability;
• hardware integration;
• security;
• privacy;
• switching costs;
• interoperability.

B. Desktop operating systems

Desktop operating systems may constitute a distinct market because their users, applications and hardware requirements differ substantially from mobile ecosystems.

C. Smart-device operating systems

Connected televisions, watches, speakers, automobiles and IoT devices can create additional OS markets.

D. In-vehicle operating systems

Automotive OS platforms increasingly control:

• navigation;
• entertainment;
• vehicle data;
• app ecosystems;
• connected services;
• charging information;
• driver interfaces.

E. App-distribution markets

An authority may separately examine app stores or app-distribution services.

F. Payment markets

Where the OS controls access to in-app payments or NFC functionality, competition issues may arise in payment services as well.

3. Sources of OS Dominance

A. Network Effects

Operating systems exhibit powerful indirect network effects.

More users attract developers.

More developers produce more applications.

More applications attract additional users.

This produces:

Users → Developers → Applications → More Users

A dominant OS may therefore become increasingly difficult to challenge even where competing technology is technically available.

B. Switching Costs

Consumers may accumulate:

• purchased applications;
• subscriptions;
• cloud data;
• photographs;
• contacts;
• device-specific accessories;
• authentication credentials;
• digital identities.

Moving to another OS may therefore involve substantial economic and practical costs.

This can reduce consumer responsiveness to competitive alternatives.

4. Default Settings and Choice Architecture

OS providers frequently control the initial configuration of a device.

Defaults can determine:

• search engine;
• browser;
• digital assistant;
• payment service;
• mapping application;
• media player;
• app store;
• cloud-storage provider.

The competitive concern is that consumers may not actively choose the default.

A dominant OS can therefore convert technical control into distributional power.

This is particularly significant where changing the default requires:

• multiple screens;
• technical knowledge;
• additional downloads;
• warnings;
• repeated confirmation.

Competition authorities increasingly examine such choice architecture rather than focusing exclusively on explicit contractual exclusion.

5. Tying and Bundling

An OS provider may bundle its operating system with adjacent services.

Examples include:

• browser;
• search engine;
• cloud storage;
• security software;
• payment services;
• media applications;
• messaging;
• advertising services.

The legal concern is whether the dominant undertaking uses the OS to obtain or maintain dominance in another market.

The classic competition-law framework asks whether:

1. the undertaking is dominant in the tying market;
2. the OS and secondary product are distinct products;
3. customers are effectively forced to obtain the secondary product;
4. the conduct restricts competition;
5. there is no adequate objective justification.

6. Self-Preferencing

An OS owner can potentially favour its own applications over competing applications.

For example, the OS could:

• give its own applications privileged API access;
• place its own applications prominently;
• restrict competing applications from accessing functionality;
• provide its own services with superior technical integration;
• use operating-system data to improve competing services.

This raises the broader question of platform neutrality.

The problem is especially serious where the OS provider simultaneously acts as:

Infrastructure operator + marketplace operator + competitor.

7. App Store Gatekeeping

App stores can become the principal gateway between developers and consumers.

An OS provider may impose:

• mandatory distribution through its store;
• commission requirements;
• payment-processing restrictions;
• anti-steering rules;
• developer disclosure requirements;
• technical review;
• restrictions on alternative app stores.

Where the OS is dominant, these rules can become competition-law issues rather than merely private contractual arrangements.

The central issue is whether the restrictions are genuinely necessary for:

• security;
• privacy;
• malware prevention;
• quality control;

or whether they primarily protect the OS provider's commercial position.

8. Interoperability and Access to APIs

APIs can function as essential technical interfaces.

A dominant OS provider may control access to:

• NFC;
• Bluetooth functionality;
• location data;
• background processing;
• notifications;
• device sensors;
• authentication;
• payment interfaces;
• vehicle data.

If competitors receive inferior access, the OS provider may distort downstream competition.

This creates a modern version of the essential-facilities/interoperability problem.

However, competition law generally does not require dominant companies to provide unrestricted access to every proprietary technology. The legal threshold for intervention is therefore important.

9. Data Advantages

Operating systems can provide access to enormous quantities of information concerning:

• device use;
• application use;
• location;
• searches;
• payments;
• interactions;
• hardware performance;
• consumer behaviour.

A dominant OS provider may potentially combine this information with data from its other services.

This can produce a reinforcing cycle:

OS dominance → data accumulation → better services → greater user retention → stronger OS dominance

Competition authorities may therefore examine data accumulation as a source of durable entry barriers.

10. Privacy and Competition

Privacy can operate in two directions.

A dominant OS provider may argue that restrictive policies are necessary to protect privacy and security.

At the same time, competitors may argue that the same restrictions:

• disadvantage rival services;
• restrict advertising access;
• prevent interoperability;
• reduce competition.

The legal challenge is distinguishing legitimate privacy protection from strategic exclusion disguised as privacy protection.

11. Major Case Laws

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

This is one of the foundational operating-system dominance cases.

Microsoft possessed substantial power in the market for Intel-compatible PC operating systems and used that position in its relationship with web browsers.

The litigation concerned Microsoft's conduct toward Netscape and other technologies, including contractual and technical strategies designed to protect the Windows ecosystem.

Significance

The case established important principles concerning:

• monopoly maintenance;
• technological tying;
• exclusionary agreements;
• leveraging operating-system power;
• network effects.

It demonstrated that an OS can function as a strategic bottleneck through which competition in adjacent software markets can be affected.

2. European Commission — Microsoft (2004)

The European Commission found Microsoft had abused its dominant position by, among other things, refusing to provide certain interoperability information and tying Windows Media Player to Windows.

The case ultimately generated extensive litigation before the EU courts.

Significance

It is particularly important for digital OS dominance because it illustrates two different theories:

OS → interoperability

and

OS → adjacent software product

The case demonstrates that dominant OS providers may face competition-law obligations concerning interoperability where their conduct substantially restricts downstream competition.

3. European Commission v. Microsoft Corp., Case T-201/04

The General Court substantially upheld the Commission's findings concerning Microsoft's abuse of dominance.

The Court accepted the importance of interoperability in allowing competing work-group server products to compete effectively.

Significance

The case is significant because it recognised that technical interoperability can be critical to preserving competition.

It provides a useful framework for analysing modern situations involving:

• APIs;
• operating-system interfaces;
• cloud interoperability;
• connected devices;
• digital ecosystems.

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

The European Commission's Android decision concerned Google's practices relating to Android devices.

The Commission examined several practices, including:

• tying Google Search and Google Chrome with certain Google applications;
• payments to manufacturers and mobile-network operators for exclusive pre-installation;
• restrictions concerning Android forks.

The Commission considered these practices capable of reinforcing Google's dominant position in general search.

Significance

This is perhaps the most directly relevant modern OS dominance case.

It illustrates the concept of:

Operating-system dominance → default/pre-installation advantages → adjacent-market dominance.

The case also demonstrates why mobile operating systems can have competition effects far beyond the OS market itself.

5. Epic Games, Inc. v. Apple Inc., 67 F.4th 946 (9th Cir. 2023)

Epic challenged Apple's restrictions concerning app distribution and payments on iOS.

The litigation examined Apple's control over app distribution and payment mechanisms.

Although the court did not accept every antitrust theory advanced by Epic, it addressed important issues concerning Apple's ecosystem and its restrictions on alternative payment mechanisms.

Significance

The case is highly relevant to:

• app-store gatekeeping;
• payment restrictions;
• anti-steering;
• developer access;
• platform governance;
• OS-level distribution power.

It illustrates the difficulty of applying conventional antitrust doctrine to a vertically integrated digital ecosystem.

6. Epic Games, Inc. v. Google LLC

Epic also challenged Google's Android ecosystem and Google Play practices.

The litigation examined Google's control over app distribution, payments and relationships with developers and device manufacturers.

A jury found Google had unlawfully maintained monopoly power in relevant app-distribution and in-app-billing markets.

Significance

The case demonstrates that OS ecosystem power can be analysed separately from the underlying operating-system market.

It also highlights:

• alternative app stores;
• payment systems;
• developer commissions;
• distribution restrictions;
• contractual exclusion;
• ecosystem governance.

7. Qualcomm Inc. v. Federal Trade Commission, 969 F.3d 974 (9th Cir. 2020)

Although not an operating-system case in the narrow sense, Qualcomm is important for digital-platform analysis because it concerns control over critical technological infrastructure and licensing relationships.

The Ninth Circuit reversed the district court's finding of an antitrust violation.

Significance

The case illustrates the importance of carefully distinguishing:

• possession of technological power;
• exploitation of that power;
• exclusionary conduct;
• legitimate intellectual-property licensing.

This distinction is equally important when analysing dominant OS providers.

8. United States v. Google LLC — Search Distribution Litigation

The U.S. government's case concerning Google's search-distribution agreements is also relevant to operating-system dominance because Android provides an important distribution channel for Google's search services.

The litigation illustrates how defaults, pre-installation and distribution agreements can reinforce an incumbent's position in a neighbouring market.

Significance

The broader principle is:

Control over a digital access point can create distribution advantages in another market.

This is central to modern OS competition law.

12. Comparative Legal Approaches

The convergence is increasingly evident: authorities are moving from examining only price effects toward examining ecosystem control, access, interoperability and contestability.

13. Traditional Antitrust v. Digital OS Dominance

Traditional competition law often asks:

Does the conduct increase prices or reduce output?

Digital OS markets require additional questions:

• Can consumers realistically switch?
• Can developers reach users without the dominant OS?
• Can competing app stores operate?
• Can rival payment systems function?
• Are APIs equally accessible?
• Does the OS provider favour its own applications?
• Can data be transferred?
• Can competing devices interoperate?
• Are defaults contestable?
• Does the ecosystem create cumulative entry barriers?

Thus, quality, innovation, privacy, interoperability and contestability become important competitive parameters.

14. The Ecosystem Leveraging Problem

The most important theoretical concern is ecosystem leveraging.

Consider:

Dominant OS

↓

App distribution

↓

Payment system

↓

Search / advertising

↓

Cloud

↓

Data

↓

AI services

The OS provider can potentially use power acquired at the first layer to strengthen its position at every subsequent layer.

This creates a form of vertical digital leverage.

The competition concern is not necessarily that every integrated service is unlawful. Rather, the concern arises when integration is accompanied by conduct that prevents effective competition at adjacent levels.

15. AI and Next-Generation Operating Systems

The problem is becoming more complex as operating systems incorporate AI agents.

An AI-enabled OS could control:

• application selection;
• search;
• purchasing;
• communications;
• scheduling;
• payments;
• advertising;
• content recommendations;
• autonomous device actions.

Instead of merely determining which application opens, an AI operating system could determine which service performs the task at all.

For example:

User asks AI OS to book travel → OS selects booking provider → payment occurs through integrated service.

The competitive issue therefore shifts from app distribution to task allocation.

This could make AI operating systems a new form of digital bottleneck.

16. Remedies

Competition authorities may consider several remedies.

Structural remedies

In exceptional cases:

• divestiture;
• separation of business units;
• restrictions on vertical integration.

Behavioural remedies

More commonly:

• interoperability obligations;
• API access;
• prohibition of discriminatory treatment;
• choice screens;
• anti-steering obligations;
• alternative app stores;
• payment-system access;
• data portability;
• default-setting reforms.

Transparency remedies

Authorities may require:

• disclosure of ranking criteria;
• disclosure of API-access policies;
• transparency concerning app-review decisions;
• explanation of default selection;
• auditing of discriminatory treatment.

17. Key Legal Issues for Future Cases

Future OS cases are likely to revolve around:

1. AI-agent control over application selection
2. App-store monopoly power
3. Mandatory payment systems
4. Default search and browser arrangements
5. Interoperability with rival ecosystems
6. Access to device APIs
7. Data accumulation
8. Self-preferencing
9. Privacy-based exclusion
10. Cloud–OS integration
11. Automotive operating systems
12. Smart-home ecosystems
13. Wearable-device platforms
14. Digital identity integration
15. AI-native operating systems

Conclusion

Global digital operating-system dominance represents a transition from traditional product-market dominance toward infrastructure-based ecosystem power.

The leading cases—particularly Microsoft, EU Microsoft, Google Android, Epic Games v. Apple, and Epic Games v. Google—demonstrate different ways in which control over an operating system or its associated distribution infrastructure can influence adjacent markets.

The central competition-law principle is not that dominant operating systems are inherently unlawful. Rather:

The greater the OS's role as a gateway to users, applications, payments, data and complementary services, the greater the competition-law significance of discriminatory access, tying, self-preferencing, interoperability restrictions and exclusionary ecosystem practices.