Mobile Operating System Tying

1. Introduction

Mobile operating system tying occurs when a dominant provider of a mobile operating system or a closely connected platform conditions access to one product or service on the acquisition, installation, use, or acceptance of another product.

Typical examples include:

• tying an app store to a search application;
• tying a mobile OS to a browser;
• tying an OS to a payment service;
• requiring OEMs to pre-install specified applications;
• conditioning access to proprietary APIs on acceptance of additional services;
• requiring a device manufacturer to install an entire package of applications rather than allowing individual selection;
• technically integrating a tied application so deeply into the OS that competing products cannot effectively compete.

The principal competition concern is leveraging: a firm uses dominance in the operating-system or app-store layer to strengthen its position in an adjacent market.

Under EU law, the principal framework is Article 102 TFEU. In India, similar conduct may be examined under Section 4(2)(d) and 4(2)(e) of the Competition Act, 2002, particularly where a dominant enterprise imposes conditions on the purchase of another product or uses dominance in one market to enter or protect another market.

2. Meaning of Tying in the Mobile Ecosystem

There are normally two products:

A. Tying product

The product in which the undertaking possesses substantial market power.

Examples:

• mobile operating system;
• Android app store;
• proprietary mobile platform;
• essential mobile-device ecosystem.

B. Tied product

The additional product that the customer is required or strongly induced to accept.

Examples:

• search engine;
• browser;
• digital assistant;
• payment service;
• mapping application;
• media player;
• advertising service.

Example

Suppose an OS provider has substantial market power in mobile operating systems and tells manufacturers:

"You may obtain our app store only if you also pre-install our search application."

The app store is the tying product, while the search application is the tied product.

The competition question is not simply whether the two products are bundled. The critical questions are whether:

1. the products are distinct;
2. the undertaking has dominance in the tying market;
3. customers are effectively compelled to accept the tied product; and
4. the practice is capable of restricting competition in the tied market.

3. Why Mobile OS Tying Creates Particular Competition Risks

Mobile ecosystems are unusually susceptible to tying because an OS is not merely an ordinary software product.

It controls:

• application installation;
• default settings;
• APIs;
• notifications;
• device permissions;
• security certification;
• app-store access;
• system updates;
• technical interoperability;
• user-interface placement.

Consequently, tying at the OS level can create ecosystem-wide effects.

A competing application may technically remain available but nevertheless face substantial disadvantages if the platform's own application is:

• pre-installed;
• made the default;
• given privileged API access;
• impossible to uninstall;
• displayed more prominently;
• integrated with system functions;
• required for access to another important service.

The European Commission specifically considered pre-installation and status-quo effects in the Google Android proceedings.

4. Legal Elements of Mobile OS Tying

A. Dominance in the tying market

The first question is whether the undertaking possesses a dominant position in the tying market.

Relevant factors include:

• market share;
• barriers to entry;
• network effects;
• switching costs;
• developer dependence;
• OEM dependence;
• access to essential APIs;
• installed user base;
• data advantages;
• ecosystem effects.

Importantly, the relevant market need not always be simply "mobile operating systems."

Depending on the facts, authorities may examine:

• licensable mobile operating systems;
• Android app stores;
• mobile search;
• mobile browsers;
• specific platform services.

The Google Android litigation illustrates the importance of defining the relevant market carefully. The European Commission's case involved separate markets for smart mobile operating systems, Android app stores and general search services.

B. Separate products

The tying and tied products must generally constitute distinct products.

Evidence may include:

• separate consumer demand;
• independent suppliers;
• separate commercial distribution;
• separate pricing;
• separate technological functionality;
• availability of competing products.

The classic Microsoft jurisprudence established that an operating system and a media player can constitute separate products even where they are technically integrated.

The same reasoning is important for mobile systems.

For example:

Mobile OS ≠ Search engine

Mobile OS ≠ Browser

App store ≠ Search application

Mobile OS ≠ Payment application

The fact that products are technically capable of integration does not automatically make them one product.

5. Coercion

Tying becomes particularly problematic where the customer has no meaningful choice.

Coercion can take several forms:

Contractual coercion

The agreement expressly requires acceptance of the second product.

Economic coercion

The tied product is technically optional but refusing it results in substantially worse commercial terms.

Technical coercion

The products are integrated so deeply that removing the tied product is practically impossible.

Ecosystem coercion

Access to an important platform service is conditioned on accepting additional products.

Default-based coercion

The customer technically can install an alternative but the platform makes switching sufficiently difficult that the default has significant competitive importance.

6. Pre-installation and Default Bias

Pre-installation is especially important in mobile markets.

Users often do not replace applications that are already available when they purchase a device.

Therefore:

Pre-installation → visibility → usage → data → advertising revenue → stronger ecosystem

This can produce a reinforcing feedback loop.

The European Commission found in the Google Android proceedings that pre-installation could produce a status-quo bias, making it difficult for competing applications to offset the advantage of Google's pre-installed applications.

Thus, a tying analysis may extend beyond the formal question of whether consumers can technically download a competing application.

7. Foreclosure of Rivals

The central competition concern is usually foreclosure.

A tied product can receive an artificial competitive advantage because the dominant platform controls the principal distribution channel.

Possible effects include:

• reduced downloads of competing applications;
• reduced advertising revenue;
• reduced data acquisition;
• reduced developer investment;
• weaker innovation;
• increased barriers to entry;
• loss of network effects;
• exclusion of smaller competitors;
• increased dependence on the dominant ecosystem.

The analysis should therefore consider actual or likely competitive effects, rather than merely observing that two products are bundled.

8. Six Major Case Laws

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

General Court, Case T-604/18 (2022); CJEU, Case C-738/22 P (2026)

This is the most directly relevant modern mobile-OS tying case.

The European Commission found that Google had engaged in several forms of conduct involving Android, including tying Google Search and Chrome with the Play Store, alongside other contractual restrictions and exclusivity-related arrangements.

The General Court substantially upheld the Commission's findings while modifying the fine.

Importantly, the litigation continued before the Court of Justice, which issued its judgment on 2 July 2026. The appeal expressly addressed, among other matters, tying, exclusionary effects, contractual restrictions, exclusive pre-installation payments and Android forks.

Principle

Mobile-platform tying must be examined in its broader ecosystem context.

Significance

This case demonstrates that:

• OS ecosystems can contain several separately relevant markets;
• app stores can constitute a tying product;
• pre-installation can materially affect competition;
• defaults can strengthen network effects;
• tying can reinforce dominance in an adjacent market.

2. Microsoft v Commission — Windows Media Player

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

Microsoft's Windows operating system was tied to Windows Media Player.

The European Commission considered Windows and the media player to be separate products and found that Microsoft possessed dominance in PC operating systems.

The General Court upheld the essential findings concerning the distinct products, Microsoft's dominance and the absence of meaningful customer choice concerning Windows without Media Player.

Principle

Technical integration does not automatically eliminate the distinction between two products.

Significance for mobile OS

The reasoning is applicable by analogy where a mobile OS provider argues:

"The browser/search/payment application is merely part of the operating system."

The legal question is whether there is separate demand and competitive supply, not merely whether the software is technically integrated.

3. United States v Microsoft Corp.

U.S. District Court, 1999–2000; D.C. Circuit, 2001

Microsoft tied Internet Explorer to Windows.

The U.S. case examined Microsoft's use of Windows' operating-system dominance to strengthen Internet Explorer against competing browsers, particularly Netscape Navigator.

The court found that browsers and operating systems were separate products and considered Microsoft's contractual and technical restrictions concerning Internet Explorer.

Principle

A dominant operating-system provider cannot necessarily use its OS position to disadvantage competing applications.

Mobile relevance

The case is highly relevant to:

• mobile browsers;
• mobile search;
• default applications;
• OEM restrictions;
• pre-installation;
• technical integration.

4. Tetra Pak II v Commission

Case C-333/94 P

Tetra Pak involved tying practices concerning packaging machinery and packaging materials.

The Court accepted that tying can constitute abusive conduct where a dominant undertaking uses its position in one market to restrict competition in another.

Principle

Dominance in one market may not lawfully be leveraged through tying into a related market where the conduct produces exclusionary effects.

Mobile relevance

A mobile OS provider could similarly use dominance over the platform to advantage:

• its payment application;
• advertising system;
• search engine;
• cloud service;
• browser;
• authentication service.

The case therefore provides an important general framework for leveraging through tying.

5. Hilti AG v Commission

Case T-30/89

Hilti was dominant in the market for certain nail-gun systems and related products and was found to have engaged in practices involving tying and other exclusionary conduct.

The EU courts upheld the basic finding that a dominant undertaking could not use its position in one market to restrict competition in complementary products.

Principle

A dominant undertaking cannot automatically use dominance in one product to control adjacent complementary products.

Mobile relevance

The analogy is particularly strong for ecosystems involving:

• OS + accessories;
• OS + applications;
• OS + payment systems;
• OS + cloud services;
• OS + security products.

6. IMS Health v Commission

Case T-184/01; C-418/01 P

IMS Health concerned access to a commercially important infrastructure and the use of market power to restrict competition in an adjacent market.

Although it is principally remembered for the essential-facilities/IP-access doctrine rather than classical OS tying, it is important for mobile ecosystems because platform control can create dependencies for competing service providers.

Principle

Competition law may scrutinise conduct where control over an important platform or infrastructure is used to restrict effective competition in an adjacent market.

Mobile relevance

The reasoning is particularly relevant where an OS provider:

• restricts API access;
• denies interoperability;
• gives its own applications privileged technical access;
• makes access conditional upon accepting another service.

9. Comparative Case-Law Table

10. Mobile OS Tying in India

The Indian framework is particularly relevant under Section 4 of the Competition Act, 2002.

Section 4(2)(d)

A dominant enterprise may abuse its position by:

making the conclusion of contracts subject to acceptance by other parties of supplementary obligations which, by their nature or according to commercial usage, have no connection with the subject of such contracts.

This provision is particularly relevant to tying.

Section 4(2)(e)

It also addresses using dominance in one relevant market to enter into, or protect, another relevant market.

This corresponds closely to the economic concept of leveraging.

11. Google Android and the Indian Competition Framework

The Indian Competition Commission has also examined Google's conduct in relation to the Android ecosystem.

The Indian analysis has involved questions concerning:

• Android OS;
• Google Play Store;
• Google Search;
• Chrome;
• OEM agreements;
• pre-installation;
• anti-fragmentation restrictions;
• competing applications.

The case is therefore highly relevant to understanding how the traditional concept of tying operates in a modern mobile ecosystem.

The broader lesson is that competition authorities increasingly examine the entire platform architecture, rather than considering each application in isolation.

12. Types of Mobile OS Tying

A. OS–Search Tying

Example:

Android → Google Search

Competition concern:

• search defaults;
• data accumulation;
• advertising scale;
• reduced search-engine entry.

B. OS–Browser Tying

Example:

OS → Proprietary Browser

Potential concerns:

• browser default;
• pre-installation;
• API privileges;
• reduced downloads of rival browsers.

The Microsoft browser case is the classic precedent.

C. OS–App Store Tying

Example:

Mobile OS/App Store → Mandatory Search Application

This is particularly important following the Google Android litigation.

D. OS–Payment Tying

Example:

A mobile OS requires developers or consumers to use its proprietary payment system for particular transactions.

Potential concerns:

• transaction fees;
• exclusion of competing payment providers;
• reduced payment innovation;
• control over payment data.

E. OS–Cloud Tying

A platform may require or strongly induce users to use the provider's cloud-storage or backup service.

Competition concerns may involve:

• switching costs;
• data portability;
• interoperability;
• ecosystem lock-in.

F. OS–Advertising Tying

The platform may condition access to an important OS service on using its advertising or measurement technology.

This may leverage OS dominance into:

• mobile advertising;
• ad exchanges;
• attribution;
• analytics.

13. Technical Tying vs Contractual Tying

Contractual tying

The contract explicitly states:

"You cannot obtain A unless you also accept B."

Technical tying

The provider makes B inseparable from A through software architecture.

Default tying

B is automatically selected as the default.

Economic tying

A is technically available separately but the pricing structure makes purchasing B practically unavoidable.

Ecosystem tying

Access to several important services depends on accepting a common bundle.

The last category is increasingly important in mobile markets.

14. Objective Justification

Tying is not automatically unlawful merely because products are bundled.

A dominant undertaking may attempt to establish an objective justification.

Potential arguments include:

• security;
• privacy;
• system stability;
• interoperability;
• technical efficiency;
• prevention of malware;
• consumer convenience;
• consistent user experience;
• reduction of transaction costs;
• funding of free platform services.

However, the justification must be connected to the actual conduct.

In the Google Android proceedings, Google advanced arguments concerning monetisation, user experience, competition with vertically integrated platforms and the economics of licensing the Play Store. The Commission rejected the claimed objective justification for the relevant tying practices.

15. When Tying Becomes Particularly Problematic

Competition concerns become stronger where several factors coexist:

Dominant OS

↓

Separate tied product

↓

Mandatory/preferential pre-installation

↓

No meaningful unbundling

↓

Default status

↓

Large installed user base

↓

Network effects

↓

Reduced rival downloads

↓

Higher entry barriers

This cumulative analysis is particularly important in digital markets.

16. Defences Available to the Platform

A mobile OS provider may argue that tying:

1. improves cybersecurity;
2. provides a consistent user experience;
3. reduces fragmentation;
4. improves interoperability;
5. prevents malicious applications;
6. reduces technical support costs;
7. encourages innovation;
8. permits free or low-cost OS distribution;
9. improves performance;
10. protects user privacy.

The authority must therefore distinguish between genuine product integration and strategic exclusion of rivals.

17. Competition Assessment Framework

A useful analytical framework is:

Step 1 — Identify the tying product

Is it:

• OS?
• app store?
• platform service?

Step 2 — Define the relevant market

Determine whether the relevant market concerns:

• mobile OS;
• app stores;
• search;
• browsers;
• payments;
• advertising;
• cloud services.

Step 3 — Establish dominance

Consider:

• market share;
• network effects;
• switching costs;
• OEM dependence;
• developer dependence.

Step 4 — Identify the tied product

Determine whether it is independently demanded or supplied.

Step 5 — Establish coercion

Was acceptance:

• mandatory?
• contractually required?
• economically compelled?
• technically unavoidable?

Step 6 — Examine foreclosure

Ask whether rivals lose:

• distribution;
• users;
• data;
• scale;
• innovation incentives.

Step 7 — Examine efficiencies

Consider:

• security;
• interoperability;
• privacy;
• technical integration;
• consumer benefits.

Step 8 — Apply proportionality

Could the legitimate objective be achieved through a less restrictive alternative?

18. Important Distinction: Bundling Is Not Automatically Tying

This distinction is essential for examination purposes.

Lawful integration

A mobile OS incorporates a browser because the browser is technically necessary for system functionality, while users can freely install alternatives and rivals are not disadvantaged.

Potentially abusive tying

A dominant OS provider:

• requires its browser;
• prevents OEMs from installing alternatives;
• makes removal difficult;
• gives its browser privileged APIs;
• makes competing browsers technically inferior;
• uses contractual restrictions to prevent rival distribution.

The second situation raises substantially greater competition concerns.

19. Economic Effects

Mobile OS tying can affect several dimensions of competition.

Price

Even where the tied application is free, competition may be harmed through:

• advertising monetisation;
• data collection;
• transaction fees;
• reduced quality.

Quality

Rivals may have less incentive to improve products.

Innovation

Potential entrants may find the market commercially unattractive.

Choice

Consumers may technically have alternatives but may rarely switch from the default.

Privacy

Reduced competition can affect competing privacy models and data practices.

Entry

The tied product benefits from immediate access to a large installed base.

20. Remedies

Competition authorities may consider several remedies.

Structural remedies

In exceptional cases:

• separation of businesses;
• divestiture.

Behavioural remedies

More commonly:

• allow unbundling;
• permit competing applications;
• prohibit contractual restrictions;
• require choice screens;
• allow default changes;
• permit OEM flexibility;
• prevent discriminatory API access.

Interoperability remedies

The provider may be required to give competing services reasonable access to technical interfaces.

Non-discrimination

The OS provider may be prohibited from giving its own applications preferential treatment.

Transparency

Authorities may require clearer disclosure of:

• default settings;
• ranking;
• access conditions;
• API policies.

21. Examination-Oriented Legal Test

A concise formula is:

Mobile OS Tying = Separate Products + Dominance in Tying Market + Coercion/Conditionality + Potential or Actual Foreclosure + Insufficient Objective Justification

The stronger the combination of these elements, the greater the competition-law concern.

22. Key Takeaways

1. Mobile OS tying is a form of leveraging.
2. The OS or app store may constitute the tying product.
3. Search, browsers, payments, advertising and cloud services may constitute the tied product.
4. The products must ordinarily be assessed for economic distinctness.
5. Dominance in the tying market is fundamental to an abuse-of-dominance analysis.
6. Pre-installation and defaults can produce substantial competitive advantages.
7. Technical integration does not necessarily mean that two products are legally one product.
8. Google Android is the most directly relevant modern mobile-ecosystem precedent.
9. Microsoft Windows/Internet Explorer and Microsoft Windows Media Player provide important OS-tying principles.
10. Tetra Pak II, Hilti and IMS Health provide broader principles concerning leveraging, complementary products and platform/access restrictions.
11. Objective justifications such as security and interoperability can be relevant but must be connected to the actual restriction.
12. Competition analysis should consider foreclosure, innovation, consumer choice, network effects and ecosystem lock-in, rather than simply the existence of a bundle.

Core authorities to remember

Google Android — T-604/18; C-738/22 P (2026)
Microsoft v Commission — T-201/04
United States v Microsoft — U.S. District Court / D.C. Circuit
Tetra Pak II — C-333/94 P
Hilti — T-30/89
IMS Health — T-184/01 / C-418/01 P

These cases collectively show the evolution from traditional software tying toward modern ecosystem-based platform tying, where defaults, pre-installation, APIs, contractual restrictions and network effects can be as important as the formal bundle itself.