Why Semi Design Copied Ant Design and How It Responded

The article explains how Douyin's Semi Design, an open‑source React UI design system, was found to contain undocumented Ant Design text, details the team's public apology, the architectural differences, license updates, and the specific components that were referenced.

Programmer DD
Programmer DD
Programmer DD
Why Semi Design Copied Ant Design and How It Responded

Douyin's frontend team recently open‑sourced its enterprise UI design system, Semi Design, which provides a complete, easy‑to‑use solution for modern admin applications, including a design language, React components, and theming.

Shortly after release, parts of the repository were discovered to contain undocumented text copied from Ant Design. On October 27, the team publicly admitted the oversight, apologizing for not crediting Ant Design.

The team clarified that Semi Design has been maintained for over two years, built on a Foundation/Adapter architecture that differs significantly from Ant Design, and that the project will continue to accept community feedback while adhering more strictly to open‑source licensing rules.

They have updated the license and added proper attribution. The statement lists the specific references:

Code references: Ant Design, rc‑tree (used in Grid, Tree, Typography components)

Technical principles or API design references: informed, formik, Material Component Web (used in BaseComponent, Form)

Images illustrating the statement and the referenced components are included below.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Reactopen sourcedesign systemSemi Design
Programmer DD
Written by

Programmer DD

A tinkering programmer and author of "Spring Cloud Microservices in Action"

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.