UI DUPLICATION INFRINGEMENT CLAIMS IN USA

1. Legal Framework in the United States

UI duplication disputes are not governed by a single statute. Instead, they fall under:

(A) Copyright Law (17 U.S.C.)

Protects:

• Source code
• Graphic elements (icons, buttons, images)
• Original arrangement of UI elements (limited protection)

Does NOT protect:

• Ideas
• Functional layouts
• Navigation systems (“idea–expression merger doctrine”)

(B) Trade Dress Law (Lanham Act §43(a))

Protects:

• “Look and feel” of a UI if it is:
  • Distinctive
  • Non-functional
  • Likely to cause consumer confusion

(C) Patent Law

Protects:

• Specific functional UI innovations (e.g., swipe gestures, interaction mechanisms)

2. Core Legal Test for UI Copying

Courts typically ask:

1. Is the UI element original expression or just an idea?
2. Is it functional (then not protected by copyright)?
3. Is there substantial similarity?
4. Would users be confused (trade dress test)?
5. Are the copied elements merger scenes à faire (standard design elements)?

3. IMPORTANT CASE LAW (USA) – UI / INTERFACE COPYING

Below are 6+ key U.S. cases shaping UI duplication law:

CASE 1: Apple Inc. v. Microsoft Corp. (1989–1994, 9th Cir.)

Issue:

Apple sued Microsoft for copying Macintosh GUI elements.

Holding:

• Most GUI elements were licensed or functional
• Apple could not claim monopoly over general “look and feel”

Principle:

General UI concepts like windows, icons, menus are not fully protectable.

Importance:

Foundational case limiting UI copyright scope.

CASE 2: Lotus Development Corp. v. Borland International, Inc. (1995, Supreme Court affirmation)

Issue:

Whether Lotus 1-2-3 menu command structure was copyrightable.

Holding:

• Menu hierarchy was a “method of operation”
• NOT copyrightable under §102(b)

Principle:

Functional UI navigation systems cannot be copyrighted.

Importance:

Major limitation on UI protection (very influential globally).

CASE 3: Apple Inc. v. Samsung Electronics Co. (2012–2018, multiple rulings)

Issue:

Samsung allegedly copied iPhone UI icons and layout.

Holding:

• Some UI elements were protectable trade dress
• But many design elements were functional or generic

Principle:

• UI may be protected if it creates source confusion
• But not if it is functional or industry-standard

Importance:

Defines intersection of UI + trade dress protection.

CASE 4: Lotus Development Corp. v. Paperback Software (1990, District Court)

Issue:

Copying spreadsheet interface structure.

Holding:

• UI “look and feel” can be protected only if expressive, not functional

Principle:

“Look and feel” doctrine has limited scope in copyright law.

Importance:

Early case addressing UI cloning concerns.

CASE 5: Digital Communications Associates v. Softklone Distributing Corp. (1987)

Issue:

Copying screen displays of terminal software.

Holding:

• Screen displays are separately copyrightable
• But only individual expressive elements, not functional structure

Principle:

• UI screens can be protected, but not underlying functional layout

Importance:

One of the first cases recognizing UI elements as potentially protectable.

CASE 6: Oracle America, Inc. v. Google LLC (2021, U.S. Supreme Court)

Issue:

Copying Java API structure (interface for developers)

Holding:

• Even if copyrighted, copying may be fair use
• Functional interfaces receive weaker protection

Principle:

Functional code-based interfaces are limited in protection scope.

Importance:

Strong reinforcement of idea–expression limitation in software/UI systems.

CASE 7: Sega Enterprises Ltd. v. Accolade Inc. (1992, 9th Cir.)

Issue:

Reverse engineering software interface to create compatible UI/game behavior.

Holding:

• Functional interface elements are not protected
• Reverse engineering for compatibility is allowed

Principle:

• UI/UX elements necessary for compatibility are not monopolizable

Importance:

Key case for software UI interoperability.

CASE 8: Feist Publications v. Rural Telephone Service (1991, Supreme Court)

Issue:

Copyright protection for structured listings.

Holding:

• No protection for non-original compilation arrangements

Principle:

“Originality is the sine qua non of copyright.”

Importance:

Applies strongly to UI layout claims (generic arrangements not protected).

4. KEY PRINCIPLES FROM CASE LAW

4.1 UI is Partially Protectable

Protected:

• Icons
• Graphics
• Unique animations
• Original visual artwork

Not protected:

• Layout structure
• Navigation flow
• Standard UI patterns

4.2 Functionality Doctrine (Very Important)

If a UI element is:

• Necessary for usability
• Industry standard
• Technically required

👉 It is NOT protected by copyright.

4.3 Trade Dress Protection is Limited

UI can be protected only if:

• It is distinctive
• Non-functional
• Creates consumer confusion

4.4 “Idea vs Expression” Rule

• Idea = not protectable (e.g., “a settings menu”)
• Expression = protectable (custom icons, animations)

4.5 “Look and Feel” is NOT Fully Protected

Modern courts reject broad protection of:

• Entire app UI duplication claims
• Generic design copying

5. PRACTICAL LEGAL STANDARD IN UI DUPLICATION CASES

A UI duplication claim usually succeeds only if:

• The copied UI is visually identical in expressive elements
• AND includes distinctive branding elements
• AND causes consumer confusion

Otherwise:

• Courts dismiss claims as copying of functional design ideas

6. CONCLUSION

In the United States, UI duplication infringement claims are narrowly interpreted:

• Copyright protects expression, not structure
• Functional UI elements are generally free to copy
• Trade dress may protect UI only in rare, highly distinctive cases
• Courts strongly avoid granting monopoly over “look and feel”

Key takeaway from case law:

You cannot own a general UI concept—but you can protect unique artistic expression within it.