Google didn't refuse to pay for Java. It nearly did — then decided the cheaper price was to build anyway and argue about it later. The argument lasted a decade.
Pairs with the Fork Decision Tree — a ready-to-use strategy tool. Included in the The Fork Casebook →
In late 2005, before Android had shipped a single phone, Google sat across a table from Sun Microsystems and tried to buy its way in. It wanted Java — the language and the vast library of shortcuts that let programmers build on it — and it wanted Sun's blessing to open-source the whole thing for a new mobile platform. By the end of April 2006, according to Google's own trial brief, Sun had agreed to take $28 million over three years for the privilege.4 Twenty-eight million dollars is a rounding error for Google. And Google walked away from it.
The story you usually hear is that Google refused to pay for Java and defiantly fought Oracle for eleven years rather than license it. That is not quite what happened. Google did try to license it. The deal died not over money but over control of the platform.4 Then Google made a colder, more interesting choice: build on Java's structure anyway, without a license, and be ready to defend that decision in court if the risk ever came due. The risk came due. It took roughly a decade to settle — and the settlement was narrower than the trophy suggests.
“Do Java anyway and defend our decision, perhaps making enemies along the way.”3
The fork wasn't pay-or-fight — it was who owns the platform: google would spend on the license; what it would not spend was control of android's future
This is the part that reframes the whole legend. The negotiation didn't break down because Google was cheap. Court documents show the two companies spent months in 2005 and 2006 working toward an open-source Java partnership, and the deal simply didn't close.35 Sun wanted a Java that stayed compatible and coordinated — a garden it still tended. Google wanted a Java it could fork, reshape, and hand out free to phone makers without asking permission. Those two futures could not both be true. So the real fork wasn't 'pay or fight.' It was: accept a controlled Java and slow Android down, or copy the parts that made Java familiar to millions of programmers — the API declaring code, the naming and structure that let anyone who knew Java write for Android on day one — and own the platform outright. Google chose ownership, and priced the lawsuit as the cost of it.
Google didn't need Java's underlying implementation — it wrote its own. What it needed was the declaring code: the familiar library names and method signatures every Java developer already knew by heart. Copy those, and the world's largest pool of programmers can build for your new platform without learning anything. That compatibility is worth more than any block of code, which is exactly why Oracle argued it was worth billions and why the case was never really about a few thousand lines of text. It was about who controls the doorway a developer walks through.
That is why a $28 million deal Google could have signed without noticing turned into a fight over billions. When Oracle bought Sun and sued in 2010, it did not ask for $28 million. Its damages expert modeled a hypothetical license worth $1.4 billion to as much as $6.1 billion, depending on the assumptions.3 The price of the doorway had been recalculated with Android's success in hand. Google had walked away from the cheap version of the toll and now faced the expensive one.
Google won twice, lost twice, then won the round that counted: this was never a straight line of losing rescued at the last minute — it seesawed for a decade
The tidy version of this saga — Google loses and loses until the Supreme Court saves it — is wrong in a way that matters. The case seesawed. At the first trial, a jury found Google had infringed the copyright but deadlocked on fair use, and the district judge then set aside the verdict and ruled that Java's declaring code, including its structure and organization, wasn't copyrightable at all.2 Google won. Then in May 2014 the Federal Circuit reversed him, holding the APIs were protected by copyright, and sent it back down on fair use.6 A 2016 jury again found for Google on fair use. And in 2018 the same three Federal Circuit judges reversed that jury too.7 Two wins for Google at the trial level, two reversals above it. Google's 'brilliant decade-long fight' was, for most of its life, a losing appellate record.
The rescue came on April 5, 2021. Justice Breyer, writing for a 6-2 majority — Thomas and Alito dissenting, Barrett recused — held that Google's copying of the declaring code was a permissible fair use.18 It restored Google's win and erased the $8.8-to-$9 billion exposure. But read the opinion's fine print and the trophy shrinks. The Court did not decide whether APIs can be copyrighted. It assumed, for argument's sake, that they could — and then ruled Google's use was fair anyway.1
Wasn't this a landmark win that settled the law?: it settled google's liability; it left the question that started the whole thing formally open
The fair objection is that this is too grudging a reading of a genuine victory. Google faced up to $9 billion in exposure, and it walked away owing nothing — that is not a technicality, that is a total win.8 True. For Google's balance sheet, the case is closed and the bet paid off spectacularly: it kept Android, kept the money, and kept control. But 'won the case' and 'settled the law' are different things. The lawsuit began in 2010 as a fight over whether APIs are copyrightable at all.2 The Supreme Court answered a narrower question — is this particular use fair? — and pointedly declined the bigger one.1 So the next company that copies an API to make its platform familiar inherits the same uncertainty Google faced in 2006, minus the reassurance that copyrightability is off the table. Google didn't clear the minefield. It proved that one specific crossing, by one specific giant, with a decade of the best lawyers money can buy, happened to be survivable.
| The legend | The record | |
|---|---|---|
| Why the deal died | Google refused to pay | Talks collapsed over control, not price |
| The case's arc | Google lost until the end | Won twice at trial, reversed twice on appeal |
| What the win settled | APIs aren't copyrightable | Only that Google's use was fair; copyrightability left open |
| The precedent for the next firm | APIs are safe to copy | One survivable crossing, not a cleared path |
The lesson of Google v. Oracle isn't 'fight for what's yours.' It's that Google, at the fork, treated a legal risk the way it treats an engineering constraint: something to be priced, provisioned for, and outrun by growth. It declined a $28 million license, built the platform it actually wanted, and carried a nine-figure — then ten-figure — liability on its back for a decade because it judged that Android, unconstrained, was worth the exposure.48 It turned out to be right. But the win it got was smaller and stranger than the myth — a narrow reprieve on fair use, not a rewriting of the law — and the very question that made the doorway worth billions is still, quietly, unanswered.
Other companies that chose the harder fork
Fork Decision Tree
Take the either/or in front of you and draw it out: the question at the fork, the two branches, and what each one triggers two and three moves later. Blank, it forces you to spell out consequences before you commit instead of after. Filled, it replays the story's fork so you can see exactly where each path led — and which downstream node actually decided the outcome.
Included, filled and blank, in the The Fork Casebook. See the set → · Preview the blank →
Sources
Where this comes from — the filings, records, and reporting behind it.
- 1On April 5, 2021, the Supreme Court ruled 6-2 for Google (Breyer writing for the majority joined by Roberts, Sotomayor, Kagan, Gorsuch, and Kavanaugh; Thomas dissenting joined by Alito; Barrett recused), holding that Google's copying of the Java SE API's declaring code was a permissible fair use, while assuming without deciding that the code could be copyrighted at all.
- 2Oracle sued Google in 2010 seeking billions in damages; a jury found Google infringed but deadlocked on fair use, after which the district judge set aside the infringement verdict and held the Java API's declaring code, including its structure, sequence, and organization, was not copyrightable.
- 3District court records show that starting in October 2005 Google and Sun Microsystems negotiated an open-source Java/Android partnership for months without reaching a deal, with Google's Andy Rubin writing internally that if Sun would not cooperate the fallback was to 'Do Java anyway and defend our decision, perhaps making enemies along the way'; Oracle's damages expert separately calculated a hypothetical reasonable-royalty license value of $1.4 billion to as much as $6.1 billion depending on assumptions.
- 4Per Google's own 2012 trial brief, by the end of April 2006 Sun had agreed to accept a $28 million payment from Google over three years to offset the risk of lost licensing revenue from an open-source Android, but negotiations broke down afterward over control of the platform rather than over price.
- 5Court documents reveal that in 2005 or 2006, Google was in ambitious discussions with Sun Microsystems to open source Java and partner on Android development, and that deal ultimately did not go through.
- 6In May 2014 the Federal Circuit reversed the district court and held that Oracle's Java APIs, including their declaring code and organizational structure, are protected by copyright, sending the case back down on the question of fair use — a jury had earlier cleared Google of patent infringement but found copyright infringement on the underlying code in 2012.
- 7The Federal Circuit's first ruling left fair use to a jury, which found for Google in 2016, but the same three Federal Circuit judges reversed that jury verdict in 2018; the Supreme Court then granted Google's petition in November 2019, heard argument in October 2020, and in April 2021 reversed the Federal Circuit, holding Google's use of the Java APIs was fair use as a matter of law.
- 8Oracle filed its lawsuit against Google in 2010 seeking as much as $9 billion in damages, and a federal appeals court ruled in Oracle's favor in 2018 before the Supreme Court overturned that decision 6-2, with Breyer writing the majority opinion and Thomas and Alito dissenting.
- 9After the March 2018 Federal Circuit reversal, Oracle was seeking $8.8 billion in damages from Google, with Oracle's general counsel Dorian Daley and Sun co-founder Scott McNealy publicly framing the ruling as vindicating Oracle's rights over Java's foundation.
More like this — beyond Alphabet (Google)
New Strategically analyses as they publish: the defining moves in business, checked against the record. No noise, and one click to leave.