techlist.io
KREN

Design Systems

252 posts

figma3 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.

Read original(opens in new tab)
Design SystemsFigmaAISoftware Development+1
figma2 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.

Read original(opens in new tab)
Design SystemsFigmaPrototypingGenerative AI+4
figma2 min readCurated summary

Dan Mall’s 10 Principles for a Worthy Design Career | Figma Blog

Dan Mall’s approach to a worthwhile design career centers on deliberate choices, continuous learning, and using experience strategically. He argues that designers should pursue goals that genuinely matter, improve their odds by leveraging their existing advantages, and define the desired outcome before beginning. His career across agencies, startups, teaching, and writing illustrates how varied experiences can reinforce one another. ## A Career Built Through Experimentation - Mall’s 25-year career has included agency work, entrepreneurship, teaching, apprenticeships, and authorship. - He views each role and project as an opportunity to learn, solve problems creatively, and grow personally. - His work includes founding an agency, launching startups, teaching thousands of students, and writing books about pricing, design systems, and scalable design. - Continuous learning means more than following trends; it involves expanding one’s capabilities and finding better ways to solve problems. ## Identify Worthy Goals - Before committing to an endeavor, Mall asks: - What outcome do I envision? - Will that outcome leave me better off? - He considers goals most worthwhile when they are thrilling, important, and daunting, following Michael Bungay Stanier’s framework. - His decision to start an agency grew from a desire to spend more time with his family while creating a more flexible career. - Excitement is especially important to him: if an idea does not inspire him, he generally does not pursue it. ## Place Bets on Unfair Advantages - Every decision is a bet because choosing one path means giving up others and accepting an opportunity cost. - Designers can improve their chances by choosing opportunities that exploit their strengths, such as: - Expertise - Reputation - Relationships and network - Resources - Unique insights - Mall’s agency benefited from his prior agency experience, established reputation, and steady client base. - He references the MILES framework for identifying advantages: - Money - Intelligence and insight - Location and luck - Education and expertise - Status - His experience running a design-at-scale agency gave him similar advantages when launching Design System University. ## Begin With the End in Mind - Mall follows Stephen Covey’s principle of defining the desired destination before starting. - When he began conference speaking, he set a specific goal: eventually speak at An Event Apart, whose speakers he admired and whose work influenced his development. - Clear, achievable outcomes help turn broad ambitions into focused career decisions. A practical takeaway is to choose goals that genuinely excite you, assess the advantages you already possess, and define success before investing significant time and energy.

Read original(opens in new tab)
Design SystemsFigmaUser ExperienceWeb Design+2
figma2 min readCurated summary

What Codegen Is (Actually) Good For | Figma | Figma Blog

Code generation is most useful as an augmentation to the design-to-development process, not as a replacement for developers. Figma found that fully automated design-to-code output often fails because teams use different frameworks, codebases, and patterns. Instead, codegen works best when it provides context, suggestions, and a useful starting point that developers can refine themselves. ## Codegen’s Broad Ecosystem - Codegen automatically produces code from rules or specifications. - It ranges from: - IDE completion tools such as Microsoft IntelliSense - Reusable templates and snippets - Visual programming and no-code platforms such as Bubble - AI assistants such as GitHub Copilot and Replit Ghostwriter - AI codegen adoption is high: 82% of developers surveyed by Stack Overflow in 2023 said they already write code with AI tools. - Trust remains low, however; fewer than 3% reported highly trusting the accuracy of these tools. ## Why Fully Automated Design-to-Code Falls Short - Figma initially envisioned Dev Mode as a way to automate design-to-code conversion. - Early results were promising, but developers often found the generated code impractical or not useful. - Producing code that fits a wide range of frameworks, architectures, and team conventions is difficult. - The better goal is “intelligence amplification”: technology should extend a developer’s capabilities while keeping the developer in control. ## From 0 to 0.5 - Codegen is particularly effective at helping developers move from a blank screen to a partial implementation. - In products with established design systems and component libraries, it can: - Suggest the appropriate component - Surface component names and property values - Reduce guesswork during design handoff - Rather than generating a complete solution, codegen helps developers reach a useful starting point faster. ## Applying Codegen to Existing Design Systems - Codegen delivers the most value when customized for a specific team, company, and workflow. - If a design system and component library already exist in Figma, teams may not need a separate automated design-to-code application. - More useful alternatives include: - Referencing design tokens and variables - Viewing component documentation - Building a Figma codegen plugin - Generating custom code snippets - These tools help developers understand a design quickly while allowing them to write code that matches their own codebase. The practical recommendation is to use codegen as a guided assistant: provide suggestions, reusable patterns, and context, but leave architectural decisions and final implementation to developers.

Read original(opens in new tab)
Design SystemsFigmaDesign To CodeComponent Library+4
figma3 min readCurated summary

How Spotify’s Design System Goes Beyond Platforms | Figma Blog

Spotify’s expansion to 45 platforms and more than 2,000 device types exposed inconsistencies between its product experiences. The company evolved Encore from separate mobile and web systems into a cross-platform design system focused on shared foundations and reusable components. Its goal is to make Spotify feel coherent everywhere without erasing the distinctive strengths of each platform. ## The Challenge of Consistency at Scale - Spotify’s 2019 ubiquity strategy aimed to make audio available across TVs, cars, computers, phones, and many other devices. - The design team needed more than broad platform coverage: users should recognize the experience as distinctly Spotify wherever they use it. - Components became central to achieving this consistency, from defining their scope to implementing them across products. ## The Birth and Evolution of Encore - When introduced in 2019, Encore had two main subsystems: - **Encore Consumer Mobile**, a flexible catalog of mobile-focused UI components. - **Encore Web**, supporting a wider range of web products. - Both systems used shared design tokens for foundational decisions such as colors and typography. - Over time, differences in component sizing, typography, and state treatments revealed that the subsystems needed greater commonality. - By 2022, flexibility had created too much divergence, prompting Spotify to rebalance the system toward reusable, consistent components. ## A Shared Layer Between Foundation and Products - Spotify created a specialized team focused on reusable components for Encore Mobile. - This new layer sits between the foundational system and Encore Consumer Mobile. - It acts as a “first line of defense,” reducing the need for product-specific teams to build every component themselves. - Developed in collaboration with Encore Web, the layer establishes platform parity from the beginning rather than retrofitting consistency later. ## Designing Components Across Platforms - The overall workflow remained familiar: research, design, and development. - The major change was coordinating design work across iOS, Android, and Web instead of designing for one platform in isolation. - Components are intended to share a coherent visual and behavioral language while still adapting to platform-specific requirements. - This requires collaboration among specialists, since web and mobile designers bring different domain expertise. - Spotify begins by bringing platform teams together and researching each platform’s unique characteristics before creating the shared component. Spotify’s approach treats a design system as more than a collection of platform-specific libraries. By establishing shared components early and combining them with platform-aware design, teams can create experiences that feel unified without sacrificing the qualities that make each device and interface effective.

Read original(opens in new tab)
Design SystemsAndroidiOSDesign Tokens+3
figma2 min readCurated summary

The Future of Design Systems is Semantic | Figma Blog

Design systems are moving from static component libraries toward semantic, reusable values that connect design and code. Figma argues that variables extend design tokens by supporting theming, dynamic prototypes, and platform-agnostic reuse. This shift can make large-scale systems more consistent and easier to maintain. ## Variables as the Next Step for Design Systems - Figma variables store reusable values for design properties and prototyping actions. - They reduce repetitive work and help teams manage complex design systems. - Unlike static tokens, variables can change based on context, enabling: - Design theming - Dynamic prototyping logic - Closer alignment between design and code - Figma introduced variables alongside Dev Mode and other features intended to connect designing and building. ## The Design Token Foundation - Design tokens represent repeatable decisions such as: - Colors - Typography - Sizing - Border radii - Numbers and strings - Tokens separate design properties from specific components or implementation details. - A single token can be updated centrally and propagated throughout one or multiple products. - This platform-agnostic structure reduces redundancy and helps maintain consistency. - Salesforce is often credited as an early design-token pioneer, using tokens to apply shared principles across platforms. ## Google Maps and Palette Governance - Google Maps discovered its product used more than 700 colors. - The team reduced the palette to 25 hues by removing subtle tones and transparency effects. - Tokens helped document and distribute the smaller palette. - Centralized values make it easier to prevent a carefully designed system from gradually expanding back into uncontrolled variation. ## From Tokens to Semantic Systems - Tokens codify design decisions, but variables add behavior and flexibility. - Their reusable, changeable values support broader system-level use cases than fixed tokens alone. - Figma presents this evolution as part of a larger industry shift toward design systems that express meaning and relationships rather than merely storing visual values. Teams should treat tokens and variables as shared semantic infrastructure: define reusable values centrally, connect them to implementation, and use contextual variation deliberately for themes and interactive experiences.

Read original(opens in new tab)
Design SystemsFigmaPrototypingDesign Tokens+2
figma2 min readCurated summary

The Shared Language of Props | Figma | Figma Blog

Design and engineering use the same component vocabulary, but often attach different meanings to terms such as “property,” “variant,” and “button.” Figma properties primarily describe visual variations, while code props may also control behavior, events, data, and rendering. Effective collaboration therefore requires translating concepts across environments rather than assuming identical names imply identical implementations. ## Components and Properties as Shared Concepts - Components are reusable elements governed by rules describing how they can look and behave. - Properties, or “props,” define the possible expressions of a component, including: - Variants - Boolean values - Instance swaps - Text values - In Figma, properties are used mainly to represent visual differences. - In code, props can also represent non-visual concerns such as event handlers and data. - A shared term can conceal different assumptions when designers and developers work in different tools and contexts. ## A Button Is Not the Same Everywhere - Designers and developers both work with buttons, but prioritize different concerns: - Designers focus on visual consistency and maintainability across design files. - Developers focus on interactivity, rendering, accessibility, and implementation. - A Figma button and a code-based button may share a name without sharing the same API or purpose. - Migrating a React and TypeScript application to a design-system-based frontend exposed conflicts between Material UI conventions and the organization’s custom design system. - The component library aimed to be intuitive and lightweight for full-stack engineers who primarily connected frontend and backend systems. ## Divergent Component Models - The design system contained two Figma components: - `Button` - `IconButton` - The codebase contained five button components. - Figma’s `Button` and `IconButton` did not use the same inheritance or primitive-component structure as the codebase. - Some properties, such as size and color variants, were duplicated in Figma because that structure better represented the design model. - Although the components shared names and broad concepts, they did not share the same purpose or complete set of properties. Teams should treat design and code components as related models rather than identical ones. Clear translation of property names, meanings, and responsibilities can preserve each environment’s strengths while reducing misunderstandings during implementation.

Read original(opens in new tab)
Design SystemsFigmaReactTypeScript+3
figma2 min readCurated summary

How Thumbtack structures their design system | Figma Blog

Thumbtack structures its Thumbprint design system as three layers: design tokens, atomic CSS, and reusable UI components. Each layer trades some flexibility for greater productivity, consistency, accessibility, and quality. The approach lets developers choose the highest-level solution that fits their needs while retaining lower-level escape hatches for custom or native experiences. ## Three-Layer Architecture - **Thumbprint Tokens** - The foundation shared by web and native clients. - Defines granular properties such as colors, typography, spacing, sizing, radii, and shadows. - Offers the greatest flexibility but the least built-in structure. - **Thumbprint Atomic** - An atomic CSS library built on the tokens. - Enables developers to build interfaces without writing custom CSS. - Includes utilities such as aspect-ratio classes for maintaining proportions in responsive or embedded media. - **Thumbprint Components** - Provides accessible, prebuilt implementations of common patterns, including alerts, buttons, date pickers, and star ratings. - Improves development speed, consistency, and accessibility. - Developers can fall back to Atomic or Tokens when no suitable component exists. ## Layered Components and Tokens - Individual layers can contain their own sub-layers for added flexibility. - Thumbprint’s modal system separates: - `ModalCurtain`, which supplies core usability and behavior without visual styling. - `Modal`, which adds the standard visual design on top of `ModalCurtain`. - Developers generally use the more prescriptive `Modal`, but can use `ModalCurtain` for unusual requirements. - Tokens can also inherit from one another. For example, a semantic token such as `button-cta-background-color` may derive from a broader token like `cta-background-color`, which ultimately maps to a raw value such as `blue-400`. - Users are encouraged to select the highest abstraction appropriate for their use case. ## Why the Structure Helps - Higher layers reduce repeated work and improve consistency. - Lower layers preserve flexibility for custom product needs. - Components allow engineers to focus on product functionality instead of rebuilding common UI patterns. - Layered primitives provide a controlled way to support exceptions without abandoning the design system. - The architecture is intended to simplify maintenance and save time for both developers and end users. Thumbprint’s model demonstrates that a design system does not need to choose between standardization and flexibility. A layered structure provides strong defaults while preserving lower-level tools for cases that require customization.

Read original(opens in new tab)
Design SystemsReactAccessibilityDesign Tokens+3
figma3 min readCurated summary

Config 2023 in Review: The Complete Recap | Figma Blog

Figma’s Config 2023 announcements reposition the platform as a workspace for the entire product development team, not just designers. The major launches—Dev Mode, variables, and advanced prototyping—aim to connect design more directly with code, development workflows, and real product behavior. Supporting updates to auto layout, fonts, and file discovery further improve everyday work, while Figma also signals a major investment in AI through its acquisition of Diagram. ## Dev Mode Connects Design and Development - Dev Mode is a dedicated Figma workspace designed around developers’ needs. - It helps developers: - Translate designs into code more quickly. - Connect Figma to Jira, GitHub, Storybook, and other tools through plugins. - Track designs and changes that need to reach production. - Inspect Figma files alongside code in VS Code. - Dev Mode launched in beta and was available free through 2023. ## Variables Bring Design Systems Closer to Code - Figma introduced variables to make design systems more flexible and scalable. - Variables can store reusable: - Colors - Numbers - Text values - Boolean values - They support aliasing and scoping, allowing teams to organize and contextualize values. - Variable modes enable themes such as light and dark designs. - Plugin and REST API support allows teams to manage variables programmatically. - The goal is to connect design tokens and systems more directly with the code that implements them. ## Advanced Prototyping Makes Designs More Dynamic - Variables can now be used in prototypes to represent changing application state. - Designers can use mathematical expressions and conditional logic, such as: - Increasing a number variable after each click. - Navigating to different screens depending on a variable’s value. - These capabilities let teams test realistic interactions before development begins. - In-context editing and inline preview allow designers to edit and play back prototypes in the same view. ## Quality-of-Life Improvements - Auto layout gained wrapping and minimum/maximum width and height controls. - The font picker now supports search, filtering, and previews displayed in each font. - The file browser makes it easier to locate files and projects shared by external teams. ## Figma’s Investment in AI - Figma expects AI to help people express ideas visually, speed up workflows, and create strong first drafts. - The company argues that turning a good draft into a world-class product will still require human judgment and expertise. - Figma acquired Diagram, founded by Jordan Singer, to accelerate AI development across the platform. - Diagram had previously built AI-assisted design tools on Figma’s platform. Overall, Config 2023 presents Figma as a shared environment spanning design, prototyping, development, and increasingly AI-assisted creation. Teams should consider Dev Mode and variables as the most significant changes for improving handoff, design-system management, and collaboration with engineering.

Read original(opens in new tab)
Design SystemsFigmaPrototypingDesign Tokens+4
figma3 min readCurated summary

Introducing Figma’s New Dev Mode | Figma Blog

Dev Mode is Figma’s dedicated workspace for developers, designed to reduce friction between design and implementation. It provides familiar inspection tools, customizable code output, integrations with development workflows, and an extension for VS Code. Figma’s broader goal is to keep designers and developers working from the same, up-to-date source of truth. ## A Developer-Focused Workspace - Dev Mode works like a browser inspector for Figma files. - Developers can inspect layers and designs to find: - Measurements and implementation specs - Exportable assets - Design-system context - Connections between visual elements and code concepts - The interface is intended to feel familiar to developers who use tools such as Chrome DevTools. ## Faster, More Flexible Code Handoff - Dev Mode’s code panel includes: - A CSS box model - Modern syntax and tree views - Configurable dimension units - Customizable output for different languages and codebases - Generated code is positioned as a starting point that reduces repetitive translation from design to implementation. ## Connecting Design to the Development Toolchain - Figma’s GitHub integration links designs and components with files, issues, and pull requests. - Plugins connect Figma to tools including: - Jira, Linear, and GitHub for project tracking - Storybook for viewing coded components alongside designs - AWS Amplify Studio, Google Relay, and Anima for code generation - Teams can also build custom plugins to match their own workflows. - Design tokens and variables further improve consistency between design systems and code. ## Tracking Work Toward Production - Dev Mode is intended to support the increasingly blurred boundary between design and development. - It helps teams understand what is ready for implementation and maintain context while designs continue to evolve. - Figma emphasizes collaboration around work that remains in progress rather than waiting for designs to be fully polished. ## Bringing Dev Mode into VS Code - The Figma for VS Code extension lets developers: - Review designs - View comments and notifications - Track design changes - Inspect designs without leaving the editor - Use design-based code autocomplete - This keeps design context inside the developer’s primary coding environment. ## Availability and Pricing - Dev Mode and the VS Code extension were announced as beta features, free to all users through the end of 2023. - Beginning in 2024, Dev Mode requires a paid plan. - Dedicated Dev Mode-only access was planned at: - $25 per seat per month on Organization - $35 per seat per month on Enterprise Figma presents Dev Mode as an initial step toward tighter designer-developer collaboration. Teams should use it alongside integrations such as GitHub, Storybook, and VS Code to keep specifications, implementation context, and feedback in one continuously updated workflow.

Read original(opens in new tab)
Design SystemsFigmaGithubCSS+4
figma3 min readCurated summary

AI: The Next Chapter in Design | Figma Blog

Figma argues that AI will become a core platform capability reshaping the entire product-development process, not merely another feature. It can accelerate ideation, design, and coding while allowing teams to focus more on problem-solving and creative judgment. Figma announced its acquisition of Diagram as part of this strategy, positioning AI as a force that will change how products are designed, what experiences are created, and who participates in the process. ## Figma’s AI strategy and Diagram acquisition - Figma acquired Diagram, founded by Jordan Singer, whose GPT-3-powered “Designer” plugin generated design concepts from simple prompts. - The acquisition brings Diagram’s team into Figma and builds on Figma’s existing investment in machine learning. - Figma’s open API has already enabled nearly 100 community-built AI plugins. - The company views AI as a platform underlying the entire product-development workflow. ## AI across the product-development process - During discovery, AI could: - Generate and synthesize early ideas from prompts. - Summarize discussions and concepts. - During design, AI could: - Use existing designs and design systems to provide recommendations. - Surface relevant components and patterns. - Help teams produce first drafts faster. - During development, AI could: - Infer design context more effectively. - Generate higher-quality, production-ready code. - The broader goal is to help teams do more work faster while moving their attention toward higher-level problem-solving. ## How design may evolve from pixels to patterns - Design systems already shifted designers away from repetitive details such as border radii and toward composition, direction, and judgment. - Atomic elements such as pixels became reusable components, enabling faster and more consistent workflows. - AI could extend this progression by generating higher-level structures and patterns. - Designers may focus less on assembling basic login components and more on inventing entirely new ways to authenticate. - AI might also recommend color palettes based on a project’s emotional tone or theme. - This could move design beyond familiar interfaces toward smoother, more intuitive, and more human experiences. ## What product teams may design - AI systems such as ChatGPT are shifting interaction away from navigating websites and apps toward asking questions and receiving answers. - AI can reduce the gap between a user’s intention and the actions required to achieve it. - For example, instead of opening a ride-hailing app, entering a destination, comparing options, and requesting a ride, a user could simply say, “Get me to JFK.” - Product builders will need to reconsider whether existing interfaces can deliver the same outcome with fewer steps and decisions. ## The changing role of designers - Technological change has historically transformed design without eliminating the need for thoughtful designers. - Designers have adapted to new platforms, collaborative workflows, and hybrid work. - Figma expects AI to change design roles and collaboration, but frames that shift as an opportunity to spend more time on creative direction, curation, and meaningful problem-solving. The practical recommendation is to treat AI as a foundational design and development capability rather than a standalone feature. Teams should explore how it can remove repetitive work while preserving human judgment, taste, and responsibility for the experiences they create.

Read original(opens in new tab)
Design SystemsAIMachine LearningGenerative AI+4
figma2 min readCurated summary

Introducing Shortcut letter from the editor | Figma Blog

Shortcut is Figma’s redesigned blog, created to tell richer stories about the people, processes, and ideas behind new products. Its central philosophy mirrors Figma itself: collaboration, experimentation, and the way user input transforms tools over time. The new experience aims to make content more immersive, discoverable, and inspiring rather than static or one-directional. ## A Blog Built Around Collaboration and Play - Figma compares product development to games, where people create “house rules” and shortcuts to improve shared experiences. - This idea reflects Figma’s history as a web-based, multiplayer design tool. - Although collaborative editing initially seemed risky, user behavior and community feedback helped shape Figma’s evolution. - Shortcut will showcase how teams and users bring collaborative design to life through stories about process, craft, and problem-solving. ## A More Immersive Content Experience - The blog redesign replaces a static reading experience with a more dynamic and visually engaging one. - New articles cover: - Design systems - Engineering - Product design and development - Company culture - Behind-the-scenes work - Technical explorations - Examples include stories about Linear responding to a DDoS attack, font failures, and how Figma’s engineers draw inspiration from gaming. ## Improved Navigation and Visual Identity - Readers can sort content by topic and browse curated special collections. - Shortcut features new illustrations and motion work from a range of independent artists. - The redesign treats editorial design, animation, and artwork as essential parts of the storytelling experience. - Figma also invites writers, designers, and other creatives to collaborate with its editorial team. ## Inspiration Through Shared Ideas - Shortcut is built around “input for output”: one idea should lead to another, with inspiration moving in both directions. - The blog aims to encourage readers—and Figma’s own teams—to experiment, share ideas, and have more fun. - Stories range from curated series such as the Future of Design Systems to opinion essays, technical deep dives, and unexpected examples like a band using a Figma slide deck to relaunch its career. Shortcut positions Figma’s blog as an extension of its collaborative product philosophy: a place where stories, disciplines, and perspectives connect to inspire new possibilities.

Read original(opens in new tab)
Design SystemsFigmaProduct DesignMultiplayer Collaboration+2
figma2 min readCurated summary

Four years in, here’s what Config tells us about the state of design | Figma Blog

Config 2023 submissions suggest that the design industry is emerging from pandemic-era uncertainty with renewed optimism. Figma analyzed more than 1,000 conference proposals and found increasing interest in accessibility, creativity enabled by design systems, and broader collaboration. Overall, the submissions portray designers as focused on turning recent challenges into opportunities for more scalable, inclusive, and effective product development. ## A More Optimistic Design Community - Config submissions increased from 420 in 2021 to 520 in 2022 and more than 1,000 in 2023. - Positive sentiment rose from 63% of submissions in 2021 to 72% in 2023. - Submissions increasingly emphasized possibilities and ways teams had “thrived,” rather than focusing on outdated practices or persistent problems. - References to the pandemic fell to one-sixth of their 2021 level. - Mentions of “remote” declined by roughly 20%, suggesting that teams are adapting to changed work patterns. ## Design Systems as Creative Infrastructure - The perceived divide between creative freedom and systematic processes is narrowing. - Designers increasingly view design systems as tools that reduce repetitive work and create more space for creative thinking. - Teams operating at scale are investing in design tokens and reusable systems to maintain speed and consistency. - In 2021, design-system discussions focused mainly on foundational tasks such as auditing, scaling, and establishing basic infrastructure. - By 2023, submissions connected design systems more directly with creativity and visual expression, using terms such as “art,” “transition,” “color,” and “creating.” The emerging view is that systems do not suppress creativity; they can provide the structure and efficiency needed to support it.

Read original(opens in new tab)
Design SystemsFigmaAIAccessibility+3
figma2 min readCurated summary

The Future of Design Systems Is Accessible | Figma Blog

Design systems can make accessibility a scalable, built-in practice rather than a late-stage compliance task. By standardizing accessible colors, components, documentation, and feedback processes, they allow improvements to spread across an entire product ecosystem. The article also highlights AI as an emerging tool for detecting and fixing accessibility issues, while emphasizing the need for responsible implementation. ## Accessibility and design systems belong together - Only about 3% of the internet was accessible to people with disabilities in 2022. - Design systems offer a way to improve that figure by embedding accessibility rules into shared components and guidelines. - In-house design system adoption increased by 22% in 2020, and 47% of surveyed organizations reported including accessibility guidelines. - Accessible design is both a social responsibility and a business opportunity, given the global population of people with disabilities and their significant purchasing power. - Accessibility can be integrated into: - Tested foreground and background color combinations - Individual UI components - Consistent documentation and usage guidance - Ongoing feedback and testing processes - System-level changes can be propagated across many product instances, making accessibility fixes more efficient and consistent. ## Responsible AI in accessibility - Design system teams are increasingly exploring AI to improve accessibility. - New AI-powered tools aim to identify and resolve common issues automatically. - Potential applications include: - Generating descriptions for images - Labeling buttons that lack accessible names - Adding semantic structure to interfaces - These tools can accelerate accessibility work, but they should supplement—not replace—human expertise, testing, and accountability. Design systems should treat accessibility as a foundational requirement from the beginning. Teams can make the greatest impact by combining accessible system components and standards with continuous testing, inclusive feedback, and carefully governed automation.

Read original(opens in new tab)
Design SystemsAIAccessibilityWcag+2
figma3 min readCurated summary

The Future of Design Systems is Automated | Figma Blog

Design systems are moving from static libraries toward automated, extensible ecosystems powered by plugins, widgets, and AI. These tools can automate repetitive work, expand Figma’s capabilities, and increasingly generate or recommend design solutions using existing system components. The article argues that automation will change designers’ responsibilities, but not eliminate the need for human judgment, creativity, and strategy. ## Plugins and Widgets as Design-System Extensions - Plugins have a long history in design and publishing software, dating back to tools such as HyperCard and QuarkXPress. - They created a broader ecosystem in which users could build and share custom effects, brushes, styles, and workflows. - In modern design systems, plugins generally serve two purposes: - Automating repetitive existing tasks. - Extending product capabilities through analytics, testing, accessibility checks, and other functionality. - Widgets add collaborative and visual tools directly to the design workspace, helping teams organize information and communicate around design systems. ## Automating Repetitive Tasks - Plugins can reduce manual work involved in maintaining and applying design-system assets. - Automation allows designers to spend less time on mechanical operations and more time on problem-solving and decision-making. - The broader trend reflects a shift from tools merely supporting designers to tools actively performing parts of the design process. ## Extending Design-System Capabilities - Plugins can provide capabilities that are not included in a core design application. - Examples include: - Gathering usage and library analytics. - Testing designs. - Improving accessibility. - Connecting design workflows to other tools and systems. - This extensibility enables teams to adapt their design environment to specialized organizational needs. ## AI-Assisted Design - Earlier experiments, such as Airbnb’s 2017 work on generating code from low-fidelity wireframes, demonstrated the potential of machine-learning-assisted design. - More recent tools such as Diagram’s Genius can analyze Figma files and suggest designs using components from an organization’s design system. - These developments suggest that AI is beginning to make earlier prototypes practical. - AI tools may eventually help generate interfaces, recommend components, complete workflows, or produce code from design input. ## Changing Roles and Responsibilities - Automation raises concerns about whether designers and developers will be replaced by software. - The article frames this as a question about how tools shape professional practice, rather than simply whether they eliminate jobs. - As routine production becomes automated, human designers may focus more on: - Defining problems. - Making judgments and trade-offs. - Establishing product direction. - Applying empathy, taste, and contextual understanding. - The future of design therefore depends on how practitioners adapt alongside increasingly capable tools. Design teams should treat plugins, widgets, and AI as ways to expand human capability rather than substitutes for design thinking. The most effective systems will combine automation for repetitive work with human oversight, creativity, and strategic judgment.

Read original(opens in new tab)
Design SystemsFigmaAIMachine Learning+4