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.
Build full-stack apps in Figma Make.
Incredible working with the @payloadcms team to make this happen!
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.
Alex Kern retweeted
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
Alex Kern retweeted
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
Alex Kern retweeted
Breaking news: things are going well.
$FIG Q2 2026 results:
→ $370M in revenue
→ 48% YoY revenue growth rate, the 3rd straight quarter of accelerated growth
→ 136% Net Dollar Retention Rate
Alex Kern retweeted
hello there the jacobian conjecture is false thanx to my close friend akhil for asking about it and my other close friend fable for working during the world cup final
((1+xy)^3 z + y^2 (1+xy) (4+3xy), y + 3 x (1+xy)^2 z + 3 x y^2 (4+3xy), 2 x - 3 x^2 y - x^3 z): \C^3\to \C^3, has jacobian determinant -2, and sends (0, 0, -1/4), (1, -3/2, 13/2), and (-1, 3/2, 13/2) to (-1/4, 0, 0)
feeling nominatively determined
thanks for the 🎁 @pierscowburn
As we've launched Figma Code Layers, MCP Server, Motion, and generative shaders and plugins, I have been thinking about the role of prompting in the creative process.
In 1978, Card, English, and Burr at Xerox PARC showed that direct pointing with a mouse outperformed the alternatives they tested in both speed and accuracy because users could point directly to a target in one movement. This result became one of the foundations for modern graphical interfaces.
Less discussed are the other devices tested. While the mouse pointed at a target, the joystick expressed a velocity: keep moving in this direction. Although effective for exploration, joysticks required iterative refinement to reach a precise destination.
Prompting is AI’s velocity input. Like a joystick, it communicates how a system should move, rather than where it should end up. It launches a search through an enormous solution space with remarkable efficiency, making it an incredible interface for exploration, ideation, and rapidly converging on promising directions.
But exploration eventually gives way to refinement, and every constraint comes into focus. Direct interaction with the artifact—be it code or design—provides a fidelity that is difficult to capture through natural language alone. Every dependency, every pixel, every interaction matters.
Each interaction model excels at a different level of precision. In a nutshell, prompting tells the computer how to move, while direct manipulation tells it exactly where to stop.
We’ve been talking a lot at Figma about how prompting and direct manipulation complement one another. Our research team recently dug into how design, code, and AI are converging, and even quantified how these disciplines are blending in practice. It’s well worth a read. 🔗⤵️
