


code and canvas. @figma ai via @dynaboard, prev @coinbase via @_dsys, @CalHacks


$FIG Q3 results: → $391M in revenue, 43% YoY growth rate and $16M above high-end of prior guidance → 131% net dollar retention rate → 36% YoY growth in non-GAAP gross profit → $1.7B in cash, cash equivalents and marketable securities → Raising our outlook for FY 2026

Excited to share more about the work behind Figma's first-party model: a specialized model for design editing that competes with top models. When we set out to build an agent, we wanted a model that understands design concepts and Figma's tools to help you quickly make edits on the canvas. We started with supervised fine-tuning (SFT) using Figma's native file format, pairing designs with synthetic edit requests. Deterministic validators, visual judges, and a self-healing pipeline helped evaluate and refine our outputs. We've since added reinforcement learning (RL) to our recipe to push for more improvements. Design is subjective, but we can still evaluate structural correctness, visual alignment, and request fulfillment using judges calibrated with expert designers. That includes checking whether an edit preserves everything it should. AI models often create unintended changes like dropped text or mismatched chart labels that we need to catch. Proud of the work of our incredible AI research team. Read more about the model here, and if this work sounds interesting, come join the team!
Figma @figma Oct 29 Article How we’re training a Figma-fluent editing model We’ve increasingly seen that specialized post-training can compete with frontier models. Here, we’re sharing the research behind how we’re translating that to design editing workflows. Designers use



ReLU is All You Need
My dear friends, I’d like to show you my latest toy project Introducing Handwired: turn your regular JavaScript code into a neural net! - no training - exact outputs vs the JS program - fully differentiable All runnable in a browser, without GPU

Code is the material
you'll do your best work in a tool that allows you to be whimsical, too! 🔊🔊🔊 — lol i've lost hours building fun stuff like this with code layers… @figma code layers starting to roll out into open beta TODAY! incredibly excited to see what you'll cook!



Today’s the day. Code layers rolling out now. Push and pull from real repositories, instantly branch with option-drag, and build anything you can dream of with best-in-class models and MCP support.
When we announced Code Layers earlier this year, we wanted design and code to live side by side so you can collaborate with code directly on the Figma canvas. Excited to share it's now rolling out in open beta!



Specs have transformed how we build at Figma. Integration with Code Layers, the Figma Agent, and Figma MCP Server makes them so much more than a markdown editor: they’re collaborative artifacts for you, your teammates, and your agents to get work done together.
Introducing Specs! A new medium for markdown on the Figma canvas. You can think of Specs as a container for your context. Use MCP, Github, etc to move context in/out of Figma and across the Figma platform. Specs is rolling out in open beta over the next few weeks!


Gemini 4 Argon is now rolling out to Figma Make Early tests show it’s great for: → Building interactive prototypes, 3D visuals, and games → Creating detailed SVG animations and realistic motion effects → Independently exploring visual directions before choosing one → Tackling complex, multi-step coding tasks

codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software. swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go. admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?". well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is: • correct • bug free • fast and cost efficient to run it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start. but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing! agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale. the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree
