We scan new podcasts and send you the top 5 insights daily.
Prompting AI for code changes is an inherently solo activity. By importing code into Figma, teams can leverage its native multiplayer features. This allows for real-time, parallel collaboration and ideation that is impossible to replicate in a single-user IDE environment.
A key reason Figma won was its cloud-based, real-time collaboration. The trend of using local AI dev tools (like Cursor) is a step backward in this regard, reintroducing friction around sharing work and getting feedback, the very problems that led designers away from local files in the first place.
Production code often evolves past design files, creating workflow friction. Figma's MCP tool uses AI to pull live application states directly into design files and push updates back to code, creating a synchronized source of truth.
The handoff between AI generation and manual refinement is a major friction point. Tools like Subframe solve this by allowing users to seamlessly switch between an 'Ask AI' mode for generative tasks and a 'Design' mode for manual, Figma-like adjustments on the same canvas.
Early user research showed designers did not want a collaborative, multiplayer tool. However, Figma's web-based architecture made a single-player experience technically terrible (e.g., tabs constantly reloading). They were forced by the technology to build multiplayer functionality, which ultimately became their key differentiator, proving the platform's needs can override initial user requests.
Using AI agents in shared Slack channels transforms coding from a solo activity into a collaborative one. Multiple team members can observe the agent's work, provide corrective feedback in the same thread, and collectively guide the task to completion, fostering shared knowledge.
The IDE Zed was built for synchronous, Figma-like human collaboration to overcome asynchronous Git workflows. This foundation of real-time, in-code presence serendipitously created the perfect environment for integrating AI agents, which function as just another collaborator in the same shared space.
Today, most AI use is siloed, with individuals prompting alone. The real value is unlocked when AI becomes a team sport, with specialists building systems that are shared, iterated upon, and used collaboratively across the entire organization.
While chat works for human-AI interaction, the infinite canvas is a superior paradigm for multi-agent and human-AI collaboration. It allows for simultaneous, non-distracting parallel work, asynchronous handoffs, and persistent spatial context—all of which are difficult to achieve in a linear, turn-based chat interface.
Figma's CEO argues that while agentic coding systems are powerful, they risk being too linear. True product innovation requires exploring a wide option space through design, using systems and components to ensure a cohesive user journey. Relying solely on code generation can lead to a suboptimal product, even if it's built quickly.
Tools like Figma's MCP act as a connector, allowing designers and engineers to work on the same component simultaneously from their preferred environments. This creates a new, fluid, back-and-forth workflow that resembles pair programming for design and code.