Elise Explains IPcast
What happens when a company copies the structure of a software system — but writes its own code? In this episode of Elise Explains IP, Elise unpacks one of the most important intellectual property cases in modern technology: Oracle v Google. The dispute centred on Google’s use of Java APIs when developing Android, and raised a major legal question: Can the structure of software systems be protected by copyright? But this episode goes beyond the legal headlines. Elise explains why this case matters for: * SaaS founders * Tech businesses * Platform operators * Advisors working with digital businesses * And any business building software products or scalable systems You’ll also learn why relying on “fair use” can be dangerous — particularly for Australian businesses operating under much narrower fair dealing rules. In This Episode ✔️ What APIs actually are (in plain English) A practical explanation of APIs and why they became central to the dispute. ✔️ What Google copied — and why it mattered The difference between: * copying code * copying structure * and replicating how a system works ✔️ Why the case lasted over 10 years A look at the commercial stakes and legal uncertainty surrounding the dispute. ✔️ The Supreme Court’s fair use decision Why Google ultimately succeeded in the US — and why that outcome doesn’t easily translate to Australia. ✔️ Fair Use vs Fair Dealing A critical distinction for Australian businesses: * US law uses broad “fair use” * Australia relies on narrow “fair dealing” exceptions ✔️ The real-world risks for businesses Including: * investor due diligence issues * forced rebuilds * licensing disputes * platform redesigns * commercial disruption Key Takeaways * Intellectual property risk in software is not limited to copied code * Structure, organisation, and system design can also become contentious * “We rewrote it ourselves” is not always a complete defence * Fair use is a US doctrine — and Australian businesses should not assume the same flexibility exists here * Licensing and early IP strategy are significantly cheaper than litigation later Practical Questions for Founders & Advisors If you’re building software or digital systems, ask yourself: * Are we modelling our product on an existing platform? * What third-party frameworks or APIs are we relying on? * Do we clearly understand the licensing terms? * Have we documented what IP actually exists in our system? * Would an investor or acquirer be comfortable with our IP position? Mentioned in This Episode * Oracle America, Inc. v Google LLC * Java APIs * Android operating system * Fair use (US) * Fair dealing (Australia) About Elise Explains IP Elise Explains IP is a practical podcast for business owners, founders, creatives, and advisors who want to better understand intellectual property and business protection. The focus is simple: 👉 helping businesses identify risk early and protect what they’re building before problems arise. Need Advice? If you’re building software, digital products, systems, or scalable platforms — and you’re unsure where your intellectual property risks sit — you can book a strategy call using the link below. www.elisesteegstra.com [https://www.elisesteegstra.com] Protecting your IP early is usually far easier than untangling it later.
26 episodios
Comentarios
0Sé la primera persona en comentar
¡Regístrate ahora y únete a la comunidad de Elise Explains IPcast!