US v. Google: Chrome's GM testified that other companies cannot develop Chrome effectively, given the browser's “interdependencies” on other parts of Google
Google is the only company that can offer the level of features and functionality that its popular Chrome web browser has today …
Context & Ripple Effects
The testimony lands in the remedies phase of US v. Google, after the DOJ's proposed Chrome sale that Google characterized as an extreme remedy and after Google tied its search position to early investment in Chrome. It makes Chrome's operational integration central to the dispute over whether separation is workable.
The case also revisits a longer-running concern: Chrome and Chromium's reach had already raised questions about Google's influence over the web's browser foundation. The evidence sharpens the distinction between open-source code availability and the ability to operate a feature-complete browser at Chrome's current level.
First-order effects
- Google gains testimony supporting its position that a Chrome divestiture could impair the browser's features and functionality because key dependencies sit elsewhere in the company.
- The court's evaluation of any Chrome-sale remedy must account for operational separation costs, not just who could acquire the browser's code or brand.
Second-order effects
- A prospective buyer or operator of Chrome would face pressure to recreate or replace Google-linked dependencies, making a sale materially more complex than a transfer of Chromium-based software.
- The testimony strengthens Google's argument that remedies should avoid breaking product integration, while giving enforcers a more specific technical claim to test against alternative remedies.
Third-order effects
- If courts increasingly treat tightly integrated consumer products as difficult to separate, antitrust remedies may shift toward conduct obligations or access requirements rather than forced divestitures.
- The dispute underscores that control of a widely used open-source browser can still concentrate platform power when the surrounding services and operating infrastructure remain proprietary.
The trend: The case is part of a broader antitrust test of whether platform integration is a genuine product dependency or a barrier that makes structural remedies harder to execute.