Figma

532 posts

figmaDec 6, 20232 min readCurated summary

Top 10 things we shipped this year | Figma Blog

Figma’s 2023 product updates focused on helping teams design and build together, from major launches like Dev Mode and variables to smaller quality-of-life improvements. Rather than ranking features strictly, the company highlights updates that improve different stages of product development. The excerpt spotlights faster font selection and more powerful component exploration. ## A Year of Design-to-Development Improvements - Figma describes 2023 as a major year, marked by: - The largest Config conference to date - The launch of Dev Mode for developer-focused workflows - Variables and advanced prototyping - More than 200 product updates, including the “Little Big Updates” - The company emphasizes that small fixes and major features both meaningfully improve users’ work. ## New Serifs in Town - Font picker previews now appear directly on the canvas. - Users can hover over typefaces and immediately see how text will look without selecting each font. - This makes comparing typefaces faster and reduces friction when choosing typography. ## The Smart Play - The component details modal and playground are available from the assets panel. - Selecting an asset opens component information and provides a link to its main library. - On Professional plans and above, the playground lets users: - Preview component variants - Test component properties - Explore variable modes - These capabilities support quicker experimentation and easier iteration within the design workflow. Overall, the featured updates show Figma’s effort to improve both everyday design tasks and the broader collaboration between designers and developers.

Figma Design Systems Prototyping Dev Mode+3

figmaDec 6, 20233 min readCurated summary

Figma’s 2023 Handoff | Figma Blog

2023’s tensions—especially between rapid AI adoption and renewed human connection—reinforced Figma’s belief that collaboration is essential. The company frames its year-end “Handoff” as a reflection on how teams can work together more continuously, rather than treating work as a series of disconnected transfers. Its major launches, including Dev Mode and FigJam AI, are presented as tools for reducing barriers and making collaboration more inclusive and iterative. ## A Year Defined by AI and Human Connection - 2023 was characterized both by AI’s rapid expansion and by people reconnecting after the pandemic. - Figma argues that these developments are not necessarily contradictory: technology can support more meaningful human collaboration. - The company emphasizes that people need one another to interpret challenges and understand the world around them. ## Reimagining the Handoff - In American football, a handoff is a coordinated pass between teammates; in product development, it has often meant throwing work “over the wall.” - Designers and developers traditionally work from different perspectives, despite being deeply dependent on each other. - Figma advocates for “multiplayer” work: shared spaces where people can solve problems together and understand one another’s needs. - A successful handoff should be an ongoing conversation, enabling faster iteration and better products. ## Dev Mode and Developer Collaboration - Figma launched **Dev Mode** to provide developers with a developer-focused view of design files. - The feature is intended to give developers the information and tools they need at the appropriate stage of the workflow. - Figma describes Dev Mode as a way to eliminate the traditional handoff barrier and make design-development collaboration more continuous. ## AI as a Collaborator - Figma’s new AI features in **FigJam** are designed to accelerate ideation. - The goal is not to replace human interaction, but to make meetings and collaborative moments more productive and meaningful. - Figma connects this approach to “lowering the floor and raising the ceiling”: making products more accessible while expanding what experienced users can accomplish. ## The 2023 Handoff Collection The article introduces several additional reflections and features from Figma’s year, including: - The year’s top ten product launches - How product managers brought AI features to market - Questions for rediscovering enthusiasm for technology - Guidance for more effective meetings - New workplace vocabulary - Professional career pivots - The enjoyment and culture surrounding mechanical keyboards Figma’s practical conclusion is that strong collaboration requires more than efficient workflows. Teams need shared spaces, continuous dialogue, inclusive tools, and enough practice and collective experience to play to one another’s strengths.

Figma AI Figjam Dev Mode+2

figmaDec 6, 20233 min readCurated summary

The Art of the Professional Pivot | Figma Blog

The article presents professional pivots as normal career adjustments rather than dramatic reinventions. Through six creatives’ stories, it shows how people can redirect their careers by reframing their approach, returning to a familiar company in a new role, or making larger changes. The central message is that pivots can help professionals align their skills and interests more effectively with their work. ## The Reframe: Small Changes with Big Effects A reframe changes how someone approaches their existing role without requiring a complete career change. - Ry Reid moved from customer support into UX writing, later working at Pinterest, Spotify, and Uber Eats. - At Uber Eats, Ry struggled to persuade colleagues through written proposals and was passed over for promotion. - A design manager suggested visualizing ideas instead of explaining them in documents. - Ry began creating rough concepts with pen and paper and Google Slides, then sharing them with colleagues. - This shift helped Ry communicate more effectively and contributed to their proposed user experience being adopted. - The experience showed that presenting an idea and polishing it into a finished design are different skills. ### Lessons from the Reframe - Accept difficult feedback and investigate why opportunities were missed. - Seek advice from mentors in adjacent disciplines. - Test a new approach in low-risk situations. - Expect some discomfort when developing unfamiliar skills. ## The Boomerang: Changing Roles in a Familiar Environment A boomerang involves making a substantial career change while returning to—or remaining within—a company whose culture and operations are already familiar. - Erica Simunovic first worked at Tatari in people operations. - After five years and completing a product design bootcamp, she returned to the same company as a product designer. - Her story illustrates how an existing relationship with an organization can reduce some of the risks of starting over in a new discipline. - The article frames this path as a way to pursue significant change while retaining familiarity with the workplace. ## The Article’s Broader Career-Pivot Framework The six profiles represent different forms of professional change: - **The reframe:** Adjusting perspective or working methods. - **The boomerang:** Taking on a new role at a familiar company. - **The unfolding:** Making a deeper, more personal leap. - **The stretch:** Exploring unfamiliar opportunities. - **The hard left:** Changing direction completely. - **The blend:** Combining experiences, skills, and professional networks. A practical approach is to begin with the smallest change that addresses the problem: seek candid feedback, experiment with adjacent skills, and use existing relationships where possible.

Figma User Experience Product Design Slack+2

figmaDec 6, 20232 min readCurated summary

Come together: A multiplayer guide to great meetings | Figma Blog

Great meetings are intentionally designed collaborative experiences, not merely calendar events or “glorified emails.” The article argues that successful meetings depend on four pillars: purpose, preparation, participation, and follow-up. Both facilitators and participants share responsibility for creating focused sessions that use everyone’s time and strengths effectively. ## Meetings as Designed Experiences - Meetings often fail because they lack a clear purpose, adequate preparation, active participation, or follow-up. - Effective facilitators design an experience that helps the team collaborate and accomplish concrete goals. - Participants also play an important role in making meetings purposeful and engaging. ## Before the Meeting: Plan for Success Preparation creates the conditions for inclusive and productive collaboration. ### Define the Meeting’s Goal - Clarify whether the meeting is intended to: - Track progress - Make a decision - Share information or insights - Build context across a team - Choose the meeting format based on its purpose. - Shishir Mehrotra’s framework groups meetings into: - **Cadence:** recurring staff meetings, standups, and project syncs - **Catalyst:** decision forums, product reviews, and design critiques - **Context:** all-hands meetings, off-sites, orientations, and one-on-ones - The right category helps determine the questions, participants, and structure required. ### Prepare and Share an Agenda - Circulate an agenda before the meeting, ideally a day in advance. - Include pre-read materials such as: - Project briefs - Documentation - Sketches - Other background information - Use an existing template rather than starting from a blank page. - FigJam templates can structure the discussion, collect participants’ ideas and questions ahead of time, and organize meetings around prompts or “provocations.” - Successful formats can be saved as reusable shared templates, while AI can help generate customized meeting structures. A practical meeting recommendation is to define the intended outcome first, then choose the appropriate format and share enough context for participants to contribute before the meeting begins.

Figma AI Figjam Coda+2

figmaDec 5, 20232 min readCurated summary

Building a Design System That Breathes with Headspace | Figma Blog

Headspace rebuilt its design system to support rapid growth, multiple brands, and products spanning apps, wearables, and VR. Its previous system relied on hard-coded colors, manual processes, and plugins, making updates slow and creating inconsistencies. By adopting design tokens and Figma variables, Headspace created a scalable source of truth for designers and engineers that could evolve with the business. ## Challenges of the Previous System - Headspace served more than 100 million members across numerous products and partnerships. - The existing design system was manual and heavily dependent on plugins. - Hard-coded color values produced multiple hex-code variations and inconsistent experiences. - Even small palette changes could take the design systems team hours or days. - Plugins often required specialized knowledge, frequent resets, and workflows that were not intuitive for occasional users. - The system was designed for a single brand, creating problems when Headspace merged with Ginger, later rebranded as Headspace Care. ## Preparing for Multiple Brands and Future Growth - Senior product designer Steven Sczepanik audited the existing system after the merger announcement. - He rebuilt components and patterns so they were easier for designers and engineers to find and use. - The redesign established Headspace’s first formal token system. - Tokens created a shared language for foundational properties such as colors and typography. - The system was designed to support Headspace Care and future partnerships without requiring separate, disconnected systems. ## Replacing Plugins with Figma Variables - Headspace converted its color tokens and typography into Figma variables. - Variables replaced many plugin-based workflows with a native Figma solution. - Steven implemented the initial color and typography variables in about a day, compared with two years spent developing the broader previous system. - The new approach made theme changes and system-wide updates faster and more reliable. - Designers and engineers gained a more dependable source of truth for shared design decisions. ## A Design System That Can Evolve - Headspace’s design system now supports a growing ecosystem of brands, platforms, and experiences. - Centralized tokens reduce duplication and improve consistency across products. - Native variables make the system easier to maintain as the visual identity changes. - The work demonstrates that scalable design systems must accommodate organizational change, not just reuse components. Headspace’s experience suggests that teams preparing for growth should replace hard-coded values and fragile plugin workflows with structured tokens and native variables. This creates a more flexible foundation for consistent design across brands, products, and future expansion.

Figma Design Systems Design Tokens Design Variables+2

figmaDec 5, 20232 min readCurated summary

All Your Questions About Variables Answered (and a Few You Didn’t Even Know You Had) | Figma Blog

Figma’s latest variable updates expand design customization while bringing design systems closer to code. Variables can now control more visual properties and respond to different modes, making responsive, platform-specific designs easier to manage. The post presents variables as more flexible than traditional tokens and highlights their potential for both practical systems work and highly creative prototypes. ## Variables Enable Broader Customization - Designers are using variables for applications ranging from production design systems to interactive, game-like creations. - Unlike regular tokens, variables are open-ended and support more flexible customization. - Figma points to Headspace as an example of using variables to improve design-system efficiency and collaboration with developers. - Beginners can start with Figma’s dedicated variables guide and community file. ## New Properties That Support Responsive Design - **Reactive effects:** Variables can control blur sizes, drop-shadow colors, and offset distances, allowing effects to change by mode. - **Dynamic stroke weights:** Designs can use different stroke weights for platforms such as desktop and mobile. - **Layer opacity:** Opacity fields can be bound to variables for more nuanced visual control. - **Adaptable layout grids:** Grid settings can switch between modes, supporting pixel-perfect desktop and mobile layouts. - **Individual corner radii:** Each corner radius can be controlled independently through variables. - **Nested instance variant binding:** Variables can be applied to component instances nested within other components, enabling more complex component structures. ## Connecting Design and Code - The updates are intended to align design variables more closely with how values are managed in code. - Mode-based values make it easier to represent platform, theme, or responsive differences within a single design system. - Figma indicates that typography is an area planned for further variable support. Overall, the post recommends adopting variables as a flexible foundation for scalable design systems, responsive interfaces, and richer prototypes—especially when designers and developers need a shared source of truth.

Figma Design Systems Design Tokens Responsive Design+2

figmaNov 21, 20233 min readCurated summary

Dev Mode: Building a Design Tool that Works Harder for Developers | Figma Blog

Figma built Dev Mode to make developers first-class participants in product design rather than secondary users of a designer-focused tool. The team initially emphasized code generation, but real-world differences in teams, workflows, and codebases exposed its limitations. By combining developer research, the acquisition of Visly, and a broader focus on inspection and collaboration, Figma shifted toward reducing the gap between design and code. ## Designing for Developers as Core Users - Figma’s multiplayer canvas was created for entire product teams, including product managers and developers. - Developers were already using Figma to explore work in progress, despite the tool not being optimized for their workflows. - By 2023, developers represented roughly one-third of Figma’s users. - The goal became a tailored developer experience that did not require developers to learn or navigate design-centric interactions. - Proposed directions included: - Component playgrounds - Code snippets - GitHub and Storybook integrations - Developer-specific resources - Design inspection and change comparison ## The Visly Acquisition - Figma acquired Visly in 2021, bringing in eight designers and engineers who had built a React UI development tool. - The Visly team contributed: - Extensive research into developer tooling - Practical experience with development workflows - A developer-oriented perspective and intuition - Their involvement accelerated Figma’s efforts and helped the company understand how developers work across different environments. ## Moving Beyond a Codegen-First Strategy - Early versions of Dev Mode focused on code generation: automatically translating designs into code according to predefined rules. - Codegen could save hours or even days when designs mapped cleanly to implementation. - Testing showed that successful code generation in controlled scenarios did not necessarily work in production. - Companies differ in their: - Team structures - Engineering practices - Toolchains - Codebases - Workflow conventions - These variations made it difficult to generate universally useful code, prompting the team to reconsider codegen as the central solution. ## Redefining Design-to-Code Handoff - Figma’s broader objective was to break down the traditional “handoff wall” between designers and developers. - Dev Mode was positioned as a dedicated space where developers could inspect designs, compare changes, work with VS Code, and access implementation-oriented information. - The team continued refining the product through beta feedback, including daily customer requests collected through an internal Slackbot. - Rather than assuming developers would live inside a design tool, Figma focused on making the parts of the design process they needed more accessible and useful. Dev Mode’s central lesson is that developer tooling must reflect real engineering practices, not just generate code from idealized designs. A practical developer experience combines accurate design context, collaboration, integrations, and workflow flexibility with code generation where it genuinely helps.

Figma React Github Dev Mode+3

figmaNov 15, 20233 min readCurated summary

The Figma + Adobe Deal, Explained | Figma Blog

Figma’s post explains why it believed its proposed acquisition by Adobe would benefit users and withstand regulatory scrutiny. It presents Figma as a collaborative tool for building digital products, distinct from Adobe’s traditional creative software, and emphasizes a broad, fast-changing competitive landscape. However, the deal was ultimately abandoned on December 18, 2023, after the companies concluded that regulatory approval was unlikely. ## Figma’s Role in Digital Product Development - Figma describes itself as a web-based platform for teams building apps and websites. - Its tools support multiple stages of development: - **FigJam** for brainstorming and concepting - **Figma** for interface design and prototyping - **Dev Mode** for helping developers translate designs into code - The company says it spent thousands of hours explaining its products and market to competition regulators. ## Product Design vs. Traditional Graphic Design - Figma focuses on creating interactive digital products rather than static advertisements, illustrations, or posters. - Building an app or website requires collaboration among designers, developers, product managers, and other specialists. - This broader, team-oriented workflow has contributed to the growth of the product development software market. ## A Broad and Competitive Market - Figma portrays its market as highly dynamic, with both comprehensive platforms and specialized tools. - Competitors and adjacent products mentioned include: - Sketch, Penpot, and Figma - Miro, Flinto, Anima, ProtoPie, and Zeplin - Salesforce’s low-code development tools - The company argues that new startups and products enter the market frequently, while AI is accelerating innovation. - Figma says its competitive landscape slide became outdated only three weeks after it was created. ## Adobe’s Position - Adobe XD had previously competed with Figma but was placed into maintenance mode after Adobe stopped developing new features. - Photoshop and Illustrator serve different purposes, such as photo editing and advanced illustration. - Figma argues that those tools are not designed for collaborative website and application development. ## The Proposed Benefits of Combining Figma and Adobe - Figma contributes collaborative product design and development expertise. - Adobe contributes widely used creative tools and access to hundreds of millions of users. - Figma argued that the companies’ complementary strengths could create new consumer benefits, including closer connections between design, creativity, and product development. - The proposed acquisition was announced on September 15, 2022, as a major collaboration between the companies. ## Regulatory Outcome - Despite Figma’s efforts to demonstrate that the deal would benefit users and occur in a competitive market, regulatory concerns continued for fifteen months. - On December 18, 2023, Figma and Adobe abandoned the proposed acquisition because they no longer saw a path to regulatory approval.

Figma AI Prototyping Product Design+4

figmaNov 13, 20233 min readCurated summary

Config 2024: Designing a Better Conference | Figma Blog

Config 2024 is presented as a community-centered conference shaped by lessons from Figma’s previous events. Scheduled for June 26–27 in San Francisco, it aims to improve both the learning program and attendee experience through reserved breakout seating, more developer content, expanded networking, and greater accessibility. Figma’s goal is to make Config a broader, more inclusive gathering for everyone involved in building products. ## A Community-Driven Conference - Config has grown from its first 1,000-person conference in 2020 into a larger global community. - Figma describes the event as more than a product conference: it is intended to support learning, idea-sharing, and celebration of craft. - The 2024 program is expected to include more than 75 speakers covering design systems, AI, development, and related topics. ## Reserved Seating for Breakout Talks - Attendees can reserve places in breakout sessions instead of relying on available seating. - Registered attendees are guaranteed a seat if they arrive on time. - Very early bird ticket holders receive access to session registration 24 hours before other attendees. ## More Content for Developers - Figma is expanding programming specifically for developers. - The developer track reflects the company’s aim to serve everyone who contributes to building digital products. - Additional details about this programming were still forthcoming when the announcement was published. ## Improving In-Person Connections - The schedule will include more downtime for networking, informal conversations, and community interaction. - A larger event footprint is intended to reduce lines and crowding. - Figma expects the changes to create a smoother overall attendee experience. ## Supporting a Global Audience - Virtual attendees will receive captions in English, French, German, Japanese, Korean, and Spanish. - In-person attendees will have access to simultaneous interpretation and translation. - Figma plans to continue adding languages to future events. ## Expanding the Leadership Collective - The executive-focused Leadership Collective will return after positive feedback in 2023. - The track will include more content, a new executive briefing center, and additional networking opportunities. - Participation is invite-only, with applications available during registration. ## Registration and Participation - Very early bird tickets were available through Config’s registration site. - Scholarships were offered for qualifying attendees. - Figma invited the community to submit ideas and suggestions by email or social media. - The call for speakers was open, with applications due by December 31, 2023. Overall, Figma’s approach is to combine product announcements and educational sessions with better logistics, accessibility, and community interaction. The event is designed for designers, developers, executives, and other people involved in building products.

Figma AI Design Systems Software Development+1

figmaNov 12, 20232 min readCurated summary

Figma’s State of the Designer Report 2023 | Figma Blog

Designers appear more satisfied and optimistic despite the disruption of the past three years. Figma’s survey of 470 designers in Europe and Asia–Pacific examines how remote and hybrid work have affected collaboration, productivity, career prospects, and fulfillment. Its central conclusion is that designers are adapting successfully, while the growing strategic importance of design is improving both morale and opportunity. ## Remote Work and Job Satisfaction - 69% of designers report greater job satisfaction than before the pandemic. - Individual contributors are especially positive: 82% say their satisfaction has improved. - Designers generally feel more in control of where and how they work. - Many believe their workflows and ability to create high-quality digital products have improved, even as remote work has become more common. - Group meetings and collaborative design practices are helping teams work together remotely. ## Design’s Growing Influence - Nearly five times as many designers feel more positive about the design profession as feel more negative. - Design is increasingly viewed as a business-wide way of thinking rather than a function limited to one department. - Visible support from CEOs and other executives reinforces designers’ sense that their work is strategically important. - Leaders who participate in design files, give direct feedback, and experience product development firsthand create stronger connections with design teams. ## Improved Career Prospects - 69% of respondents say their employment options have improved or greatly improved. - Designers are encouraged by organizations placing design at the center of product and business decisions. - The profession’s growing influence is changing how designers view their roles and future opportunities. The report suggests that remote collaboration and increased executive engagement have helped designers feel more satisfied, empowered, and optimistic. Organizations can build on this momentum by supporting flexible work, investing in collaborative practices, and treating design as a core part of business strategy.

Figma User Experience Collaborative Design Design Thinking+2

figmaNov 8, 20232 min readCurated summary

Little Big Updates: When going big means thinking small | Figma Blog

Figma argues that meaningful product progress often comes from small, frequent improvements rather than headline features. Because designers may spend 40 or more hours a week in Figma, reducing friction in everyday workflows can have a greater cumulative impact than adding rarely used capabilities. Its annual “Little Big Updates” initiative formalizes this focus on quality, usability, and user joy. ## Why Small Improvements Matter - Subtle changes can save users clicks, eliminate recurring frustrations, and fix long-standing bugs. - Figma users invest heavily in learning the tool, creating a responsibility for Figma to continually improve it. - Quality-of-life updates are difficult to market, but often affect the actions users perform most frequently. - A small improvement repeated hundreds of times a day can matter more than a flashy feature used occasionally. ## The Origin of Little Big Updates - Figma originally released product updates weekly. - After accumulating four updates, the team released one per day from Monday through Thursday. - Users compared the experience to opening a new present each day. - This response inspired the “Little Big Updates” format, which gives individual improvements their own attention. ## Examples of High-Impact Details - Figma fixed paste behavior that previously placed content in seemingly random locations. - Although the change was not headline-worthy, it removed a frustration users encountered hundreds of times daily. - Text selection when switching between frames was also improved, eliminating unnecessary double-clicking. - These examples show how workflow friction can be more important than feature novelty. ## Prioritizing Big and Small Features - Major initiatives, such as AI features for FigJam, require deliberate planning and coordination. - Large features may need to be sequenced carefully so related capabilities work together. - Small improvements should be prioritized differently: teams should avoid over-planning and allow decisions to remain decentralized. - Individual teams are often best positioned to identify which usability improvements will have the greatest effect. - Every team should treat product quality as an ongoing responsibility, not as a secondary concern. Figma’s recommendation is to balance ambitious new capabilities with sustained attention to everyday details. Product teams can create substantial user value by identifying frequent sources of friction and steadily removing them.

Figma AI Figjam Product Design+2

figmaNov 7, 20232 min readCurated summary

Three Creator Fund projects to know and love | Figma Blog

The Figma Creator Fund supports creators building free plugins, widgets, templates, and educational resources for Figma Community. Since launching in March, it has awarded nearly $300,000 to 13 creators in nine countries, reaching almost a million users. The post highlights how these grants help creators solve difficult, practical problems while keeping their tools freely available. ## The Creator Fund’s Purpose - The program funds resources that expand what creators can do in Figma. - Supported projects include: - Mandarin-language design systems tutorials - Developer-platform education tools - Design-to-code plugins - Free templates and widgets - Figma prioritizes projects that: - Address challenging problems - Save users time - Offer practical value - Can remain free for the wider community - Applicants are encouraged to present a clear vision, invest effort in their application, prepare visuals, and pursue ideas they genuinely care about. ## Figma to Code by Bernardo Ferrari - Based in Curitiba, Brazil, Bernardo Ferrari created Figma to Code, a plugin that converts Figma designs into: - HTML - Tailwind CSS - Flutter - SwiftUI - The project began during the COVID-19 pandemic, when Bernardo helped rebuild a state-level virus-tracking website. - Although he had not worked extensively with web development since 2015, he used Figma as a bridge between design and implementation. ## Problems with Existing Design-to-Code Tools Bernardo found that existing plugins were limited because they were: - Too slow - Dependent on too many steps - Paywalled for full functionality - Incomplete in their support for Figma’s API - Missing important capabilities such as auto layout - Restricted to a single programming language or framework - Weak at handling responsive design and accessibility He spent two months building his own plugin, which launched in July 2020. ## Using the Grant to Modernize the Plugin - Figma and web frameworks evolved significantly after the plugin’s release, but the plugin had fallen behind. - Earlier limitations included: - Only horizontal and vertical padding - Auto layout support limited to “min” and “fixed” - The Creator Fund gave Bernardo the resources to update the plugin without introducing a paid tier. - The grant also enabled him to add support for Figma’s Dev Mode. - He completed the major update in roughly a month and launched it during Config 2023. - Bernardo describes the fund committee as supportive and encouraging toward creators with ambitious ideas. The post’s supplied excerpt ends during Bernardo’s account of launching the update at Config 2023, before the other Creator Fund projects are presented.

Figma Design To Code HTML Figma Plugins+3

figmaOct 25, 20232 min readCurated summary

Storyboarding the Future of Design and Creativity | Figma Blog

The post imagines how a Figma–Adobe partnership could transform design workflows by connecting products, assets, collaboration, AI, and storytelling. It envisions a future where ideas move instantly from user research to interactive storyboards, 3D models, prototypes, and marketing videos. The proposed merger was ultimately abandoned in December 2023 after the companies concluded regulatory approval was unlikely. ## From User Journeys to Storyboards - User journeys could be converted from basic sticky-note diagrams into visual storyboards. - More engaging formats would make it easier for teams to understand, discuss, and improve product experiences. ## Connected Assets Across Tools - Assets created in Adobe Substance 3D could be placed into Figma mockups. - Linked assets would remain synchronized, reducing manual updates across products. - Shared design systems could connect colors, fonts, and other design tokens between Adobe and Figma. - Adobe Fonts could become available directly within Figma. ## Multiplayer Collaboration in 3D - Adobe’s 3D tools could gain Figma-style multiplayer collaboration. - Multiple designers could work simultaneously on different aspects of a model, such as geometry, lighting, and textures. - Real-time collaboration could make learning complex 3D workflows easier. ## Generative AI in Product Design - Adobe Firefly could integrate directly into Figma workflows. - Designers could generate backgrounds that match an interface’s visual style. - Generative Fill could extend images to fit responsive layouts without leaving the design process. ## Prototypes Connected to Marketing - Working app prototypes could be inserted directly into launch videos. - Updates made to the product could automatically appear in the video, helping marketing teams keep pace with last-minute design changes. The post presents these integrations as a vision for a more connected and collaborative creative ecosystem, though the planned Figma–Adobe merger did not proceed.

Figma Design Systems Prototyping Generative AI+4

figmaOct 24, 20232 min readCurated summary

Figma Participates in TISAX Assessment for the European Automotive Industry | Figma Blog

Figma announced its participation in the Trusted Information Security Assessment Exchange (TISAX), a security and compliance benchmark for Europe’s automotive industry. The assessment is intended to reassure automotive customers that their design files are securely managed according to industry standards. Figma positions TISAX alongside its broader European data-protection efforts, including EU Cloud Code of Conduct certification and EU-based file hosting. ## TISAX and Automotive Data Security - TISAX is governed by the ENX Association on behalf of the German Automotive Industry Association (VDA). - It is widely recognized as a data-security and protection benchmark in Europe’s automotive sector, particularly in Germany. - Participation gives automotive product designers greater confidence that their Figma work is handled securely and compliantly. ## Figma’s Assessment Details Figma’s participation can be verified through the ENX portal using: - **Company:** Figma, Inc. - **Scope ID:** S3XH77 - **Assessment ID:** AV01AK-2 ## Broader European Compliance Efforts Figma describes TISAX as part of its wider investment in serving European customers: - It has received a compliance mark under the **EU Cloud Code of Conduct**. - Customers can choose to host Figma and FigJam files within the **European Union**. - These measures complement Figma’s broader security and compliance program. Figma’s participation in TISAX signals that organizations in the European automotive industry can use its collaborative design tools with greater assurance about security, compliance, and regional data-handling requirements.

Figma Information Security Compliance Cloud Hosting+1

figmaOct 17, 20233 min readCurated summary

Figma's commitment to FedRAMP | Figma Blog

Figma is pursuing FedRAMP Moderate certification to make its collaborative design platform available to US government agencies and public-sector organizations. The certification process demonstrates that Figma meets rigorous security and privacy requirements and would allow government teams to safely design, prototype, and test digital services. Figma argues that its browser-based, collaborative workflow could help agencies iterate faster and improve citizen-facing software. ## FedRAMP Status and Purpose - Figma’s FedRAMP Moderate authorization is currently “in process.” - Listing on the FedRAMP Marketplace indicates that Figma has completed an audit and is moving through the final certification steps. - FedRAMP evaluates cloud applications against government security controls and categorizes them as low, moderate, or high impact. - Certification is necessary before Figma can fully host government data. ## Benefits for Public-Sector Users - Certification would allow government agencies, contractors, and civic-technology teams to: - Create software designs in Figma - Build and test interactive prototypes - Validate ideas through rapid iteration - Improve the usability of government applications - Figma says the certification will give customers confidence that their data and content meet demanding security and privacy standards. - Its browser-based and platform-agnostic design supports collaboration among distributed teams, including agencies and contingent workers. ## Public-Sector Collaboration and Modernization - The shift toward hybrid and remote work has increased demand for accessible, collaborative digital tools in government. - Figma connects this trend with broader efforts to improve customer experience and rebuild trust in government services. - The company believes public-sector organizations often work similarly to private companies despite having different missions and business models. - Collaborative design could help agencies ship services more quickly and achieve better outcomes for citizens. ## Building a Federal Government Team - Figma is expanding its federal-government organization, beginning with federal sales leader James Kohler. - The company is seeking people who understand government procurement and security requirements while also being able to build new programs from the ground up. - Kohler’s role is to adapt lessons from Figma’s private-sector work to the needs of government users. - Figma plans to encourage knowledge sharing between its commercial and government teams. ## Next Steps - Figma’s immediate goal is to complete FedRAMP certification and become authorized for federal use. - The company intends to continue engaging public-sector customers and sharing updates about its government efforts. Figma’s certification effort is a prerequisite for broader government adoption. If completed, the platform could give public-sector teams a secure way to collaborate on and rapidly improve digital services.

Figma Prototyping User Interface Security+4