Marcin Wichary, Design Architect at Figma, made this interactive essay about fingers, latency, and why our interfaces still fail the hands using them. Starting with 1890s typists who routinely hit 70 wpm when scientists said 40 was the ceiling, he traces a direct line from terminal echo buffers and UI blocking to Notes on a Mac that can’t keep up with your typing in 2026. The embedded demos — where you feel the difference between a blocked UI and a parallel thread — do more to explain debouncing and latency than any amount of text could. This essay is a fantastic companion to Marcin’s Unsung blog on software craft and quality.

Nikita Prokopov makes the case that great UI isn’t just about nailing the start and end states of an animation, it’s about every frame in between. His rule of thumb: if you freeze the screen at any moment, you should be able to explain what you’re looking at. The post walks through a set of GIF examples — from Safari’s misaligned cursor-and-placeholder animation to YouTube’s inexplicable rectangle transition — showing how mid-animation frames that don’t hold up on their own erode user trust.

“As code becomes cheaper, an increasingly large portion of it is written for prototyping, not production.” Yitong Zhang argues that prototype coding and production coding are diverging into distinct disciplines with near-opposite requirements: prototyping wants speed, mock data, no types, no tests, and wide-ranging agents; production wants the opposite. Cursor, Stripe, and Notion have already shown this with their internal playground environments — and Figma just needs to follow that path. Parallel design exploration means more inference runs, less complexity per run, and better margins than production – making Figma one of the best-positioned companies outside the labs to run agents at scale.

“Behind products that just ​‘feel good’, there is an insane amount of design and engineering that you never get to see.” Enri Tarta got rare access to Figma’s product team for a day, and the result is the kind of process tour we almost never get to see.

A design vocabulary guide by Emil Kowalski and Glenn Carstens-Peters. 188 terms across 12 categories — typography, color, layout, IA, accessibility, measurement — defined with the precision designers reach for when they actually know what they’re looking at. It’s a preview of a larger ​“design education for an era of change” arriving fall 2026.

The Community profile redesign adds role, experience, tech stack, pinned work with images and links, and social channels. Combined with the FigPal customization, it reads less like a profile page and more like a creator landing page. Figma clearly wants Community to function as a discovery layer for designers, not just for resources.

Soleio’s guest is Rasmus Andersson: founding designer of Spotify, one of Figma’s first designers, co-creator of GraphQL, and creator of Inter. The part that stayed with me is his description of how Figma operated: one person on one problem for a year, sometimes binned at the end, while shipping something visible every month. He also makes a case that the production side of design — the part AI is eating fastest — was never actually the hard part. What’s left is the intention. The other link in this section is Soleio’s talk on the geometry of luck, making this pair worth watching together.

“Luck isn’t something that you have. It’s something that you leave behind.” Soleio — designer of the Like button and angel investor in Figma, Cursor, and Framer — delivered this as the closing line of his Tokyo Design Forum talk, and it’s the kind of sentence that reorganizes how you think about a career. The talk, now archived by The Forum Library, reframes luck as a generative force you shape through how you live and work, not a resource you accumulate.

Matt Colyer, Figma’s director of product management for developers, makes the case on Dan Shipper’s AI & I podcast that the SaaS apocalypse narrative has it exactly backwards. He’s been running his own agents for two years and is buying more software subscriptions than ever, because shipping and maintaining a personal agent teaches you fast why people pay for someone else to run it. The more interesting half is about design specifically: chat is linear, which makes it good at converging on a single direction but terrible at generating lots of options. Figma’s on-canvas agent is a first attempt at the divergent side — letting you branch frames in different directions, then bring in a convergent agent to cluster them. He also walks through how the MCP server closes the code-to-design loop, and why ​“review” has quietly become the biggest bottleneck in AI-assisted product work.