The Antitrust Attorney Blog
Author: Luis Blanquez
The class chapters of the Google Play fight are closing. A federal court gave final approval in 2026 to the $700 million settlement resolving the claims of consumers and a coalition of state attorneys general. Small app developers took $90 million in an earlier class settlement. Google’s conduct has been found illegal and the finding has been affirmed on appeal.
But look at who is not in those cases. Epic Games took its case to a jury and won a monopolization verdict. Match Group settled its own claims on the eve of trial. Neither rode a class. Both pursued their own direct actions—and both did so because the developers with the most at stake often recover more on their own than they do as a line item in a class fund.
What the class settlements actually cover
Three tracks ran through the same multidistrict litigation before Judge James Donato in the Northern District of California. The consumer and state track produced the $700 million settlement. An earlier developer class settled for $90 million, but that class reached only small developers—those earning roughly $2 million a year or less through Google Play. The largest developers were never in it. And Epic and Match brought and controlled their own direct claims.
The theory across all of them was the same one Epic proved at trial: Google holds monopoly power over Android app distribution and in-app payments, and it used contractual and technical restraints to keep its commission—up to 30% on every transaction—flowing. A jury agreed. The Ninth Circuit affirmed the verdict and the injunction, and the Supreme Court declined to stay it. The remedy fight is over too: Epic and Google finalized their settlement in March 2026, the 30% commission is dead, and Google’s Supreme Court petition was dismissed—so the liability finding is not just affirmed but final.
That is the backdrop a developer should weigh. The unlawful conduct is established, but the overcharge—your commissions above what a competitive market would have charged—is different for each developer.
Two ways to be a direct-action plaintiff
In the U.S. system, a damages class under Rule 23(b)(3) sweeps in everyone it defines unless a member affirmatively excludes itself. That produces two routes to a direct claim, and the difference decides what clock you are on.
The first is the true opt-out: a developer that was a class member and affirmatively excluded itself before the class’s opt-out deadline, preserving its own claim to litigate directly. If you miss that deadline, you are bound by the class result and the release that comes with it. In the Play Store developer class (those earning less than $2 million a year through Google Play), that exclusion deadline has already passed, and the developers who stayed in gave up their claims for the covered period.
The second route is larger and, for these purposes, better positioned: developers the class never covered at all. The developer settlement reached only smaller developers. Any developer above that ceiling was carved out by definition. It was never a class member, never released anything, and had no opt-out deadline to miss. Its claim is still live today, subject to the statute of limitations. If you moved serious volume through Google Play, you are probably in this second group—and may not realize your claim is still potentially available.
Either way, the reason to go direct is the same. A class settlement divides a compromised, discounted pool across the entire class. A direct action seeks your damages, and antitrust damages are trebled by statute. A developer whose overcharge—the commission above a competitive rate, not the whole fee—ran to, say, $20 million is looking at serious claim, especially considering trebling available under the antitrust laws. Going direct also buys control: your own counsel, your own theory of overcharge, your own experts, your own timing, and a settlement posture that reflects your leverage rather than the class’s average. Epic and Match did not litigate separately for sport. They did it because their damages justified it and the class may have left much of their recovery on the table.
Of course, there are downsides to bringing your own claim, as you have to actually litigate an antitrust case.
For a similar situation, you might read our article about companies considering direct actions in the Google Search monopolization cases.
Who qualifies, and the deadline you may be facing
The plaintiffs this analysis is built for share a profile: a business that distributed a paid app, a game, or a subscription service through Google Play and paid substantial commissions on its in-app transactions. Gaming studios, subscription and SaaS developers, and any company that moved real volume through Google’s billing system carried the overcharge the Epic jury found unlawful. If your Play Store payments ran into the millions, you are the kind of plaintiff a direct action is designed for—and, in all likelihood, you were above the developer class’s revenue ceiling and never bound by its release in the first place.
The deadline that governs that second group is not a class notice date. It is the antitrust statute of limitations—four years. It runs on a rolling basis. Because Google collected its commission continuously, each overcharge starts its own four-year clock, so a claim filed today reaches back four years automatically, and tolling doctrines may extend the reach further. The practical consequence is a window that is closing quietly. Every month that passes drops another month of recoverable damages off the far end, and the largest and oldest overcharges are the first to expire. Whether tolling extends your reach, and how far, is a fact-specific question—one worth answering before more of the claim ages out.
For a developer that was inside the class and let the opt-out deadline pass, the picture is different and harder: the release likely reached your claims for the covered period. That is precisely why the distinction matters, and why the first step is always the same—determine which group you are in before you assume the door is closed.
Why the timing favors a direct claim now
A direct action is most attractive when someone else has already borne the cost and risk of proving liability. That is exactly the position Google’s conduct is in.
Epic tried the case and won. The verdict and injunction were affirmed on appeal. A direct plaintiff today inherits a public trial record, a proven theory of harm, and a monopoly finding that has cleared the Ninth Circuit—a real head start on the hardest and most expensive part of an antitrust case. In the right posture, that affirmed finding can support offensive issue preclusion, sparing a direct plaintiff from re-proving what Epic already established. That argument is fact-specific, a court retains discretion over it, and Google will contest it—but even where preclusion is not available, the evidentiary roadmap and the affirmed liability finding cut litigation risk and cost.
There is also a structural advantage: Developers pay Google’s commission directly, which makes them direct purchasers of Google’s distribution and payment services. That forecloses a potential defense argument that the developer simply passed the overcharge on to consumers—a defense the Supreme Court has long barred against direct purchasers. The combination of an affirmed liability finding, a direct-purchaser posture, and treble damages is a substantial starting point for an antitrust plaintiff.
The questions to answer before you commit
A direct action is not free and is not for everyone. Bona Law can help you answer the three questions below that determine whether this makes sense for your company.
- Did you release your claims? If you were a member of a class that settled and you did not opt out in time, you likely gave up the claims that settlement covered, for the period and conduct it covered. If you were above the class’s revenue ceiling, you released nothing. Which situation you are in is the first thing to check, and it is fact-specific.
- Are your damages large enough? A direct action makes economic sense above a threshold—meaningful commission payments over the relevant years, capable of documentation. Trebling helps, but the case has to be worth building.
- Can you commit to it? A direct action is your case to run. It takes management attention and a tolerance for litigation that a claim form does not. For a developer carrying a real overcharge, that investment is usually dwarfed by the difference between a class share and a trebled direct recovery.
The bottom line
The $700 million settlement is just a headline. For most consumers it is also the right outcome—their individual harm was small, and a class is how small harms get redressed. But a class is a blunt instrument, built for the average member, not the one who paid the most. The developers Google overcharged the hardest are precisely the ones a class serves least well—and here, the ones a class never covered at all.
Google’s liability has been proven and affirmed. The overcharge is measurable. The clock, for those who were never bound, is the statute of limitations, and it is running.
Bona Law represents opt-out and direct-action plaintiffs, not classes, in antitrust matters. If you paid Google significant Play Store commissions and want to know whether a direct claim beats the class recovery—and how much of it is still in time—we are glad to run that analysis with you. This post is attorney thought leadership, not legal advice; whether you hold a viable claim depends on your facts, and no result is ever guaranteed.