Will the US Supreme Court End the Android API Copyright Battle?
The US Supreme Court has agreed to revisit the landmark Java API copyright dispute between Oracle and Google, a case that could reshape software licensing and API protection, with hearings likely postponed until next year, while the tech community watches closely.
In April, Open Source China reported that the US Supreme Court asked the Trump administration for help in deciding whether to continue hearing Google's appeal against the Federal Circuit's ruling that Android infringed.
The latest development is that the Supreme Court has agreed to rehear what is considered the most important software copyright dispute of the past decade.
However, the Court has not announced when it will hear the case, likely postponing it until next year; Open Source China will continue to follow the story.
Google used Java to develop the Android operating system. After Oracle acquired Sun, it obtained ownership of Java and in 2010 sued Google for infringing Java's copyrights. APIs are standard function calls that allow third parties to build software compatible with platforms such as Java.
Before the Federal Circuit found Android infringing, copyright law was widely believed not to apply to API usage. The appellate court's decision challenged this assumption, so the Supreme Court's review—primarily on whether "APIs are copyrightable"—will have far‑reaching effects on the software industry.
Event Review
In 2010, Oracle bought Sun for $7.4 billion and, within eight months, sued Google for alleged copyright infringement of the Java language, seeking $8.8 billion in damages.
Oracle claimed that Google’s use of 37 Java API packages in Android infringed Oracle JDK. The 37 packages are:
java.awt.font
java.beans
java.io
java.lang
java.lang.annotation
java.lang.ref
java.lang.reflect
java.net
java.nio
java.nio.channels
java.nio.channels.spi
java.nio.charset
java.nio.charset.spi
java.security
java.security.acl
java.security.cert
java.security.interfaces
java.security.spec
java.sql
java.text
java.util
java.util.jar
java.util.logging
java.util.prefs
java.util.regex
java.util.zip
javax.crypto
javax.crypto.interfaces
javax.crypto.spec
javax.net
javax.net.ssl
javax.security.auth
javax.security.auth.callback
javax.security.auth.login
javax.security.auth.x500
javax.security.cert
javax.sqlIn these 37 packages, Google copied class and method names as well as functionality, matching Oracle JDK exactly, which Oracle, as the owner of Java, deemed infringing.
Key milestones in the Oracle‑Google Java copyright saga:
2010: Oracle sued Google, alleging unauthorized use of Java APIs in Android.
2012: A district court ruled that APIs are not subject to copyright protection, rejecting the case.
2012: Oracle appealed to the US Court of Appeals for the Federal Circuit.
2014: The appellate court reversed the district court, holding that APIs are copyrightable.
2014: Google appealed the decision to the US Supreme Court.
2015: The Supreme Court denied Google’s appeal and sent the case back to the district court for retrial.
2016 Mar: Oracle increased its claim to $9.3 billion.
2016 Apr: A settlement meeting between the CEOs of Google and Oracle failed.
2016 May: A San Francisco court affirmed Google’s use of Java APIs as protected by “fair use”.
2016 Oct: Oracle appealed to the Federal Circuit.
2017: The Federal Circuit heard Oracle’s appeal.
2018 Mar: The Federal Circuit ruled Android infringed, granting victory to Oracle.
2018 Aug: Google’s subsequent appeal was rejected.
2019 Jan: Google petitioned the US Supreme Court for a final ruling on the Java API copyright case.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
21CTO
21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
