Charles Guillocher

I’ll start an experiment: design in public. Walking in the footsteps of “Build in public”, I want to try it for 2 reasons:

Nice error copy from Slack 🤌

we’re not really “designing” right now, we’re just constantly switching contexts trying to not get left behind every week there’s a new tool claiming to be the future → paper, pencil, magicpatterns, magicpath… now noon shows up with $44M and changes the narrative again so instead of going deep, everyone’s just sampling everything trying prompts here, generating screens there, tweaking in figma, jumping to code, back to AI again half the industry is already inside code editors the other half is still figuring out which tool is even worth committing to fomo is doing more damage than we realise because depth needs stability and right now the stack itself is unstable so no one is mastering anything everyone is just trying to be early eventually this will settle and a default will emerge till then, we’re all just beta testers pretending to have a workflow 👀

Created what I'm calling "zombie UI". @v0 moved a lot of the settings from the sidebar into a new settings modal. ... but we didn't tell anybody. After more than a few confused users, I whipped this up yesterday. It's a pattern that we can reuse I think, if/when UI changes around. Basically, there's a fake version of the old UI, when you click on it, it shows where it now lives, and then when you do the new action (open the modal) it deletes the zombie UI. I'm personally very opposed to full screen modals and videos showing what's new, as they intercept logged in users and usually just get dismissed. This seems like a good middle ground. It's live now.

Nespresso machine sound is the new dial-up modem.

Wow, so many interesting takes from the OG. open.substack.com/pub/jakobniels… Here are a few selected tidbits (continues in thread ⤵️)

Petite pétition du dimanche soir pour lutter contre la dérégulation agressive des droits qui nous protègent en tant que citoyens, travailleurs et PME. petitions.bloomassociation.org/fr/danger-omni…

This coins why even if I'm in love with the idea of vibe-coding/designing, leveraging AI has not felt like a 10x boost in speed or quality in my real day-to-day product work. Please change my mind.

when aligning icons with text, you can set the height to 1lh it equals the element's line-height, so icons align perfectly

Most product feedback sucks. It's an immediate gut reaction: "Ooh, I love this!" or "Meh." Want to get better at actually giving useful, actionable product feedback? Run yourself through these 7 questions. 1) What is the user journey to get here? You can’t furnish a room if you don’t know how someone lives. So learn the context: Who is the user? When do they use this product? Why? How did they arrive here, and what's on their mind? Don't critique unless you know this. 2) What do we want users to feel and achieve here? “If you don’t know where you’re going, you’ll end up someplace else.” Let’s understand what a successful outcome looks like before we start lobbing feedback about the design. 3) How important is this page/experience? In a perfect world, we make everything perfect. In the real world, let's spend more collective energy on the stuff that really matters. More eyeballs? More high-stakes? = more thorough inspection of every detail. 4) What is our scope/timeline/team? If speed is critical, let’s get the greatest bang for the least effort. If we have more time and people, then let's remove constraints (#7) and dream bigger. The "best" design differs according to the time/people/money you have. 5) For every proposed design change, am I confident it is better that what currently exists? If no: a) cut it b) iterate on / improve the design c) get more user feedback d) A/B test it 6) What can we remove from this experience and have it work just as well? When faced with a problem, we bias toward adding stuff to solve it rather than removing. So gut check if it's necessary. 7) If we could throw all our constraints away, would we still design it like this? While we can't typically throw all constraints away (see #4), it's still worthwhile to ask because we accept some things as constraints (due to legacy, etc) when they really aren't.

Did you know your MacBook has a sensor that knows the exact angle of the screen hinge? It’s not exposed as a public API, but I figured out a way to read it and make it sound like an old wooden door.

Pour Merali, ChatGPT c’est oui.

Ok if @lovable is paying him it's genius

Mother of All Toggles. 2025

@syswarren 1. Do you manage generating production-ready code, eg tailwind classes with custom variables ? (and if yes, how) 2. Is it faster than devs handling it overall?

what i like about implementing my own designs? it’s pixel perfect what devs like about my implementation? the free migraine that comes with trying to understand how the hell i got there

@CleanShot Is there a way to set a "fixed region template" (i.e. x,y,w,h)? The closest I've found is the URL scheme API but I'd like to do it from the app (or need guidance to do it outside of Arc). Thx!

Interesting collection of UI patterns for AI 👉 shapeof.ai

Spot on.