Designer's Manifesto

I am a designer.

I may not be erudite, but I understand the taste of pain. Through countless project refinements, I haven't learned a set of grand theories, only grasped some stubbornly simple truths.

Complexity is the root of all evil

I despise complexity. Whether it's the myriad buttons on design software or the rigid rules in design systems, they both give me a headache. There's a saying that goes well: "If your design requires a manual, then it's too complex by itself."

I seek to convey the richest meaning with the fewest shapes. My button should look like a button, not a bird.

Fewer options are better

When I see a Figma file with ten variants of the same component, I truly lose my mind. My experience is: instead of offering ten "maybe okay" options, it's better to focus on refining one truly useful one.

I will firmly say "no" to the following:

• Flashy hover effects like a spaceship taking off.
• Custom scrollbars that only work on Tuesdays.
• Colors with pretentious names like "Soul Mist Blue".

I'll just use gray, which is clear and reliable.

High information density is good

Many designers cherish whitespace, but I don't. I believe whitespace is only valuable when it helps the brain quickly identify information. Excessive whitespace only leads users to constantly scroll, exhausting their brains. I prefer information-dense interfaces that present all tools at a glance.

Remember, "simplicity" doesn't mean emptiness; the true meaning of "simplicity" is "solving problems in the fastest way possible".

Grids bring order

I don't believe in so-called "magic layouts" or intuitive alignment; I only use grids. Grids make everything fall into place, bringing inner peace. I will align text and images strictly, rather than placing them by "feeling".

Typography is sound

I usually choose only one core font and never mix seven or eight fonts on a page. Before starting, I ask myself: is this font shouting, whispering, or echoing in a cave? I don't need to use "ultra-fine condensed italics" to show an error message; that's absurd.

Icons are for communication, not art

My purpose is not decoration, but communication. If an icon requires a text tooltip to be understood, it's not a good icon. I like icons that look exactly like what they represent, simple and clear.

Processes serve people

I despise rigid processes like "design sprints" and hate "review meetings" where no one speaks truthfully. I enjoy prototyping and observing difficulties users encounter in actual use. The simple cycle I believe in is: "Do it → Test it → Frustrated reflection → Revise".

Systems are not religions

Design systems are good things, but if they force me to do stupid things that harm user experience, I will question them. I always remember: systems are created by people, and people can change them at any time. They serve me, not the other way around.

Defend user experience

When I present design drafts, a group of leaders often surrounds me and says, "Make the logo bigger again." I nod on the surface but internally choose to ignore them. My duty is to protect users from the interference of amateurs.

Fight alongside engineers

I work closely with engineers from the very beginning, rather than simply tossing design drafts to them. I know they dislike complex shadows like "8px blur, 3.6% opacity" and vague requirements like "make the animation feel natural." I communicate with them, we compromise, and ultimately reach consensus to create something that can actually be implemented.

Users' feelings matter more than peers' likes

I don't design to get likes on design websites; I design to make users no longer suffer. Something beautiful is not necessarily useful, but clear design is never wrong. Users never say "Wow, your new material design is awesome," they only ask "Where is that button?".

I don't want design awards; I just want what I make to be usable and easy to use.

The moment when users completely don't notice my existence because everything flows naturally and smoothly is the happiest moment for me.