Competition Law And Competition Concerns In Recommendation Monopolies .
Competition Law and Competition Concerns in Reflexive Infrastructures
1. Introduction
“Reflexive infrastructures” is not a conventional statutory category in competition law. It is better understood as an analytical concept describing infrastructures whose use strengthens the conditions that make them more valuable, influential, or difficult to replace.
In digital markets, an infrastructure may become reflexive when users generate data, data improves the service, the improved service attracts additional users, and the additional users generate still more data or complementary participation. Similar feedback can arise through network effects, developer ecosystems, defaults, standards, reputation systems, recommendation algorithms, payment systems, cloud infrastructure, or interoperability arrangements.
This idea closely resembles what competition authorities and economic literature call positive feedback loops, indirect network effects, data feedback loops, ecosystem effects, and self-reinforcing advantages. The OECD, for example, describes digital feedback loops as self-reinforcing processes in which changes on one side of a market can be amplified through network effects or data collection.
Competition law does not prohibit such infrastructures merely because they become large or successful. The central question is whether a firm possessing substantial market power uses control of the infrastructure in ways that unlawfully exclude rivals, reinforce dominance, foreclose adjacent markets, discriminate against dependent businesses, or impede effective entry.
2. Meaning of Reflexive Infrastructure
A simple example is a digital operating system:
More users → more developers → more applications → greater value of the operating system → more users.
The process therefore feeds back into itself.
The Competition Commission of India expressly identified this phenomenon in its Android proceedings. It explained that Android's large user base encouraged developers to create applications for Android; the availability of many applications then increased consumer demand for Android. The Commission described this as a “positive feedback loop.”
The same basic structure can appear in:
- search engines;
- app stores and operating systems;
- social networks;
- online marketplaces;
- payment networks;
- advertising technology;
- cloud and AI ecosystems;
- recommendation systems;
- identity and authentication infrastructure;
- developer platforms.
The competition problem becomes especially important when the feedback loop makes the infrastructure both commercially indispensable and increasingly difficult to challenge.
3. Main Characteristics
A. Network Effects
The usefulness of a platform may increase as more users or businesses participate.
Network effects can be direct, where additional users directly increase value for other users, or indirect, where growth on one side attracts participants on another side.
An app store illustrates indirect effects:
more consumers → more developers → more apps → more consumers.
These dynamics can create substantial entry barriers.
B. Data Feedback Loops
Data can produce another reflexive cycle:
more users → more data → better algorithms/services → better user experience → more users.
A rival entering later may therefore confront not merely a large incumbent but an accumulated informational advantage.
C. Ecosystem Effects
Modern platforms frequently operate interconnected products.
For example:
operating system → app store → browser → search → advertising → data → improvement of ecosystem services.
Control of one strategically important layer may strengthen the firm's position elsewhere.
D. Defaults and User Behaviour
Default settings can reinforce infrastructure dominance because many consumers do not change preselected services.
A platform controlling distribution can consequently increase usage of its own product, and increased usage may generate additional data or network effects.
E. Developer Dependency
Developers may invest substantial resources in APIs, programming tools, payment infrastructure and platform-specific applications.
Once these investments have been made, changing platforms can become costly.
F. Standards and Interoperability
Control over technical standards or interfaces may determine whether competitors can interact effectively with an ecosystem.
Restrictions on interoperability can therefore reinforce an incumbent's position.
4. Competition Concerns
4.1 Self-Reinforcing Market Power
Traditional market power may become more durable where the firm's existing scale itself generates advantages.
Suppose Platform A has substantially more users than Platform B.
Its greater user base may attract developers. More developers create more applications. More applications attract consumers. Consumer growth then attracts still more developers.
Competition law becomes concerned where conduct by the dominant undertaking artificially protects or intensifies this cycle.
The Android proceedings in India provide a particularly clear illustration: the CCI found substantial indirect network effects connecting Android users and application developers.
4.2 Barriers to Entry
Reflexive infrastructures can create entry barriers that cannot easily be overcome simply by developing a technically superior product.
A new operating system, for example, might need simultaneously to persuade:
- consumers to switch;
- developers to build applications;
- manufacturers to support the system;
- service providers to integrate with it.
This creates a coordination problem.
The historic Microsoft litigation similarly examined the “applications barrier to entry.” Evidence in the U.S. proceedings described a self-reinforcing relationship between widespread Windows adoption and developers' incentives to write software for Windows.
4.3 Tying and Bundling
A dominant infrastructure provider may connect access to an indispensable product with use of another product.
For example:
dominant operating system + browser
or
app store + proprietary payment system.
Tying can become especially significant in reflexive infrastructures because the additional usage generated for the tied service may strengthen its own feedback loop.
4.4 Self-Preferencing
A vertically integrated platform can operate infrastructure while simultaneously competing with businesses that depend on that infrastructure.
Examples could include:
- a marketplace ranking its own products;
- a search engine favouring a specialised service;
- an app ecosystem privileging proprietary applications.
The concern is not vertical integration itself. Competition authorities examine whether the infrastructure operator uses its gatekeeping position in a manner capable of excluding effective competition.
4.5 Leveraging Between Markets
Control over Infrastructure A can potentially strengthen the firm's position in Market B.
For example:
OS dominance → distribution advantage for search → more search queries → additional data → improved search → stronger search position.
The feedback loop therefore operates across markets rather than exclusively inside one market.
The CCI's Android decision found, among other matters, that Google leveraged its position in Android app-store infrastructure in relation to search, browsers and online video services.
4.6 Switching Costs and Lock-In
Competition can weaken when consumers or businesses cannot realistically migrate without losing:
- accumulated data;
- applications;
- contacts;
- purchased content;
- integrations;
- reputation;
- transaction histories;
- complementary services.
Lock-in can reinforce the underlying feedback mechanism because users who remain on the infrastructure continue contributing value to it.
4.7 Interoperability Restrictions
A powerful infrastructure provider might restrict access to APIs, interfaces or technical functionality.
Such restrictions can sometimes have legitimate reasons, including security, privacy, integrity or product-quality considerations.
Competition analysis therefore generally requires examining both:
exclusionary effects and objective/procompetitive justifications.
4.8 Acquisition of Emerging Rivals
Reflexive markets can also create merger-control concerns.
A large ecosystem may acquire businesses providing complementary technologies, important datasets or potential alternative infrastructure.
Modern competition analysis therefore increasingly examines ecosystems dynamically rather than considering only immediate horizontal overlaps. Recent scholarship comparing major digital merger decisions notes the growing importance—and difficulty—of ecosystem-level and forward-looking analysis.
5. Important Case Laws
Case 1 — United States v. Microsoft Corp.
United States – D.C. Circuit, 2001
This is one of the foundational cases for understanding self-reinforcing digital infrastructure.
Microsoft possessed substantial power through the Windows operating system. One central economic feature was the applications barrier to entry.
A large Windows user base encouraged software developers to develop programs for Windows. The large availability of applications then made Windows more attractive to consumers.
Thus:
Users → applications → users → applications.
The U.S. proceedings expressly discussed this self-reinforcing network effect.
Microsoft's practices concerning Internet Explorer and restrictions affecting OEMs and other parties became central to the monopolisation analysis.
Principle
Competition law may intervene where exclusionary conduct protects monopoly power that is already reinforced by network effects and ecosystem dependency.
6. Case 2 — Microsoft Corp. v Commission
European Union – Case T-201/04
The European Microsoft proceedings concerned, among other matters:
- interoperability information;
- work-group server operating systems;
- tying Windows Media Player with Windows.
The case demonstrates the significance of interoperability where a dominant technological platform forms an important part of a broader ecosystem.
Where complementary products need access to technical interfaces controlled by a dominant undertaking, restrictions can potentially impede effective competition.
Reflexive-infrastructure significance
Microsoft illustrates how infrastructure control can generate advantages beyond the infrastructure itself.
A large operating-system ecosystem attracts complementary products, and complementary products increase the attractiveness of that ecosystem.
The case therefore remains highly relevant when considering interoperability and ecosystem foreclosure.
7. Case 3 — Google Search (Shopping) v European Commission
European Union – Google and Alphabet v Commission, Case T-612/17
The European Commission found that Google had given favourable treatment to its own comparison-shopping service while rival comparison-shopping services were treated differently in general search results.
The General Court substantially upheld the Commission's decision.
The case is significant for reflexive infrastructure because search visibility can affect traffic.
A simplified feedback mechanism is:
ranking → traffic → transactions/data → service development → competitive position.
If the infrastructure controlling discovery systematically advantages its own downstream service, competitors may struggle to obtain the scale necessary to compete.
Principle
A dominant infrastructure's rules concerning visibility and access can have competitive consequences extending into neighbouring markets.
8. Case 4 — Google Android
European Commission, AT.40099; subsequent EU judicial proceedings
The Android proceedings examined contractual restrictions associated with Google's mobile ecosystem.
The Commission focused on practices involving:
- Google Search;
- Chrome;
- Play Store;
- device manufacturers;
- Android forks;
- revenue-sharing arrangements.
The Android ecosystem illustrates indirect network effects particularly well:
Android users → developers → applications → attractiveness of Android → additional Android users.
The case therefore shows why competition authorities may analyse contractual restrictions together with the economic characteristics of the ecosystem.
Academic analysis of the litigation likewise emphasizes the significance of pre-installation, defaults and restrictions concerning alternative Android versions.
Principle
Contractual restrictions imposed around a dominant platform can reinforce ecosystem advantages and make alternative infrastructure more difficult to establish.
9. Case 5 — Umar Javeed & Others v Google LLC & Another
Competition Commission of India – Android Mobile Device Ecosystem Case
This is particularly important for the concept of reflexive infrastructures.
The CCI expressly analysed the interaction between Android users and application developers.
It observed that Android's large user population encouraged application development, while the extensive availability of applications strengthened consumer demand for Android.
The Commission specifically characterised this as a self-reinforcing “positive feedback loop.”
The CCI ultimately found Google dominant in several relevant markets and identified violations involving practices connected with pre-installation, search, browsers, video services and restrictions concerning alternative Android implementations.
Principle
Indian competition law can take network effects, ecosystem structure, entry barriers and feedback loops directly into account when assessing dominance and exclusionary practices under Section 4 of the Competition Act.
10. Case 6 — XYZ / Match Group / Alliance of Digital India Foundation v Alphabet/Google
Competition Commission of India – Google Play Billing Case, 2022
This proceeding concerned Google's Play Store ecosystem and payment requirements.
The CCI considered Android app stores to be multi-sided digital marketplaces connecting developers and users. It found Google dominant in the identified Android operating-system and app-store markets and found contraventions of several provisions of Section 4.
Among its directions, the CCI required Google not to prevent app developers from using third-party billing/payment-processing services or discriminate against applications using them.
Reflexive significance
The case illustrates how an infrastructure can contain several dependent layers:
OS → app store → developers → consumers → transactions → payment infrastructure.
Control over one layer can therefore affect competition in another.
11. Case 7 — United States v Google LLC
U.S. District Court for the District of Columbia – Search Litigation
The U.S. search litigation provides another major example of feedback-driven infrastructure.
The court's 2024 liability decision found Google had unlawfully maintained monopoly power in general search and general search text advertising through distribution arrangements.
Evidence discussed in subsequent legal analysis showed the significance of default placements across browsers, devices and other distribution channels.
The economic mechanism is important:
default distribution → additional queries → scale/data → service and monetisation advantages → stronger ability to secure distribution.
Principle
Competition law may scrutinise agreements controlling default distribution when they help preserve monopoly power by denying rivals sufficient opportunities to achieve competitive scale.
12. Case 8 — Intel Corp. v European Commission
European Union – Case C-413/14 P
Intel is not principally a digital-platform case, but it remains important for assessing exclusionary conduct by dominant undertakings.
The litigation concerning Intel's rebate arrangements helped develop EU law regarding assessment of whether conduct by a dominant undertaking is capable of restricting competition.
Its broader relevance to reflexive infrastructures is methodological.
Authorities examining ecosystem conduct must consider matters such as:
- market position;
- coverage of the practice;
- duration;
- conditions attached to benefits;
- capability of excluding efficient competitors;
- economic evidence.
Principle
Dominance does not automatically make commercial conduct unlawful. Competition analysis must examine whether the challenged behaviour is capable of producing anticompetitive foreclosure under the applicable legal test.
13. Comparative Case Table
| Case | Main Infrastructure | Main Competition Concern |
|---|---|---|
| United States v Microsoft | PC operating system | Network effects and applications barrier to entry |
| Microsoft v Commission | Windows ecosystem | Interoperability and tying |
| Google Shopping | Search infrastructure | Self-preferencing and downstream foreclosure |
| Google Android – EU | Mobile ecosystem | Tying, defaults and ecosystem restrictions |
| Umar Javeed v Google – India | Android ecosystem | Positive feedback loops, leveraging and foreclosure |
| Google Play Billing – India | App-store infrastructure | Payment restrictions and developer dependency |
| United States v Google | Search/distribution ecosystem | Default distribution and maintenance of monopoly power |
| Intel v Commission | Processor ecosystem | Exclusionary arrangements/rebates |
14. Application under Indian Competition Law
Under India's Competition Act, reflexive infrastructure concerns can principally arise through Section 4, dealing with abuse of dominant position.
Potential issues can include:
Section 4(2)(a)
Unfair or discriminatory conditions or prices.
Section 4(2)(b)
Limiting production, services, markets, or technical/scientific development to consumers' prejudice.
Section 4(2)(c)
Denial of market access.
Section 4(2)(d)
Making contracts subject to supplementary obligations unrelated to their subject matter.
Section 4(2)(e)
Using dominance in one relevant market to enter into or protect another relevant market.
The Android decisions demonstrate particularly clearly how these provisions can operate in digital ecosystems.
15. The Central Economic Problem
The central competition issue can be represented as:
Initial Advantage
↓
More Users
↓
More Data / Developers / Complementors
↓
Better or Broader Ecosystem
↓
Greater Consumer Dependence
↓
Higher Entry Barriers
↓
More Users
↺
This cycle is not inherently anticompetitive.
Indeed, network effects can produce substantial benefits, including better services, interoperability, innovation and lower transaction costs.
The legal concern arises when exclusionary practices artificially prevent competitors from challenging the cycle.
16. Possible Competitive Benefits
Competition analysis should therefore distinguish success through superior performance from maintenance of market power through exclusionary conduct.
Reflexive infrastructures may generate:
- lower transaction costs;
- easier interoperability;
- larger developer communities;
- improved product quality;
- stronger security;
- faster innovation;
- broader product availability;
- more efficient matching between different groups of users.
Accordingly, size, integration or network effects alone do not establish an infringement.
17. Remedies
Where an infringement is established, possible competition remedies can include:
Interoperability obligations allowing competing products to communicate with important infrastructure.
Anti-tying measures separating infrastructure access from mandatory adoption of another product.
Choice mechanisms allowing consumers genuine alternatives to predetermined defaults.
Non-discrimination requirements preventing infrastructure operators from unfairly disadvantaging dependent competitors.
Data portability reducing switching costs where legally and technically appropriate.
Contractual restrictions may also be prohibited where exclusivity or related arrangements unlawfully foreclose competitors.
Remedy design is particularly difficult because simply stopping an unlawful practice may not immediately reverse advantages accumulated through earlier feedback loops. Research examining platform remedies therefore stresses that network effects and established defaults can continue influencing behaviour after the original practice ends.
18. Conclusion
Reflexive infrastructures describe systems in which participation strengthens the infrastructure itself. Users attract developers; developers attract users. Data improves algorithms; improved algorithms attract more users. Distribution generates usage; usage can improve scale and reinforce distribution advantages.
For competition law, the important distinction is:
Self-reinforcing success is not itself unlawful.
The concern arises when a firm with substantial market power uses tying, exclusivity, discriminatory access, self-preferencing, restrictive defaults, interoperability restrictions or leveraging practices to protect or intensify a feedback loop in a manner prohibited by competition law.
The leading cases—United States v Microsoft, Microsoft v Commission, Google Shopping, Google Android (EU), Umar Javeed v Google, the Google Play Billing proceedings, United States v Google, and Intel v Commission—collectively show how competition law has developed tools for analysing network effects, ecosystem dependence, interoperability, foreclosure, defaults and self-reinforcing market power.
For Indian competition law in particular, the CCI's Android decisions are especially instructive because the Commission expressly recognised the “positive feedback loop” connecting users, applications and the Android ecosystem.
Thus, competition analysis of reflexive infrastructures ultimately asks whether the infrastructure remains contestable—whether competitors can realistically enter, obtain users, interoperate, innovate and achieve sufficient scale—or whether control over the infrastructure is being used to prevent that competitive process.

comments