返信の攻略ガイド · Design
What designers post on X, the reply angles that get a designer to answer, six sample post and reply pairs, and the mistakes that read as noise.
Design X is product designers, brand designers, illustrators and design engineers posting work in progress, redesign breakdowns, typography opinions and the occasional story about client feedback. Most of it is visual: a screenshot or a short screen recording with one line of text.
That makes a good reply rare and valuable, because most people like the image and scroll on. A reply that notices one specific choice, like the spacing on a button or the weight of a heading, proves you looked. Designers answer people who looked.
01
A screen or a logo at an early stage. The author usually wants feedback on one thing, so read the caption to find out which.
02
Two screenshots side by side. The best replies ask about the constraint that drove the change.
03
Fonts, grids, dark mode, motion, icon styles. Strong takes that invite a counterexample from a product people know.
04
Feedback rounds, "make the logo bigger", handoff to developers. Shared frustration, with room for a useful aside.
01
Name the exact element you noticed and why it works. "The way the shadow is offset 2px down" beats "love this" every time.
02
Every design decision has a reason behind it, often a brand rule or a dev deadline. Asking which one shaped this screen gets a long, generous answer.
03
Mention how the screen behaves for someone using it for real: one hand on a phone on a train, a very long name in a field, a user with low vision.
04
When someone says "never do X", name a product where X works and say why in one line. It starts a conversation instead of a fight.
05
If you build or ship designs, a reply about how the thing will survive implementation is useful and rare. Designers want to hear it before the dev does it differently.
このページのために書いた投稿例です。実在のアカウントではありません。
ポスト
Redesigned our onboarding. Cut it from 6 screens to 3. Feedback welcome.
返信
the 3 screens look great. where did the content from the other 3 go, later in the app or cut entirely? that's usually where activation changes
ポスト
Unpopular opinion: pure black backgrounds in dark mode are a mistake. Use a dark grey and your shadows start working again.
返信
mostly agree, except on OLED phones where some people turn dark mode on to save battery. would you ship two themes or just pick the grey?
ポスト
Client asked for the logo to "pop more" for the third time this week.
返信
next round try showing it at the size it'll actually be used, like a 32px favicon. the "pop" requests tend to stop once they see it tiny
ポスト
Spacing scale I use on every project: 4, 8, 12, 16, 24, 32, 48, 64. Nothing else allowed.
返信
what happens when a dev needs 20 for a one-off? I've never kept a scale clean past the first handoff without a lint rule
ポスト
Spent the whole day on empty states. Nobody will notice them and that's the point.
返信
for a lot of features the empty state is the first screen a new user ever sees, so someone notices. what did you put in the search one?
ポスト
Hot take: your portfolio needs fewer case studies. Three deep ones beat ten shallow ones.
返信
hiring side here: I read the first case study and the first paragraph of the second. so the order matters more than the count