figjam

98 posts

figma

4 Ways We’re Using Our MCP Server at Figma | Figma Blog (opens in new tab)

Figma’s MCP server has expanded beyond design-to-code workflows to support Slides, FigJam, Figma Make, and the Figma design agent. The post argues that agents can now create and update production-ready artifacts while preserving team context, design systems, custom fonts, and brand consistency. In practice, humans still provide review and polish, but agents can complete much of the initial content and formatting work. ## Broader MCP capabilities - Agents can create or update: - Figma Slides presentations - FigJam boards - Figma Make prototypes - Canvas designs through the Figma agent - The server supports: - Custom fonts uploaded from a user’s computer - Downloading assets as SVG, PDF, JPG, or PNG through `download_assets` - Reusable MCP skills that encode team decisions and workflows - These capabilities connect external context and coding tools with Figma’s design environment. ## Creating and refreshing Figma Slides decks - Designer advocate Mallory Dean maintains an evergreen deck about Figma’s AI product launches. - She prompted an agent to: - Update the deck with the new Figma agent - Gather information from Slack, Google Drive, Shortcut blog posts, and release notes - Suggest content updates and new slides - The agent used the `use_figma` tool and `/figma-use-slides` skill to modify the existing deck template. - The first 80% of the content work was completed before human review. - Mallory still needed to replace images, edit copy, and approve the final slides. - Uploaded custom fonts allowed the deck to use the correct brand typefaces rather than web-safe substitutes. - Similar workflows can support: - Product kickoff decks - Design explorations - Go-to-market presentations - Sales decks with current product information - The stated benefit is faster production of presentations that remain aligned with a team’s design system and brand. ## Generating FigJam boards from live data - Product manager Prasant Lokinendi frequently prepares feature kickoff workshops. - Building an engaging FigJam board requires collecting company context and formatting the board for each session. - To streamline this process, he created the `/figjam-builder` skill. - Figma describes skills as a way to make agent outputs more consistent and context-aware. - Teams can use community-created skills or submit their own through Figma’s community-resources repository. Figma’s MCP workflows are most useful for accelerating repetitive preparation and production work while leaving humans responsible for review, judgment, and final creative decisions.

figma

FigJam Is Now Your Coding Agent’s Whiteboard Too | Figma Blog (opens in new tab)

FigJam is being positioned as a shared whiteboard for coding agents and engineering teams. New MCP skills let agents generate architecture and ER diagrams, write to and read from FigJam, and turn research or project plans into collaborative visual boards. The workflow connects agent-generated planning, human review, and implementation, reducing architectural confusion as teams ship code faster. ## Turning Agent Output into Visual Plans - The author built on Figma’s existing `generate_diagram` MCP tool to support more complex architecture and ERD layouts. - The new `figma-use-figjam` MCP skill allows agents to read and write directly to FigJam boards. - Skills such as `generate-project-plan` can transform documentation, codebases, and conversations into visual project plans. - Diagrams can include: - Architecture and entity-relationship diagrams - Notes and annotations - Code blocks - Implementation context and technical decisions ## Step 1: Research, Plan, and Visualize - The coding agent gathers relevant documentation, codebase structure, existing patterns, and implementation constraints. - It evaluates possible solutions, researches tradeoffs, identifies affected services and files, and proposes stacked PRs and testing strategies. - Instead of leaving the plan in a dense Markdown document, the agent exports it to FigJam as an interactive architecture review. - Visualizing the options helps teams understand the system and identify the cleanest approach more quickly. ## Step 2: Collaborate Before Coding - Engineers share the FigJam board with teammates for asynchronous or live review. - Team members can comment on concrete design questions, such as: - Whether a tool should support multiple file types - Whether it should accept a `folderId` - Where newly created files should be stored - FigJam provides a collaborative format that preserves technical context for distributed teams. - Teams can review and refine agent-generated diagrams before implementation begins. ## Step 3: Feed Decisions Back to the Agent - After review, the author uses the `get_figjam` tool to retrieve the board’s diagrams, comments, and decisions. - The coding agent uses that context to update the implementation plan and begin coding. - Pull requests can link back to the FigJam board, preserving the architectural rationale alongside the code. - Because the design has already been reviewed, the resulting PR is easier to evaluate and merge. ## Broader Figma Integration - The workflow builds on `use_figma`, which lets agents create or edit designs directly on the Figma canvas using real components. - `create_new_file` allows agents to generate designs in new Figma files. - Together, these capabilities extend agent collaboration beyond code into design, architecture, planning, and technical communication. Teams adopting coding agents can use FigJam as a reviewable source of shared context: let agents generate the initial plan, have humans refine the architecture visually, then return the approved decisions to the agent for implementation.

figma

Think Outside of the Box—with Claude and FigJam | Figma Blog (opens in new tab)

Figma and Anthropic have integrated FigJam with Claude so teams can turn AI conversations into editable diagrams. Users can generate flows, timelines, architecture diagrams, and other visual artifacts from prompts, PDFs, images, screenshots, documentation, or code. The integration is intended to make AI-assisted thinking more collaborative by moving ideas from a private chat into a shared workspace where teams can refine and act on them. ## Turning Conversations into Diagrams - Claude can create editable FigJam diagrams directly from written prompts and uploaded materials. - Product teams can generate user flows from PRDs to identify friction, edge cases, and missing steps. - Visualizing ideas reduces copy-pasting and context switching while making abstract concepts easier to discuss. - Teammates can comment, react, and build on the generated diagrams in FigJam’s shared canvas. ## Supporting Product Planning - Product managers can use Claude and FigJam to create initial project plans and Gantt charts. - Generated timelines can map milestones, dependencies, and sequencing. - Early visual drafts help teams spot planning problems, unblock work, and align more quickly. ## Helping Engineers Explain Complex Systems - Claude can generate diagrams from technical documentation or uploaded code files. - Diagrams can represent: - System architecture - Services and APIs - Databases and dependencies - Request and response flows - Sequence and state transitions - These diagrams provide shared context for front-end and back-end teams and help reduce implementation risk. - Claude can compare system patterns and suggest suitable visualization styles. ## FigJam as a Collaborative Workflow - Ideas generated in Claude can move into the broader Figma ecosystem: - Refined in Figma Design - Shared through Figma Slides - Translated into code - Figma is also improving FigJam with more advanced shape collections and connector types. - Anthropic has released a UI kit for designing Claude MCP apps in Figma. - The workflow connects brainstorming, planning, refinement, and execution in one process. ## AI as an Ongoing Collaborator - Multi-turn conversations let teams iteratively develop user journeys, prioritization strategies, and implementation plans. - Claude can propose alternative solutions and recommend chart formats such as decision trees, Gantt charts, sequence diagrams, and state diagrams. - FigJam diagrams become shared, evolving artifacts rather than one-off AI outputs. - Figma presents this integration as a step toward making complex systems easier for teams to understand and improve together. Teams can access the feature through the Figma Connector in Claude’s browser or desktop apps, with support listed for Claude Opus 4.5 and Sonnet 4.5.

figma

Show Don’t Tell: Embed Make Prototypes Everywhere You Work in Figma | Figma Blog (opens in new tab)

Figma is introducing live Figma Make prototype embeds for Figma Design, FigJam, and Figma Slides. The goal is to replace static screenshots and abstract explanations with interactive experiences that support alignment, feedback, and faster iteration. New editing controls also let users refine text, styling, and individual elements directly in prototypes. ## Embed Prototypes Across the Workflow - **FigJam:** Teams can use interactive prototypes as the focus of early discussions, making it easier to prioritize features and identify gaps in user journeys. - **Figma Design:** Designers and collaborators can review UI, copy, and interactions in context, compare iterations side by side, and turn feedback into concrete Make updates. - **Figma Slides:** Presenters can let stakeholders experience concepts directly and use Slides’ voting tool to gather input before refining the prototype. ## Refine Prototypes with Direct Editing - Users can edit text directly in a prototype to explore content variations and respond quickly to feedback. - The point-and-edit tool supports precise changes to color, spacing, and text styling. - Specific prototype nodes can be deleted without disrupting the rest of the structure. - `Command+Z` can undo deletions, supporting rapid experimentation. ## Greater Visibility Into AI-Generated Work - As prototypes become more complex, Figma Make is adding visibility into how the model builds them. - This allows users to review the model’s approach and course-correct while ideas evolve. Figma’s update positions Make prototypes as interactive, continuously refined artifacts that can travel from brainstorming through design review and stakeholder presentation. Teams can embed prototypes where decisions happen, gather more realistic feedback, and make targeted changes without leaving the workflow.

figma

Figma Make Is Now Available in Figma for Government | Figma Blog (opens in new tab)

Figma Make is now available in Figma for Government, giving federal agencies a secure way to create and test interactive prototypes. Figma argues that faster, collaborative design can help modernize public services, improve accessibility, and build public trust. The feature is available within Figma’s FedRAMP Moderate–authorized environment, although some cloud infrastructure will not reach full compliance until 2026. ## Modernizing Public Services - Government teams are improving services such as public portals, operational systems, benefits platforms, and research tools. - The online passport renewal system demonstrates the potential impact: by 2025, more than two million people had renewed passports online, with 97% reporting a positive experience. - Public-sector projects are difficult because policymakers, technologists, and operational leaders must coordinate under changing requirements and limited resources. - A 2025 executive order highlighted usability, accessibility, and design consistency as essential to citizen-facing services. ## Faster Prototyping and Collaboration - Figma Make enables teams to turn ideas into interactive prototypes in hours rather than weeks. - Designers, policy leaders, researchers, engineers, and IT staff can collaborate in a shared workspace. - Teams can test workflows and validate assumptions with citizens before development begins. - Shared libraries, integrations, accessibility standards, and design patterns help agencies maintain consistency. - Prototyping supports a wide range of initiatives, including federal benefits, financial communications, education platforms, space systems, and internal agency tools. ## Security and Compliance - Figma Make is included in Figma for Government and operates within its authorized environment. - Figma for Government is FedRAMP Moderate authorized, providing agencies with a compliant foundation for design and prototyping. - Figma notes that part of its cloud infrastructure is expected to achieve full FedRAMP Moderate compliance in 2026, while Make is usable today within the authorized environment. ## Broader Government Design Efforts - Federal agencies are already using Figma to modernize complex public services. - Shared design systems can improve accessibility and consistency across agencies and products. - Examples such as the National Park Service’s digital app illustrate how small teams can transform large, paper-based systems into accessible digital experiences. Figma positions Make as a practical tool for helping agencies adopt faster, citizen-first design processes. Government teams can use it to explore ideas early, collaborate across disciplines, and test accessible services before committing development resources.

figma

Introducing Three New Tools For Precise Image Editing In Figma | Figma Blog (opens in new tab)

Figma introduced three AI-powered image editing tools—Erase object, Isolate object, and Expand image—to make detailed image manipulation possible without leaving the design canvas. The tools complement existing features such as background removal, cropping, and AI image generation, helping designers refine assets in context. A new image-editing toolbar brings these capabilities together for faster, more integrated workflows. ## Erase and Isolate Objects - **Erase object** removes a selected object from an image. - **Isolate object** separates an object or person so it can be edited or repositioned without changing the background. - Users can select objects with a lasso and apply: - Lighting and color adjustments - Blur and focus effects - Color correction - Shadows - These tools are useful for refining product photos, removing distractions, and emphasizing key visual elements. - Text-prompt editing remains available through Figma’s **Edit image** feature, but the new tools provide more precise manual control. ## Expand Images for New Layouts - **Expand image** generates additional background content to fit a new aspect ratio. - It adapts images for formats such as: - Mobile layouts - Web banners - Social media assets - Unlike cropping, expansion preserves the original subject and surrounding context without distortion. - For example, a square product image can be expanded into a wide banner while leaving room for text. ## A Unified Image-Editing Toolbar - The new toolbar combines the three AI tools with existing capabilities, including: - Remove background - Crop - AI image generation and editing - Remove background is now easier to find because it is one of the most frequently used AI actions in Figma. - The tools are available across Figma, including FigJam, Slides, and Buzz beta, with some seat restrictions. - In Figma Design and Figma Draw, they are available to Full-seat users on Professional, Organization, and Enterprise plans with AI enabled. - AI actions consume Figma credits. These updates aim to keep image editing inside Figma, reducing the need to switch between external tools. Designers can now make precise object-level edits, adapt images to different formats, and maintain visual consistency directly within their workflows.

figma

Gemini 3 Is Now Available In Figma Make | Figma Blog (opens in new tab)

Figma has made Gemini 3 Pro available as an experimental model in Figma Make, positioning it as a tool for turning design ideas into polished, interactive prototypes. Early tests suggest it is particularly strong at exploring varied visual styles, layouts, motion, and interaction patterns while preserving functional fidelity. Figma’s broader conclusion is that AI expands designers’ creative range rather than replacing their role in directing and refining ideas. ## Bridging the Design-to-Code Leap - Gemini 3 Pro was tested on a Thanksgiving gratitude board designed in Figma Design. - It generated animated SVG leaves with on-screen physics, creating a calm, organic motion. - A Supabase connection allowed visitors to submit gratitude notes. - New notes appeared as leaves that revealed their messages on hover. - The example demonstrated how a visual concept could quickly become a functional, code-backed experience. ## Exploring Distinct Visual Styles - A New Year’s Eve RSVP page was used to test Gemini’s stylistic flexibility. - The model first created a Y2K-inspired design with: - Retro-futuristic visuals - Dark chrome styling - A functioning RSVP form - It then transformed the same experience into a “concrete poetry” treatment featuring: - Severe typography - Brutalist tension - Minimal decoration - Gemini maintained the core interaction and form functionality across both radically different aesthetics. - Motion and interactive details were adapted to match each visual direction. ## Working Within Design Systems - Figma tested Gemini 3 Pro in a mature UI environment using Make kits, npm imports, and Figma’s UI3 library. - Starting with a FigJam template, the team asked it to add a canvas background-style switcher. - Gemini produced 12 background styles using the correct UI3 components and functional interactions. - It also added unexpected refinements, including: - Animated transitions between textures - Sticky-note layering - Scaling effects - The result showed that the model could extend an existing design system rather than only generate isolated concepts. ## A Wider Canvas for Design - Figma argues that AI can increase the range of ideas designers are able to explore. - Gemini 3 Pro combines rapid iteration with visual and interaction fluency. - Gemini 3 Flash is also available as a faster, lighter option for quick ideation and refinements. - Both models can be enabled through Figma’s settings under the experimental models section, marked by the lab icon. Overall, Figma presents Gemini 3 Pro as a practical bridge between design, code, and experimentation. It is most valuable when designers use it to explore possibilities quickly while continuing to guide the creative direction and quality of the final result.

figma

15+ Ways We're Improving Accessibility in Figma | Figma Blog (opens in new tab)

Figma is rolling out more than 15 accessibility improvements to make its products easier to use with keyboards, screen readers, and enhanced contrast settings. The updates expand keyboard control across Figma Design, FigJam, Slides, Buzz, commenting, and Dev Mode, while improving screen-reader navigation and object descriptions. Together, they aim to make collaboration, canvas editing, and handoff more reliable for people with different access needs. ## Expanded Keyboard Controls - Users can navigate and manipulate more canvas objects without a mouse. - **Figma Design:** Add and edit lines, adjust ruler guides, and create or edit arcs from ellipses. - **FigJam:** Manage table rows and columns, adjust stamps, votes, washi tape, marker lines, and highlighter strokes, and navigate embedded content and other canvas objects. - **Figma Slides:** Resize presenter notes and adjust writing tone with AI. - **Across products:** Open and move between links in edit or view-only mode. ## Keyboard Support for Comments and Collaboration - Add, move, and navigate comments across Figma products. - Navigate and manage Dev Mode annotations with shortcuts. - Move between discussions without losing keyboard focus. - New personalization toggles let users disable Figma-exclusive shortcuts while typing and choose whether Spotlight automatically follows other users. ## Improved Screen Reader Support - Tab navigation through buttons, menus, panels, and other actions now follows a more logical order. - Users can jump directly to specific actions, such as opening menus or activating toolbar controls. - Object announcements include details such as type, name, and state. - More consistent announcements help users detect new comments and file updates. - Screen readers preserve rich-text meaning, including bold, italics, lists, and links. - Canvas objects in Buzz and Slides can now be recognized and announced. ## Enhanced Color Contrast - A new setting increases contrast between text, interface elements, and backgrounds in both light and dark modes. - The option can be enabled through Accessibility settings, the Actions menu, or General settings. - Stronger contrast improves text and icon legibility, clarifies interface structure, and makes buttons and outlines easier to identify. - It can also improve visibility in glare, sunlight, and prolonged or multitasked screen use. Figma’s updates make accessibility a broader part of everyday editing and collaboration rather than a separate workflow. Users who rely on keyboards or screen readers should explore the new controls, while all users may benefit from enabling enhanced contrast when working in difficult lighting or for extended periods.

figma

Turn Your ChatGPT Brainstorms Into FigJam Diagrams | Figma Blog (opens in new tab)

Figma’s new ChatGPT app turns brainstorms, sketches, uploaded files, and technical documents into editable FigJam diagrams. It supports flowcharts, sequence and state diagrams, and Gantt charts, helping users move quickly from exploration to collaborative artifacts. The feature is powered by Figma’s remote MCP server and is available to logged-in ChatGPT users outside the EU. ## Turning Conversations into Diagrams - Users can mention Figma in a prompt, such as “Figma, make a diagram from this sketch.” - ChatGPT can recommend the Figma app when diagramming is relevant. - Photos, drawings, PDFs, and other files can provide context. - Generated diagrams can be revised, expanded, or represented in alternative formats. - Figma plans to add more diagram types over time. ## Accelerating Design Iteration - Hand-drawn sketches can become shareable FigJam files. - Designers can ask ChatGPT to update diagrams or explore different visualizations. - Dense documents can be uploaded so ChatGPT can produce an initial draft. - This helps teams move ideas from informal notes or whiteboards into a collaborative workspace. ## Clarifying Technical Systems - Developers can use uploaded documentation and screenshots to create or update software architecture diagrams. - ChatGPT can research technical approaches using blogs and case studies, then visualize them. - Screenshots, such as a pricing page, can be used to map likely React component structures. - The resulting diagrams support system design discussions, technical communication, and interview preparation. ## Planning Products and User Experiences - Product managers can visualize tradeoffs, such as simplicity versus power in a permissions flow. - PRDs can be converted into user journey or process flowcharts. - Product, engineering, and design requirements can be combined into Gantt charts for launch planning. - ChatGPT supports individual exploration, while FigJam enables teams to review and iterate together. The feature is currently live for logged-in ChatGPT users outside the EU. It offers a practical workflow for using ChatGPT to generate a first visual draft and FigJam to refine, discuss, and collaborate on it.

figma

The Duolingo Method: Collaboration As A Core Practice | Figma Blog (opens in new tab)

The Duolingo Math team treats collaboration as a continuous practice rather than a one-time handoff from design to engineering. Designers, engineers, and product managers co-create ideas, validate them through rapid prototypes, and refine features together. This approach helps the team make better decisions quickly while building entirely new learning experiences. ## Ideating Together - The Math team develops new lessons and games without established templates or patterns to follow. - Designers, engineers, and product managers begin projects together in a shared FigJam file. - After agreeing on a direction, designers create detailed Figma mockups, including interactions and motion. - Engineers participate early by evaluating technical complexity and commenting on implementation challenges. - Jira is connected directly to Figma, reducing context switching during development. ## Experimenting Through Rapid Prototyping - Engineers quickly build initial prototypes using components from Duolingo’s design system. - Designers and engineers share Figma files, working prototypes, questions, and feedback in Slack. - The team repeats a “prototype, test, tweak” cycle for each feature. - Duolingo’s “show don’t tell” principle encourages building and experiencing ideas instead of debating them abstractly. - Prototypes reveal how an interaction actually feels, helping the team test assumptions and make decisions before investing in a polished implementation. ## Polishing and Shipping Together - Continuous collaboration allows the team to make decisions and polish features during development. - The team may simplify animations or remove nonessential mechanics to ship faster. - When exploring educational games, Duolingo first created a batch of simple prototypes instead of building two fully developed games. - The team tested seven different prototypes to learn what resonated with users and prioritized features based on those findings. The Duolingo method replaces rigid handoffs with shared ownership, frequent communication, and working software. For exploratory products, teams should involve engineers early, prototype quickly, and use real user or team feedback to guide what gets polished and shipped.

figma

In Good Company: How Retailers Use Figma to Elevate E-commerce | Figma Blog (opens in new tab)

The article argues that successful e-commerce depends on cohesive, trustworthy digital experiences that connect customer needs, operational systems, and brand values. It highlights how Nuuly, Ruggable, and GitHub use Figma to improve collaboration, maintain consistency, and create more engaging shopping experiences. Nuuly’s example shows how thoughtful design systems can simplify highly complex business processes for customers and employees alike. ## Nuuly: Simplifying Clothing Rental - Nuuly aims to make clothing rental an everyday habit, giving subscribers flexibility to experiment with their style. - Its business requires complex behind-the-scenes systems for: - Circular inventory management - Cleaning and repairs - Rental logistics - Nuuly built two separate design systems: - One for the customer-facing experience - One for internal rental-management tools - Both systems use flexible color and typography tokens so the brand can evolve seasonally. - The “My Nuuly” feature makes more than 26 rental statuses understandable by showing customers what is happening now and what to expect next. - In 2023, Nuuly migrated to Figma and consolidated 16 fragmented design files into two shared libraries. - Figma’s prototyping and collaboration tools helped the team: - Work faster - Communicate interaction details more clearly to developers - Stay aligned across departments - Content, photography, and other teams also adopted Figma, FigJam, and Figma Slides for brainstorming, reviews, and customer-journey improvements. ## Ruggable: Creating Consistent Digital Experiences - Ruggable’s UX leadership encountered siloed workflows across social advertising, the homepage, and product-detail pages. - These disconnected processes produced inconsistent digital experiences. - The article presents Ruggable as an example of how shared design practices can connect marketing and e-commerce touchpoints, though the supplied text ends before describing its specific solutions. ## GitHub and Design Business Company: Designing for Developers - The article also introduces a collaboration between GitHub and Design Business Company. - Their goal was to create a storefront specifically tailored to developers. - The partnership illustrates how brands can use design to add personality and delight while remaining aligned with their audience’s expectations. By combining scalable design systems with cross-functional collaboration, retailers can make complicated services feel simple, improve internal efficiency, and deliver a more consistent brand experience across every digital surface.

figma

How Headspace Built an AI Companion that Fosters Trust and Transparency | Figma Blog (opens in new tab)

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.

figma

Figma Localizes Product and Support for Korean Market | Figma Blog (opens in new tab)

Figma is launching an open beta of its fully localized Korean product and support experience on April 16. The rollout responds to strong adoption in South Korea and aims to remove language barriers across design, development, and collaboration. It is Figma’s third product localization, following Japanese and Spanish, with more languages expected this year. ## Korean Market Expansion - The localization includes: - A complete Korean product translation - Culturally adapted user interfaces - Dedicated Korean-language customer support - South Korea already has a significant Figma user base: - Nearly one-third of KOSPI 200 companies use Figma. - More than four million files were created in the country over the past year. - More than 75,000 files are edited daily. - The Seoul Friends of Figma community has over 1,000 active members. - Customers include Gangnam Unni, Daangn, KakaoBank, and Woowa Brothers. ## Benefits for Customers - KakaoBank reports a 30% increase in employee productivity attributed to Figma. - Its design team expects full Korean support to speed up critical projects by eliminating the need to work across two languages. - Woowa Brothers says Korean-language access will lower barriers and bring more people into the product development process. - Figma emphasizes that localization benefits both designers and non-designers, including developers. ## Supporting the Full Product Development Process Figma’s localization arrives alongside an expanding product ecosystem: - **FigJam**, launched in 2021, supports brainstorming, meetings, and collaborative work. - **Dev Mode**, launched in 2023, helps teams turn designs into coded products. - **Figma Slides**, launched in 2024, brings Figma’s design and collaboration features to presentations. - New AI-powered features help users develop and refine ideas. ## Global Context and Rollout - About 85% of Figma’s monthly active users are outside the United States. - Non-U.S. markets generated approximately 50% of revenue at the end of 2024. - Nearly two-thirds of users work outside traditional design roles, and about 30% identify as developers. - The Korean version will roll out gradually in open beta beginning April 16. - Figma will also showcase new products and features at Config in San Francisco on May 6–8 and London on May 14. Figma’s Korean localization is intended to make collaborative product development faster and more inclusive by allowing teams to work entirely in their native language.

figma

Finding a Forever Home for FigPals | Figma Blog (opens in new tab)

FigPals were temporary customizable companions in Figma files, designed to make long hours of creative work feel more playful and social. Inspired by nostalgic virtual pets and toy culture, they quickly became a hit, with users creating emotional connections to their pixel-based friends. Although FigPals will not remain permanently active, Figma is preserving them through sticker packs and other commemorative experiences. ## What FigPals Were - Users could create, customize, and name companions across Figma products. - More than 9,000 combinations were possible, including animals, food, colors, and accessories. - FigPals followed users’ cursors and interacted with other companions in the same file. - Users could pose them in a photobooth and save images as keepsakes. - Easter eggs included feeding pals layers and nodes and surprising them by detaching components. ## Nostalgia and the April Fun Day Launch - FigPals launched on April 1 as part of Figma’s annual April Fun Day tradition. - The concept drew on nostalgia for products such as Pet Rocks, Tamagotchis, Neopets, and Furby commercials. - Figma partnered with Night Shift to create a deliberately zany, vintage-style promotional video. - The goal was to make work feel less lonely and repetitive by giving designers playful companions. ## From Maker Week to FigPals - FigPals evolved from internal Maker Week experiments: - **Figmagotchi** featured Tamagotchi-inspired creatures fed with sticky notes. - **FigPets** introduced pixelated pets that moved around Figma toolbelts. - A small team across engineering, product, and design developed the limited-release version. - The project reflected Figma’s emphasis on experimentation, play, and building enjoyable web experiences. ## The FigPal Frenzy - Users saved more than 1.5 million FigPals within a week. - They fed their companions more than 250,000 times. - Five FigPals were saved as the only examples of their particular model, color, and accessory combination. - One user created and saved 210 pals, while the most popular design—a pink cat with a heart speech bubble—accounted for 13% of saved pals. - Community members became emotionally attached, with some modeling their FigPals after real pets. ## Preserving FigPals Through Stickers - A petition seeking to make FigPals permanent attracted more than 2,000 signatures. - Figma extended the feature by one additional week but ultimately chose not to keep the companions active indefinitely. - Instead, it released FigPal sticker packs so users could continue displaying them in Figma files. - Additional FigPal-related surprises were planned for attendees of Config. Figma’s response shows how a short-lived playful feature can create lasting community engagement. While the interactive FigPals have ended, sticker packs provide a simple way to preserve the experience and keep the characters present in users’ work.

figma

The Designer's Handbook for Developer Handoff | Figma Blog (opens in new tab)

Design-to-development handoff works best as an ongoing collaboration rather than a final transfer of files. Designers and developers bring different priorities—elegance and consistency versus performance and stability—so teams should involve engineering early, communicate openly, and agree on what “good” means. The article organizes this collaboration around aligning on the product, choosing how to build it, sharing vocabulary, and clarifying design intent. ## Align on What You’re Building - Involve developers during wireframing or early feasibility checks, when design ideas are still easy to change. - Early engineering input can: - Clarify scope and technical constraints - Reveal difficult implementation logic - Identify opportunities to reuse or extend existing functionality - Prevent costly rework later - Use wireframes in Figma or FigJam to make ideas concrete without overcommitting to visual details. - Figma is suited to more structured, concrete visuals. - FigJam supports exploratory thinking and feedback from outside collaborators. - Less realistic wireframes help teams focus on user flows and overall direction instead of prematurely debating polish. ## Ask Developers Targeted Questions - Developers may notice redundant work or reusable patterns, but designers often need to prompt them explicitly. - Ask about: - Constraints and possible friction in the data layer - Missing states in a sequence of screens - Existing product patterns that could be reused - Asking these questions turns developers into proactive design partners rather than people who only implement finished screens. ## Work Within Developer Workflows - Developers frequently switch contexts and need uninterrupted time to reach a productive flow state. - Designers can build trust and improve collaboration by understanding how developers work and meeting them in their existing tools and processes. - The article also points to shared artifacts, such as using code blocks in FigJam to align on component APIs in design-system documentation and development workflows. ## Broader Collaboration Principles - Effective handoff depends on curiosity, continuous communication, and a shared point of view about quality. - The remaining focus areas are deciding how the design should be built, adopting a shared language, and explaining design intent in ways that account for the developer experience. Designers should treat handoff as a shared problem-solving process, involving developers early and asking precise questions about constraints, states, reuse, and implementation. This reduces rework while producing designs that are both ambitious and practical to build.