Home » Blog » GOOGLE LLC v. ORACLE AMERICA INC. (2021)

GOOGLE LLC v. ORACLE AMERICA INC. (2021)

Authored By: Prisha Dhimmer

Bharti Vidyapeeth, New Law College, Pune

Name of the Judges- Justice Stephen Breyer delivered the judgement

Majority Opinion – CJ John Roberts, J Soniya Sotomayor, J Elena Kagan, J Neil Gorsuch, J Brett Kavanaugh

Dissenting Opinion- J Clarence Thomas, J Samuel Alito

J Amy Cony Barett did not participate

Judgment delivered on 5 April, 2021

Parties Involved- 

Petitioner: Google LLC: Started as a search engine firm, it then grew to become a conglomerate technology firm with a global presence. In this regard, it can be noted that Google developed Android, the most widely used operating system for mobile technology in the entire world. The aim of Google was to develop an open operating system for mobile devices that would enable developers to apply their skills developed for desktops.

Respondent: Oracle America, Inc.Oracle America, Inc. is a large software company that acquired Sun Microsystems (the creators of the Java programming language) in the year 2010. Oracle owns the Java SE (Standard Edition) platform. Oracle’s business model includes the distribution of the Java platform and the guarantee that any “forks” associated with the Java platform must be compatible with Java.

Facts of the case:

Oracle America, Inc. owns the copyright for Java SE. It was developed on the popular Java computer programming language. In 2005, Google purchased the company Android Inc., which was a start-up company that aimed at developing software platforms for smartphone devices and also dreamed of building a free and open Android platform.

Later, Google attempted to negotiate a licensing agreement with Sun Microsystems, which is currently Oracle America, Inc., and is the creator of the Java platform, to obtain a license to use the entire Java platform in smartphones, but this failed due to their condition that “all programs written on the Android platform be interoperable.”

Google created their own platform for Android. In their endeavor to ensure that applications for Android can be created without altering commands used for java application developers, Google copied 11,500 lines “of declaring code” contained in the Java API, primarily because such lines relate to the satisfaction of commands accomplished through SSO principles in java. Google would later develop implementing code independently of the API since most lines belong to it.

Oracle Corporation bought Sun in 2010. A case for copyright and patent infringement was filed against Google. The jury counteracted the patents but found no infringement, therefore resulting in a deadlock on fair use.

The Federal Circuit overturned in May 2014, finding that SSOs are copyrightable and remanding the issue of fair use.

Google sought a writ of certiorari in the Supreme Court in 2015. A second jury found for fair use in 2016.

In March 2018, the Federal Circuit reversed, finding no fair use as a matter of law, remanding damages.

Legal Issues:

  1. Whether Java SE API’s source code (~11,500 lines) and SSO constitute copyrightable “expression” under Section 102(a) or uncopyrightable “system/method of operation” under Section 102(b).
  2. Whether Google’s use of the API declaring code/SSO for Android qualifies as fair use within the meaning of §107 factors relating to purpose and character of use, its nature, extent, and effects on the potential market.

Arguments of the Parties: 

Google LLC (Petitioner)

The Merger Doctrine: Google argued that the declaring code and its organization were the only way to express the specific functional system. Since the “idea” and the “expression” had merged, the code was not copyrightable.

Nature of Software: They argued that APIs are functional means and not a work of literature like a novel. They, therefore, fall within the concept of a “method of operation” under Section 102(b) of the Copyright Act.

Market Transformation: Google contended that Android did not compete with Java SE – that focused on desktops, therefore, their use was transformative as they created a “new” thing in the mobile market.

Minimal Taking: Google indicated that only “11,500 lines of declaring code” were needed to comprise “roughly 0.4%” of the “2.86 million” Java SE platform lines. This was the minimum necessary to enable developers to apply their existing knowledge to a new platform.

Transformative Use:  Google claimed that their use of the API was “transformative” because they did not copy the code, they “reimplemented” the code in a new setting (the smartphone market) to build a new platform (Android).

Oracle Inc (Respondent):

Statutory definition: Oracle emphasized that the Copyright Act expressly embraces computer programs as one would “literary works”; and the declaring code was an original, creative expression. That the statute makes no distinction between “declaring” and “implementing” code.

Creative Choice: According to Oracle, the naming, structure, and organization of the 37 API packages required “thousands of creative decisions” by the engineers of Sun Microsystems. Google could have developed “its own distinctive naming conventions” but instead opted for theft of Oracle’s “creative choice” because of time constraints

Commercial Harm: Oracle asserted that Google’s “unlicensed” use was responsible for billions of dollars in commercial harm because it removed the possibility for Oracle to license the platform themselves for use by the mobile manufacturers like Amazon and Samsung. 

Commercial substitution: Oracle claimed Google’s use was nonetheless commercial, as opposed to being considered fair and therefore transformative. Google’s usage of the Java API was the same as its intended usage and was aimed at giving Google a competitive advantage in the mobile market

Judgement:

The decision by the Supreme Court came after multiple federal cases and reversals, on 5th April, 2021, J. Breyer delivered the judgement in the favour of Google LLC. In a 6–2 decision, the Supreme Court reversed the Federal Circuit’s decision and held that Google’s copying of the Java SE API was a fair use as a matter of law. Justice Breyer, writing for the majority, opted to “decide no more than necessary” to resolve the dispute. The Court thus sidestepped the question of copyrightability, assuming the code was protected only for the sake of argument and addressed only the statutory fair use factors under 17 U.S.C. § 107. The Court held that Google’s “reimplementation” of the interface was consistent with the constitutional objective of copyright that is to promote creative progress rather than stifle it.

Reasoning of the decision:

The Court held that the declaration code (functional interfaces) is closer to the “core of copyright” than the implementing code (creative instructions). As the value lies in the “accrued talents” of the users (programmers) and not in any creative expression, it falls short of copyright under the Fair Use test.

Transformative copying under Factor 1 is that kind of copying that enables the development of a new platform within a new environment (for example, from desktop to mobile). The Supreme Court gave precedence to the “Progress of Science” over the financial interests of the copyright owner.

In respect of Factor 3, “the amount and substantiality” is assessed comparatively to the whole work. The copying of 11,500 lines, 0.4% of the whole, is a minimal taking.

In factor 4, the court stated that copyright law cannot be used as a “lock” to monopolize skills in a labor force. It would have a negative effect on competition and public harm if a company is allowed to own a copyright to an interface which has turned out to be a standard in its field.

The Court held that although the jury decides the facts, the ultimate conclusion regarding the facts being within the parameters of Fair Use is a question of law for the judge to make in a de novo review.

Precedent cases that held a great impact on the judgement include:
Baker v. Selden, 101 U.S. 99 (1879), the Court established the “idea-expression dichotomy,” holding that a work’s expression is protected by copyright but not its underlying functional system or mode of operation. This precedent was applied in this instance to categorize the Java API’s declaring code as a functional “method of operation” that makes a system easier to use, giving it far less copyright protection than innovative implementing code.

According to Campbell v. Acuff-Rose Music, Inc., 510 U.S. 569 (1994), the term “transformative use” refers to a usage that does more than just replace the original, it adds something new with a distinct purpose or character. This was used in Google v. Oracle to determine that reimplementing the Java API in a new mobile smartphone environment was revolutionary because it produced a unique platform that increased the code’s usefulness for a different market.

Justice Thomas’s dissent, however, contended that the majority simply discarded the plain text of the Copyright Act, which grants all computer code copyright protection as “literary works” and draws no distinction between declaring code and implementing code. He insisted that, because Google’s use of the Java code was both commercial in nature and notransformative, the code served exactly the same function in Android as it did in Java. The use was not fair since it directly replaced Oracle’s market, thereby erasing its potential licensing revenues and capturing for Google the value of Oracle’s intellectual property.

Conclusion:

The Supreme Court’s decision came as a landmark victory, Court held that Google’s “reimplementation” of the Java API was a Fair Use, thus ensuring that copyright would not become a “lock on the accrued skills of programmers.”

The decision specifies that functional interfaces are entitled to less protection than creative code. On the basis of the transformative test set out in the Campbell vs. Acuff-Rose decision, the Court gave more importance to the value of “creative progress” than to the rights of exclusion. This ensured that industry-standard commands are not blocked and that the new platforms can be developed using the same. This decision gave the programmers, developers a shared space to make the most out of their acquired knowledge and software interface and ensuring that copyright law fosters progress and not hinder the progress of new technologies.

Reference(S):

  1. Rugved Mahamuni,Case Study Of Google LLC V. Oracle America Inc.,Journal of Legal Research and Juridical Sciences,last visited Dec 22, 2025 https://jlrjs.com/case-study-of-google-llc-v-oracle-america-inc/
  2. Priyanka Saraswat,Google v Oracle: the fair use debate,blog.ipleaders.in,May1, 2021https://blog.ipleaders.in/google-v-oracle-fair-use-debate/
  3. Supreme Court of United States Opinion https://www.supremecourt.gov/opinions/20pdf/18-956_d18f.pdf
  4. Google LLC v. Oracle America, Inc,[135],[Harvard Law Review],2021https://harvardlawreview.org/print/vol-135/google-llc-v-oracle-america-inc/
  5. 17 U.S.C. § 102(a) and 17 U.S.C. § 102(b), 17 U.S.C. § 107

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top