brett
371 posts

brett
@brettmcm
Designer Advocate @figma
Oceanside, CA Katılım Mart 2009
329 Takip Edilen400 Takipçiler
brett retweetledi

Building fast is table stakes now. The harder problem is whether what ships still matches what you meant (and whether you catch your blind spots before they ship with it). New article on what it can look like when the canvas and codebase stay in conversation.
figma.com/blog/workflow-…
English
brett retweetledi

The memory side of this was a compounding effort six months in the making.
A 4x reduction in out-of-memory crashes. 76% fewer weekly out-of-memory events. 71% reduction for our highest-risk files. We got there through smarter memory loading, more aggressive memory cleanup, geometry cache reductions, font unloading, and data structure optimizations that cut roughly 100MB of memory usage.
No single fix did it, but each one made the improvement larger. So proud of the team for the grit it took to deliver this win for our most complex files! 🫶
Figma@figma
Made some improvements to make your workflows faster. Like a lot faster. → Vector editing up to 10x faster → Make frame rates 4x smoother → Faster load times → 92% fewer memory warnings
English

"Working visually keeps me close to the problem and is slow enough gives me time to think while I work ... It is part of how clarity emerges.
There is something cathartic about that process, in the same way writing can be. Writing helps clarify thought because the act itself forces you to organize it ... The value is not only in the output. It is in the gradual understanding that comes through doing the work."
If this is not it, then you are not designing. You're sprinting to output. Which is fine. But don't call it design.
Karri Saarinen@karrisaarinen
English
brett retweetledi

brett retweetledi
brett retweetledi
brett retweetledi

Had a lot of fun designing some alternate app icons for Glass, all done in @figma Draw! Read more here: glass.photo/highlights/a-n…

English

Join me on the livestream next week exploring the latest updates to Figma MCP and what it means for creative workflows when an AI agent can directly control the Figma canvas!
Small, niche topic..
Figma@figma
Join @brettmcm and @trq212 → figma.bot/CCtoFigmaTw
English
brett retweetledi
brett retweetledi

@Dianadotlu this is lovely. one of the most human and intimate interactions with an AI workflow i've seen. do more.
English

SLOTS
Stoked to be a part of this feature launch! I know y'all have been waiting on this and patiently juggling local content components. The future is (now) composable!
Figma@figma
Behind-the-build for slots → Best practices → Use cases → Tips & tricks
English

@dannyjpwilliams tbh, i’m still getting used to the idea of not “maintaining” a source of truth in Figma. next challenge: build the habit of housekeeping the collection of Untitled’s in my Drafts.
English

@brettmcm great take and honestly hadn't considered this when posting!
I'm so used to having artifacts in figma that are "close enough" to what's in code already that i never thought "converting prod to figma would sure help".
English

Claude Code → Figma Design...
I can’t help but think… this feels backwards... right? 🤔
As a designer, the last thing I need is more* Figma files...
The real friction today isn’t:
code → design.
It’s:
design → code.
The most exciting tools in our space aren’t turning code into static mockups.
They’re helping designers ship.
Agentation -> @benjitaylor
skills. sh -> @vercel
Artifact -> @shopify design team
All of them push in the same direction:
Fewer static artifacts.
More execution.
More experimentation.
More craft in production.
Design isn’t about files.
It’s about bringing ideas to life.
Figma’s real opportunity isn’t becoming better at reconstructing UI from code.
It’s enabling a fluid, high-quality, low-friction path from canvas → live product.
Otherwise?
We risk watching @figma slowly become @Adobe... the irony!
Strong opinion. Loosely held.
But I think this moment matters.
What do you think?
Dylan Field@zoink
English








