App interface copyright disputes between FDI companies and design agencies tend to erupt at the worst moment: right before a major update launch, or when the company moves to a new developer and the old agency declares ‘the interface is ours’. These disputes are rarely decided by feelings about design — they are decided by the contract and the handover evidence.
What decides an app interface dispute
- The design contract is evidence number one — Article 39 of the IP Law defaults economic rights to the commissioning party, but clauses on the agency’s pre-existing components (UI kits, libraries) can reserve a significant share of the interface.
- Creativity versus common patterns — platform-convention interface elements (standard buttons, navigation bars) lack individual originality; protection covers the overall layout, illustrations and distinctive graphic elements — a dispute must pinpoint exactly those.
- Creation evidence and registration — Article 49: a copyright registration certificate, timestamped design files and version history are the evidence separating who created what, and when.
- Escalation remedies — Articles 202-205: the rights holder may seek interim injunctions against continued use of the disputed interface and claim damages; contract disputes usually pair with demands to hand over digital assets.
A response path when the agency claims the interface
- Freeze evidence immediately: the contract, annexes, design approval emails, payment records and delivered files — before either side revokes the other’s access.
- Independently assess the disputed interface: separate the project’s original creative elements from the agency’s platform components and stock libraries.
- Negotiate a buy-out or licence for the missing share where litigation would cost more than the disputed part is worth; sue only when what is withheld is the product’s core.
App interface disputes are an expensive lesson in design contracts: the winner is the side with clean paperwork, not the side that ‘feels’ the design is theirs. FDI companies should prevent them with clauses separating custom components from pre-existing ones — once a dispute erupts, every solution costs many times that clause.
Frequently asked questions
We are disputing app interface copyright with our agency — how is it resolved?
Start from the contract: apply the Article 39 default, check pre-existing component clauses, assemble creation evidence, then negotiate a buy-out or licence, or sue under Articles 202-205.
What clauses should a design contract have from the start?
A clear split between custom components owned by the company and the agency’s platform/library parts, delivery of source design files, and the right to hire others to continue development.
Should we register copyright before any dispute?
Registration creates no rights, but a certificate under Article 49 is strong evidence of ownership and creation date — file it when the interface is final, not when trouble starts.
This article has been quality-reviewed by the FLAW AI Legal Council
Related articles
- Copyright Assignment Terms for Commissioned Works: Model Clauses
- Copyright in Online Employee Training Courses of FDI Companies
- Performers Rights in Corporate Introduction Videos
- Collecting Vietnamese Data to Train AI: Copyright Limits
- Copyright in Application Programming Interfaces (APIs) of FDI Software