Figma

532 posts

figmaMay 4, 20252 min readCurated summary

How Polaroid Is Building its Next Era of Innovation | Figma Blog

Polaroid is reinventing its iconic instant-photography business for the digital era while preserving its creative heritage. The company uses Figma to unify design across its website, camera products, and mobile apps, enabling faster collaboration and more consistent user experiences. A centralized design system and more capable prototypes help the team validate ideas early and reduce costly development changes. ## Preserving Polaroid’s Creative Legacy - Polaroid became culturally significant through Edwin Land’s instant-camera innovations and its use by artists such as Andy Warhol, Ansel Adams, and David Hockney. - Digital photography threatened the company’s survival, leading to the closure of its last film factory in 2008. - The Impossible Project acquired the factory, recreated Polaroid film chemistry, and eventually obtained the Polaroid brand. - The modern company now combines instant cameras and film with photo printers, connected-camera apps, and other digital products. ## Building a Single Source of Truth - Before adopting Figma, designers worked in separate files and fragmented workflows. - The lack of shared components and a centralized design system caused duplication, slowed iteration, and limited the team to designing primarily for iOS. - Figma’s cloud-based collaboration gives designers and other departments shared visibility, supporting remote work and cross-functional discussion. - Design tokens and variables allow Polaroid to: - Support light and dark modes. - Adapt designs across iOS and Android. - Change default fonts by platform. - Match an app’s theme to a camera’s colorway. - Show users only the camera model they own during device setup. - Figma UI kits provide starting points, while plugins such as Autoflow help map user journeys. ## Using Prototypes to Validate Ideas Earlier - More powerful Figma prototypes let the team test realistic user flows before development. - Users can navigate freely and change settings, producing more natural feedback than earlier prototype methods. - User testing reveals actual behavior instead of relying on assumptions. - Early validation improves product quality, saves time, and prevents expensive revisions later. Polaroid’s experience suggests that a shared design system combined with realistic prototyping can help legacy brands modernize efficiently while maintaining a recognizable creative identity.

Figma Design Systems User Experience Prototyping+4

figmaApr 30, 20252 min readCurated summary

How Figma Helps You Learn Figma | Figma Blog

Figma’s Product Education team has built a learning ecosystem to help users move from beginner concepts to practical design skills. It combines written guides, videos, interactive files, community support, and a refreshed beginner course based on feedback from millions of learners. The central message is that consistent, hands-on practice—and not fear of mistakes—is the best way to become comfortable with Figma. ## An Evolving Educational Ecosystem - The Help Center provides feature documentation, tutorials, and troubleshooting guidance. - YouTube tutorials demonstrate concepts through practical examples. - Interactive playground files let learners experiment safely. - The new **Figma Design for beginners** course teaches users by helping them create a portfolio website. - Students and teachers may qualify for Figma’s Education plan, which provides Professional plan features for free. ## Improving the Beginner Course Through Feedback - Nearly three million people have watched Figma’s original beginner course since its launch in 2020. - Learner feedback highlighted the need for: - More hands-on practice - Clearer explanations of complex features - Real-world examples - Greater emphasis on free features - The updated course includes feature deep dives, guided creative exercises, professional tips, and a usable portfolio website template. ## Turning Knowledge into Skill Figma recommends continuing to learn through practical projects and community interaction after completing the course. - **Start small:** Recreate manageable elements such as interactive buttons or loading animations before attempting a full website. - **Practice often:** Set weekly learning goals and use tutorials to build consistency, confidence, and familiarity with shortcuts. - **Get inspired:** Browse and duplicate projects in the Figma Community to study how other designers work. - **Make mistakes:** Experiment freely, iterate, and use undo shortcuts such as `Cmd/Ctrl + Z`. - **Be kind to yourself:** Skill development takes time, so learners should celebrate incremental progress and accept trial and error. Figma’s recommendation is to begin with the updated **Figma Design for beginners** course, then reinforce the lessons through small, regular projects and community exploration.

Figma Prototyping User Interface Interaction Design+1

figmaApr 23, 20253 min readCurated summary

Figma's 2025 AI report: Perspectives From Designers and Developers | Figma Blog

Figma’s 2025 AI report, based on a survey of 2,500 users, shows that AI adoption is accelerating across product development. Agentic AI is growing especially quickly, while established practices such as prototyping, iteration, and collaboration remain essential. However, developers generally see greater quality benefits from AI than designers, and widespread adoption is still limited by concerns about reliability. ## Agentic AI Is Growing Fast - Text generation remains the most common AI product category. - Agentic AI is the fastest-growing category, with 51% of AI builders developing agents, up from 21% the previous year. - Agents perform multi-step tasks by interpreting inputs, reasoning, and taking action. - Building them requires decisions about: - When users should be asked for confirmation - How much information the system should reveal - Whether conversational interfaces or direct controls are more effective - Designers and developers need extensive testing and prototyping to make agent behavior intuitive and trustworthy. ## Human-Centered Best Practices Still Matter - 52% of AI builders say design is more important for AI products than for traditional products, while 95% consider it at least equally important. - Successful teams continue to rely on: - Rapid iteration - Prototyping - Exploring multiple technical and design approaches - Close collaboration between disciplines - 60% of successful AI teams explored multiple approaches, compared with 39% of unsuccessful teams. - AI product development differs from conventional software work because outputs and interactions can change unpredictably. - Human judgment remains critical for explaining AI behavior and keeping people involved in AI-assisted actions. ## Smaller Companies Are Investing More Aggressively - 61% of users at companies with 1–10 employees say AI is very or critically important to their market-share goals. - The number of small-company respondents calling AI essential to their products doubled from the previous year. - Smaller businesses may be moving faster because they have fewer organizational constraints and can experiment more easily. - They may also view AI as a way to accelerate growth and compete with larger companies. ## Developers and Designers Perceive AI Differently - Developers report higher satisfaction with AI tools: - 82% are satisfied with AI tools. - 68% say AI improves their work quality. - Designers report lower—but still substantial—levels: - 69% satisfaction. - 54% saying AI improves quality. - Developers use AI more directly in core responsibilities such as code generation; 59% do so, compared with 31% of designers using AI for core design work such as asset generation. - 68% of developers use prompts to generate code, and 82% are satisfied with the results. - The gap suggests that AI currently fits more naturally into developers’ daily workflows, while designers are still evaluating where it provides meaningful value. ## Efficiency Has Outpaced Trust - 78% of respondents agree that AI significantly improves work efficiency. - Only 32% say they can rely on AI output in their work. - This contrast highlights the difference between AI’s potential to speed up tasks and its ability to produce consistently dependable results. - Teams must therefore focus not only on adoption, but also on quality control, human oversight, and designing workflows that account for AI’s limitations. Figma’s findings point toward an AI-driven future, but successful adoption will depend on disciplined experimentation, thoughtful product design, and systems that keep humans informed and involved.

Figma AI Agents Prototyping Generative AI+3

figmaApr 22, 20253 min readCurated summary

The Art Of Art Direction | Figma Blog

Art direction is a collaborative practice built on balance: aligning a brand’s identity, an illustrator’s style, and a project’s constraints without suppressing creative individuality. Figma’s Maria Chimishkyan and Jefferson Cheng argue that strong art direction depends on trained visual judgment, clear communication, and trust in collaborators. The best results often emerge when the initial concept is clear but the final execution remains open to surprise. ## Craft in Illustration and Art Direction - Illustration craft develops through repetition and practice until technical skills become intuitive. - For art directors, craft also means “training the eye”—filtering the vast number of visual artifacts in the world and recognizing what resonates. - Good art direction requires: - Strong editing and decision-making. - A compelling starting concept. - The ability to communicate ideas clearly. - Collaboration throughout the process. - The art director’s role is not only to direct, but also to create the conditions for collaborators to become personally invested in the work. ## Choosing the Right Illustrator - Finding an illustrator is compared to casting an actor: the artist must suit the project while bringing a distinctive perspective. - Important qualities include: - A clear understanding of their own style. - The ability to communicate ideas in unexpected ways. - Confidence working through ambiguity. - Once the core idea is established, art directors give illustrators room to execute rather than over-managing every decision. - Artists may be selected specifically because they have not tackled the requested subject before, allowing them to stretch into unfamiliar constraints. ## Turning Complex Ideas into Visual Narratives - Technical or dense subjects are often reduced to a concise metaphor before visual development begins. - Art directors then decide whether the metaphor should be represented literally or abstractly. - Abstract interpretations can leave more room for viewers—and illustrators—to find meaning. - Examples include: - Hoi Chan’s dreamy botanical illustration for an article using gardening as a metaphor for engineering feedback. - Haik Avanian’s clay-like illustrations for Config talks, including an exaggerated heirloom tomato that became especially memorable. - The strongest work can move beyond its original metaphor and create an independent emotional or visual experience. ## The Advantage of Being an Illustrator - Art directors with firsthand illustration experience better understand: - How mysterious and time-consuming creative work can be. - The expectations and pressures illustrators face. - How to give realistic, constructive feedback. - Experience encourages greater empathy and trust in collaborators. - Over time, the art directors learned to stop pre-visualizing the final result and instead let the illustrator guide the project toward an unexpected outcome. - Effective feedback should make collaborators excited and invested, sometimes encouraging them to push their work further. Art direction works best when it combines a clear foundation with creative freedom. Define the purpose and constraints, choose collaborators whose perspectives add something distinctive, and trust them enough to let the final work evolve beyond the original plan.

Figma Visual Design Animation Illustration+3

figmaApr 21, 20252 min readCurated summary

The Power of Play | Figma Blog

Laura Fehre’s experiment creating the Figma-based “Mani Mansion” shows how play can unlock creativity when perfectionism and rigid expectations get in the way. Although she initially rejected structure, she discovered that a flexible design system made experimentation easier and more enjoyable. The project ultimately became less about producing a perfect digital salon and more about creating something delightful and inspiring. ## Finding Inspiration in Everyday Experiences - Fehre drew inspiration from the childhood game *Barbie Nail Designer* and her own nail-salon appointments. - She explored real nail salons to capture their sounds, scents, textures, and ’90s aesthetic. - Sketches of plush seating, neon signs, and glossy counters helped translate the physical experience into an interactive Figma playground. - Her goal shifted from designing for efficiency to creating a space where users could lose track of time. ## When Disorder Needs Structure - Fehre initially made every nail shape unique, hoping to create a wild and unconventional experience. - This approach made layering and combining elements difficult, producing endless duplicates and a frustrating file. - She realized that structure and reusable components were necessary to support creative freedom. - The experience also exposed her insecurity about rusty graphic-design skills and unrealistic expectations. ## Reframing Problems as Play - Collaborating with fellow Designer Advocate Miggi Cardona helped Fehre turn creative frustration into experimentation. - They played with nail shapes and patterns without focusing on whether the results were “useful.” - Fehre recognized that trying to impress others had made failure feel threatening. - Letting go of perfection allowed setbacks to become opportunities for learning, humor, and discovery. ## Designing and Sharing the Final Manicure - Fehre created a mood board combining disco glitter, ’80s Versace influences, bold black clothing, “baddie” energy, and Valentine’s Day hearts. - A systematic set of nail shapes and colors gave her enough consistency to explore combinations freely. - She brought the resulting design to her nail technician as creative inspiration rather than an exact template. - The final manicure demonstrated how digital play can inspire real-world collaboration and expression. The practical lesson is that structure and play are not opposites. Designers can use systems as a foundation, then experiment freely within them—especially when the goal is delight rather than perfection.

Figma Design Systems Graphic Design Vector Design+1

figmaApr 16, 20253 min readCurated summary

Version Control: How a UX Writer Weighs One Word Against Another | Figma Blog

A UX writer explains how a seemingly simple menu label for Figma’s offline prototyping feature revealed deeper questions about user expectations and product behavior. The team tested technically accurate, goal-oriented, and action-focused wording, but each option created confusion about what would happen after clicking. The central lesson is that UX copy must connect users’ intentions with the system’s actual behavior. ## The Challenge: Explaining Offline Prototyping - Users wanted a way to present prototypes reliably without an internet connection. - Engineers built an initial version that loaded prototype content in advance. - The remaining challenge was finding a few words that accurately explained the feature without requiring technical knowledge. - The writer argues that language exposes underlying product assumptions: choosing a verb forces the team to clarify what the system is really doing. ## Version One: “Preload Prototype” - “Preload prototype” accurately described the technical behavior: - Prototypes normally load screen by screen. - The feature gathers the necessary content upfront and retains it for later presentation. - However, “preload” implies that loading happens before the prototype appears, like “preheating” an oven. - Users had already loaded the prototype, so the prefix “pre-” did not match their experience. - Alternatives such as: - “Load full prototype” - “Load all screens” - “Load all assets” - These labels created a trust problem: users might reasonably assume that a prototype shown on screen was already fully loaded. - The wording needed to communicate that the initial load was incomplete without making the product seem unreliable. ## Version Two: Focusing on the User’s Goal - The team shifted from describing the technical process to describing the intended outcome: - “Present prototype offline” - “Prepare to present offline” - These phrases connected more directly to the user’s motivation: presenting without an internet connection. - However, “Present prototype offline” suggested that clicking the option would immediately begin presenting, even though it only prepared the prototype. - “Prepare to present offline” was more accurate but ambiguous: - Users would not know what preparation involved. - They would not know how far in advance to select it. - Both options might have worked within a larger workflow with explicit preparation steps, but they felt too imposing and unclear for a simple toggle menu. ## Language as an Interface to Computing - UX writing treats menu labels as actions or intentions: - Imperatives tell the program what to do. - Phrases can also express what the user wants to accomplish. - Terry Winograd’s principle that “people act through language” captures the problem: words connect a user’s mental model to a computer’s behavior. - When the wording, user intention, and system result are out of alignment, the interaction becomes confusing. - The article’s third iteration begins by examining what users can actually control, but the provided text ends before that approach is explained.

Figma User Experience Prototyping Web Performance+2

figmaApr 15, 20253 min readCurated summary

Version Control: Three Ways Figma Explored Horizontal Scrolling | Figma Blog

Figma’s request for horizontal scrolling in the Layers panel exposed significant design and engineering complexity. The panel contains interactive, virtualized layers whose names and nesting change dynamically, so scrolling could easily obscure hierarchy or disrupt users’ mental models. Through three unshipped prototypes, the team learned that preserving context and preventing accidental actions mattered more than applying seemingly simple scrolling behaviors. ## Why Horizontal Scrolling Was Difficult - Nested layers can extend beyond the panel, requiring users to move horizontally to see their full hierarchy. - Layers are interactive: users can hide, lock, collapse, and expand them while scrolling. - Virtualization renders only visible layers for performance, meaning newly visible rows may have different text lengths. - The design needed to communicate that more content existed without making the hierarchy harder to understand. - Code-based prototyping with JavaScript, HTML, CSS, and React helped the team test behavior across thousands of layers and complex interactions. ## Version One: Indicators at the Panel Edges - The team explored showing icons at the top-left and bottom-right edges when layers moved out of view. - This symmetrical treatment was intended to help users understand their position in the hierarchy. - Engineering challenges arose because edge icons needed opaque backgrounds that covered layer text while scrolling. - Layer rows did not have enough positional knowledge to determine which areas should be covered or revealed. - The design also created a ragged edge where partially visible layer names ended, introducing visual clutter. - The experiment demonstrated that a symmetrical solution could create new problems, particularly around unused white space. ## Version Two: Automatically Scrolling to Selected Layers - Another prototype automatically scrolled the Layers panel to center a layer selected on the canvas. - Although this made the selected layer easy to find, it often moved the panel both vertically and horizontally. - Testers found the behavior disorienting because parent layers and surrounding context disappeared. - Figma compared the experience to a map suddenly jumping to another location while driving. - The team concluded that users need to retain their mental model of a layer’s name, location, and relationship to parent components. ## Version Three: Renaming Layers While Scrolling - Horizontal scrolling created ambiguity when a user began editing a layer name and then scrolled to another layer. - One possible behavior was to save the edited text automatically when scrolling away. - The team rejected this because scrolling was not a strong enough signal that the user intended to confirm the rename. - The issue highlighted the need to avoid turning navigation actions into irreversible edits. Figma’s experiments show that horizontal scrolling in a dynamic hierarchy is not merely a visual or mechanical feature. The best solution must preserve orientation, context, and user control while handling virtualization and interactive layer states.

Figma User Interface React JavaScript+4

figmaApr 14, 20252 min readCurated summary

Figma has confidentially submitted a draft S-1 with the SEC | Figma Blog

Figma announced on April 15, 2025, that it had confidentially submitted a draft S-1 registration statement to the U.S. Securities and Exchange Commission. The filing gives the company the option to pursue an initial public offering, but the IPO remains conditional on SEC review and further decisions by Figma. ## Confidential S-1 Submission - Figma submitted a draft Registration Statement on Form S-1 to the SEC. - The filing concerns a potential offering of Figma’s Class A common stock. - Because the submission is confidential, Figma has not yet committed to completing an IPO. - The announcement was made under Rule 135 of the Securities Act of 1933. ## No Offering Details Yet - Figma has not determined: - The number of shares that might be offered - The potential price range - The timing of a public offering - Any future sale or solicitation of securities would occur only after the SEC completes its review and applicable registration requirements are satisfied. - The announcement itself is not an offer to sell securities or a solicitation to buy them. Figma’s announcement signals that it is preparing for a possible transition to public ownership while emphasizing that the process is preliminary. Investors will need to wait for later filings and SEC review before receiving financial details or confirmation of an IPO.

Figma AI User Experience Collaborative Design

figmaApr 14, 20252 min readCurated summary

Figma Localizes Product and Support for Korean Market | Figma Blog

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 User Experience Figjam Design To Code+4

figmaApr 14, 20252 min readCurated summary

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

“Skill share,” Figma’s April 2025 issue, gathers practical lessons for designers, developers, and product builders ahead of Config 2025. Its central argument is that strong products depend not only on speed or technical execution, but also on craft, communication, storytelling, experimentation, and long-term thinking. The issue encourages readers to keep learning across disciplines and apply these skills collaboratively. ## Craft as a Competitive Advantage - Linear CEO Karri Saarinen shares ten principles for creating products that stand out. - The advice reflects a shift away from “move fast and break things” toward deliberate quality and attention to detail. - Craft is presented as an organizational value that should influence every level of product development. ## Better Designer–Developer Handoff - Successful handoff depends on collaboration rather than simply transferring designs to engineering. - Figma’s guide focuses on three principles: - Encourage curiosity between designers and developers. - Keep communication open throughout the build process. - Establish a shared understanding of what “good” means. - The goal is to reduce friction, clarify expectations, and preserve design intent during implementation. ## Writing and Storytelling for Product Builders - Clear writing helps teams explain technical architecture, new features, product roadmaps, and broader visions. - Storytelling is not limited to writers or marketers; people in every product role benefit from articulating ideas effectively. - Strong communication can make complex concepts easier to understand and build support for new directions. ## Building for the Long Term - In a period of rapidly advancing AI tools, product teams must focus on making things work well—not merely making them work. - Dylan Field and Garry Tan discuss experimentation, play, and exploring an “idea maze” as essential parts of product development. - They also address vibe coding, AI-assisted creation, and the importance of preserving human craft even as AI models become more capable. - Founders are encouraged to remain deeply focused on quality and to develop products with lasting value. ## Broader Exploration - The issue also includes a “Rabbit hole” section featuring additional visual and editorial explorations. - Together, the featured topics present skill development as an ongoing process spanning design, engineering, communication, and strategy. The practical takeaway is to treat craft and collaboration as core product skills. Teams can improve their work by communicating clearly, aligning early, experimenting freely, and maintaining high standards even when new tools make development faster.

Figma AI Software Development Developer Handoff+2

figmaApr 9, 20253 min readCurated summary

Finding a Forever Home for FigPals | Figma Blog

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

Figma User Experience Figjam Product Design+3

figmaApr 7, 20253 min readCurated summary

How to Streamline Your Design System Workflow in Figma | Figma Blog

Figma’s latest design-system updates reduce the repetitive work involved in organizing variables, styles, components, and documentation. The post combines nine quality-of-life improvements with a set of plugins covering the workflow from color and typography foundations through documentation, component specs, and code handoff. Together, these tools aim to make design systems faster to build, easier to maintain, and more useful to developers. ## Reordering Modes and Collections - Modes and variable collections can now be rearranged with drag and drop. - Existing modes and IDs remain intact, avoiding resets, broken dependencies, or out-of-sync designs. - Teams can: - Move frequently used collections to the top. - Group related modes. - Reorganize collections during rebrands or product-line updates. - The default mode can also be changed more easily. ## Nine Quality-of-Life Improvements Figma introduced several smaller improvements intended to remove workflow friction: - A shortcut for jumping directly to a component’s main source. - The ability to duplicate and copy styles. - Options to hide and reveal variable paints. - A clearer component-description interface. - A variable modal that can be dragged from anywhere in its header. - Automatic saving for variable changes. - Tooltips that provide context for component names. - Better alignment for the Edit button. - Improved text overflow handling for long style names. ## Building the Foundations The post recommends using community plugins to accelerate the foundational work of creating colors, typography, spacing, and other core design-system decisions. ### Creating Color Palettes The highlighted tools support different aspects of color-system creation: - **CSS color-mix()** helps create color palettes and gradients. - **Colorbox** generates complete color ramps. - **The Genome Color Tool** helps build color scales that meet WCAG accessibility requirements. ### Establishing Typography and Variables - **Peppercorn** assists with setting up an entire type system. - **Print Variables** creates sticker sheets for variable collections. - **Auto Documentation** generates visual documentation for variables. - **Variables and Styles List** presents variable sheets inside a Figma canvas widget. ## Documenting Components and Styles Documentation tools help teams make systems easier to understand and adopt: - **Propstar** maps component property and prop variations. - **Specs** generates component specifications. - **Similayer** filters for particular layers and properties. - **Style Finder** locates styles across pages. These tools can reduce the manual effort required to explain component behavior and find existing design decisions. ## Bridging Design and Development The recommended implementation tools connect Figma variables and styles with code: - **CTRL Var** supports variable renaming. - **Export Import Variables** moves variables into or out of Figma. - **Handoff** copies CSS variables quickly. - **Variables Converter** translates variables into code. - **Shaper** helps manage token architecture and generate CSS. ## Practical Recommendation Start with Figma’s built-in improvements for organizing collections, modes, styles, and variables, then add plugins selectively for color generation, documentation, component specification, and code handoff. The goal is not to use every tool, but to create a repeatable workflow that keeps design-system foundations consistent and makes implementation easier for developers.

Figma Design Systems Design Tokens CSS+4

figmaApr 7, 20252 min readCurated summary

Double Click: You Can Just Do Things—But Should You Always? | Figma Blog

AI tools are creating a renewed sense of possibility, making it easier for people—even nontechnical users—to build, write, design, and research. Figma’s article celebrates the excitement behind the “you can just do things” mantra while questioning whether constant creation may also become exhausting. Its central tension is whether AI is ushering in a creative golden age or overwhelming people with too many possibilities. ## The “You Can Just Do Things” Mantra - The phrase has become a tech-world rallying cry alongside: - “Move fast and break things” - “Don’t ask for permission” - “It’s time to build” - “Founder mode” - “Fuck around and find out” - AI-powered tools make the idea feel more attainable than ever by lowering the barriers to execution. - Writing assistants, design generators, and research platforms allow more people to create without specialized technical skills. - The article connects this mindset to earlier advocates such as Steve Jobs and contemporary online creators. ## The Thrill of Discovery - The current AI boom is compared to the early 2010s, when discovering apps such as Instagram and Uber felt especially exciting after the App Store’s emergence. - Michael Mignano of Lightspeed Venture Partners observes that people are once again hearing about impressive new products every day. - Crucially, these recommendations increasingly come from ordinary friends—not only people working in technology. - This suggests AI products are becoming broadly accessible and relevant beyond the traditional tech community. ## Possibility Versus Overload - The proliferation of AI tools creates a powerful sense that almost anything can be attempted. - At the same time, the sheer number of available tools and projects may become mentally exhausting. - The article asks whether high agency and constant experimentation empower people or pressure them to stay perpetually productive. - It frames the issue as a balance: embracing AI’s creative potential without feeling obligated to act on every possible idea. People should take advantage of AI’s expanded creative possibilities while resisting the expectation to “do everything.” The most sustainable approach is selective experimentation—use tools that meaningfully support a goal rather than treating constant activity as the goal itself.

Figma AI Generative AI Product Design+2

figmaMar 31, 20252 min readCurated summary

The Designer's Handbook for Developer Handoff | Figma Blog

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

Figma Design Systems Figjam Wireframing+2

figmaMar 26, 20252 min readCurated summary

What Makes Designers and Developers Happy at Work? | Figma Blog

Designers and developers are generally becoming happier at work: 41% report higher satisfaction than the previous year. Based on a survey of 943 product builders, Figma identifies organizational design strategy, hybrid-work policies, leadership, and cross-functional collaboration as major influences. The article argues that clear expectations, empowered teams, and stronger designer-developer partnerships can improve workplace satisfaction. ## Design’s Place in the Organization - Designers are more satisfied when design is treated as a strategic partner rather than a service function. - Strategic design encourages greater customer focus and gives designers more influence on product direction. - Designers can strengthen this position by balancing exploration with execution. - Wise recommends a “now, next, future” model: - 70% of effort on current deliverables - 20% on upcoming work - 10% on longer-term possibilities ## Company Policies on Hybrid Work - 97% of respondents work remotely at least part of the time; more than half are fully or mostly remote. - One-size-fits-all hybrid policies can create logistical problems, such as overcrowded offices on certain days and empty workspaces on others. - Organizations should establish clear, predictable expectations around where and when employees work. - Companies may need to choose a coherent model—fully remote, mostly in-office, or a deliberately structured hybrid approach. ## How Leaders Empower Their Teams - Managers influence happiness by understanding what support employees need and ensuring good work is recognized. - Effective leadership focuses on results rather than monitoring hours or physical location. - A flexible management philosophy can give employees autonomy while maintaining accountability for the quality of their work. ## Effective Collaboration and Communication - Among highly satisfied designers, 69% rate collaboration with developers as effective or very effective. - Developers with higher job satisfaction also collaborate with designers more frequently. - 84% of designers work with developers at least weekly. - Whiteboarding and collaborative design tools support the real-time, iterative nature of modern product development. - Despite frequent collaboration, 91% of developers and 92% of designers believe their processes could improve. - Misalignment remains a significant issue, including gaps in designers’ understanding of engineering constraints. Organizations can improve satisfaction by positioning design strategically, creating practical work policies, empowering managers and employees, and investing in better designer-developer collaboration.

Figma Collaborative Design Multiplayer Collaboration Whiteboarding+1