A motion withdrawn, and a five-day fuse lit
On 15 July 2026, Google and Epic jointly withdrew their motion to modify the US court's injunction. A Google spokesperson, Dan Jackson, framed it as a choice to stop the clock rather than run it: the companies agreed to withdraw rather than prolong a process that creates uncertainty for the ecosystem. It reads like a truce, and in the trade press it was covered as one.
The practical effect landed elsewhere. Google's own developer notice states that if you do not choose an option, Google Play will begin to provide your app listing(s) to third-party US Android app stores starting on July 22, 2026. That is seven days from the withdrawal, and five working days for most European studios who read the headline and moved on.
The mechanism is a default, not an announcement
Why it matters: a default does not need your agreement, only your silence. Every policy change that arrives with a form to sign gets a decision. This one arrives with a settings page nobody was told to open. The distribution of your app changes because a human did not visit Play Console, and that is a category of change most owners have no process for.
Google's US policy hub page carries a last-updated stamp of 15 July 2026, the same day as the withdrawal. The notice, the fee terms and the policy hub are all Google-authored pages in the Play Console Help set. There is no ambiguity in the language and no grace period named in it.
US-only is exactly why European owners will miss it
All three Google pages say third-party US Android app stores, and that scope is the trap. An EU or UK studio reads "US" and files the story under American platform politics. But scope describes the stores, not the developers. If your app is listed for US users, your US listing is in scope, and your company is European.
Yes, but: this is not a story about damage. Opting in is reach, and reach is usually what a studio wants. The objection is narrower and harder to argue with. A change to how your product reaches its largest market should be a choice somebody made, not a deadline somebody missed.
The $5,000 and the 1% are the stores' problem, not yours
The money and the compliance burden sit on the other side of the table. Google's terms require a store seeking Play Catalog access to pay Google an upfront service fee of $5,000 to perform the necessary security and policy reviews during onboarding, and to pay that fee on an annual basis thereafter. Roughly 4,300 euros, or about 3,700 pounds, at the order of magnitude that matters here.
The same page sets a quality floor: a store must not have more than 1% of malware distribution (install attempts) over a 30-day rolling window, across all devices, globally. Read together, the two conditions describe a gate, not a free-for-all. Developers pay neither and clear neither. If you have heard that developers owe $5,000, you have heard it wrong.
Google's cut survives the change
Your unit economics with Google do not move. The notice is explicit that Google Play's service fee will continue to apply to apps downloaded in this manner. Whatever a third-party store does at its own storefront, the Play service fee follows the app.
That is what makes this a distribution decision rather than a margin decision, and it is why it deserves ten minutes rather than an afternoon. Someone in your company should open Play Console, read the Catalog Settings page, decide in or out on the merits of your US business, and record the reason. Then 22 July is a date you passed, not a date that passed you.
Read next: Brussels Just Put a Price on Google's Search Data | OnePlus Quits Europe and Kills the OS You Bought It For
