Design Tweet Examples - Copy & Post

bad design makes you feel stupid. good design makes you feel capable. the user's self-perception after using your product is a design outcome.

every 'quick design question' from a stakeholder is either a solved problem being re-opened or a new constraint that was never communicated. ask which one before answering.

the loading screen that doesn't communicate progress is a design failure. the loading screen that shows you something useful is a design opportunity.

the best UI is one the user doesn't notice. the worst UI is one the user can't stop noticing.

we spent 3 weeks on the visual design and 2 days on the onboarding flow. users dropped off at onboarding. lesson: design where the user actually is, not where you want them to be.

white space is not empty space. it's the visual equivalent of a pause. removing it to 'use more of the screen' is like removing pauses from a speech to make it shorter.

the designer who says 'users just need to learn how it works' has given up. the designer who redesigns until users don't need to learn anything has done the job.

typography is design. a page with bad typography and great layout is still a bad design. most people getting into design underinvest in understanding type.

the font that is 'fine' is the font that is wrong. every design decision either helps or hurts. nothing is neutral.

the best design feedback you can give: describe what you experienced as a user, not what you want to change. 'I felt confused here' is useful. 'make this bigger' is not.

consistency is more important than perfection. a slightly imperfect system that is applied everywhere is better than a perfect component used in three places.

if you're designing for all users, you're designing for no user. the most successful products are designed for one person and discovered by everyone who is that person.

the button that looks clickable but isn't is a broken promise. every design element creates an expectation. meet the expectations you set.

mobile first isn't a design constraint. it's a prioritization discipline. if it works beautifully on mobile, the desktop version is just more room to do it better.

the design that needs a tooltip to explain what it does has failed the design brief. the tooltip is an apology for the design.

your dark mode is not a feature if you built it in two hours. dark mode that's designed from first principles is a feature. dark mode that's just inverted colors is a lawsuit waiting to happen.

accessibility is not a feature you add at the end. it's a constraint you design within from the start. designing for accessibility makes the product better for everyone.

design debt compounds faster than technical debt because users feel it immediately and technical debt hides until it doesn't.

the most important design decision is what to not design. every feature you add competes for attention with every feature that was already there.

the designer who can explain why in business terms will have more influence over the product than the designer who can only explain why in design terms.

signs of taste in web ui: > every interaction happens in 100ms > no product tours > url /slugs are short and simple, no UIDs > persistent resumeable state > not more than 3 colors > no visible scrollbars > all navigation is under 3 steps > copyable svg logo + brandkit > skeleton loading states > copy paste from clipboard > larger hit targets for buttons/inputs > honest one click cancel > cmd + k > very minimal tooltips > copy is active voice, max 7 words per sentence > optical alignment vs geometric > optimized for L to R reading > reassurance about loss