App Ecosystem Competition Enforcement
App Ecosystem Competition Enforcement
1. Meaning
App Ecosystem Competition Enforcement refers to the application of competition law to digital ecosystems in which an operating-system provider, app-store operator, payment provider, advertising platform, cloud service, browser, or other interconnected service can influence how applications compete for users.
An app ecosystem generally contains:
mobile operating system;
app store;
app-distribution infrastructure;
payment/billing system;
developer tools and SDKs;
APIs and interoperability systems;
advertising and discovery services;
user accounts and authentication;
cloud and data services;
ranking and recommendation systems.
Competition enforcement examines whether control over one part of this ecosystem is being used to exclude competitors, disadvantage developers, restrict consumer choice, or extend market power into neighbouring markets.
2. Why App Ecosystems Create Competition Concerns
Traditional markets usually have relatively clear boundaries between suppliers and distributors.
Digital ecosystems are different.
A single company may simultaneously be:
Operating-system provider + app-store operator + payment provider + application developer + advertising provider + data controller.
This creates the possibility of vertical integration.
For example:
OS → App Store → Payment System → Developer → Consumer
If the same undertaking controls several stages, it may potentially use control at one stage to influence competition at another.
3. Main Objectives of Competition Enforcement
Competition authorities generally seek to protect:
Effective competition
Consumer choice
Innovation
Market access
Fair opportunities for developers
Interoperability
Competitive pricing
Freedom to use alternative services
Competition law does not generally require a platform to help every competitor. The legality of particular conduct depends on the applicable legal rules and evidence.
4. Relevant Markets
A central enforcement question is:
What is the relevant market?
Possible markets include:
smartphone operating systems;
mobile app distribution;
Android app stores;
iOS app distribution;
in-app payment processing;
mobile advertising;
music-streaming services;
mobile gaming;
app discovery;
digital wallets;
browser services;
cloud services.
Market definition is important because dominance can look very different depending upon how the market is defined.
5. Ecosystem Market Power
Traditional market-share analysis may be insufficient for digital ecosystems.
Authorities may also examine:
network effects;
switching costs;
installed user base;
developer dependence;
default settings;
pre-installation;
interoperability;
data advantages;
technical barriers;
ecosystem lock-in;
multi-homing.
A platform may therefore possess substantial competitive advantages even where competitors technically exist.
6. Network Effects
App ecosystems often exhibit strong indirect network effects.
Users attract developers
More users make an operating system attractive to developers.
Developers attract users
More applications make the ecosystem attractive to consumers.
This produces:
Users → Developers → Applications → More Users
The resulting feedback loop can make entry difficult.
7. Multi-Homing
Multi-homing occurs when users or developers use several platforms.
For example, a developer may distribute an application through multiple app stores.
If multi-homing is easy, market power may be weaker.
If the platform makes multi-homing difficult through:
contractual restrictions;
technical restrictions;
payment restrictions;
interoperability restrictions;
then competition authorities may examine whether those restrictions reinforce market power.
8. App-Store Access
An important enforcement issue is whether developers can access consumers through alternative distribution channels.
Potential restrictions include:
prohibition of alternative app stores;
technical blocking of third-party stores;
contractual restrictions;
restrictions on sideloading;
restrictions on linking to external websites;
restrictions on alternative payment systems.
The legal analysis depends on the jurisdiction and the specific conduct.
9. Payment-System Enforcement
App stores frequently provide integrated payment systems.
A platform may require developers to use its own billing infrastructure.
This can raise questions concerning:
tying;
exclusion of rival payment providers;
excessive commissions;
anti-steering restrictions;
foreclosure of competing payment services.
The important distinction is between legitimate payment-security requirements and restrictions that unnecessarily prevent competitive alternatives.
10. Anti-Steering Restrictions
A developer may wish to tell consumers:
“You can purchase this service directly from our website.”
An app-store operator may restrict that communication.
Such restrictions can reduce the ability of consumers to discover cheaper alternatives and can prevent developers from avoiding platform commissions.
Consequently, anti-steering provisions have become an important subject of app-ecosystem enforcement.
11. Self-Preferencing
Self-preferencing occurs where an ecosystem operator allegedly gives its own products or services preferential treatment over competing products.
Examples could include:
preferential app ranking;
privileged access to APIs;
better default placement;
preferential recommendations;
superior technical functionality;
access to platform data unavailable to competitors.
The legal question is whether the conduct constitutes prohibited exclusionary behaviour under the applicable law.
12. Tying
Tying may occur when access to one service is conditioned upon acceptance or use of another service.
For example:
App distribution → compulsory use of a particular payment service.
or:
Operating-system access → mandatory installation or use of another service.
Competition authorities examine whether the arrangement forecloses competitors or otherwise harms competition.
13. Interoperability
Interoperability is particularly important in app ecosystems.
A platform may control:
APIs;
messaging interfaces;
device functionality;
authentication;
payment interfaces;
operating-system functions.
A refusal or restriction of interoperability can become legally significant where it substantially restricts competition and satisfies the relevant legal test.
14. Refusal to Deal and Essential Infrastructure
One of the classic competition-law problems is refusal to provide access to infrastructure.
The important EU authority is Bronner v Mediaprint.
The essential-facility doctrine is applied cautiously.
Generally relevant questions include:
Is access indispensable?
Is there a realistic substitute?
Is duplication possible?
Would refusal eliminate effective competition?
Is there an objective justification?
The fact that infrastructure is commercially important does not automatically create an obligation to provide access.
15. App Ecosystem Lock-In
Lock-in can arise from:
purchased applications;
subscriptions;
user accounts;
cloud storage;
device-specific data;
loyalty programmes;
developer investments;
proprietary APIs;
platform-specific software.
High switching costs may reduce competitive pressure.
Competition enforcement may therefore examine whether the platform deliberately increases switching costs or prevents consumers and developers from moving to competing ecosystems.
16. Data Advantage
App ecosystems generate valuable information concerning:
downloads;
searches;
purchases;
application usage;
subscriptions;
advertising;
consumer preferences.
If an ecosystem operator uses this information to compete against developers that depend on the platform, competition concerns may arise.
The analysis can overlap with:
competition law;
data protection law;
consumer law;
digital-market regulation.
17. Important Case Laws
Case 1: Epic Games, Inc. v Apple Inc.
This U.S. litigation concerned Apple's App Store system and Fortnite's alternative payment mechanism.
Major issues included:
App Store distribution;
mandatory payment arrangements;
commissions;
anti-steering restrictions;
competition between distribution channels.
The court did not treat every Apple restriction as an antitrust violation, but it found the anti-steering provision unlawful under the relevant California law.
Significance
The case demonstrates that contractual control over app distribution and payment can generate both antitrust and consumer/competition-related litigation.
18. Epic Games v Google
Epic's litigation against Google concerned Google Play and Android's app-distribution and billing arrangements.
The case examined allegations concerning:
Google Play;
alternative app stores;
payment systems;
developer agreements;
distribution restrictions;
incentives involving manufacturers and developers.
A U.S. jury found Google liable on Epic's principal antitrust claims.
Significance
The case illustrates how agreements surrounding app distribution can potentially affect competing app stores and payment systems.
19. European Commission — Google Android
The European Commission's Android decision concerned Google's conduct involving the Android ecosystem.
The Commission examined, among other matters:
tying of Google Search and Google Chrome;
licensing arrangements;
restrictions affecting Android variants;
practices affecting competing search services.
The Commission concluded that several practices infringed EU competition law.
Significance
The decision demonstrates how an operating system can operate as a strategic gateway into neighbouring digital markets.
20. Google Shopping — Google LLC v European Commission
Google Shopping concerned Google's treatment of its own comparison-shopping service in search results.
Although it was not principally an app-store case, it is highly relevant to app ecosystems because it addresses the broader issue of self-preferencing by a dominant digital platform.
The EU courts upheld the finding of an abuse of dominant position.
Significance
A platform controlling an important digital gateway may face competition scrutiny when it systematically gives preferential treatment to its own downstream service.
21. Microsoft v Commission
Microsoft Corp. v Commission, T-201/04, concerned Microsoft's conduct involving interoperability information and the integration of Windows Media Player.
The case addressed:
interoperability;
refusal to supply;
tying;
leveraging of operating-system dominance.
The EU General Court largely upheld the Commission's approach.
Significance for app ecosystems
It demonstrates how control over an operating-system layer can potentially be leveraged into adjacent software markets.
22. Bronner v Mediaprint
Oscar Bronner GmbH & Co. KG v Mediaprint, C-7/97, is one of the leading EU authorities concerning refusal of access to infrastructure.
The Court adopted a demanding test for compulsory access.
Significance
For app ecosystems, it helps explain why:
“This infrastructure is important” ≠ “competitors automatically have a legal right to access it.”
Indispensability and other stringent conditions remain important.
23. IMS Health v NDC Health
IMS Health GmbH & Co. OHG v NDC Health GmbH & Co. KG, C-418/01, concerned access to a copyrighted structure used in pharmaceutical sales information.
The Court considered when refusal to license intellectual-property-related infrastructure can amount to an abuse.
Significance
The case is relevant to app ecosystems because digital infrastructure can simultaneously involve:
intellectual property;
proprietary technology;
data;
interoperability;
network effects.
24. Slovak Telekom v European Commission
Slovak Telekom a.s. v European Commission, C-165/19 P, concerned exclusionary conduct involving telecommunications infrastructure.
The Court addressed the relationship between refusal-to-supply principles and Article 102 TFEU.
Significance
The case helps establish that competition enforcement must carefully distinguish between:
ordinary commercial decisions;
refusal to supply;
exclusionary infrastructure conduct.
25. Qualcomm v Commission
Qualcomm Inc. v European Commission, T-235/18, concerned alleged exclusionary payments in the semiconductor market.
Although not an app-store case, it is relevant to ecosystem enforcement because components and technology suppliers can influence competitive conditions throughout interconnected digital markets.
Significance
Competition enforcement can examine contractual incentives and payments where they may foreclose rivals.
26. Epic Cases and the Concept of Platform Gatekeeping
The Epic litigation is particularly significant because app-store operators can act simultaneously as:
marketplace;
distributor;
payment intermediary;
rule-maker;
technical gatekeeper;
competitor.
This creates a potential conflict of economic roles.
For example:
Platform operates marketplace + platform sells competing application.
The competition-law question is whether the platform's rules unfairly advantage its own service or otherwise exclude rivals.
27. Digital Markets Act
European enforcement has increasingly moved from exclusively ex post competition law toward ex ante regulation.
The EU Digital Markets Act identifies certain large digital services as subject to specific obligations.
For app ecosystems, important areas include:
alternative app distribution;
alternative payment mechanisms;
interoperability;
anti-steering;
user choice;
data use;
restrictions on combining certain data;
business-user access.
The DMA therefore supplements traditional Article 101 and Article 102 TFEU enforcement.
28. Ex Ante vs Ex Post Enforcement
| Ex post competition law | Ex ante digital regulation |
|---|---|
| Investigates suspected conduct | Establishes predefined obligations |
| Often requires market analysis | Applies specified gatekeeper rules |
| Focuses on particular abuse | Seeks to prevent certain practices |
| Article 102 TFEU | Digital Markets Act |
| Effects may need detailed assessment | Certain conduct prohibited/regulated in advance |
Both approaches can operate simultaneously.
29. Enforcement Challenges
A. Rapid technological change
Technology can change faster than litigation.
B. Market definition
It can be difficult to determine whether the relevant market is:
app stores;
mobile ecosystems;
payment services;
operating systems;
broader digital services.
C. Free services
Many ecosystem services are provided without direct monetary charges.
Traditional price-based analysis therefore becomes less informative.
D. Network effects
Market power can arise from ecosystem scale.
E. Security justifications
Platforms can argue that restrictions protect:
privacy;
cybersecurity;
fraud prevention;
consumer safety.
Authorities must distinguish legitimate security measures from unnecessary competitive restrictions.
30. Security vs Competition
This is one of the most important issues.
Platform argument
Alternative app distribution increases malware, fraud and privacy risks.
Competition concern
Security requirements may be designed or applied in a way that unnecessarily prevents competing distribution channels.
A proper legal assessment therefore examines:
whether the risk is genuine;
whether the restriction addresses that risk;
whether less restrictive alternatives exist;
whether the rule is applied consistently.
31. Remedies
Competition authorities and courts may consider several forms of remedies.
Behavioral remedies
permitting alternative payments;
allowing external links;
prohibiting discriminatory treatment;
requiring interoperability;
modifying developer agreements.
Financial remedies
fines;
damages;
restitution.
Structural remedies
In exceptional circumstances, structural separation may be considered.
Regulatory monitoring
Digital-market regulation may require continuing compliance and reporting.
32. Civil-Law Dimension
App ecosystem disputes can also generate private-law claims.
Developers may claim:
breach of contract;
wrongful suspension;
wrongful termination;
unpaid revenues;
damages;
unfair contractual treatment;
intellectual-property violations.
Competition-law findings may sometimes support follow-on private litigation, depending on the jurisdiction.
33. Future Competition Issues
Emerging app ecosystems may involve:
AI app stores
AI systems may determine which applications users see.
AI assistants
An AI assistant may become a new distribution gateway, recommending applications instead of traditional app-store search.
Super-apps
One platform may combine:
payments;
messaging;
commerce;
applications;
financial services.
Spatial computing
AR/VR operating systems may create new distribution bottlenecks.
Autonomous devices
Cars, robots and smart appliances may develop their own app ecosystems.
Decentralized applications
Blockchain-based distribution may challenge centralized app-store models.
34. Six-Case-Law Revision Table
| Case | Main issue | Key significance |
|---|---|---|
| Epic Games v Apple | App Store/payment/anti-steering | Platform rules and external payment communication |
| Epic Games v Google | Google Play/payment/distribution | Competition between app stores and billing systems |
| Google Android | Android ecosystem/tying | OS power can affect neighbouring markets |
| Google Shopping | Self-preferencing | Digital gateway and downstream competition |
| Microsoft v Commission | Interoperability/tying | OS control can affect adjacent markets |
| Bronner v Mediaprint | Essential infrastructure | High threshold for compulsory access |
| IMS Health v NDC Health | IP/infrastructure access | Exceptional circumstances for compulsory licensing |
| Slovak Telekom | Infrastructure exclusion | Framework for refusal-to-supply analysis |
35. Conclusion
App Ecosystem Competition Enforcement concerns the use of competition law and digital-market regulation to preserve competitive conditions within interconnected app ecosystems.
The principal enforcement concerns are:
Market power → App-store control → Payment control → Anti-steering → Self-preferencing → Tying → Interoperability → Alternative distribution → Data advantages → Lock-in.
The central legal challenge is to balance legitimate platform governance and security against conduct that may unnecessarily restrict competition.
The leading authorities—Epic Games v Apple, Epic Games v Google, Google Android, Google Shopping, Microsoft, Bronner, IMS Health and Slovak Telekom—provide different pieces of the legal framework for analyzing digital gatekeeping, infrastructure access, interoperability, tying and exclusionary conduct.

comments