Aptoide antitrust lawsuit: a second Android store war

By UA Ledger staff — Archive date: 6 min read

Two storefront icons on opposite sides of a locked gate, flat editorial style

The Aptoide antitrust lawsuit against Google opens a second front in the Android app store fight, distinct from the ongoing Epic v Google case.

Aptoide, the Portugal-based alternative Android app store, has filed an antitrust lawsuit against Google, alleging what the complaint characterises as an anticompetitive chokehold over how Android apps reach users.

This is not the Epic case. The filing sits separately from Epic Games' long-running action against Google, and it arrives more than a year after the 2024 injunction in that case was meant to open Android distribution to genuine competition. Reporting available at time of writing did not make the specifics of Aptoide's claims fully accessible, so what follows describes the general shape of the dispute rather than a line-by-line account of the complaint. The framing is clear enough: Aptoide argues that the practical barriers to running a competing Android app store have not gone away just because a court ordered Google to stop some of its most direct anti-steering conduct.

Why this is a separate fight from Epic v Google

Epic's case concentrated on Google's revenue-share terms and on its restrictions on steering users toward alternative payment methods and app stores, and it produced a real remedy: the 2024 injunction, upheld through the appeals process and reinforced when the Supreme Court declined to pause it in October 2025, requires Google to allow rival app stores and alternative billing on Android in the US. That remedy addressed the legal terms of Google's dominance. It did not necessarily address every practical friction a rival store operator meets while trying to compete for users once those terms changed.

Aptoide's complaint appears to sit in that gap.

An alternative store operator's core problem is not whether Google's contracts technically permit competition; it is whether an ordinary user can find an app outside Google Play and install it without hitting friction that Google itself controls, such as the security warnings that greet a sideloaded app. Discovery mechanics favour Play by default. Developer agreements can make listing on a rival store commercially unattractive. Whether or not Aptoide's filing names any specific one of those mechanisms, that is the category of harm a chokehold claim distinct from Epic's usually describes.

The timing is not an accident

Google has spent the past several months implementing changes required by the 2024 injunction, including steps that let rival Android stores register and become more visible on Play, moves that began in earnest in late 2025. A second antitrust suit arriving now, rather than before those changes, suggests Aptoide's argument is not that Google has done nothing but that what it has done falls short of a level playing field in practice. That is a harder claim to litigate. It turns on how effective a remedy has been rather than on whether one technically exists, which is slower ground to fight on, though it is also the kind of claim that keeps regulatory and legal pressure on Google's Android distribution model long after the headline injunction looks, on paper, satisfied.

What changes for a UA team this quarter

Nothing changes today. No UA team needs to change its channel mix or its measurement setup because of a lawsuit filed this week, and the same goes for budget allocation; treating this as an urgent operational item would be overreacting to a case that will likely take months or years to produce any concrete outcome.

What the lawsuit does is add another data point to a trend worth tracking at the planning level rather than the campaign level. Android app distribution outside Google Play is becoming a more contested and more actively litigated space, not a settled one. Plenty of studios have started to think about a genuine third-party-store distribution strategy, whether that means Epic's own storefront or a smaller regional player like Aptoide. Samsung's Galaxy Store belongs on the same list. For all of them the relevant planning question is not whether Google's current terms permit that strategy today; it is whether the practical experience of sending a user down a non-Play install path is good enough yet to be worth the friction, and cases like this one are an ongoing public record of where that experience still falls short.

What to watch

Two things are worth tracking as the case develops. The first is whether Aptoide's complaint produces factual findings about specific Google practices, because those findings would be useful evidence regardless of how the case itself ends. The second is whether Google's response signals any voluntary change to sideloading or discovery friction ahead of a ruling. Companies under sustained legal pressure sometimes make practical concessions well before a court forces them to, and a second live antitrust case is exactly the kind of pressure that produces that behaviour.

Why Aptoide specifically, and why now

Aptoide is not a new or opportunistic entrant to this fight. The company has raised concerns about Google's Android distribution practices in various regulatory venues for years, predating the current wave of DMA and Epic-driven scrutiny, which makes it a credible plaintiff with a long institutional memory of exactly which practical frictions have and have not changed as Google's legal obligations shifted. That history matters for how seriously a court, or a regulator watching the case, is likely to weigh the complaint. A company that has documented the same category of friction across several distinct waves of Google policy change is harder to dismiss as reacting to a single bad quarter than a newer plaintiff would be.

Set against that, note what the case does not do.

It creates no new legal obligation for Google on its own, and it does not accelerate the timeline on which any existing obligation, from the Epic injunction or from EU-level regulatory action, gets enforced. Antitrust litigation of this kind typically moves over years rather than months, so studios building a distribution strategy around eventual third-party-store viability should plan against the slower of the timelines currently in play, not the faster one a favourable early ruling might suggest.

The broader signal for anyone planning outside Google Play

Taken together with the ongoing Epic case and Google's own gradual compliance rollout, this lawsuit reinforces a simple planning principle: Android distribution outside Google Play is trending toward more options over time, but litigation and regulatory pressure set the pace of that change, not Google's own product roadmap. A studio that wants to be ready to use a third-party store the moment one becomes genuinely competitive should keep a lightweight watch on cases like Aptoide's without over-investing in any single alternative store today, because which one, if any, ends up with the most credible user base and technical support remains an open question. This lawsuit does not resolve it.

Related archive reading

These articles provide related context and remain subject to their stated review status.

Featured

Related posts

platforms

·

1 min read

Vietnam local payment methods on a first Android test

platforms

·

1 min read

US COPPA / kids F2P: ad and store checks

platforms

·

1 min read

GRAC rating versus ad creative for Korea: operator checklist

platforms

·

2 min read

Japan store payment steering: what a game IAP screen may show

More from the Platforms desk

platforms

·

Archive date: 4 min read

Roblox Everywhere: when a platform ships standalone apps, it competes for your installs

measurement

platforms

·

2 min read

AppLovin Ad Review drops user-level journeys for aggregate-only reporting

measurement

platforms

·

2 min read

Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets

platforms

·

1 min read

DMA steering links on an EU IAP screen