Figma

532 posts

figma3 min readCurated summary

7 Moments That Shaped Figma, as Told by Dylan Field | Figma Blog

Figma’s story, as told by co-founder Dylan Field, was shaped by unlikely experiences, persistent experimentation, and lessons from mentors and early mistakes. His path ran from child acting and mathematical curiosity to founding a company at 20, with setbacks—including a brief meme-generator idea—helping clarify Figma’s direction. ## Persistence Learned Through Acting - As a child actor, Field once fell asleep during a *Peter Pan* performance, which he considered his most embarrassing acting moment. - The experience nevertheless gave him stunt-flying skills that helped him land a Windows XP commercial. - Auditioning taught him that persistence over time can create opportunities: continuing to try increases the chances of eventually succeeding. ## A Janitor Sparked His Interest in Mathematics - Field was solving algebra problems as early as age six and became bored in middle school. - He spent time with a cerebral school janitor who discussed mathematics and physics with him. - The janitor encouraged him to study proofs and set theory, pushing Field toward deeper mathematical thinking. ## An Unusual Fellowship Application - Applying for the Thiel Fellowship, Field answered the question about what most people get wrong by arguing that “chocolate is repulsive.” - He treated the response as a “meta-contrarian” idea—challenging not only conventional wisdom but also Silicon Valley’s tendency to prize contrarian opinions. - The playful, unexpected answer may have helped his application stand out. ## Figma Briefly Considered Becoming a Meme Generator - Field and Evan Wallace initially wanted to use WebGL—the JavaScript API for high-performance graphics in browsers—to build a design product. - Unsure how to apply the technology, they briefly considered making a meme-creation tool. - Field called this five-day period Figma’s “darkest week,” after realizing that memes were not a sufficiently serious direction. - The episode illustrates the founders’ willingness to explore ideas before committing to a larger product vision. ## Growing Into Leadership - At 20, Field struggled with the responsibilities of being CEO after previously identifying more like an intern. - He acknowledged micromanaging because he had intensely considered every part of the product experience. - Pressure to launch and control the details created tension, teaching him that building Figma required developing as a manager as well as refining the product. The post presents Figma’s development as the result of accumulated experiences rather than a perfectly planned startup journey. Field’s advice and example emphasize persistence, intellectual curiosity, experimentation, and the willingness to learn from immature decisions.

Read original(opens in new tab)
figma2 min readCurated summary

Welcoming Payload to the Figma Team | Figma Blog

Figma has welcomed the team behind Payload, an open-source headless CMS and application framework, to strengthen its developer tools and connect design more closely with development. Payload will remain open source, with continued investment and no immediate changes for users. The partnership supports Figma’s broader vision of letting teams design, build, and deploy digital products within a collaborative ecosystem. ## Why Figma Chose Payload - Payload is known for its highly customizable architecture, extensibility, and strong developer experience. - It has become one of the leading open-source projects in its category and is used by several Fortune 100 companies. - Figma was especially impressed by Payload’s active open-source community and its practice of incorporating developer feedback into the product. - Both companies emphasize collaboration, community participation, and continuous improvement. ## What Happens to Payload - Payload will remain an open-source product. - There will be no immediate changes for existing users. - Figma plans to continue investing in the project and improving it. - Figma and Payload users will receive ongoing communication as the combined CMS strategy and product roadmap develop. ## Bridging Design and Development - Figma aims to become a central hub where teams can create and deploy digital products. - Payload’s CMS and framework capabilities can help connect Figma’s design tools with production websites and applications. - As AI accelerates the generation of code and content, controlling deployments and refining user experiences across channels becomes increasingly important. - The partnership is intended to reduce the traditional gap between designers and developers. ## The Broader Context - The announcement follows Figma’s push into web publishing through Figma Sites. - Payload’s flexibility and developer-focused tools could expand what developers can build across Figma’s platforms. - The companies expect their combined teams and communities to create more integrated design, development, and content workflows. Figma’s acquisition of the Payload team is positioned as a long-term investment in collaborative, developer-friendly product creation, while preserving Payload’s open-source identity and existing user experience.

Read original(opens in new tab)
figma3 min readCurated summary

What They’re Not Teaching in Design Class—and What You Can Do About It | Figma Blog

Design education often teaches craft and user experience but not how design affects revenue, costs, growth, or product strategy. The authors argue that business fluency and product sense make designers more effective collaborators and decision-makers. Early-career designers should build these skills beyond the classroom through business courses, conversations with professionals, industry media, and hands-on product work. ## Why Business Matters in Design - Design choices influence user engagement, retention, growth, and profitability. - Poor experiences can frustrate users and cause them to abandon a product. - Designers need to balance user needs with business goals and stakeholder priorities. - Business knowledge helps designers: - Understand how decisions affect revenue and costs - Prioritize features in response to market competition - Contribute to product roadmaps - Communicate more effectively with product, research, marketing, and business teams - Leaders from Figma, Microsoft, and Netflix describe business acumen as a major distinction between good and exceptional design organizations. ## The Gap in Design Education - Many design programs focus heavily on design fundamentals and craft. - Early-career designers often receive little instruction on connecting their work to measurable business outcomes. - The authors discovered this gap through their experiences as Figma Campus Leaders and early-career product designers. - They argue that creative quality and business impact should not be treated as opposing priorities; combining them can be a designer’s “superpower.” ## Take Business and Marketing Courses - Students should supplement design coursework with classes in fields such as marketing and business. - Case-study-based courses can show how companies approach market, customer, and product problems. - Even courses without a direct UX focus can help designers understand how products are positioned, launched, and evaluated. ## Learn from Industry Professionals - Coffee chats provide practical insight into how products are actually developed and how companies succeed. - Designers should speak with more than product designers, including: - Content designers - UX researchers - Business researchers - Product and marketing professionals - These conversations reveal how different stakeholders contribute to product decisions and understand industry economics. ## Follow Product and Business Discussions - Newsletters and podcasts can help designers connect design decisions with broader business trends. - Recommended resources include: - **Lenny’s Newsletter**, focused on product building, growth, and careers - **Masters of Scale**, featuring advice from business leaders - **Dive Club**, which interviews design executives about product experience and organizational strategy ## Build and Ship Real Products - Hands-on work is presented as one of the most effective ways to develop product sense. - Student startups, industry roles, and other practical projects expose designers to constraints that classroom exercises often miss. - Building and shipping products teaches designers how ideas perform in the real world and how design interacts with product and business decisions. Designers should treat business understanding as a core part of their professional education, even when their formal programs do not. Combining design craft with product sense enables them to create work that is both valuable to users and meaningful to the organizations building it.

Read original(opens in new tab)
figma2 min readCurated summary

The Long and Short of It: Issue no.11 | Figma Blog

AI is changing how people build, but Figma argues that it does not replace craft, quality, or emotional connection. The issue highlights tools and practices that combine automation with design intent, context, safety, and care. Its central conclusion is that meaningful work still requires human judgment and deliberate practice. ## Building with Figma Make - Figma Make is a prompt-to-code tool that turns natural-language prompts or static designs into interactive prototypes. - It can be used at different stages of the design and development process. - Figma recommends experimenting with prompts and applying practical techniques to get better results. ## Bringing Design Context into Coding - Agentic coding tools are limited when they lack context about the intended design. - Figma’s MCP server connects Figma files to AI coding tools. - It gives language models access to variables, components, and styles, helping them generate code that better reflects design intent. - This positions AI as part of the developer workflow rather than an isolated automation tool. ## When Efficiency Undermines Care - The issue examines the idea that excessive focus on efficiency can weaken connection and emotional investment in creative work. - Themes from Config 2025 include AI evolving from a tool into a teammate and the importance of reaching “minimum viable play.” - The broader message is that faster production should not come at the expense of thoughtful, resonant design. ## Designing AI with Trust and Transparency - Headspace’s Ebb AI mental-health companion was designed with trust and safety as priorities. - Product and brand teams considered details such as the character’s name, visual identity, and conversational guidelines. - The goal was to keep Ebb’s AI nature visible while ensuring users felt supported. - The example illustrates the additional responsibility involved in creating AI products for sensitive contexts. ## Craft Requires Practice - Figma’s third annual Config publication, *Practice*, explores how designers develop mastery. - It emphasizes patience, precision, experimentation, and a willingness to push boundaries. - The accompanying microsite, created with Other Means, includes a custom font by Kia Tasbihgou. ## Rabbit Hole - The issue closes with a visual collection of colorful abstract forms, collages, and photography, extending its focus on experimentation and creative inspiration. AI can accelerate making, but strong results still depend on context, care, taste, and practice. Figma’s recommendation is to use AI as a creative partner while preserving the human attention that gives work its meaning.

Read original(opens in new tab)
figma3 min readCurated summary

8 Essential Tips for Using Figma Make | Figma Blog

Figma Make works best when users provide clear context, prepare clean design files, and refine complex projects incrementally. Detailed initial prompts reduce revisions, while organized Figma layers and Auto Layout help designs translate into functional prototypes. For ambitious builds, breaking work into focused prompts and separate code folders improves control, maintainability, and debugging. ## Provide Detailed Initial Prompts - Include: - The task Figma Make should perform - Product or flow context - Essential design elements - Expected interactions and behaviors - Device, layout, and visual constraints - Front-loading requirements helps produce a stronger first version with fewer follow-up prompts. - Use precise, measurable instructions instead of vague requests: - “Move this element down 20 pixels” - “Add 16px of space between these buttons” - If repeated adjustments are not working, restart with a new file and use lessons from the first attempt. - Effective project prompts can include an overview, platform, purpose, features, visual direction, technical details, and an explicit first implementation step. ## Clean Up Figma Files Before Importing Them - Figma Make can either create new designs or turn existing Figma frames into interactive prototypes. - Before copying a frame into Figma Make: - Organize the file - Apply appropriate constraints - Use Auto Layout correctly - Name layers according to their purpose - Figma tools such as Suggest Auto Layout and Rename Layers with AI, along with plugins like Clean Document, can help prepare files. - If the result is too large or not responsive, use prompts such as: - “Scale this to the size of my screen and make it responsive.” - “Keep this mobile-sized.” - A well-structured Auto Layout design can enable complex interactions from a single prompt, such as making a CD spin when a music player starts. ## Build Complex Projects Incrementally - Use a detailed first prompt to establish the overall foundation, then make smaller, focused changes. - Smaller requests allow the model to respond more precisely and reduce the risk of unwanted changes elsewhere. - Incremental prompting is useful for: - Building complex interfaces - Creating multi-page flows - Adding individual features - Maintaining the intended visual direction - Ask Figma Make to place separate elements in separate code folders to improve organization, maintainability, and error isolation. - Large projects may require many prompts; one financial dashboard and onboarding flow took more than 150 focused iterations. - Example follow-ups included adding journal post-its, inserting a detailed finance table, and adding a currency-selection checkbox. - Separating 3D landmarks into individual coded files similarly makes it easier to refine components without affecting the wider environment. Use Figma Make as an iterative design-and-development tool: prepare the source file carefully, describe the desired result precisely, and make complex changes one manageable step at a time.

Read original(opens in new tab)
figma2 min readCurated summary

Bill Atkinson’s 10 Rules for Making Interfaces More Human | Figma Blog

Bill Atkinson’s work at Apple showed that powerful technology can feel natural, accessible, and even joyful. Through QuickDraw, MacPaint, and HyperCard, he transformed complex computing tasks into intuitive creative experiences. The post distills his approach into principles centered on designing within limits, democratizing creation, challenging assumptions, and making interfaces disappear into the user’s work. ## Designing Within Constraints - Atkinson developed QuickDraw for the original Macintosh, which had only 128KB of RAM and limited processing power. - Instead of lowering the ambition for smooth graphics, he created highly efficient algorithms for drawing shapes and curves. - His approach favored elegant solutions that respected constraints rather than brute-force hardware improvements. ## Democratizing Creativity - HyperCard aimed to let people create interactive software without years of programming experience. - Its visual tools and natural-language scripting enabled teachers, artists, and businesses to build their own applications. - Atkinson believed transformative tools should serve everyone, not only technical specialists. ## Making Interfaces Feel Inevitable - Atkinson helped establish interface conventions such as the menu bar, double-clicking, and smooth graphical interactions. - These features made drag-and-drop and point-and-click computing accessible to non-programmers. - Great interface design, in this view, lets users focus on their work instead of the software. ## Questioning Conventional Wisdom - Atkinson challenged assumptions that computing had to be text-based or that bitmap editing was too difficult for ordinary users. - He later acknowledged that HyperCard’s architecture was limited by Apple’s “box-centric” worldview and might have become an early web browser in a network-oriented environment. - Designers should scrutinize ideas that seem obviously correct or impossible. ## Optimizing for Delight - MacPaint was designed to be immediately understandable, even to young children. - Tools such as the brush and paint bucket behaved like their real-world counterparts. - The goal was not merely task completion, but encouraging experimentation, play, and creative exploration. Atkinson’s legacy suggests that human-centered software combines technical rigor with empathy: work within limitations, remove unnecessary complexity, and make creation feel inviting.

Read original(opens in new tab)
figma2 min readCurated summary

Double Click: What Does MCP Mean for Agentic AI? | Figma Blog

MCP is emerging as a common interoperability layer between AI assistants and external tools or data sources. By allowing models to discover and invoke tools during a conversation, it can make agentic systems faster, more scalable, and less dependent on bespoke integrations. The growing ecosystem—including Figma’s own MCP server—suggests MCP could become foundational infrastructure for the agentic web. ## What MCP Is - Anthropic introduced the Model Context Protocol in November, 2024; support from OpenAI helped drive widespread adoption. - MCP standardizes how assistants such as Claude, Copilot, and Cursor communicate with tools and data. - Developers can avoid building separate custom integrations for every AI assistant and service. - The protocol is compared to: - **USB-C**, as a universal connection for AI applications. - **HTTP**, because it is lightweight, composable, interoperable, and largely unconcerned with the payload. - Microsoft CTO Kevin Scott described MCP as a potential backbone for agent communication and evolution. ## MCP and Agentic AI - MCP gives large language models real-time access to tools and information. - This enables AI agents to act on a user’s behalf rather than merely generate text or code. - The number of available MCP servers is growing rapidly. - Figma created an MCP server that connects design information directly to developer workflows, supporting design-informed code generation. ## MCP as an Accelerant - Traditional API-based workflows often require an LLM to generate code and execute it whenever it needs to interact with a tool. - With MCP, the model can recognize available tools and invoke them directly during a conversation. - This reduces friction and improves speed, efficiency, and scalability. - The resulting experience makes complex actions feel more immediate—users can increasingly “just do things.” ## Early Examples of MCP Use - An automated AI travel agency used four agents across Google Maps, Airbnb, Google Calendar, and Weather. - A Blender MCP server generated a 3D scene of a low-poly dragon guarding treasure from a few natural-language instructions. - Y Combinator hosted a large MCP hackathon, demonstrating the rapid growth of experimentation around the protocol. MCP’s main promise is not simply connecting AI to APIs, but creating a shared, extensible standard that lets agents use many tools dynamically. Its long-term impact will depend on how reliably and responsibly these increasingly capable systems operate.

Read original(opens in new tab)
figma3 min readCurated summary

Introducing our MCP server: Bringing Figma into your workflow | Figma Blog

Figma’s beta MCP server connects Figma to AI coding tools such as Cursor, Copilot in VS Code, Windsurf, and Claude Code. It gives LLMs richer design context than screenshots or API responses alone, helping them generate code that reflects a team’s design system, codebase patterns, and intended behavior. Figma argues that accurate design-to-code work requires a holistic understanding of both visual design and implementation context. ## Why Design Context Matters - LLMs can produce functional code without additional context, but it may not match a team’s: - Architecture and file structure - Framework and terminology - Existing components and workflows - Evolving codebase conventions - These team-specific patterns form a unique “fingerprint” that models cannot reliably infer from training data. - MCP provides a standardized way for applications such as Figma to supply targeted context to agentic AI tools. ## Translating Design Intent for LLMs - Human developers typically: - Zoom out to understand overall structure and layout - Examine screen sequences and application flows - Infer how designs should map to code files and components - Interpret placeholder content as real data or backend requirements - Move between high-level patterns and low-level implementation details - The Figma MCP server aims to give LLMs the same broad perspective. - Its tools expose different kinds of context, allowing users to control which information is included and avoid wasting context-window space. ## Pattern Metadata - Figma can provide references to specific: - Components - Variables and design tokens - Styles - Code files - This is especially useful when design and code are already aligned through a design system. - Code Connect can identify the exact code component associated with a Figma component, reducing unnecessary codebase searches and preventing duplicate implementations. - For design tokens, Figma can identify the precise variable used—even when several tokens share the same visual value. - If code syntax is defined for a variable, the MCP server can pass the exact implementation syntax to the LLM. - Supplying this metadata improves precision and reduces token usage. ## Screenshots - Screenshots supplement metadata when visual or interactive meaning is difficult to express structurally. - They can communicate: - Embedded or interactive content represented by imagery - Relationships between sections and nodes - Sequences of screens - Mobile and desktop layouts - Overall application flow - Screenshots are not intended as pixel-perfect specifications. - Figma emphasizes that generated code should reflect design intent rather than merely reproduce pixels. - Combining screenshots with Figma’s code-oriented outputs is more effective than relying on either alone. ## Interactivity and Behavior - Code examples and pseudocode can express behavior more effectively than raw design metadata. - They are useful for: - Stateful components - Encapsulated functionality - UI sequences and transitions - Differences between related states or screens - Pseudocode becomes more valuable when it incorporates codebase context, such as variable syntax and Code Connect component mappings. ## Beta Roadmap - The MCP server is an early beta release. - Figma plans to add remote server capabilities and deeper integrations with codebases. - The company is seeking feedback while continuing to expand the design-to-code workflow. Figma’s MCP server is most valuable when teams maintain strong alignment between their design systems and codebases. Combining structured metadata, visual context, and behavioral examples gives AI coding agents a better foundation for producing implementation-ready code.

Read original(opens in new tab)
figma2 min readCurated summary

Double Click: Does Efficiency Kill Love? | Figma Blog

Config 2025 framed AI less as a tool for maximizing efficiency and more as a way to deepen connection, care, and creative purpose. The article contrasts the slogan “Efficiency kills love” with the idea that “Design is chasing a feeling,” arguing that craft and intentionality should remain central as technology accelerates. AI’s role, therefore, depends on the values people choose to embed in it. ## From Efficiency to Care - Figma’s community expressed renewed enthusiasm for craft, emotion, and meaningful creative work. - Smith & Diction’s presentation, “The Wild West of Collaborative Brand Design,” captured the mood with the declaration that “Efficiency kills love.” - Figma CEO Dylan Field’s keynote offered a complementary idea: “Design is chasing a feeling.” - Together, these statements suggest a shift away from treating productivity and speed as the sole measures of successful design. ## Craft as the Conduit - Yang You, Head of Design at Paradigm, summarized the emerging attitude: “Craft is king, and care is the conduit.” - Designers are looking beyond target metrics and faster workflows toward: - Storytelling - Purposeful making - Emotional resonance - A sense of magic and meaning - Microsoft design leader Brittany Mederos similarly described Config’s theme as making meaningful things with purpose. ## Technology Should Reflect Human Values - Madeline Gannon argued that automation is not inevitable; it is intentional and reflects collective cultural choices. - This reframes AI from an unstoppable force into a technology shaped by human decisions about what should—and should not—be automated. - The central question becomes not simply what AI can make faster, but what people want to create with it and why. ## Slowing Down in an Automated World - Polaroid’s approach illustrates how technology can support, rather than replace, human creativity. - Its app provides AI-powered photography advice while preserving the company’s emphasis on slowing down, making physical things, and creating objects with personal meaning. - The example suggests that even advanced tools can reinforce deliberate, hands-on experiences instead of eliminating them. Ultimately, the article recommends treating AI as an augmentation of creative practice rather than an automatic substitute for it. Efficiency is valuable, but designers should protect the care, craft, and emotional intent that make creative work meaningful.

Read original(opens in new tab)
figma2 min readCurated summary

The Making of Practice, a Book on Design and Craft by Figma | Figma Blog

Practice, Figma’s third annual Config magazine, explores craft as intentional making shaped by patience, precision, experimentation, and repetition. The project argues that quality depends not only on whether something works, but on how it works. Its editorial and visual design connect historical craftsmanship with contemporary digital tools and creative practice. ## Craft as the Theme - The magazine focuses on what it means to make with intention. - Craft is presented as a process of: - Practicing repeatedly - Learning through failure - Studying more experienced makers - Taking risks and pushing boundaries - Dylan Field summarizes the central idea: “The question is not just, can you make it work? It’s how it works that actually matters.” - The contributors demonstrate that patience, observation, and intentionality apply across disciplines and mediums. ## A Contemporary Take on Traditional Bookmaking - Design studio Other Means created the print edition with type designer Kia Tasbihgou. - The visual direction draws inspiration from William Morris and the Kelmscott Press, particularly its emphasis on intrinsic quality and artistic taste. - Traditional bookmaking elements—including: - Initial caps - Fleurons - Decorative borders - Drop caps - These details were reinterpreted in a contemporary style to connect historical craft with modern design. ## Craft Across Design and Technology - Practice brings together articles, interviews, and essays from Figma’s Story Studio. - Its contributors work with screens, pixels, data, and digital tools, but share principles with makers in more physical disciplines. - The project presents craft as both rooted in tradition and driven by innovation. - The magazine’s featured subjects explore craft through themes including adaptation, iteration, application, and value. ## Practice as a Typeface - The book’s distinctive drop caps were expanded into a complete typeface. - The resulting font includes a full alphabet of visually distinctive characters. - Figma created a type specimen website using Figma Sites. - The typeface is available to view and download through the Practice website. Practice ultimately recommends treating making as a deliberate, ongoing discipline rather than a race to a working result. Whether designing software, typography, books, or physical objects, strong work comes from sustained practice and attention to how the final result is made.

Read original(opens in new tab)
figma2 min readCurated summary

Config 2025 Launches Deepen Figma's Design Capabilities As Its Platform Expands | Figma Blog

Figma’s Config 2025 announcements expand the platform from collaborative design into a broader product-development environment. New tools combine AI, code, visual design, websites, and marketing workflows, enabling teams to move from ideas to production within Figma. The company’s conclusion is that design and AI can help more people contribute throughout the development lifecycle. ## New Products - **Figma Make** turns written prompts or existing designs into working prototypes and applications. - **Figma Sites** lets designers build and publish dynamic websites with customizable interactions, code, and AI. - **Figma Draw** adds advanced vector editing and illustration tools to Figma Design. - **Figma Buzz** helps brand and marketing teams produce visual assets at scale while preserving brand consistency, with integrated AI features. ## Expanded AI Capabilities - New image-generation and image-editing tools support faster visual exploration. - Contextual auto-suggestions provide workflow guidance and help users work more efficiently. - FigJam receives additional AI features for brainstorming and collaboration. - Together with Figma Make, these tools are intended to make ideas easier to visualize and turn into functional outputs. ## Responsive Design and Developer Handoff - **Grid** introduces responsive layouts that adapt across screen sizes. - Grid can generate CSS code in Dev Mode, improving communication between designers and developers. - The feature supports Figma’s broader effort to connect design work more directly with implementation. ## Figma’s Expanding Platform - The new offerings join Figma Design, FigJam, Dev Mode, and Figma Slides. - About two-thirds of monthly active users in Q4 2024 worked outside traditional design roles, including roughly 30% who identified as developers. - The announcements reflect Figma’s shift from a design tool toward an integrated platform for ideation, design, development, publishing, and marketing. ## Global Growth - Figma announced full localization for Brazil, including Portuguese translation, culturally adapted interfaces, and dedicated language support. - Brazilian support joins existing Japanese, Spanish, and Korean localization. - Approximately 85% of Figma’s monthly active users were outside the United States in Q4 2024, while more than half of its 2024 revenue came from non-U.S. markets. - The company now employs more than 1,600 people worldwide. The new products and features will roll out over the following weeks. Overall, Figma is positioning itself as a unified environment where designers, developers, marketers, and other collaborators can take products from early concepts through launch.

Read original(opens in new tab)
figma3 min readCurated summary

Config 2025: Pushing Design Further | Figma Blog

Figma’s Config 2025 announcements frame design as more than visual production: it is the process of solving problems, shaping quality, and turning ideas into working products. As AI makes software easier to build, Figma argues that human craft, judgment, and point of view become even more important. Its new tools aim to connect ideation, prototyping, illustration, websites, and production in one collaborative platform. ## Figma Make: From prompts to working prototypes - Figma Make is a prompt-to-code tool that converts natural-language instructions or existing Figma designs into interactive prototypes. - Designers can: - Start with a text prompt or an existing file. - Generate high-fidelity app and interface concepts. - Select a specific area of a prototype and modify it with a prompt. - Test interactions and animations earlier in the design process. - Because Make is embedded in Figma, teams can explore, iterate, and validate ideas within a shared source of truth. - The tool is intended to reduce the separation between design and production while giving designers more control over generated results. ## Figma Sites: Taking designs to production - Figma Sites extends the platform from designing websites to publishing them. - It is intended to let teams move from visual design to production without relying on disconnected tools or complex handoffs. - Designers can use Figma’s existing collaboration and design workflows while creating real, publishable web experiences. - This reinforces Figma’s broader goal of supporting the full path from initial idea to live product. ## Grid: Moving from freeform to structured layouts - Grid addresses the tension between Figma’s flexible canvas and the structured layouts required for real interfaces. - It enables designers to shift more smoothly between exploratory, freeform work and organized, production-ready arrangements. - The feature is designed to make structured layout systems easier to create without sacrificing creative flexibility. ## Figma Draw: Expanding vector expression - Figma Draw adds more expressive illustration capabilities to vector layers. - It focuses on unbounded visual exploration, including texture, gesture, and richer vector-based artwork. - The tool helps designers create more distinctive illustrations and visual assets directly inside Figma rather than switching to a separate application. ## Figma Buzz: Creating branded content at scale - Figma Buzz is aimed at producing marketing and brand assets across many formats. - It brings design quality and brand consistency to content creation that may otherwise be handled through repetitive, disconnected workflows. - Teams can adapt designs for different channels and use cases while maintaining visual standards. - The product broadens Figma’s audience beyond product-design teams to include marketing and brand professionals. Figma’s Config 2025 direction is to make the platform a more complete environment for creative work: prompt ideas into prototypes, organize them into structured designs, add expressive visual detail, and publish or adapt the results for production. The central recommendation is to treat AI as an accelerator while preserving human design judgment, quality, and originality.

Read original(opens in new tab)
figma3 min readCurated summary

Figma Launches Brazilian Portuguese Localization | Figma Blog

Figma is launching a full Brazilian Portuguese localization on May 7, expanding its global reach and reducing language barriers for Brazilian users. The release includes translated interfaces, cultural adaptations, and Portuguese-language support. It follows Figma’s growing adoption in Brazil, where millions of files are created annually, with Latin American Spanish planned for later this year. ## Brazilian Market Expansion - Brazilian Portuguese is Figma’s fourth localized product language, after Japanese, Spanish, and Korean. - Brazil has a substantial Figma user base, including enterprises such as iFood, Itaú Unibanco, Nubank, Mercado Libre, TOTVS, and BTG Pactual. - More than one-third of Brazil’s Ibovespa-listed companies use Figma. - Nearly 5.5 million Figma files were created in Brazil over the past year, with more than 85,000 edited daily. - The São Paulo Friends of Figma community has nearly 1,000 active members. ## Localization and Accessibility - The localization provides: - A complete Brazilian Portuguese product translation - Culturally adapted interfaces - Dedicated support for Portuguese-speaking users - Figma says the goal is to make its tools feel more native and intuitive while encouraging broader collaboration among designers, developers, and other contributors. - Customers such as Itaú Unibanco and Mercado Libre expect the change to reduce friction and make Figma more accessible to Brazilian teams. ## Figma’s Global User Base - Approximately 85% of Figma’s monthly active users were outside the United States in Q4 2024. - More than half of the company’s 2024 revenue came from non-U.S. markets. - About two-thirds of monthly active users work outside traditional design roles, including roughly 30% who identify as developers. ## Expanding Product Ecosystem Figma’s localization arrives as the company expands its tools across the full product development lifecycle: - **Figma Design:** Digital product exploration, iteration, and prototyping. - **FigJam:** Collaborative whiteboarding, brainstorming, and meetings. - **Dev Mode:** Design-to-code handoff and developer workflows. - **Figma Slides:** Collaborative creation of interactive presentations. ## New Products and Features Announced updates at the Config conference include: - **Figma Make:** An AI prompt-to-code tool for creating prototypes and applications from descriptions or existing designs. - **Figma Sites:** Tools for designing and publishing dynamic, highly customizable websites. - **Figma Draw:** Enhanced vector editing and illustration capabilities. - **Figma Buzz:** Brand and marketing asset creation at scale, with AI support and brand-consistency controls. - **Enhanced AI features:** Image generation and editing, contextual workflow suggestions, and new FigJam capabilities. - **Grid:** Responsive layouts that can generate CSS code in Dev Mode. These products and features are scheduled to begin rolling out in the weeks following the announcement. Figma also plans to launch Latin American Spanish localization later in the year. Figma’s Brazilian Portuguese release is both a response to strong local demand and part of its broader strategy to make collaborative design and development accessible to a global audience.

Read original(opens in new tab)
figma2 min readCurated summary

Figma Buzz Is Where Design and Marketing Teams Co-create | Figma Blog

Figma Buzz is a new open-beta workspace designed to help brand designers and marketers create on-brand assets together. It addresses fragmented tools and workflows by combining Figma’s design precision with approachable editing and reusable templates. The product aims to speed up production while letting marketing teams create independently within brand guidelines. ## A Shared Space for Design and Marketing - Product launches require extensive marketing materials beyond the original design work. - Designers often need control and precision, while marketers need simple tools for adapting content quickly. - Figma Buzz brings both groups into one collaborative environment. - Designers can copy existing Figma designs into Buzz, build templates, or create assets directly with Figma Design functionality. - Marketers can customize materials without worrying about departing from brand standards. ## Types of Assets Figma Buzz supports a broad range of branded content, including: - Social media posts in multiple platform-specific sizes - Digital display and social advertisements - Flyers, email headers, and promotional announcements - Event invitations, schedules, and badges - Internal communications such as signage, infographics, and one-pagers - Personalized cards and other celebration materials ## Flexible Ways to Start Users can begin creating assets in several ways: - Choose from pre-made templates. - Start with a blank design. - Create images using OpenAI’s `gpt-image-1` or Gemini. - Copy and paste designs from Figma Design. - Use an intuitive inline toolbar for editing. The examples highlighted include Instagram feed and story ads, Pinterest and Twitter/X promotional posts, event invitations, and thank-you cards. Figma Buzz is intended to reduce repetitive executional work, allowing creative teams to focus more on brand strategy and larger ideas while giving marketers the tools to produce high-quality content quickly and consistently.

Read original(opens in new tab)
figma3 min readCurated summary

How Headspace Built an AI Companion that Fosters Trust and Transparency | Figma Blog

Headspace built Ebb as an AI companion for reflection between therapy sessions—not as a replacement for human care. Because mental-health AI carries significant safety and trust risks, the team prioritized clinical grounding, transparency, user autonomy, and careful cross-functional design. Early alignment workshops, iterative prototyping, and explicit interface guidelines helped shape Ebb into a friendly but clearly non-human companion. ## Defining Ebb’s Role - Headspace created Ebb in response to growing use of general-purpose AI for emotional support. - The companion was intended to: - Support reflective practices between therapy sessions. - Help people who may be unable to access or afford therapy. - Complement, rather than replace, human care. - The team first clarified the complete user experience and business objectives through FigJam workshops. - This early alignment helped address internal concerns and ambiguity around using AI in mental health. ## Building a Non-Human, Approachable Identity - The team explored names including Odom, Ibo, and Scribe before choosing **Ebb**. - The name suggests the fluidity and changing nature of emotions. - Designers avoided a gendered human name to reduce stereotypes that associate caregiving with women. - Ebb was designed as a friendly, human-adjacent entity without a specific gender. - Brand, product, illustration, animation, and copy teams used FigJam “playgrounds” to explore how Ebb could look and sound. ## Iterative Collaboration and Prototyping - Headspace followed a “build-to-learn” approach, bringing brand and product teams together early. - The teams tested approximately six brand identities before selecting a direction. - Figma allowed designers to apply different visual treatments directly to product screens. - Sharing prototypes in one workspace kept teams connected and enabled rapid iteration. - The team deliberately stress-tested ideas before rejecting them. ## Designing for Trust and Safety - Ebb was trained with input from clinical psychologists, providing a strong scientific foundation. - Designers focused on reducing adoption barriers by helping users understand: - That Ebb is an AI system. - How it can support them. - How their information and conversations are handled. - The interface was designed to make users feel safe expressing themselves. - Users retain agency to exit and delete conversations at any time. - A central principle was that AI should never be invisible: members should always know whether they are interacting with AI or a human. - The team’s broader guidelines emphasized differentiating AI from human-delivered care, reinforcing privacy and safety, supporting member choice, and creating a reflective environment. Headspace’s approach suggests that mental-health AI should be designed transparently and collaboratively, with safety and user control treated as foundational product requirements rather than features added later.

Read original(opens in new tab)