Hand-picked since 2012
41 newer days available →
  • Building a UI without breakpoints by Amit Sheen

    While breakpoints were an excellent answer to a real problem when multiple screen sizes emerged, modern interfaces are no longer page-first. They are component-first, nested, and reused across wildly different contexts.

  • You're not behind by Joey Banks

    You’re not falling behind. You’re in the middle of learning something new, along with everyone else. Me included. The reminder I keep coming back to is this: we're designers, not our tools.

  • Every feature should earn its place by Karri Saarinen

    A common story in product development goes like this: execution is cheap now, so why not build more things and see what sticks?

  • Do researchers still need to take notes in interviews? by Phil Morton

    Don’t just default to your usual way of taking notes. Think about what data you’ll need at the other end, and design your notes around it. The analysis (human or AI) will be much better for it.

  • Design token naming conventions by Stuart Robson

    Naming design tokens can look and feel simple right up until you have to do it for real. Choose a weak pattern and things get inconsistent fast. Choose a clear pattern and you get a shared language that helps both design and engineering move quicker.

Read all week, picked once. The best design links — every Tuesday.

  • Advanced icon design: Dots by Helena Zhang

    We’ll cover optical effects that elevate icons from good to great, borrowing heavily from type design.

  • I love AI, but it still can't design for shit by Jonny Burch

    Without a critical human eye, AI produces slop. The quality bar is yours to maintain.

  • Good taste the only real moat left by Raj Nandan Sharma

    Taste has become a serious topic in tech. When everyone can produce something that looks decent, the advantage shifts to judgment.

  • Mouth coding by Brad Frost

    Lately, I’ve been talking websites into existence. Not metaphorically, but actually sitting in important meetings with people — clients, collaborators, my wife, friends, neighbors — watching real websites materialize in front of us as we converse.

  • Output isn’t design by Karri Saarinen

    Design keeps being misunderstood in our industry. New tools keep promising to generate interfaces faster, move words to product instantly, or collapse design directly into code. The assumption behind them is clear: that design is the act of producing.

  • Creating taste as a designer (video) by Brandon Jacoby, Michael Riddering

    Interesting thoughts on taste, being creative with AI, and how to thrive in a 0-1 environment.

  • Start designing in content, not in code by Pavel Samsonov

    Putting the cart before the horse is not giving you real velocity wins.

  • Figma's woes compound with Claude Design by Martin Alderson

    I think Figma is increasingly becoming a go-to case study in the victims of the so-called "SaaSpocalypse".

  • Sketches through the fog by Roger Wong

    Possible paths for where the judgment goes when AI handles the production.

  • FigClaw by Pavel Laptev

    A Claude-powered Figma plugin built around an agent loop — not a chat window.

  • Design isn’t dying. It’s shifting left by Alice Ferng, Chelsea Simek, Tony Chan

    When the model is the new medium, shaping how it behaves in humanistic ways is design.

  • Expansion artifacts by Matt Ström-Awn

    The real danger happens when expansion artifacts show up in the training data for the next generation of generative AI.

  • An artifact without an author by Gabe Kelley

    There's a kind of work that happens before anything gets made. It's the work of sitting with a decision long enough to actually believe in it.

  • Introducing Claude Design by Anthropic Labs

    Claude Design gives designers room to explore widely and everyone else a way to produce visual work.

  • Claude Design just dropped by Tommaso Nervegna

    Here's how it completes the designer's AI stack, and why you still can't delegate taste.

  • Design system archaeology by Murphy Trueman

    Software archaeology is a term engineers have been using for decades to describe reading legacy code you didn't write, and the design systems version needs the same name.

  • Charcuterie: A visual explorer for Unicode by David Aerne

    Browse the character set, discover related glyphs, and learn more about the scripts, symbols, and shapes that make up the standard.

  • Multi-stroke text effect in CSS by Yuan Chuan

    I kept stacking several elements and accidentally varied the text-stroke-width for each layer.

Share this day

HeyDesigner is the go-to newsletter for product people, UXers, PMs, and design engineers.

The week’s best design links — hand-picked, every Tuesday. Join 10,000+ designers.

No spam. Unsubscribe anytime. By submitting you agree to our Privacy Policy.