dev-mode

30 posts

figma

Introducing Figma Motion: Your Canvas Now Has a Timeline | Figma Blog (opens in new tab)

Figma Motion brings animation directly into the Figma canvas, alongside components, variables, and team collaboration. Its timeline, keyframes, presets, agent assistance, and Dev Mode support aim to make motion a shared design activity rather than a specialist handoff. The feature also enables reusable motion systems through animated components and motion variables. ## Design and Animate in the Same File - Motion is a new canvas mode alongside Design, Draw, and Dev modes. - Designers can switch a frame into Motion mode to access a timeline. - The timeline supports: - Dragging layers to control timing - Scrubbing through animations - Independent keyframes for position, scale, rotation, and opacity - Auto keyframing while the playhead is moving - Time-based comments tied to specific moments - Preset styles such as fade, move, and scale provide a quick starting point. - Animation styles can be stacked to run simultaneously or sequenced across the timeline. - Figma’s agent can guide less experienced designers and help generate or refine animations. - Motion remains in the same file as the rest of the design, reducing context switching and handoff friction. ## Build a Reusable Motion System - Animated components carry their motion behavior wherever the component is reused. - Motion can become part of a design system instead of being recreated as one-off work. - Motion variables allow teams to define reusable animation properties such as easing. - Variables can have multiple modes, letting teams switch animation behavior across an entire page or file. - Custom animation styles are planned for a future release. ## Collaboration and Handoff - Time-based canvas comments let teams review precise points in an animation. - Dev Mode gives developers access to the motion work, supporting smoother implementation. - Figma presents motion as a shared responsibility across designers, developers, and collaborators. - Atlassian users cited improved collaboration, faster feedback, and easier adoption by designers who are less familiar with animation. ## Shader Effects and Motion - Properties exposed by shaders can be keyframed on the motion timeline. - Any shader-controlled value with a slider or input field can potentially be animated over time. - This expands animation beyond Figma’s traditionally limited set of animatable properties. Figma Motion is positioned as a way to make motion native, systematic, and collaborative. Teams can prototype animations alongside interface designs, encode them into components and variables, and bring developers into the process earlier.

figma

Figma Opens a New Hub in India | Figma Blog (opens in new tab)

Figma has opened a new hub in Bengaluru to support India’s rapidly expanding design and product-development community. India is now Figma’s second-largest market by monthly active users, with strong adoption among major companies and growing interest in AI-assisted design and development. The Bengaluru office is intended to bring Figma closer to local users while helping shape the future of product creation in India. ## Bengaluru Hub and India’s Growing Community - The office opened on November 12, 2025, after more than 7,000 people registered for the launch event. - Figma says India has nearly 25,000 Friends of Figma community members. - More than 40% of Bombay Stock Exchange 100 companies used Figma as of September 2025. - Major customers include Airtel, Flipkart, Swiggy, Zomato, Myntra, Groww, and TCS. ## AI’s Impact on Design and Development Research surveying 730 design, engineering, and product leaders found that: - 93% of designers’ companies already use AI in design. - 85% of designers believe AI makes writing code easier. - 81% of developers say design is increasingly important to successful AI-powered products. These findings support Figma’s broader strategy of connecting design, code, collaboration, and AI in one platform. ## Figma’s Expanding Product Platform At the Bengaluru launch, Figma highlighted tools across its product ecosystem: - **Figma Design:** Create digital products. - **Figma Make:** Turn prompts or designs into prototypes and applications. - **Dev Mode:** Help developers translate designs into code. - **Figma Sites:** Design and publish websites. - **FigJam:** Collaborate through online whiteboards. - **Figma Slides:** Build interactive presentations. - **Figma Draw:** Create advanced vector illustrations. - **Figma Buzz:** Produce branded marketing assets at scale. Figma also introduced **Figma Weave**, based on its acquisition of Weavy, to add AI-native capabilities for image, video, animation, motion design, and VFX creation. ## Figma’s Global Expansion - 85% of Figma users were outside the United States in Q1 2025. - About half of Figma’s 2024 revenue came from international markets. - Bengaluru joins Figma offices in cities including Tokyo, Singapore, London, Paris, Berlin, Sydney, São Paulo, and New York. The new hub reflects Figma’s shift from a standalone design tool toward a global, AI-powered platform supporting the full journey from idea to product.

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

Figma Launches Brazilian Portuguese Localization | Figma Blog (opens in new tab)

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.

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

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

Figma is launching a fully localized Spanish experience for users in Spain, including translated products, culturally adapted interfaces, and dedicated support. The move reflects Spain’s strong adoption of Figma and the company’s broader strategy to serve its largely international user base. Spanish becomes Figma’s second fully localized language after Japanese, with more languages planned later this year. ## Spanish Localization Goes Beyond Translation - Figma is adapting its product experience for Spanish-speaking users through: - Full product translation - Culturally relevant user interfaces - Dedicated Spanish-language support - The rollout begins March 27 and is expected to finish by April 17. - Figma says it aims to understand the specific needs of Spanish businesses and product teams. ## Figma’s Strong Presence in Spain - Nearly half of Spain’s IBEX 35 companies use Figma, including: - Amadeus - Banco Sabadell - Cabify - SEAT - Repsol - Telefonica - Spanish users created more than 1.5 million Figma files in 2024. - Nearly 34,000 files are edited daily across the country. - The Barcelona Friends of Figma community has more than 2,000 active members, making it Figma’s largest community chapter. ## Benefits for Spanish Teams - Companies such as Telefonica and Cabify expect the Spanish interface to improve collaboration and make Figma more accessible. - Localization is intended to help designers, developers, and broader product teams communicate and work more efficiently. - The effort supports Figma’s shift toward serving the entire product development process, not only traditional design roles. ## Part of Figma’s Global Expansion - About 85% of Figma’s monthly active users are outside the United States. - Approximately half of its revenue comes from non-U.S. markets. - Around one-third of users identify as developers, while nearly two-thirds work outside traditional design roles. - Spanish localization arrives alongside Figma’s expanding product ecosystem, including: - FigJam, launched in 2021 - Dev Mode, launched in 2023 - Figma Slides, launched in 2024 - New AI capabilities and other product development tools Figma’s Spanish launch is both a response to Spain’s established user community and a broader investment in international growth. By combining language support with localized product experiences, Figma aims to reduce barriers for Spanish teams while preparing to add more languages throughout the year.

figma

Everything You Need to Know About Figma for Government | Figma Blog (opens in new tab)

Figma for Government is now FedRAMP Moderate certified, allowing U.S. federal agencies to use Figma’s collaboration and design tools in a secure, privacy-focused environment. The platform is intended to help agencies replace siloed workflows with a shared process spanning ideation, design, prototyping, and development. Figma argues that improving how digital services are built is essential to creating more accessible, consistent, and effective experiences for citizens. ## FedRAMP Certification and Product Availability - Figma for Government meets the federal government’s security and privacy requirements at the Moderate level. - The offering includes: - Figma Design - FigJam - Dev Mode - Figma Slides, planned for a future release - The certification builds on Figma’s earlier commitment to achieving FedRAMP status. ## Why Figma Built a Government Offering - Government agencies increasingly need to provide healthcare, assistance, and other services through seamless digital experiences. - Federal digital-first policies emphasize accessibility, consistency, and ease of use. - Siloed tools and disconnected teams can reduce efficiency and produce less usable products. - Figma for Government aims to give agencies secure access to the same collaborative workflows used by leading private-sector organizations. ## Government Use Cases and Examples - More than 100 government agencies and contractors already use Figma to modernize their processes. - Examples include: - The National Park Service creating an app for 431 parks and monuments. - Amtrak streamlining systems for more than 20,000 employees and 28 million passengers. - Agencies working on passport, visa, taxpayer, and citizenship services. - The official United States Web Design System design kit contains 42 components built with variables and smart layouts. - A shared Figma link gives teams a common source of truth for viewing, editing, and commenting on work. ## Collaborative Planning with FigJam - FigJam supports real-time and asynchronous collaboration for distributed teams. - Agencies can use it to: - Brainstorm ideas - Build project roadmaps - Map user journeys - Align stakeholders around strategy - Keeping planning materials in one shared workspace helps teams communicate across locations and time zones. ## Design Alignment with Figma - Designers, developers, product managers, executives, and other stakeholders can access the latest design files. - Teams can move efficiently from wireframes to prototypes, reviews, and refinements. - Shared feedback reduces delays and keeps everyone aligned on design direction. - Design systems help agencies maintain consistency, quality, and recognizable brand identities. ## Connecting Design and Development with Dev Mode - Dev Mode provides a shared space for designers and engineers. - It is designed to reduce misunderstandings about design intent, changes between iterations, and how designs map to code. - By connecting design and development workflows, agencies can reduce clarification work and move products toward implementation more efficiently. Figma for Government is best suited to agencies seeking a secure, centralized environment for collaborative digital-service development—from early planning through engineering handoff and implementation.

figma

Documentation That Drives Adoption | Design Systems 103 | Figma Blog (opens in new tab)

Clear documentation turns a design system from an abstract set of rules into a practical tool teams can use consistently. The article argues that effective documentation must explain both how to implement components and why design decisions were made. When treated as a living resource, it improves adoption, onboarding, cross-functional communication, and product consistency. ## Documentation Bridges Design and Development - Razorpay’s teams often missed details such as button states and text-field error behavior before adopting its Blade design system. - Custom, hard-coded implementations made it easy for teams to omit important states or interactions. - Designers and developers may use different terminology, leading to: - Inconsistent naming conventions - Misaligned component properties - Different expectations about product behavior and appearance - Documentation connects design intent with technical implementation. - It should capture the reasoning behind decisions, not merely catalog available components. ## Benefits of Effective Documentation - Helps teams understand design principles and implementation details. - Encourages consistent decisions across products and platforms. - Speeds up onboarding for new team members. - Creates a shared language between designers and developers. - Reduces the risk that a carefully built design system will go unused. ## Choosing a Source of Truth - The first documentation decision is determining where information should live, rather than deciding what to write first. - Maintaining consistency becomes more difficult as design systems and organizations grow. - Static PDFs stored in shared drives quickly become outdated and disconnected from daily workflows. - Modern teams can choose among dedicated documentation sites and collaborative workspaces. - The best source of truth should fit the organization’s tools, processes, and scale. ## Custom Documentation Sites - Custom sites are particularly useful for large organizations. - They can integrate deeply with existing design and development tools and organizational processes. - A dedicated site provides a centralized, discoverable location for design principles, components, usage guidance, and implementation details. Effective design-system documentation should be centralized, searchable, and continuously maintained so that it remains aligned with both the system and the teams using it.

figma

It’s Time We Expand Our Definition of Design | Figma Blog (opens in new tab)

Figma argues that design should no longer be viewed as the exclusive domain of professional designers. Marketers, developers, product managers, and other collaborators already make visual and communication decisions every day, but often lack the confidence or tools to do so effectively. Expanding access, simplifying workflows, and changing organizational mindsets can help more people participate meaningfully in design. ## Design Tools as Spaces of Belonging - Figma files can feel intimidating to non-designers, much like entering an unfamiliar gallery or professional critique. - Simply inviting someone into a design tool does not guarantee that they will feel comfortable contributing. - Tools can help create belonging by making collaboration more approachable and welcoming. ## Everyday Work Is Design - The author describes repeatedly creating thumbnails, event invitations, and other assets in marketing, product, and sales roles to avoid design bottlenecks. - These activities involve visual communication, creativity, and decisions about how audiences understand and engage with information. - Products such as FigJam, Dev Mode, and Figma Slides are already helping marketers, developers, and other partners work more confidently. - The larger shift requires organizations and individuals to recognize that design participation is not limited by job title. ## Making Design More Inclusive - Teams can support “everyday designers” through: - Templates that provide a reliable starting point. - Simpler, more accessible tools. - Features for staying on brand and finding approved assets. - Assistance with copy exploration and approval workflows. - Organizations should also educate, validate, and celebrate colleagues who want to improve their design skills. - As work becomes faster and more collaborative, these forms of support become increasingly important. Figma’s broader recommendation is to treat design as a shared organizational practice. By giving non-designers better guidance, accessible tools, and permission to contribute, teams can produce stronger work while helping more people feel that they belong in the design process.

figma

The Long and Short of It: Issue no.8 | Figma Blog (opens in new tab)

Figma’s Issue No. 8 reflects on how its community shaped the company’s 2024 releases and culture. The year included 180 product updates, a major Config conference, expanded tools for developers and product teams, and a refreshed brand identity. The central message is that Figma builds products through continuous dialogue with the people who use them. ## A Year Shaped by the Community - Figma published 180 new releases in 2024. - More than 10,000 people attended Config. - Over 220 Friends of Figma groups operated worldwide. - The company emphasizes that users do more than receive new features: they influence how those features evolve in practice. ## Expanding Figma’s Products - Figma refined its UI3 interface to give users more control. - AI tools were reworked with a more deliberate approach. - Dev Mode was enhanced to improve connections between design and code. - Figma Slides was launched to support presentations and give design work a broader stage. - The company highlights that the design process continues after launch, when users apply new tools to real workflows. ## Config and the Future of Product Building - Config 2024 was Figma’s largest conference yet, held in San Francisco with more than 10,000 attendees. - Figma points readers toward talks and advice from Config speakers. - Featured guidance focuses on creating memorable presentations and sessions that genuinely inspire audiences. - Early-bird tickets for Config 2025 were already available. ## A New Brand and Web System - As Figma expanded toward developers, marketers, and broader product teams, it updated its visual identity. - The redesign introduced a new typeface and a refreshed brand system. - Figma used its own tools to audit and rebuild its web system. - The process included streamlining components, improving workflows, refining variables and styles, and preparing the system for future growth. ## Design Inspiration and Cross-Functional Collaboration - Community templates for Figma Slides offer ways to create more engaging presentations. - Ableton Note designer Pablo Sánchez shares seven principles for designing surprising and memorable digital experiences. - One North’s Nick Villapiano argues that developers should participate actively in design rather than treating design as a handoff. - These examples reinforce Figma’s broader view that design is collaborative and extends across disciplines. Figma’s year-end message is ultimately a recommendation to keep building in conversation with users. Product launches, brand systems, developer workflows, and community events become more valuable when people actively shape how they are used.

figma

Figma 2024: We shipped it, you shaped it | Figma Blog (opens in new tab)

Figma’s 2024 product work was driven by community feedback, spanning 180 releases, UI3, AI tools, performance improvements, and new workflows for moving from concept to delivery. The company’s central conclusion is that meaningful progress comes from reducing friction while preserving designers’ existing habits. Community input shaped both major launches and small refinements across Figma, FigJam, and Figma Slides. ## UI3: Putting the Work Front and Center - Figma redesigned its interface for the first time substantially since 2019, updating typography, layout, colors, icons, labeling, and panel behavior. - Early UI3 testing revealed that floating panels disrupted users’ speed and daily workflows. - Based on feedback, panels became docked and resizable, while users could hide panels to maximize canvas space. - The eyedropper was upgraded to reuse styles and variables, switch between color formats, and create new styles or variables. ## Improving Core Design Workflows - Multi-edit simplified making changes across multiple designs. - Typography improvements added support for italic, bold, underline, underline styling, mixed paragraph spacing, and better local-font detection. - File organization improved through pinning, enhanced search filters, page dividers, and split tabs. - Drafts, content transfers, and file-moving workflows became easier for teams working across organizations. - “Suggest Auto Layout” helped users make designs more responsive. - Figma also introduced playful retro cursors inspired by DOS, Y2K, skeuomorphism, and Windows Vista. ## Performance, Collaboration, and Administration - Dynamic page loading made large design files more manageable. - Memory optimization and a revamped memory-management system improved performance in large files. - Multiplayer collaboration became smoother and more reliable. - Admin tools received new sidebar navigation and a dedicated content-management tab. - Infrastructure improvements included EU-localized file hosting, better support for large asset libraries, and stronger Enterprise security controls. ## AI Features That Reduce Friction - Visual search lets users find designs by uploading an image or selecting part of the canvas. - Asset search understands context instead of relying only on exact component names. - AI-assisted layer renaming improves file organization. - Replace Text Content generates realistic copy, while Rewrite, Translate, and Shorten help revise text. - Make an Image enables image creation and editing directly on the canvas, and Remove Background isolates subjects without requiring another tool. - FigJam’s AI mindmaps became a popular way to explore ideas and visualize connections. - Figma AI can turn a FigJam board into a Figma Slides outline and generate presenter notes. - First Draft, formerly Make Designs, was redesigned to help users move from an idea to an initial design. It was in limited beta, with planned support for custom libraries and deeper integration with existing design systems. ## Moving from Work in Progress to Shipping - Figma continued expanding tools intended to connect design work with development and presentation. - Dev Mode and Code Connect aimed to reduce developer context switching by translating design components into code. - Figma Slides supported creating high-fidelity presentations, extending Figma’s workflow beyond interface design. - The broader goal was to help teams move more smoothly from early concepts to implementation and delivery. ## Community-Led Product Development - Figma reported 10,000 Config attendees and more than 220 Friends of Figma groups worldwide. - Product decisions were shaped through beta testing, user conversations, and feedback from individual designers and organizations. - The company emphasized thoughtful AI development: AI should help express ideas and remove tedious work without replacing designers’ judgment. - Community members influenced both flagship features such as UI3 and First Draft and smaller quality-of-life improvements. Figma’s 2024 updates show a strategy focused on practical acceleration rather than novelty alone: improve the fundamentals, apply AI where it removes real friction, and build stronger bridges between design, development, and presentation. For teams, the most valuable improvements are likely the cumulative ones—better organization, faster search, stronger performance, and workflows shaped directly by how people already work.

figma

Why Devs Should Play an Active Role in Design | Figma Blog (opens in new tab)

Developers should participate actively in design rather than treating design files as read-only specifications. Nicholas Villapiano argues that Figma’s Dev Mode reduces friction, improves confidence, and creates a shared workflow between designers and developers. Teams should advocate for these tools because they understand day-to-day collaboration problems better than management often does. ## Shared Tools Create a Common Language - Dev Mode gives developers a dedicated space within Figma instead of forcing them to work cautiously in designer-oriented files. - It treats developers as contributors to the product process, not merely implementers of finished designs. - Figma’s Auto Layout offered an early example of shared understanding by resembling CSS Flexbox and making designs behave more like responsive web layouts. - Dev Mode extends that connection into a broader framework for collaboration between design and engineering. ## Developers Should Advocate for Better Workflows - Managers may not see the practical pain points developers encounter when translating designs into code. - Developers already advocate for change through GitHub issues, pull requests, and technical discussions, so they should apply the same behavior to design and collaboration tools. - Useful opportunities to raise these needs include one-on-ones, sprint retrospectives, and team meetings. ## Exploring Designs Without Fear - Dev Mode is read-only by default, preventing accidental edits or deleted work. - This works much like branch protection on `main`: developers can investigate freely without risking the source file. - Greater confidence encourages developers to explore designs instead of avoiding or cautiously navigating them. ## Comparing Design Changes Clearly - Dev Mode provides version history and visual comparisons similar to Git commit history and pull requests. - Developers can see what changed, when it changed, and who made the change. - Differences become an actionable checklist, such as updating copy, adjusting margins, or adding a component variant. ## Reducing Context Switching - Developers often lose time switching between design files, documentation, and code. - Dev Mode and related tools such as Code Connect aim to bring implementation details closer to the design workflow. - Centralizing relevant information can reduce the “tab-switching tax” and make design-to-code work more efficient. ## Practical Recommendation Developers should actively evaluate and promote shared design-development tools like Dev Mode. By creating safer exploration, clearer change tracking, and a common language around implementation, teams can improve productivity, collaboration, and morale.

figma

The Long and Short of It: Issue no.7 | Figma Blog (opens in new tab)

Figma’s “Building better” issue argues that developer experience depends on more than tools or individual teams. Strong cross-functional culture, clear processes, and intentional product principles help engineers stay productive and create better outcomes. The issue highlights approaches from VS Code, Atlassian, Linear, Decathlon, and Crunchyroll. ## Protecting the Developer’s Inner Loop - VS Code distinguishes between: - The **inner loop**: focused coding and heads-down work. - The **outer loop**: bug tracking, support tickets, meetings, and collaboration. - Frequent context switching disrupts productivity. - Teams can improve developer experience by protecting uninterrupted editor time and reducing unnecessary transitions between tools and tasks. ## Measuring Developer Joy - Atlassian extends the idea of developer experience into **“developer joy.”** - The concept emphasizes: - Pride in craft. - Foundational engineering values. - Operational practices that make work satisfying. - Atlassian treats developer joy as a guiding metric and explores how to connect it to business impact and scale it across the organization. ## Building Opinionated Software - Linear believes effective software should have a clear point of view. - Strong product opinions establish default workflows and reduce decision-making for users. - The company deliberately goes against conventional expectations when its principles lead to a better experience. - These opinions influence both Linear’s product design and internal processes. ## Integrating Design and Development with Dev Mode - Decathlon’s engineering team shares lessons from a year of using Figma Dev Mode. - A central recommendation is to start small and pursue quick wins rather than attempting a complete workflow transformation immediately. - Dev Mode can help align design-system work, engineering implementation, and collaboration between designers and developers. ## Managing Complexity with a Universal Design System - Crunchyroll operates across 15 platforms and 12 languages, making consistency difficult. - Its Universal Design System supports: - More consistent experiences across web, mobile, consoles, and other touchpoints. - Greater design-system adoption. - Clearer handoff and implementation workflows in Dev Mode. - A shared system helps teams navigate complexity without sacrificing consistency. ## Bridging Design and Code - Figma’s Toronto meetup featured Simple Design System, a UI kit backed by realistic code. - The project demonstrates how design systems can connect visual components with their implementation. - The discussion also raises a broader concern: bridging the design-development gap is not enough; teams must also maintain implementation quality. Organizations seeking better developer outcomes should treat developer experience as a company-wide practice: protect focus time, establish thoughtful defaults, invest in shared systems, and measure whether tools and processes genuinely improve engineers’ work.

figma

How Crunchyroll Clarified Confusing Workflows with Dev Mode | Figma Blog (opens in new tab)

Crunchyroll’s global scale—15 platforms, 12 languages, and many legacy workflows—makes consistent product design difficult. Its Universal Design System helps standardize experiences and improve delivery speed, but outdated processes and fragmented documentation created confusion. Moving handoff and implementation guidance into Dev Mode has made design-to-development collaboration faster, clearer, and easier to maintain. ## Crunchyroll’s Design Complexity - Crunchyroll serves around 15 million fans across: - Web and mobile applications - Smart TVs, game consoles, set-top boxes, and Roku - Nine living-room platforms - Supporting multiple languages and complex licensing requirements increases product complexity. - The company also extends beyond streaming through the Crunchyroll Store and Game Vault. - Its goal is to create a deeply relevant experience for anime fans rather than a generic service for everyone. ## Measuring Design Success - James Hsu defines successful design through two baseline criteria: - It looks good, using sound typography, grids, spacing, and visual hierarchy. - It works well, with clear content, thoughtful interactions, and no frustrating edge cases. - A design can be visually polished but still fail if users become trapped in confusing flows or loops. ## The Role of the Universal Design System - The design system promotes consistency across devices, reducing cognitive load caused by inconsistent fonts, grids, spacing, or responsive behavior. - Reusable components improve team efficiency, much like meal preparation: - Teams can build from existing solutions. - New components can be evaluated based on their cost and value. - Shared patterns speed up product delivery and help product teams validate ideas quickly. - Engineers also benefit from avoiding duplicated implementations, reflecting the “Don’t Repeat Yourself” principle. ## Adapting the Design System to Reality - Crunchyroll uses: - A foundational design layer - Separate component libraries for individual clients - The system still contains many one-off components, numerous variants, and an underdeveloped type system. - The team rejects treating the existing system as an unchangeable process. - The design system should serve current product needs, not constrain teams because of decisions made by previous teams. - Different designers are at different stages of understanding and adopting the system, making education and early investment important. ## Problems with the Previous Workflow - Design and code parity was managed through complicated Jira workflow triggers. - Component changes generated automated alerts, but time-zone dependencies and convoluted processes meant stakeholders often lacked the latest information. - Documentation was split across separate Zeplin projects for iOS, Android, tvOS, and Android TV. - Finding the right flow required invitations, navigating branches, and comparing against outdated designs. - Searching for a specific payment signup flow could take several minutes per artboard, making implementation research slow and frustrating. - Handoff statuses were ambiguous: - Designers submitted work for review. - Reviewers moved it back to “in progress.” - Exported designs were not necessarily final. - Engineers had to rely on labels such as “ready for development.” ## How Dev Mode Improved Handoff - Dev Mode gives engineers direct access to design values and helps them identify the correct component. - Designers now create a dedicated, organized page when work is ready for development. - The page is labeled “ready for development,” and engineers receive a link directly to it. - Engineers no longer need to sift through ideation or outdated explorations. - Faster loading and parsing removed a major pain point from the previous tool. - The team supported adoption through documentation and onboarding workshops for developers. - Crunchyroll is also interested in integrating Code Connect to make its existing design-system code more accessible. Crunchyroll’s experience suggests that a design system is most effective when paired with clear ownership, focused documentation, and a streamlined handoff process. Dev Mode helped replace fragmented legacy workflows with a faster path from approved design to implementation.

figma

HP Powers Up Design Handoff with Dev Mode | Figma Blog (opens in new tab)

HP built its Veneer design system to unify digital experiences across more than 100 product lines and many independent business units. By combining design language, reusable components, documentation, governance, and community feedback, HP reduced duplication and improved consistency. Figma’s Dev Mode further streamlined handoff, helping developers interpret designs faster and cutting development time by up to 50% on some projects. ## Building a multilayered design system - HP’s diverse products—including printers, laptops, and gaming systems—each have distinct brand and product requirements. - Teams previously worked in isolation, making it difficult to maintain a consistent digital experience. - Veneer evolved from a frontend component library into a broader system containing: - Design language and tokens - Shared components and patterns - Usage guidelines, code standards, and snippets - Governance and community collaboration - Its multilayered structure supports HP’s numerous sub-brands rather than forcing every product into one rigid system. ## Measuring adoption and impact - HP tracks both usage data and feedback from designers and developers. - Veneer’s iconography library includes 915 components used by 320 teams. - The library averages approximately 85,000 component inserts per week. - HP reported that Veneer saved projects 500% more time than the time invested in creating the system during 2023. - Some projects experienced a 50% reduction in development time. - Adoption remained challenging because designers were protective of their product-specific work and teams needed flexibility for different sub-brands. ## Dev Mode improves design handoff - Dev Mode gives developers direct access to design specifications in Figma, reducing meetings and repeated clarification between design and engineering. - **Compare changes** helps teams identify differences between design versions, especially when updating existing products. - **Ready for development** lets designers indicate which parts of a design are prepared for implementation, helping developers focus on the correct work. - **Variables** connect designs to primitive and semantic tokens, allowing HP’s system to scale across themes and modes. HP’s experience suggests that a successful enterprise design system must be flexible, measurable, and supported by strong collaboration. Pairing such a system with Dev Mode can make handoff clearer, reduce redundant work, and give both designers and developers more time to focus on higher-value work.