In 2002, Electronic Arts banned ICQ — the office chat app — and put a single internet terminal in the center of the building. A programmer named Steve Ganem responded with what he calls “civil disobedience”: he built his own LAN chat program, taught himself network programming, and parlayed that into the job that made him the sole engineer behind the first PlayStation 2 online game — Tony Hawk’s Pro Skater 3.
Two decades later, Ganem is VP of Product at Unity, and he’s doing roughly the same thing: building the infrastructure that lets people connect directly, bypassing the platform sitting in the middle. This time, the platforms are Apple and Google. This time, the connection is between game developers and their players. And this time, it’s legal.
---
Unity’s IAP SDK 5.4 went generally available on June 30th. It lets any Unity game developer sell directly to players — in-game via a web payment flow, or through a hosted webshop — without routing every purchase through the App Store or Google Play. The webshop is free to set up and free to operate. Unity charges nothing. You pay only Stripe or Coda, whichever payment processor you choose.
That “zero” is the most important number in this announcement. Not because free is surprising — plenty of tools are free. But because this free is doing something specific and strategic that’s worth understanding before you decide whether to build on it.
The guy who earned the right to sell this
Before the analysis, the biography — because it’s why this product exists the way it does.
Ganem spent 19 years in the games industry before leaving it. He was at EA, at Activision on the Tony Hawk franchise, and then co-founded his own studio. It was during that studio’s 11-year run that the entire business model collapsed and was rebuilt.
“Going from launching a game and having it be $50, $60... switching from that to being free to play and having to convince users to part with their money was extremely hard,” he told me. “And a lot of game studios didn’t make that transition.”
His studio had some hits and some misses. Ultimately, it was one of the reasons he exited the games industry entirely. He went to Google for a decade — specifically to Google Analytics — not because he was done with games but because he had a hypothesis: the data developers were collecting could be super powerful, not just for insights but for improving their marketing ROI.
When the Unity role came up, it was, in his words, “the marriage of my two careers.” He knows the monetization problem from inside the studio. He knows what the data can do from inside the measurement stack. And the product he’s now selling? “I wish this was around back in the 2012 days when we had our popular free-to-play titles. So it connects with me on a very emotional level, this connection to the developers.”
That’s the brief version of why his answers in this conversation carry more weight than a standard exec talking point. He’s not describing a customer he studied. He’s describing himself, ten years ago, trying not to go under.
---
Watch or listen to my full conversation with Steve Ganem below. What follows is my analysis of what this launch actually means — for developers, for the D2C market, and for Unity itself.
Why free makes sense (and what Unity kept)
The setup: every other company in this market monetizes on a take rate. Xsolla, Stash, Appcharge, and Tebex, the established D2C specialists, all charge a percentage of revenue flowing through their infrastructure. Unity charges nothing.
Ganem, on the record: “What Unity offers is free.” The Terms of Service state there are no fees, and notice would be required before Unity even considered any change. “Nothing retroactive or silent about it.”
The analytical question isn’t whether it’s free; it clearly is. The question is why free makes sense for Unity when no one else is doing it.
The answer becomes obvious when you map what Unity gave away against what it kept.
What Unity gave away: merchant-of-record risk, tax across jurisdictions, fraud, chargebacks, local payment-method complexity, and regulatory compliance with Apple's and Google’s ever-shifting terms. That’s all with Stripe, Coda, and the developer. On compliance, Ganem is explicit: “Ultimately, it’s going to be up to the developer, because they’re the ones that have the relationships with Apple and Google.”
What Unity kept: the SDK, the routing layer, the dashboard, and — critically — the data.
Unity took the asset-light slice of the stack and left every dollar of liability with its partners and customers. Free is cheap when your slice has no cost of goods.
Three reinforcing reasons the zero price is rational
1. It’s a customer acquisition cost for data.
Unity’s actual business is advertising. Its AI ad platform, Vector, runs on purchase signals from developers’ games. When those purchases happen in the App Store, Unity sees a receipt — enough to feed Vector, just like any other ad network. But when a developer goes D2C without routing that purchase data back to Vector, something breaks.
Ganem’s framing here is the sharpest thing in the entire conversation, and it’s been almost entirely missed in coverage of this launch: “Unless that substantially that same data continues to flow into Vector... you’ll actually be losing signals. So there’s a risk that if you don’t act and start bringing in those same signals, you’ll actually suffer from a user acquisition perspective.”
Read that carefully. He’s not pitching D2C as a data upside for Unity. He’s saying that going D2C without Unity degrades the signal developers already depend on. The developer’s incentive to opt in isn’t growth — it’s fear of degradation. The opt-out has a cost.
2. It’s absorptive, not defensive.
The natural instinct is to frame Unity’s zero-price move as an attempt to block D2C specialists from disintermediating it. That framing is wrong, and Ganem corrected it directly when I raised it: “It’s interesting that you sort of position it in your question as Unity competing with these providers. But actually, I’ve spent the last seven months... trying to court these other payment providers to join in partnership with us.”
The move isn’t exclusion — it’s layer capture. Stripe and Coda are in today. Stash is coming. And Ganem confirmed Unity is thinking about webshop-level mediation too, not just payments: “We also are thinking in the future about at the web shop, because you might want to experiment with a different shop provider. And that could be a unique value prop that Unity is going to offer that probably these other providers won’t.”
If that works, Unity becomes the abstraction layer through which all the specialists sell. Their take rate becomes a line item Unity compares on a leaderboard. Ad networks know how that ends.
3. Free is only credible because of the Runtime Fee.
This is the counterintuitive one. Unity learned, in public and in the worst possible way, that it cannot extract rent retroactively. That scar is precisely what makes a promise of zero believable today. Ganem acknowledged it directly: the runtime fee “was a very hard lesson learned... even joining now, this is very commonly talked about and is a lesson learned that Unity still takes very, very seriously.”
What came out of it wasn’t just a policy reversal; it was a structural constraint. The ToS commits to no fees. Notice is required before any change. Nothing retroactive. A believable zero is the whole strategy. The humiliation became an asset.
What this does to the D2C market
The D2C category in mobile gaming has been compounding fast. GamesBeat pegs the market at roughly $17B — about 15% of the $113.3B mobile gaming IAP market — and growing. A well-funded cohort of specialists has formed around the thesis that D2C infrastructure is a durable take-rate business.
Unity just set the price of a single layer in that stack to zero.
The claim isn’t “Unity kills the D2C startups.” It’s sharper than that: value gets squeezed out of the middle and into the two ends of a barbell.
The payments/merchant-of-record end survives. There's real work and real risk there — tax, fraud, chargebacks, and the sprawl of local payment methods players actually use (iDEAL in the Netherlands, Pix in Brazil, RuPay in India). You can charge for eating liability. Unity explicitly won't.
The intelligence end is wide open. Unity doesn’t ship segmentation, LTV prediction, or personalization… yet. Ganem says the routing optimization “doesn’t exist within the product today.” That gap is a real opportunity for specialists who want to own the decision layer above the infrastructure.
The middle — “we’ll host your webshop and give you a dashboard” — is what Unity just priced at zero. Anyone whose take rate is primarily defended by that layer now has to explain what they’re charging for.
The margin myth — and what D2C is actually for
Before going further on market dynamics, there’s a framing error worth correcting — one that Ganem flags as the most common misconception he encounters.
“If you think margin equals opportunity, then you’re really missing the big picture. The bigger opportunity here above and beyond margin is this direct relationship with your players. That’s missing today when you hand over the purchase flow to the platforms.”
This is the argument the blog posts and press releases keep underselling. Right now, Apple and Google own the player relationship at the moment of purchase. D2C gives it back. The margin can be eroded — Apple’s “reasonable commission” on external links is still being litigated, and whatever it lands at will set a floor on savings. The direct relationship is harder to take away.
The conversion tradeoff (the thing people are glossing over)
Here’s the part of the D2C story that gets significantly less coverage than the margin math: web checkout is harder than Face ID.
When a player hits an in-app purchase prompt, it’s one tap or a biometric. When they hit a web payment flow, they’re potentially looking at a new browser, a credit card form, and unfamiliar UI. Some of them leave.
Ganem is direct about the implication: “If you just divert all your users from the app stores to DTC... what you’ll find is that your conversion rates will fall and the juice won’t be worth the squeeze.”
The winning strategy — what he calls “thoughtful segmentation” — is to route D2C flows toward players who already buy repeatedly, see value in the game, and are likely to tolerate a little extra friction in exchange for a bundle or bonus. New players, first-time purchasers, impulse buyers: keep them on the App Store path.
The routing intelligence to do this automatically doesn’t exist in Unity’s product today. Developers are managing it themselves. But this is where the flywheel eventually comes into play, and it’s the operating decision every monetization PM needs to model before they launch.
What this does to Unity
Ad platforms compete on signal. What signal does a normal ad network get from a game? A purchase receipt. AppLovin has it. Meta has it. Everyone has it. It’s parity.
What does a webshop give you? Ganem’s answer is the most important strategic disclosure in the conversation:
“From the platforms, you basically just get a receipt... But there’s a lot more going on in the user’s purchase journey when they’re on your website. What items they’re looking at, what they added to their cart. Maybe they removed items from their cart, or they bought things in bundles.”
Browse behavior. Cart-adds. Cart-abandons. Bundle preference. Price sensitivity by SKU.
That is signal no other ad network can get — because no one else sits inside the engine and inside the store. Unity is the only company that could plausibly see the runtime, the ad impression, and the full commerce funnel in one place. That’s not an incremental data advantage. It’s a structurally different one.
And it’s the first credible answer I’ve seen to the question that’s haunted Unity’s ad business since AppLovin started pulling away: why would Vector ever beat AppLovin?
The discipline (important: this isn’t live yet)
Ganem is careful here, and the carefulness matters: “We haven’t yet tested it. This is not something live. It’s something that’s future roadmap.”
Step one is parity — make sure that when purchases move off-platform, the receipt data still flows into Vector so developers don’t lose the signal they already had. The richer webshop data layer comes next.
There’s also a real structural gate on the whole thesis: developers own the data.
Unity brought the IAP SDK under its Developer Data Framework (DDF) last year. That means the data generated by integrating the SDK belongs to the developer, who chooses whether to share it with Unity. Ganem again: “The developer can choose whether or not to share that data with Unity for the purposes we listed before.”
D2C adoption is not the same as data adoption. Unity has to earn its share per developer every time. That’s the number I’d want to track as this rolls out — not installs of the SDK, but the percentage of developers who opt in their data to Vector.
The second-order bet
If the flywheel works at the UA level, the longer-term play is bigger. Vector stops merchandising ads and starts merchandising your store — which SKU goes on the first screen, which bonus, which discount. An AI system that’s running your storefront is a much larger business than one that’s running your ad campaigns.
Ganem put it this way: “By bringing Vector closer to the actual game in the runtime, it can play a much bigger role in monetization, not just in user acquisition.”
That’s the second-order bet. It’s a roadmap, not a product. But it’s the reason this D2C launch is worth watching as a signal about where Unity is actually trying to go.
Where I’d plant my flag
Ad-platform concentration is the ecosystem’s real problem. AppLovin’s dominance isn’t bad because AppLovin is doing something wrong — it’s bad because no one else can match the signal quality that comes from owning the distribution layer. A performant Vector with first-party purchase data that no competitor can replicate is one of the few structural counterweights games have.
As a game developer, I want this to work. That’s a position, not a prediction.
But the position comes with a legitimate open challenge. Ganem said notice would be required before any fee change, “nothing retroactive or silent.” The ToS commits to it. The structural constraints are real.
Nobody asked for how much notice. Put a number on it, Unity, and you retire the objection forever.
The fee war was never the story. Unity looked at a market where everyone was fighting over take rates and declined to charge one — because it’s playing a different game, on a different P&L, for a different asset. Whether that asset becomes what they’re betting it will be depends on decisions that developers haven’t yet made, including whether to trust them.
The most important number in this launch is zero. The most important question is what comes next.
