Alex
alexmakesthngs.bsky.social
Alex
@alexmakesthngs.bsky.social
Founding product designer @Junior. Ex-PayPal, Hodinkee. Design systems geek.
With my ankles, I'd probably have the most fun on 2017-15, but I think you're good enough to stick the landing on the last month.
April 8, 2025 at 8:06 PM
Oh my god.

Hot take—if you’re not prototyping regularly in Figma, you don’t need interaction states in your components. Only build what you’re using.
February 15, 2025 at 6:43 PM
Also hello 👋 lol @justin.thrlkld.me sent me here bc we’re pals and he knows im a systems geek. 😂
February 15, 2025 at 6:39 PM
We’ve really jumped the shark with big components in Figma systems. I like slot components a lot, and the notion of “merchandising” UI elements. Ie: your card doesn’t need every possible version of it to be configurable. Just build common ones and make them available. And empower designers to riff.
February 15, 2025 at 6:38 PM
Yeah, I think we need to be prepared for an era really bad design next to really good design. These tools aren’t silver bullets, and I fear a lot of folks are going to think they are, and leave a lot of good habits behind in favor of speed. Also fewer junior and mid level roles (nothing new here).
February 15, 2025 at 6:36 PM
I think as with most things in design, it depends. It’s easy to over-engineer a Figma UI kit. But a well built system in code really speeds up your engineers. I think the way things are tracking, we’ll all be promoting AI tools to build interfaces with systems very soon (it’s already here).
February 15, 2025 at 6:32 PM