The United States should require Google Play to carry rival Android app stores.

PRO — Opening · Champ (tencent/hy3:free)

The United States should require Google Play to carry rival Android app stores because a federal court found Google unlawfully monopolized Android app distribution and billing, and placement inside Play is the only remedy that gives competitors a realistic path to users. The Ninth Circuit affirmed the jury verdict that Google willfully maintained monopoly power in both markets and upheld the permanent injunction as supported by those findings (packet article 4). The trial record shows why softer alternatives fail: most Android users get software through Play, so a rival store forced to rely on sideloading faces a fatal network-effect disadvantage, and the court viewed in-Play placement as the necessary correction (packet article 1). Google’s own withdrawn settlement would have restored only a sideloading-based “Registered App Store” model, which leaves rivals dependent on the very network effects the monopoly created (packet article 2, article 5). Requiring carriage is therefore not a speculative intervention but the judicially endorsed, proportionate response to proven antitrust harm.

The operational details confirm the requirement is workable and safe rather than a chaotic free-for-all. Under the injunction Google will distribute rival stores through Play starting July 22, 2026, with access to the full catalogue by default subject to developer opt-out, and may charge only a reasonable $5,000 annual fee for security review (packet article 1, article 3). Approved stores must block malware, respect IP, and allow updates and uninstalls, and lose access if over 1% of installs are malicious (packet article 1, article 2). Google’s own policy page frames this as compliance with the upheld injunction and runs it through its eligibility systems (packet article 3), so the security objection is met by conditions the parties already accept.

Finally, the requirement advances consumer choice and developer opportunity without destroying Android’s model. The Verge records Google itself portraying the change as pursuing greater choice, lower prices, and developer opportunity while maintaining security (packet article 2). Because the appellate court rejected Google’s market arguments and upheld the remedy, the terms of this debate should be: given proven monopoly conduct, is in-Play carriage the effective and bounded remedy the court found it to be? The packet answers yes — and the United States should therefore require it.

CON — Opening · Challenger (xiaomi/mimo-v2.5)

The United States should not require Google Play to carry rival Android app stores. The motion asks whether this is good policy, and the packet answers no — the remedy is legally extraordinary, practically uncertain, and security-jeopardizing, while less coercive alternatives already exist.

Start with the most damaging admission in the packet, which my opponent’s own case cannot escape: even after the injunction takes effect, the economics of app distribution and billing remain “unsettled” and the remedy may only create “a formal route to competition without guaranteeing prominent placement, viable business models, or a uniform global system” (packet article 2). This is not the confident cure the pro side described. The United States should not mandate a structural overhaul of the world’s largest mobile marketplace on a theory that the court itself acknowledges may produce no meaningful competitive gain. The Ninth Circuit opinion upholds the injunction as a response to found monopoly conduct, but the opinion makes clear this is “an extraordinary response to findings about particular conduct and markets” and “does not establish that every compelled-distribution rule is automatically beneficial, nor does it eliminate the need to weigh security, implementation, and proportionality” (packet article 4). The motion asks whether the US should require carriage; the court says proportionality must be weighed, and the packet shows it hasn’t been.

Third, the security architecture is weaker than the pro side claims. Approved stores must block malware and are removed if more than 1% of attempted installs appear malicious (packet article 1, article 2). But this threshold is a blunt instrument: a store could expose millions of users to malware before hitting 1%. The entire program is brand-new, launches in days, and leaves the question of “whether additional requirements will apply to storefront distribution” unresolved (packet article 1). Google’s own policy page shows this is US-specific, opt-out-based, and mediated through Google’s eligibility systems (packet article 3) — but none of this means the system is ready. Requiring carriage now, before the security model is proven, is an unnecessary risk. The Registered App Stores program, which the packet describes as an alternative global approach offering “quality and safety benchmarks, with a simpler installation experience” (packet article 5), achieves competition goals without forcing Google to embed untested rivals directly into the primary storefront used by hundreds of millions of people.

Fourth, the pro side frames carriage as the only way to give competitors access to users (packet article 1). But the packet itself notes the Registered App Stores program allows stores outside the programme to be “installable through the existing flow” (article 5). That means competition does not require embedded carriage — it already exists through installation paths the pro side dismisses as insufficient. The question is whether the state should compel a private platform to feature its competitors, and the answer is no when viable alternatives are available and the mandated remedy’s own outcomes are uncertain.

The US should reject this motion. The court-ordered remedy is an extraordinary measure responsive to specific findings of monopoly conduct; it is not a model general policy. The economics are unresolved, the security model is untested, and less coercive alternatives exist. Mandating carriage of rival stores inside Google Play is not the proportionate, effective policy the pro side claims. It is a sledgehammer where a scalpel will do.

PRO — Rebuttal · Champ (tencent/hy3:free)

My opponent’s weakest move is their reliance on article 2’s “unsettled” language to claim the remedy may produce no meaningful gain. Article 2 says the economics of distribution and billing “remain unsettled” and the remedy may not guarantee “prominent placement, viable business models, or a uniform global system” — but it does not say the remedy fails to create competition. It says the opposite: the injunction “may create a formal route to competition” (packet article 2). A route that exists is the realistic chance the court found lacking under sideloading alone (packet article 1). My opponent conflates “not guaranteed to be prominent” with “no competitive gain,” which the source does not support.

They also stretch article 4. They cite it for the proposition that “proportionality must be weighed, and the packet shows it hasn’t been.” But article 4 says the Ninth Circuit upheld the injunction as “supported by the verdict and the district court’s findings” and rejected Google’s arguments against the remedy (packet article 4). The court itself did the proportionality weighing and affirmed it. The article’s caveat that the remedy is “extraordinary” and doesn’t establish “every compelled-distribution rule is automatically beneficial” is about future cases, not this one — it does not say this injunction was disproportionate. My opponent imports a generic warning as a finding against the specific order.

Their security objection is overclaim. They say a store could “expose millions to malware before hitting 1%,” but the packet states stores “can be removed if more than 1% of attempted installs appear to be malware or unwanted software” and must “block malware” as a condition of approval (packet article 1, article 2). That is a binding ex-ante condition plus a removal trigger, not a free pass. They call the model “untested” and “brand-new,” but Google’s own policy page shows the program is built on the upheld injunction and Google’s existing eligibility systems, with developer opt-out and $5,000 security review (packet article 3) — a mediated, not chaotic, rollout.

Their alternatives argument fails on the packet’s own terms. They cite article 5 that stores outside the Registered program are “installable through the existing flow” — but article 5 also says that flow is sideloading, and article 1 records the court’s finding that sideloading leaves rivals with a “network-effect disadvantage” because most users get apps through Play. Article 5 explicitly notes the counterargument: softer reforms “leave rivals dependent on sideloading and Google’s existing network effects” (packet article 5). My opponent presents the existing flow as sufficient while the packet says it is the very mechanism of monopoly retention.

Pressing my side: the motion is whether the US should require carriage, and the packet shows a court of appeals already found Google willfully monopolized these markets and upheld in-Play carriage as the remedy (packet article 4, article 1). Google’s withdrawn settlement would have replaced that with sideloading-based registration (packet article 2, 5) — the model the court rejected as inadequate. Requiring carriage is thus not a sledgehammer; it is the judicially endorsed correction to proven harm, bounded by security conditions and a nominal fee (packet article 1, 3). The con side offers no evidence that sideloading alternatives work; the packet says they don’t.

CON — Rebuttal · Challenger (xiaomi/mimo-v2.5)

The PRO’s rebuttal overclaims on three fronts and leaves its core vulnerability untouched.

First, they invent a distinction between the CON’s reading of article 4 and the packet’s actual text. They say the court’s caveat—that the remedy “does not establish that every compelled-distribution rule is automatically beneficial, nor does it eliminate the need to weigh security, implementation, and proportionality” (article 4)—is “about future cases, not this one.” But read the sentence again: it says the panel opinion does not eliminate the need to weigh those factors. That is in the opinion itself, about this injunction, not a hypothetical for future litigants. The PRO treats a court’s own instruction to continue weighing security, implementation, and proportionality as dead language, then claims the court already did the weighing. It didn’t—it upheld the injunction as legally supported by the verdict, which is a different standard from declaring the policy wise. The motion asks whether the United States should require this; the court says proportionality remains an open question. The PRO has not answered it.

Second, they claim the CON’s alternatives argument fails on the packet’s terms, but they misread article 5 along the way. The PRO says the “existing flow” and sideloading are “the very mechanism of monopoly retention.” But article 5 describes the Registered App Stores program as having “quality and safety benchmarks, with a simpler installation experience” (article 5)—that is not raw sideloading. It is a structured, quality-controlled alternative the PRO simply ignores. Article 2 further notes that the proposed settlement would have relied on “developer payment and distribution flexibility”—another less coercive path (article 5). The PRO frames the choice as “carriage or sideloading” when the packet describes a third option: a registration system with quality benchmarks and simpler installation. The court’s finding that sideloading is insufficient does not foreclose this middle ground, and the PRO offers no reason it shouldn’t work.

Third, they dismiss the economics concern by saying the remedy may “create a formal route to competition.” A “formal route” with no guarantee of “prominent placement, viable business models, or a uniform global system” (article 2) is not the cure the PRO promised. It is an admission that the competition may remain theoretical—that users may never encounter rival stores, developers may never profit, and the system may not even apply outside the US. The PRO’s own citation undermines their confidence: they say “a route that exists is the realistic chance the court found lacking,” but the packet says that route carries no guarantee it works. Why should the United States mandate a structural overhaul of the platform that powers hundreds of millions of devices on a Maybes-ton of uncertain outcomes?

Finally, the PRO’s security argument remains the thinnest. They say the 1% threshold is a “binding ex-ante condition plus a removal trigger.” But a trigger fires after damage is done: 1% of installs in a store with millions of users is still thousands of compromised devices. The PRO calls the model “mediated, not chaotic”—but article 1 says it is “unclear whether additional requirements will apply to storefront distribution.” The program launches in days, with unresolved questions. The CON’s argument is not that the program is chaotic; it is that requiring it before these questions are resolved is premature and disproportionate as a matter of policy.

The PRO ties everything to the court: Google was found to have monopolized, so the court’s remedy is the answer. But the motion is not about whether the court was justified; it is about whether the United States should adopt this as a requirement. The court itself says proportionality, security, and implementation must still be weighed. The PRO has not weighed them. They have simply said the court ordered it and it is therefore good policy. That is not an argument; it is an appeal to authority over discretion, while the packet itself shows the outcomes are uncertain, the alternatives exist, and the security model is unfinished.

PRO — Closing · Champ (tencent/hy3:free)

The con side never displaced the central fact in the packet: a federal jury found Google willfully monopolized Android app distribution and billing, and the Ninth Circuit affirmed that verdict and the injunction requiring in-Play carriage as supported by the district court’s findings (packet article 4). The con’s claim that proportionality “remains an open question” misreads article 4 — the opinion says the remedy is extraordinary and doesn’t bless every such rule, but it explicitly upheld this injunction after rejecting Google’s arguments, so the weighing was done for this case, not deferred. Their alternatives argument collapsed on the packet’s own text: they pitched the Registered App Stores program as a quality-controlled “middle ground,” but article 5 states that program is sideloading-based outside the US and explicitly notes softer reforms “leave rivals dependent on sideloading and Google’s existing network effects” — the exact disadvantage the court found fatal (packet article 1, 5). The con’s “unsettled economics” point concedes the injunction “may create a formal route to competition” (packet article 2); a route inside Play is the realistic chance the court said sideloading denied, not a meaningless gesture. Their security scare — millions exposed before a 1% malware trigger — ignores that approved stores must block malware ex ante and are removed above 1% unwanted installs, under Google’s eligibility systems with a $5,000 review (packet article 1, 3), and article 1’s “unclear” footnote is about global program differences, not US safety failure.

My points all survived: monopoly proven and remedy affirmed; in-Play placement is the only judged-effective correction to network-effect lockout; operational terms are bounded, opt-out, and security-conditioned. Theirs did not: the authority they cited supports me, their alternative is the rejected sideloading model, and their uncertainty claim is a conceded route to competition.

The strongest version of the case is this — the United States should require Google Play to carry rival stores because the packet shows a court of appeals upheld a finding of willful monopoly and a remedy of in-Play carriage as the proportionate fix to a proven network-effect barrier, with the rollout mediated by Google’s own $5,000 security-reviewed, opt-out catalog program (packet article 1, 3, 4); the con offers only the sideloading alternative the packet says preserves Google’s monopoly, and no evidence it works. Requiring carriage is the judicially endorsed, bounded response to found harm — not a sledgehammer, but the key the court said competition needs.

CON — Closing · Challenger (xiaomi/mimo-v2.5)

The pro side rested their entire case on an appeal to the court’s authority, and the packet undercut it at every turn.

Their central claim was that proportionality was settled by the Ninth Circuit. But article 4 says the opinion “does not eliminate the need to weigh security, implementation, and proportionality” — about this injunction, not hypothetically. The court upheld legal sufficiency; it did not declare the policy wise. The pro side never engaged with that distinction because they cannot: the packet tells us the economics “remain unsettled” and the remedy may produce only “a formal route to competition” without “viable business models” (article 2). They conceded this by calling a route that “exists” sufficient — but the packet says a formal route with no guarantee of viability is not the realistic chance the court demanded. That is their own citation conceding the core uncertainty.

Their alternatives argument failed because they mislabeled the middle ground. They repeatedly called the Registered App Stores program “sideloading” and said the packet rejects it. But article 5 describes that program as having “quality and safety benchmarks, with a simpler installation experience” — a structured, quality-controlled path. Article 5 also notes the settlement would have relied on “developer payment and distribution flexibility.” The pro side presented a binary — embedded carriage or monopoly-preserving sideloading — when the packet describes at least two intermediate options they never substantively addressed. They simply asserted those options don’t work while the packet describes them as operational and quality-controlled.

Their security defense collapsed under scrutiny. They repeated that the 1% malware trigger and $5,000 review constitute ex-ante protection. But a trigger fires after harm: 1% of millions of installs is thousands of compromised devices. Article 1 says it remains “unclear whether additional requirements will apply to storefront distribution” and the program launches with unresolved details. Requiring carriage before the security architecture is finished is the definition of premature.

The con case was never that Google should be permitted to monopolize — the jury verdict stands. It was that mandating embedded carriage of competitors inside a platform serving hundreds of millions of users is a disproportionate policy response when the outcomes are uncertain, the economics are unsettled, the security model is unfinished, and structured alternatives exist. The pro side never weighed those costs. They said the court ordered it and therefore it is sufficient. That is not a policy argument. It is a compliance report.

The United States should not require Google Play to carry rival app stores.