- DevelopersStrengthens legal remedies for developers through private treble-damages suits and public enforcement by federal and st…
- DevelopersMay increase competition in the app economy by reducing platform gatekeeper control, enabling alternative app stores an…
- DevelopersCould boost revenues and market access for independent app developers and smaller platforms by allowing multiple in-app…
Open App Markets Act
Read twice and referred to the Committee on the Judiciary.
This bill, titled the Open App Markets Act, targets large "covered companies" that both operate a dominant app store (over 50 million U.S. monthly users) and control the underlying operating system. It prohibits those companies from requiring developers to use their in‑app payment systems, from conditioning distribution on pricing parity, from penalizing developers for offering apps or payment alternatives elsewhere, and from using nonpublic developer data to compete against third‑party apps.
Security vs. competition: liberals and centrists see pro‑competition gains but worry about security tradeoffs from sideloading; conservatives emphasize security risks and platform autonomy.
Relative to its intended legislative type, this bill is a clearly focused substantive statute that defines covered actors and prescribes specific prohibitions and duties to reshape competitive conditions in app distribution.
This bill, titled the Open App Markets Act, targets large "covered companies" that both operate a dominant app store (over 50 million U.S. monthly users) and control the underlying operating system.
It prohibits those companies from requiring developers to use their in‑app payment systems, from conditioning distribution on pricing parity, from penalizing developers for offering apps or payment alternatives elsewhere, and from using nonpublic developer data to compete against third‑party apps.
The bill requires covered companies to permit third‑party app stores and sideloading, to allow users to set third‑party apps/app stores as defaults and to remove preinstalled apps, and to provide developers timely access to OS interfaces and documentation.
The bill is targeted and administrable in many respects and addresses a high-profile policy area with cross-ideological interest, which supports some chance of passage. However, its substantive disruption to entrenched digital-platform business models, the private triple-damages cause of action, and likely intense industry opposition make enactment challenging—particularly in the Senate where supermajority support is often required for controversial measures. The absence of a phased rollout or explicit compromise on liability increases friction.
Relative to its intended legislative type, this bill is a clearly focused substantive statute that defines covered actors and prescribes specific prohibitions and duties to reshape competitive conditions in app distribution. It pairs those obligations with strong enforcement mechanisms and a mandated multiagency review.
Security vs. competition: liberals and centrists see pro‑competition gains but worry about security tradeoffs from sideloading; conservatives emphasize security risks and platform autonomy.
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- DevelopersEnabling sideloading and third‑party app stores could increase security and malware risks for users and raise device su…
- ConsumersCovered companies may pass increased compliance, litigation, and security-mitigation costs to consumers through higher…
- Potential burdenRequirements to provide API access and equivalent terms could impose substantial technical and administrative burdens o…
Why the argument around this bill splits.
Security vs. competition: liberals and centrists see pro‑competition gains but worry about security tradeoffs from sideloading; conservatives emphasize security risks and platform autonomy.
A mainstream liberal view will likely be broadly favorable: the bill is seen as a meaningful step to curb concentrated gatekeeper power in the app economy, expand consumer choice, and protect small developers from extractive platform practices.
Supporters will highlight that enabling alternative app stores, forbidding forced use of platform payment systems, and banning the use of nonpublic developer data to compete will lower barriers and increase competition.
They will note the bill includes privacy/security carveouts, but may worry those carveouts are tightly constrained and enforcement must be robust.
A centrist/ moderate reaction will be cautiously supportive of the bill's pro‑competition goals but attentive to tradeoffs around security, litigation risk, and impacts on investment incentives.
They will appreciate the measured exceptions for security and law compliance, but will want clearer definitions and calibrated standards (for example for "unreasonably preference" and the burden of establishing a security justification).
They will emphasize staged implementation, oversight, and safeguards to limit unintended consequences for consumer safety and platform stability.
A mainstream conservative view will be skeptical and likely opposed to many provisions as undue regulatory interference that undermines property rights and platform autonomy, increases litigation risk, and threatens device security.
While some conservatives favor limiting concentrated corporate power, many will see the bill as expanding government reach into private business models and imposing compliance costs that could harm innovation.
They will be particularly concerned about sideloading mandates, forced interoperability, and the private treble‑damages right which could encourage litigation and uncertainty.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
The bill is targeted and administrable in many respects and addresses a high-profile policy area with cross-ideological interest, which supports some chance of passage. However, its substantive disruption to entrenched digital-platform business models, the private triple-damages cause of action, and likely intense industry opposition make enactment challenging—particularly in the Senate where supermajority support is often required for controversial measures. The absence of a phased rollout or explicit compromise on liability increases friction.
- Economic and budgetary effects are not quantified in the bill text (no cost estimate included), leaving uncertainty about impacts on consumers, developers, and federal enforcement resources.
- How courts would interpret and apply the statutory standards (e.g., 'unreasonably preference,' scope of 'nonpublic business information') and how frequently private suits with treble damages would be brought.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Security vs. competition: liberals and centrists see pro‑competition gains but worry about security tradeoffs from sideloading; conservativ…
The bill is targeted and administrable in many respects and addresses a high-profile policy area with cross-ideological interest, which sup…
Relative to its intended legislative type, this bill is a clearly focused substantive statute that defines covered actors and prescribes specific prohibitions and duties to reshape competitive conditions in app distribu…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.