UA Ledger

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

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

Roblox used its Roblox Developer Conference on September 12 to announce "Roblox Everywhere," a plan letting creators release individual games as standalone apps on mobile, on PC, on console, with cross-play between them. No launch date came with it. The announcement is a statement of direction rather than a shipped feature, which matters for how heavily to weight it today, though the direction itself deserves attention regardless of timing.

What Roblox standalone apps change if this ships as described

Today a Roblox creator's game lives inside the Roblox app, competing for attention against every other experience on the platform but never against the wider mobile app market for a discrete install. A standalone app changes that. It gives a single Roblox game its own App Store and Play Store listing, plus an icon fighting for space on somebody's home screen. It also gives that game its own install event, which a UA team somewhere will have to buy and measure like any other app.

That is a meaningfully different competitive position than Roblox has held until now, and the platform got here by spending years pulling attention through its own discovery surface. Standalone apps drop individual Roblox titles straight into the install marketplace that mobile game publishers already fight over, carrying a built-in audience and IP recognition no new studio can match.

The context that makes this plausible

This is not a surprise pivot. Roblox updated its advertising policies in May, clarifying that content involving brand compensation or off-platform promotion counts as an advertisement. That change aimed squarely at protecting and growing sponsorship revenue as the platform matures its monetisation model. A company tightening its ad policy while also planning standalone distribution is a company behaving like a publisher with a portfolio to manage. Not a hosting service for creator content.

A measurement question nobody has answered yet

Standalone distribution also raises a question the announcement left alone: how installs and cross-play activity get attributed when the same player identity spans a Roblox-hosted experience and a standalone app of that same game. Existing mobile measurement infrastructure assumes a single app with a single install event: SKAdNetwork, AdAttributionKit, the MMP integrations stacked on top of both, none of it designed for a title that exists simultaneously inside a platform and as its own downloadable product. That is no reason to delay planning, since no standalone app exists yet to measure. It is a reason to expect the eventual rollout to arrive with its own attribution guidance, which will need reading closely rather than assuming the existing mobile playbooks carry over.

What it means for a UA team

If Roblox Everywhere ships broadly, the most successful individual Roblox games become new entrants in whatever genre category they land in on the mobile charts, arriving with a warm audience and none of the cold-start problem most new apps face. A UA team in adjacent genres, particularly anything skewing younger or casual, should treat this as a category-level risk worth monitoring. Not an immediate budget decision. There is no install event to react to yet. No app to benchmark against, and no confirmed timeline either.

The practical step available now is to work out which Roblox experiences in your competitive set look most likely to get the standalone treatment first, judging by their existing scale inside Roblox, and to flag those names to creative and bidding teams so they're watching before any of them shows up as a downloadable app. Reacting after the fact to a well-known IP arriving on the charts fully formed is a worse place to be than having mapped the candidates in advance.

Apple's Supreme Court brief, in plain language

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

Apple filed its opening merits brief with the Supreme Court on September 14 in Apple v Epic, case number 25-1311. Epic's response is due November 13, which sets the pace for the rest of the year: no ruling is coming before then, and likely not for some time after.

The Supreme Court filing, and a separate contempt motion

The next day, September 15, Apple separately asked the court to vacate the underlying contempt finding against it, arguing it never violated the text of the injunction it was found to have breached. That is a narrower, more technical argument than the headline case. The Ninth Circuit had already sent the case back to Judge Gonzalez Rogers in April specifically to determine what fees Apple can charge on external payment links, and Apple's position now is that the contempt ruling itself, the one that forced US link-out payments without commission, rested on a misreading of what the injunction actually required.

What this means in plain language

For UA and finance teams tracking the payments side of this case, the plain-language version is: nothing changes in the next few weeks. The current situation, US developers able to link out to external payment without Apple taking a commission, remains in force while the court process runs its full length into next year. Apple's petition covers a narrow procedural question about the contempt finding, not a wholesale reopening of the external-payment-link ruling, so even a win for Apple on the specific question asked would not automatically restore commission collection on those links.

The practical instruction is patience rather than contingency planning. Any product or pricing decision built around an assumption that this case resolves soon, in either direction, is building on a timeline the court has not offered.

The Epic case is also not the only fee fight Apple is managing this year. In August, Apple overhauled its EU App Store terms under the DMA, moving to a flat 5% Core Technology Commission for apps distributed outside the App Store, alongside a tiered 26%, 20% and 15% commission structure for standard listings, effective from October 1. Both changes are narrow, technical adjustments rather than a wholesale rewrite of how Apple charges developers, the same pattern showing up in the US contempt filing. Buyers running web shop or external-payment flows in both the EU and the US are managing two separate fee regimes on two separate timelines, and progress or a setback in one jurisdiction says nothing reliable about what happens in the other. Treating the two cases as a single storyline is the mistake most likely to produce a wrong assumption in a pricing model this quarter.

The Ledger #8: September so far

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

Five items from the first two weeks of September, with what each one changes for a buyer.

September so far

Savvy Games Group's chief executive, Brian Ward, stepped down on September 1. He had overseen close to $38 billion of PIF gaming investment that runs through Scopely and Niantic and into the Moonton deal that still has not closed, and PIF's Turqi Alnowaiser now runs the fund on an interim basis. Committed Q4 budgets do not change on that news. But anyone with joint planning running through Scopely or Niantic or Moonton should confirm those assumptions still hold rather than bank on continuity through a leadership change.

Pixel Gun 2 launched on September 7, six weeks later than its original date. Nobody has offered an official reason, and no performance data has surfaced yet. Watch the first weeks of live data and treat the delay as a production signal, not as a verdict on the game either way.

Roblox used its September 12 developer conference to announce Roblox Everywhere, a plan to release individual creator games as standalone apps on mobile and PC and console, with cross-play. No launch date yet. That makes it a category-risk item to track rather than an action item, because once specific Roblox titles start shipping as standalone apps they arrive as chart competitors with an audience already attached.

Apple filed its opening Supreme Court brief in Apple v Epic on September 14. A day later it separately asked the court to vacate the contempt finding tied to external payment links. Epic's response to the main brief falls due on November 13. So the link-out-without-commission arrangement holds through this filing cycle. No near-term ruling is coming.

One creative vendor's September data claims AI-UGC and creator-style ads fatigue 30 to 40% slower than studio-shot video. Worth testing against your own account before it reshapes a briefing calendar, given that the claim comes from a single vendor with no published methodology.

Roblox real-time player targeting for advertisers

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

Roblox real-time player targeting arrived this week as an expansion of the platform's first-party analytics suite, and it lands in an unusual spot in Roblox's own news cycle: three days after the platform used its Developer Conference to announce Roblox Everywhere, standalone cross-play apps that will eventually compete for install attention the way any other mobile game does. This announcement is smaller in scope. It's also more immediately useful to anyone already building on Roblox, because it changes what a creator can actually see and do with player data while a game is live, rather than describing a future distribution plan.

The update is distinct, too, from Roblox's ad-labeling policy change back in May, which clarified what counts as a disclosed advertisement on the platform. That was a rules change governing sponsored content; this is a tooling change governing how creators measure and react to player behaviour, and the two shouldn't be conflated even though both fall under Roblox's broader push to professionalise how commercial activity works on the platform.

What Roblox's real-time player targeting tools actually do

Four capabilities make up the announcement. Player segmentation now lets developers filter analytics along five dimensions (in-game activity, engagement level, platform, tenure, spending pattern), which is a meaningfully more granular slice than Roblox has previously exposed to creators building live-service experiences. A harm-detection system layered on top of experimentation provides near real-time alerts when playtime or ARPU drops below a threshold the developer sets, or when conversion rates do. It's meant to catch a bad experiment or a broken update before it does sustained damage rather than after a weekly report flags it. Real-time configuration lets developers change live settings without a server restart (difficulty tuning for newer players, say, or removing ads for paying users), collapsing what used to require a deploy cycle into an immediate toggle. And expanded performance monitoring adds custom reporting rules alongside standard technical metrics: crash rates, memory usage, CPU time, frame rate.

Roblox pointed to Adopt Me! developer Uplift Games as an existing user of these capabilities for testing new features and measuring player behaviour, though it gave no specifics on how Uplift applies the tools beyond that reference. Roblox says analytics capabilities will extend to its mobile-first Build creation tab later in 2026, alongside additional custom experiment actions. Both are promises, not shipped features.

Why this matters for a measurement-minded UA lead

The interesting part isn't any single feature. It's what the combination implies about where Roblox wants creators focused: retention and monetisation quality inside an experience, measured and adjusted continuously, rather than acquisition volume alone. A platform investing in near-real-time harm detection for playtime and ARPU drops is signalling that it expects creators to run frequent experiments and wants the tooling to catch failures fast, a meaningfully different posture from a platform focused primarily on top-of-funnel install and traffic metrics.

For a team running paid UA into Roblox experiences, or evaluating Roblox as an acquisition channel, this changes what a reasonable measurement setup looks like on the receiving end. If Roblox itself now offers granular segmentation by tenure as well as spend and platform, any UA team feeding traffic in should expect to correlate acquisition source against those same first-party segments, at least in principle, which wasn't previously as native a capability. It also raises the bar for what counts as a properly monitored live experience. A harm-detection alert on ARPU or playtime makes silent post-launch degradation harder to excuse, whether that degradation came from a bad update or from a UA push bringing in a cohort that behaves differently from your existing base.

The gap this closes relative to third-party tooling

Studios building sophisticated Roblox experiences have generally had to stitch together first-party Roblox data with external analytics platforms to get anything approaching this level of segmentation, exporting engagement data and rebuilding cohort views outside the platform because Roblox's own dashboards didn't expose the underlying dimensions natively. That workaround isn't free. Every export and reconciliation step introduces lag between when player behaviour actually shifts and when a team notices, and lag is exactly what a near real-time harm-detection alert exists to eliminate. By building segmentation and alerting into its own tooling, with live configuration alongside, Roblox isn't introducing a capability that didn't exist anywhere before; sophisticated teams already approximated most of this with third-party stacks. What it is doing is making that capability available by default to studios that lacked the resources or expertise to build the equivalent pipeline themselves, and that kind of default-availability shift tends to raise the baseline quality bar across an entire platform's catalogue over time, well beyond the studios already investing heavily in measurement.

A short setup checklist

For any team already running or planning a Roblox experience with meaningful paid traffic:

Map your existing acquisition source tagging against Roblox's new segmentation categories (tenure, platform, spend pattern, engagement level) to see whether you can already distinguish paid cohorts inside the new tooling or need additional instrumentation.
Set harm-detection thresholds on playtime and ARPU before your next UA push into an experience, not after; the value of a real-time alert depends entirely on having a baseline and threshold defined ahead of the traffic that might trigger it.
Treat the real-time configuration capability as a live-testing tool for onboarding adjustments aimed at newly acquired cohorts, given the explicit example Roblox gave of tuning difficulty for newer players without a deploy cycle.
Hold off on planning around the promised extension to the mobile-first Build tab until it actually ships. Roblox has only committed to "later in 2026" without a firm date.

Roblox Everywhere got the bigger headline from RDC, and rightly so given its longer-term implications for install competition. This tooling update is the more immediately actionable news for anyone already building revenue on the platform today, because it's live now rather than a future distribution plan still waiting on a launch date.

Puzzle ad creative after Arrows Puzzle Escape: mechanic as hook

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

Arrows Puzzle Escape overtook Block Blast! for top global downloads in May, according to Sensor Tower's monthly tracking reported in early June, in a month where ad-supported titles made up 84.1% of all downloads. Honor of Kings kept the revenue lead that month on the strength of a Ne Zha 2 crossover, but the download story belonged to a puzzle mechanic simple enough to explain in a single still frame: clear a path by sliding arrow-shaped pieces out of a grid.

That simplicity is the whole creative argument for puzzle games, and it's worth stating plainly because teams overcomplicate it so easily. A puzzle mechanic you can understand from one frame doesn't need a narrative wrapper or a character or a voiceover explaining the stakes. The mechanic is the hook.

Why mechanic-first creative keeps winning in this genre

Sensor Tower's State of Mobile report in January already flagged playables nearly doubling their creative share to 13.3%, against video's 53.7%. Puzzle sits among the genres best placed to benefit from that shift, because a playable built around a genuinely solvable mechanic gives a user something to do rather than something to watch. A five-second playable that lets someone slide one piece and see it click into place sells the core loop more honestly than any video cutaway can; the user felt the satisfaction instead of hearing about it.

Video creative for puzzle games should borrow the same discipline. The strongest puzzle ads open on the mechanic itself, mid-solve, with no scene-setting beat before it. No establishing shot. A grid already full of pieces about to resolve into place communicates the entire pitch faster than one.

Where teams get this wrong

The common failure is treating puzzle creative like it needs the narrative scaffolding a strategy or RPG ad needs: a framing device, a fabricated stakes-setup, a character reacting to the puzzle, anything except the puzzle itself. That scaffolding adds production time and dilutes the one thing puzzle creative has going for it, which is instant legibility. Two seconds. A viewer who can't tell by then what the mechanic is has already lost interest in the loop that made Arrows Puzzle Escape work.

Testing mechanic-first creative properly

Mechanic-first doesn't mean untested. The same discipline that applies to any creative portfolio still applies here: run several distinct mechanics against each other rather than assuming the mechanic already in the app is automatically the best hook. A title can have more than one puzzle mechanic worth isolating for a playable, and the strongest performer isn't always the one the core game leads with. What changes is the shape of the test. Where a strategy game might test different narrative framings of the same mechanic, a puzzle test should isolate different mechanics shown with the same plain, unadorned presentation, so the result reflects which mechanic is more compelling rather than which framing was more polished.

The operator takeaway

Building puzzle creative around the mechanic isn't a stylistic preference; it's the format matching the product. Any team briefing puzzle creative this quarter should ask a blunt question of every concept before it goes into production: does this communicate the core mechanic within the first two seconds, with no narrative device standing in front of it? If the answer is no, the concept needs a rewrite rather than a better hook line, because in this genre the mechanic and the hook are the same thing.

Google Play UK settlement: tribunal approves GBP260m

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

The Google Play UK settlement cleared its final procedural hurdle this week when the Competition Appeal Tribunal approved a 260 million pound payout, roughly 350 million dollars, resolving a collective claim over Google Play commission practices. Keep it separate from the ongoing Epic v Google saga. The two cases share a general subject, Play Store fee levels, but this settlement is a distinct UK legal action led by academic Professor Barry Rodger on behalf of app developers, not a continuation of Epic's litigation.

Of the total, 160 million pounds goes to eligible developer compensation, with the remaining 100 million covering litigation costs and legal expenses. Google made no admission of liability or wrongdoing as part of the settlement. That is standard practice in this kind of resolution, but it deserves stating plainly rather than implying the payout amounts to a finding against the company. The compensation structure reaches developers of every size (individual and small studio operators up through larger publishers) rather than weighting toward whichever claimants had the resources to litigate longest.

What the settlement actually pays for

Professor Rodger called the outcome "a historic outcome for thousands of UK app developers and for the UK's collective action regime," and that second half of the quote points to something beyond the money itself. UK collective actions, the closest domestic equivalent to a US-style class action, are a relatively young mechanism; a settlement of this size moving through the Competition Appeal Tribunal to approval is a data point about the mechanism's viability as much as about Google Play commissions specifically. Developers considering their own claims against platform commission structures now have a concrete example of a collective claim reaching a funded settlement rather than stalling in procedure.

A separate, larger claim remains unresolved. Don't conflate it with this settlement. Consumer advocate Liz Coll is pursuing a claim on behalf of an estimated 20 million UK consumers, alleging that Google passed its roughly 30% Play Store commission through to consumers as inflated prices on digital purchases made between October 2015 and July 2026. That case is opt-out, meaning covered consumers are automatically included without registering, and the trial date is October 5. Nothing about the developer settlement approved this week resolves or predicts the outcome of the consumer case, which addresses a different injured party and a different legal theory.

What changes for Play Store planning

For a UA or platform-operations lead, the direct financial impact of this settlement is small unless your studio is one of the eligible developers due compensation, in which case confirm eligibility and the claims process promptly rather than assuming compensation arrives automatically. The more useful reading is what the settlement signals about where commission pressure on Google is heading.

This is the second major UK-specific financial resolution touching Play Store economics in recent memory, alongside Google's broader commission reductions in the EU, UK and US earlier this year.
Together they point to sustained regulatory and legal pressure specifically on Google's take rate, independent of the Epic litigation track.
The unresolved consumer claim, with its October 5 trial date, is the bigger number to watch. A finding that Google's commission structure inflated consumer prices would have implications well beyond this developer settlement, potentially touching how commission costs get modelled into IAP pricing strategy industry-wide.
Treat this settlement as confirmation that UK collective actions against platform commission practices can now reach a funded resolution, which changes the calculus for any studio weighing whether pursuing a claim over historic commission charges is worth the time and legal cost.

Why the tribunal route matters for future disputes

The Competition Appeal Tribunal's role here deserves understanding beyond this one case. It is the specialist UK body that hears competition claims (collective actions included), and its approval was a necessary procedural step before the 260 million pound fund can actually reach anyone, not a rubber stamp on a deal the parties had already finalised informally. Tribunal approval typically requires the court to assess whether the settlement terms are fair and adequate for the represented class, which in this case spans developers of very different sizes with correspondingly different individual claims. That the settlement cleared this bar with a 160 million pound compensation pool against 100 million in costs is itself a data point on how UK courts are willing to size these funds relative to the underlying claim. That information will shape how any future platform-commission collective action gets structured and funded from the outset, the still-pending consumer claim included.

What this does not change

Google's current commission structure stands. The settlement addresses historic practices rather than mandating any change to current fee levels, so nothing here should feed into your Q4 or 2027 fee assumptions beyond what Google has already announced separately about its commission reductions. The settlement closes a chapter on past commission disputes; it does not open a new one about future rates.

Be clear, too, about what "eligible developer" means before assuming your studio qualifies automatically. Collective settlements of this kind typically define the compensated class by the specific period and jurisdiction the underlying claim covered, in this case UK-based developers who paid Play Store commissions during the years the claim addresses; the precise eligibility criteria and claims process usually appear separately from the headline settlement figure once the tribunal's approval becomes final. A studio that operated in the UK market during the relevant years shouldn't assume compensation arrives without checking the actual claims mechanism, and should treat any third party offering to process a claim on its behalf with the same scepticism due any unsolicited approach after a large settlement announcement.

The claim to watch for anyone planning further ahead is the consumer case set for trial in October, since a verdict there would speak directly to whether commission levels charged over the past decade were defensible at all. That question carries far more weight for how platforms price access going forward than a developer compensation fund settled without any admission of fault.

PIF EA Savvy merger report links two big spenders

UA Ledger staff

Archive: review pending. Archive date retained; first public availability is unverified. See the article for source records and review limits.

A PIF EA Savvy merger report surfaced this week, citing people familiar with the matter, and it's the kind of story that deserves scrutiny before conclusions rather than after. According to the report, Saudi Arabia's Public Investment Fund is weighing whether to combine Savvy Games Group with Electronic Arts, the publisher of console and PC franchises that PIF took private roughly a year ago. A corroborating listing appeared on a second industry outlet around the same time, but it points back to the same underlying story rather than standing as an independent second source. So, plainly: this is one report, sourced to people close to the matter, not a confirmed transaction.

If PIF really is weighing this, the logic isn't hard to follow. We covered EA's roughly $55 billion take-private buyout last September, led by PIF alongside Silver Lake and Affinity Partners, reportedly the largest leveraged buyout on record. Savvy, PIF's dedicated games investment vehicle, has spent the years since assembling one of the largest mobile portfolios in the industry: a $4.9 billion acquisition of Scopely in 2023, Scopely's own $3.5 billion purchase of Niantic's games business, a stake in Loom Games valued above $1 billion, and a pending $6 billion acquisition of Moonton, the Mobile Legends: Bang Bang developer. Reports put the value of gaming shares transferred into Savvy's structure at around $12 billion on top of those direct deals. Add EA's $55 billion price tag and PIF would be unifying two of the largest single sources of gaming acquisition spend in the world, one built on console and PC franchises, the other almost entirely mobile.

Why the timing lines up for a PIF EA Savvy merger

Two recent developments make this report land at a plausible moment rather than an arbitrary one. We wrote about Savvy chief executive Brian Ward stepping down on September 1 after overseeing roughly $37.8 billion of PIF gaming investment, with Turqi Alnowaiser, a senior PIF executive, taking the role on an interim basis. The report notes Alnowaiser helped arrange the original EA take-private deal, which gives him a specific, direct connection to both sides of a potential merger rather than a general PIF mandate. Interim periods are when reporting lines get redrawn. Restructuring an organisation in the middle of a settled executive tenure is, mechanically, the harder option.

The report also indicates the merger wouldn't proceed before Savvy completes its Moonton acquisition, which remains pending. That sequencing makes sense on its own terms. Folding an unfinished $6 billion deal into a larger corporate restructuring at the same time would complicate both processes, and PIF has generally moved its gaming acquisitions one substantial deal at a time rather than in parallel.

What remains genuinely unconfirmed

Treat everything past the fact of PIF's consideration as speculative. The report doesn't specify a deal structure. It gives no timeline and no valuation for a combined entity. It's silent on how a restructuring that folded EA into a larger PIF gaming vehicle alongside Savvy's portfolio companies would treat EA's existing minority partners (Silver Lake and Affinity Partners), and that silence matters because those partners have their own return expectations tied to EA specifically, not to a broader gaming conglomerate. Whether Scopely and Niantic and Moonton would sit inside a merged structure as distinct operating units, or fold more tightly into EA's studios, is also unaddressed; that question bears directly on anyone doing business with, or competing against, any of those studios.

What a combined entity would actually look like on paper

Sketch the shape of it anyway, purely as a hypothetical, because the scale is what makes the report notable rather than routine. EA brings console and PC franchise breadth built over decades, plus whatever mobile spin-off strategy it pursues under private ownership, a question we raised when the take-private deal closed last September without a clear answer at the time. Savvy brings Scopely's mobile publishing operation, Niantic's location-based portfolio, a pending Mobile Legends acquisition in Moonton, plus a stake in Loom Games. None of these businesses currently share reporting lines or marketing infrastructure, and as far as public information shows they have no meaningful operational overlap either. A merger report is easy to write as a headline. Executing it as an integration is much harder, and the report gives no indication PIF has resolved, or even publicly addressed, how two organisations built on almost entirely different platforms and business models would actually combine beyond sitting under the same ownership umbrella. That gap between financial consolidation and operational integration is usually where the real timeline risk in a deal like this lives, well beyond whatever headline valuation eventually gets attached to it.

What this means for a UA team watching the market

There's nothing actionable here yet. Treating rumour-stage consolidation reports as planning inputs is a common mistake, and one worth naming directly. What is worth doing:

Track this as a market-structure story, not a near-term operational one. Even confirmed mega-mergers of this scale typically take a year or more to close, and this one isn't confirmed.
If you compete for user acquisition against EA's mobile titles, Scopely's portfolio or Moonton's Mobile Legends franchise, note that a combined entity would represent an unusually large share of total mobile ad spend concentrated under one ownership structure.
Model that as a scenario, not a current reality.
Watch for confirmation or denial from EA or Savvy directly, since a report sourced to unnamed people familiar with the matter carries meaningfully less weight than a company statement either way.

Take the report seriously as a signal of where PIF's gaming strategy might be heading, given how directly its logic follows from moves the fund has already made in public. Don't take it as a fact about who will own what in mobile gaming a year from now.

UA Ledger

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

What Roblox standalone apps change if this ships as described

The context that makes this plausible

A measurement question nobody has answered yet

What it means for a UA team

Apple's Supreme Court brief, in plain language

The Supreme Court filing, and a separate contempt motion

What this means in plain language

Related archive reading

The Ledger #8: September so far

September so far

Related archive reading

Roblox real-time player targeting for advertisers

What Roblox's real-time player targeting tools actually do

Why this matters for a measurement-minded UA lead

The gap this closes relative to third-party tooling

A short setup checklist

Related archive reading

Puzzle ad creative after Arrows Puzzle Escape: mechanic as hook

Why mechanic-first creative keeps winning in this genre

Where teams get this wrong

Testing mechanic-first creative properly

The operator takeaway

Related archive reading

Google Play UK settlement: tribunal approves GBP260m

What the settlement actually pays for

What changes for Play Store planning

Why the tribunal route matters for future disputes

What this does not change

Related archive reading

PIF EA Savvy merger report links two big spenders

Why the timing lines up for a PIF EA Savvy merger

What remains genuinely unconfirmed

What a combined entity would actually look like on paper

What this means for a UA team watching the market

Related archive reading