A competitor launches an app that looks unmistakably like yours: same layout, same colour system, same icon grid, same onboarding flow. The instinct is to call it stealing. The legal question is narrower and stranger — which specific elements were copied, and does any regime protect that particular kind of thing?

U.S. law offers three main answers, and they do not overlap neatly. Trade dress protects appearance that identifies the source of a product to consumers. Design patents protect ornamental designs, including screen displays and icons. Copyright protects original expression, but not functionality, ideas, or the useful things an interface does. A single screen can contain elements falling into all three categories and elements protected by none.

Three regimes, three different things protected

What each regime covers for a software interface
RegimeProtectsKey requirementRough duration
Trade dressOverall look that signals sourceNon-functional plus distinctivenessIndefinite while used and distinctive
Design patentOrnamental design of a screen or iconNovel, non-obvious, ornamental; timely filingFixed term from grant
CopyrightOriginal expression: art, text, code, some arrangementOriginality; no protection for function or ideasLong term from creation
TrademarkNames, logos, and distinctive marks in the productUse in commerce and distinctivenessIndefinite with use and renewal
Utility patentHow a feature works, if patentable at allNovelty, non-obviousness, eligible subject matterFixed term from filing

The regimes are administered by different offices. Patents and federal trademark registrations come from the U.S. Patent and Trademark Office, which sits within the Department of Commerce; copyright registration is handled by the U.S. Copyright Office. Different filings, different timelines, different evidence.

Trade dress: two hurdles, both real

Trade dress is the appearance of a product or its packaging, protected under federal unfair-competition law because it tells consumers where the product comes from. The Cornell LII overview of trade dress sets out the framework. For a software interface, two requirements do the deciding.

Non-functionality. A feature is functional, and therefore unprotectable as trade dress, when it is essential to the use or purpose of the product or affects cost or quality. Interfaces are full of functional choices: a bottom navigation bar sits where thumbs reach, a red colour signals errors, a shopping cart icon communicates instantly because everyone uses it. None of that can be owned through trade dress. Protection lives in the arbitrary choices — a distinctive visual system, unusual proportions, a particular ornamental treatment — that could have been made a hundred other ways without affecting how the product works.

Distinctiveness. Courts treat product design as never inherently distinctive: it must acquire secondary meaning, which is consumer recognition of the design as identifying one source. Interfaces are generally analysed as product design rather than packaging, so an app that launched last quarter almost certainly cannot claim trade dress in its look, however original the look may be.

Claims also have to be defined. A plaintiff must articulate the specific combination of elements said to constitute the trade dress — a list, not a vibe. "The overall look and feel of our app" is the formulation courts most often reject as too indefinite to adjudicate.

Watch out: Publicly bragging that a design choice makes the product faster, cheaper, or easier to use is helpful marketing and damaging evidence. Statements about functional advantage are routinely quoted back at trade dress plaintiffs. Coordinate marketing copy with whoever owns the IP strategy.

Design patents on interface elements

A design patent covers the ornamental design of an article of manufacture, and the USPTO grants design patents on graphical user interfaces — icons, screen layouts, and animated transitions — claimed as applied to a display screen or portion of one. Drawings define the claim, with solid lines showing what is claimed and broken lines showing unclaimed environment, which makes drawing strategy the central drafting decision.

The best-known reference point is the long-running Apple and Samsung smartphone litigation, in which design patents covering elements including the arrangement of icons on a screen were central to the case. It reached the Supreme Court in 2016 on a damages question — whether the "article of manufacture" for calculating a design-patent damages award could be a component of a product rather than the entire device — and the Court held that it could be, sending the valuation question back for further proceedings. The practical lessons for product teams are that design patents on interface elements are real and enforceable, and that the value attributed to them turns heavily on how the infringing article is defined.

The advantages are real: no secondary-meaning requirement, no need to prove consumer confusion, and a registered right an examiner has reviewed. The trade-offs are cost per design, scope keyed narrowly to the drawings, a fixed term, and unforgiving timing — public disclosure starts a statutory clock, so filing decisions belong before launch, not after a competitor copies you.

Copyright is the cheapest and fastest right to secure, and the most misunderstood in this context. It protects original expression — the icon artwork, illustrations, animation, photography, marketing text, help content, and the source code itself. Registration through the Copyright Office is a prerequisite to filing an infringement suit and unlocks remedies unavailable to unregistered works, which is why registering key assets early is inexpensive insurance.

What copyright does not protect is equally important. It does not cover ideas, systems, methods of operation, or functionality. Where there are only a few ways to express something, expression and idea merge and protection thins to nothing. Standard elements that follow from the subject matter get no protection either. And in a 2021 decision addressing the reuse of software interface declarations, the Supreme Court held that copying a portion of an application programming interface to allow programmers to use familiar calls was fair use in the circumstances presented — a reminder that interoperability arguments carry real weight in software copyright disputes.

Two consequences follow. Copyright is strong against wholesale copying of assets — a lifted icon set or onboarding illustrations — and weak against a competitor who rebuilds a similar layout with its own artwork. And ownership must be nailed down: employee work within scope generally vests in the employer, while contractor work usually does not without a written assignment. Check for that language in every design and development contract, alongside the terms discussed in software and SaaS agreements.

A layered plan, in the order it pays to do it

  1. Secure ownership first. Written assignments from every contractor, agency, and freelancer who touched the design. Without this, nothing else is worth building on.
  2. Register the trademarks. Product name, logo, and any distinctive in-product mark. These are the rights most often enforced in practice, and they pair with the domain-side remedies described in domain name and trademark disputes.
  3. Register key copyrights. Icon sets, illustration libraries, marketing pages, documentation, and code deposits for major releases.
  4. Decide on design patents before launch. Pick the two or three screens or elements that genuinely define the product and file within the applicable deadlines rather than after the fact.
  5. Start the secondary-meaning file on day one. Trade dress will not be available for years, but the evidence must be collected as it happens.
  6. Document the non-functional choices. Keep design rationale showing which decisions were aesthetic rather than performance-driven, and keep the alternatives that were considered and rejected.

Practical step: Maintain a running evidence folder: advertising spend tied to the visual identity, unsolicited press describing the design, awards, user research showing recognition, sales volumes, and any "look for the [design element]" advertising. That folder is what turns a trade dress theory into a claim three years from now.

Quick answers

A competitor copied our layout but drew its own icons. Do we have a claim?

Copyright is unlikely to help, since the copied part is arrangement and function rather than expression, and the artwork is different. A design patent could reach it if the claimed drawings cover the layout and an ordinary observer would find the designs substantially the same. Trade dress is possible only if the layout is non-functional and has acquired consumer recognition — a demanding combination.

Is "look and feel" a legal category?

No. It is a business phrase that maps loosely onto trade dress and, in narrow circumstances, copyright in the selection and arrangement of expressive elements. Courts require a plaintiff to specify the discrete features it claims, then test each for functionality and distinctiveness. Framing a demand letter around "look and feel" signals that the analysis has not been done.

How long does secondary meaning take to build?

There is no fixed period. It depends on advertising reach, market share, media coverage, and the strength of survey or recognition evidence, and courts assess it on the record presented rather than by a timetable. Some products establish it quickly through heavy exposure; many never do. Treat the evidence file as the project and the years as a by-product.

Should a small company bother with design patents?

Sometimes. They cost meaningfully more than a copyright registration and cover narrowly what the drawings show, so filing broadly is rarely justified. But for a product whose distinctive screen is its main commercial asset, one or two well-drafted design patents give a registered, enforceable right without the years of consumer recognition trade dress demands. Decide before public launch.

Where this leaves you

Separate what was actually copied from what merely feels stolen, then match each piece to the regime that can reach it. Lock down ownership through written assignments, register trademarks and key copyrights early, make a deliberate design-patent decision before launch, and start collecting recognition evidence from the first day of trading. If you are on the receiving end of a letter, run the same analysis in reverse — functionality and lack of distinctiveness are the defenses that most often carry. Neighbouring topics, from enforceable website terms to data and vendor obligations, are collected in the technology, privacy, and IP pathway.