Figma

736 posts

www.figma.com/blog/engineering

Filter by tag

figma2 min readCurated summary

Version Control: How Figma Make Helped Us Figure Out Video Playback | Figma Blog

Figma’s team used Figma Make to rapidly prototype video playback for Figma Buzz under a two-month deadline. The tool helped translate complex interaction ideas into working code, clarify feasibility with engineers, and expose edge cases before implementation. Although the project began with support for one video, technical progress expanded the scope to multiple videos and required revisiting the original playback design. ## The Challenge of Video Playback - Figma Buzz lets teams create branded assets containing video, text, images, and other layered elements. - Playback controls could not simply be placed in the center of the canvas because they might obscure important design content. - The team needed to account for videos being: - Moved within or outside their parent frame - Partially visible or completely off-canvas - Enlarged and cropped - Used alongside other assets in grid view - Designer Natasha Tenggoro used Figma Make because the interaction logic was difficult to communicate with static Figma designs and would have taken too long to build in another tool. ## Version One: Single-Video Playback - The initial release focused on the common case: assets containing one video. - Natasha imported an existing Figma Design frame and prompted Figma Make to create: - A draggable media frame - Media that could extend beyond a fixed parent without clipping - Reduced opacity for media outside the parent - Playback controls pinned to the media’s top-right corner - Automatic repositioning of controls when they would leave the parent frame - Control fading when less than 20% of the video was visible - The working prototype gave engineers a concrete demonstration of the intended behavior. - This helped establish technical feasibility, clarify scope, and turn an uncertain idea into a prioritized feature. ## Expanding to Multiple Videos - Further engineering investigation showed that multiple videos could potentially be supported within the original release timeline. - The expanded capability forced the team to reconsider earlier decisions about playback controls. - For a collage containing several videos, the team chose a single overall playback control rather than separate controls for each video. - This approach reduced interface clutter, avoided covering design elements, and provided a more unified preview experience. ## Practical Conclusion Figma Make served as a bridge between design intent and engineering implementation, enabling fast exploration of complex motion and interaction behavior. The experience suggests that functional prototypes are especially valuable when requirements involve dynamic positioning, visibility rules, and changing technical scope.

Read original(opens in new tab)
figma2 min readCurated summary

Forrester Analyzes The ROI Of Dev Mode | Figma Blog

Dev Mode is presented as a way to reduce friction between designers and developers, especially during handoff and implementation. A Forrester Total Economic Impact study found that it can increase developer output by 20–30%, save more than 90 minutes per developer each week, and generate significant financial benefits over three years. The central conclusion is that a shared, inspectable source of truth helps teams ship faster without sacrificing product quality. ## The Business Case for Dev Mode - Figma commissioned Forrester two years after Dev Mode launched. - Forrester interviewed four decision-makers and modeled a composite organization with 100–1,000 designers and developers. - The study identified inefficient handoffs and redundant work as major sources of lost time. - Its modeled benefits include: - 20–30% higher developer output - More than 90 minutes saved per developer each week - Approximately $10 million in developer-efficiency time savings over three years - Approximately $2 million in increased profit from faster time to market ## One Shared Source of Truth - Teams working in a shared space can collaborate continuously instead of waiting for a formal design handoff. - One organization reportedly moved from design completion to release in six to eight months, compared with an earlier process that could take two or three years. - A survey of 200 developers at another company found average savings of 98 minutes per week. - Developers can inspect design files directly to find: - Variables and specifications - Exact assets - Documentation - Code snippets - This reduces dependence on Slack messages, meetings, time-zone coordination, and manually maintained annotations. ## More Autonomous Developers - Dev Mode allows developers to resolve many implementation questions independently. - By seeing design intent and technical details directly in Figma, developers spend less time clarifying requirements with designers. - Reduced context switching and fewer back-and-forth conversations let developers focus more of their time on building products. - The broader benefit is not simply faster execution, but lower mental overhead and smoother collaboration between disciplines. The study supports adopting Dev Mode—or similar workflow improvements—when teams need to accelerate delivery while preserving design quality. Its strongest value comes from making design information immediately accessible and enabling designers and developers to collaborate before either side has finished their work.

Read original(opens in new tab)
figma3 min readCurated summary

The Anatomy of an Activation | Figma Blog

Figma marked its 2025 public-market debut by turning the New York Stock Exchange into a public celebration of design and community. Rather than follow a conventional IPO event, the company created “Figma Commons,” supported by citywide murals, posters, billboards, and street experiences. The activation aimed to make the milestone accessible and enjoyable for both longtime users and people encountering Figma for the first time. ## A Citywide Celebration of Design - The July 31 NYSE event centered on the message “Design is everyone’s business.” - Figma’s events and community teams expanded the celebration beyond the exchange with: - A large Brooklyn mural - Posters across New York City - A Times Square digital billboard - The Figma Commons outdoor event - The initiative reflected Figma’s belief that its community is central to the brand and should share in major milestones. ## Building Figma Commons - Community and events leads Jordan Scott and Kelley Sauer shaped the experience over weeks of planning. - The project required approvals from the NYC Department of Buildings, NYPD, and the mayor’s office. - Temporary structures had to be mounted on wheels to comply with emergency-access regulations. - Storms complicated installation, with work stopping for 30 minutes after each lightning strike. - The team deliberately chose a larger, more ambitious event than a standard NYSE listing ceremony. ## Extending the Invitation - Because communications were embargoed until a press release was issued, Figma had fewer than 15 hours to promote the event. - The team relied on grassroots and physical marketing: - Flyers at subway stations and ferry terminals - Wildpostings around Manhattan and Brooklyn - Direct outreach to longtime local customers - Posters included QR codes linking to free invitations, reinforcing the idea that the event was open to everyone. ## Designing the Experience - Figma paid close attention to visual and physical details because its community values design craft. - The event included: - Bespoke signage from Figma’s brand team - Limited-edition merchandise designed to feel fresh rather than excessively branded - Food and drinks from popular New York eateries - A live mural by graffiti artist Greg Lamarche featuring the word “make” - Additional citywide creative work promoted Figma Make, including Times Square billboards and a Brooklyn mural built from more than 200 hand-drawn glyphs. Figma Commons demonstrates how a corporate milestone can become a participatory public experience. By combining strong visual design, local culture, grassroots outreach, and careful logistical planning, Figma made its IPO celebration feel like an invitation to join the company’s broader design community.

Read original(opens in new tab)
figma2 min readCurated summary

8 Tips for Designers Building Branded Templates in Figma Buzz | Figma Blog

Figma Buzz templates should be designed as flexible systems, not just finished compositions. The post argues that brand designers need to anticipate marketers’ editing needs by building in guardrails for content, spacing, scaling, and branding. Thoughtful template structure helps teams create accurate, on-brand assets at scale without requiring constant designer review. ## Design in Figma Design First - Begin by creating the asset in a Figma Design frame, where designers can use components and Figma Draw’s vector tools. - Once the design is ready, copy it into Figma Buzz for final adjustments and publication as a template. - This workflow combines expressive design capabilities with Buzz’s collaborative marketing features. ## Use Auto Layout for Flexible Templates - Auto layout keeps elements aligned and maintains consistent spacing as content changes. - It is especially useful for buttons, text boxes, and image containers. - Longer headlines or other variable content can expand without pushing surrounding elements out of alignment. - Auto layout provides the responsive foundation needed for templates used across different assets and formats. ## Separate Text Layers by Input - Create a separate text layer for every unique piece of content, particularly when inputs use different fonts, sizes, or styles. - Modular text layers are essential for Bulk create, which maps CSV or XLSX fields to individual design layers. - Combining multiple inputs or styles in one layer can cause formatting problems and make bulk updates difficult. - Separating layers keeps formatting consistent across campaigns and generated assets. ## Lock Image and Vector Aspect Ratios - Lock the aspect ratio of images and vector graphics using the square icon beside the width and height controls. - Templates often need to be adapted from one format—such as a 1080 × 1080 social post—to others, including Instagram Stories or web banners. - Aspect-ratio locking prevents logos, portraits, illustrations, and other graphics from becoming stretched or compressed. - This setting acts as a simple safeguard against accidental distortion during editing. ## Name Layers Clearly - Rename layers so teammates can understand what each editable field controls in Buzz’s Edit Content panel. - Text layers are initially named after their visible canvas text; use Command + R or edit the layer name directly to replace it. - Figma AI can help rename large numbers of layers. - Clear labels make template editing more intuitive, much like completing a form, especially when many layers are available for customization.

Read original(opens in new tab)
figma2 min readCurated summary

Getting into the groove: How music shaped the scatter brushes in Figma Draw | Figma Blog

Figma Draw’s 10 new scatter brushes were inspired by music genres, using rhythm, repetition, and texture as guides for visual experimentation. Product designer Rogie King created 99 designs, which the team narrowed down to brushes named Bubblegum, Witch house, Shoegaze, Honky-tonk, Screamo, Drone, Doo-wop, Spoken word, Vaporwave, and Oi!. The project also emphasizes making digital art feel approachable and expressive for users without formal artistic training. ## Music as a Design Framework - Scatter-brush patterns resemble musical beats because their elements repeat along a stroke. - Brush settings such as gap, wiggle, and jitter parallel musical controls like tempo, texture, and volume. - UX writer Molly Rosen Marriner gathered genre ideas from the Every Noise At Once genre map and Figma employees. - Visually suggestive genres—including Electroclash, Drone, and Witch house—helped guide the brush concepts. ## From Genres to Brush Strokes - Rogie began with familiar uses such as stippling and shading, then explored more expressive interpretations. - He listened to representative songs and researched each genre’s visual culture. - The Screamo brush, for example, drew on early-2000s imagery associated with mosh pits, dark clothing, and heavy eyeliner. - He also consulted others, including his son, to better understand genres such as Shoegaze. ## Selecting the Final Collection - Rogie produced 99 scatter-brush designs through an intentionally exploratory process. - The Figma team voted on designs that offered the most flexibility and expressive potential. - Molly later matched the selected brushes to music genres, sometimes inventing or adjusting associations to fit the visuals. - The final set includes 10 brushes designed for stippling, shading, texture, and playful decoration. ## Making Digital Art More Accessible - The brushes expand the emotional and stylistic range available in Figma Draw, from mysterious wisps to repeated smiley-face splatters. - The genre-based names avoid overly technical art-school terminology. - Rogie wanted users to feel free to experiment without needing formal artistic education or experience with physical media. - The collection presents artistic expression as accessible, playful, and open to everyone.

Read original(opens in new tab)
figma3 min readCurated summary

Design Systems And AI: Why MCP Servers Are The Unlock | Figma Blog

Design systems provide the shared language AI agents need to generate code that is not merely functional, but consistent with a company’s brand, accessibility standards, and engineering practices. Figma argues that its MCP server unlocks this value by transferring design context—such as components, variables, styles, and code mappings—directly into developer workflows. The result is a feedback loop in which stronger design systems produce better AI output, while AI makes those systems more useful and scalable. ## Design Systems as Context for AI - Design systems already connect design and engineering through: - Shared patterns and terminology - Documentation and best practices - Brand guidelines and reusable code - These same elements give AI agents the context required to produce the “right” output rather than generic interfaces. - A mature design system can therefore become a productivity multiplier for AI-powered product development. - Organizations without a robust system can also use Figma’s MCP server to help implement tokens and components. ## Design Systems as the Shared Language - As AI lowers the barrier between ideas and implementation, product differentiation increasingly depends on craft, visual identity, and user experience. - Design systems help scale that craft while preserving speed, quality, and consistency. - Effective systems provide: - **Scalable foundations:** Tokens for color, spacing, typography, and other design decisions - **Reusable components:** Flexible elements built around a shared source of truth - **Built-in accessibility:** Inclusive experiences by default - They also prevent teams from shipping interchangeable, generic interfaces assembled from common AI-generated parts. ## Why Context Improves AI Code Generation - Figma reports that 68% of developers use AI to write code, but only 32% trust its output. - Without design-system context, AI behaves like a new engineer who has not been onboarded: its code may work, but it may not follow team conventions. - With that context, AI can: - Reuse existing components and patterns - Apply design tokens consistently - Generate higher-quality starting code - Reduce misunderstandings and shorten design-engineering feedback loops ## How Figma’s MCP Server Works - When developers inspect a Figma frame, the MCP server sends relevant context to an AI agent, including: - Components - Styles - Variables - Variable code syntax - **Code Connect** can map design elements to real code resources, allowing agents to use existing implementation libraries. - Even without these mappings, the server supplies styling information that helps agents create more design-informed code. - Automated design-system rule generation can scan a codebase and produce a structured rules file covering: - Token definitions - Component libraries - Style hierarchies - Naming conventions - This file gives AI agents system-level defaults, reducing the need for developers to repeat detailed instructions in every prompt. - Figma MCP also provides annotations that can communicate extra context, including accessibility and interaction behavior. ## The Design-System and AI Flywheel - Better design systems provide richer context to AI agents. - Better context leads to more accurate, on-brand code. - Improved AI output can make design-system adoption and maintenance more valuable. - This creates a reinforcing cycle: robust systems improve AI results, and AI helps teams apply and extend those systems more effectively. Teams seeking reliable AI-generated product code should treat their design system as essential infrastructure and connect it to development tools through mechanisms such as MCP, Code Connect, tokens, rules, and annotations.

Read original(opens in new tab)
figma2 min readCurated summary

Who Says Design Needs a Mouse? | Figma Blog

Figma is introducing keyboard accessibility features to make end-to-end design possible without a mouse. Developed with feedback from keyboard- and screen-reader users, the updates improve canvas navigation, object insertion, and selection while providing better spoken feedback. The goal is to remove barriers so more designers can participate fully in design work. ## Keyboard-Only Canvas Navigation - Users can pan across the canvas with the arrow keys. - Holding `Shift` enables faster movement or scrolling. - New shortcuts provide finer zoom control and access to the move and hand tools. - These changes address problems such as getting stuck at the top of the canvas or zooming into the wrong area. ## Inserting Objects Without a Mouse - Most object types, including shapes and text, can now be added using the keyboard. - Frames can be inserted with keyboard shortcuts through a crosshair-guided view. - Pressing `Enter` places text in the center of the current screen. ## Selecting and Positioning Objects - A keyboard box-selection tool allows users to select objects on the canvas. - Arrow keys move a pink cursor between objects. - Pressing `Enter` selects the object under the cursor. - Multiple objects can be selected using a selection box. ## Broader Accessibility Improvements - Enhanced screen-reader support announces actions as users work, helping them stay oriented. - Figma’s accessibility efforts also include a color-picker contrast checker for evaluating WCAG compliance. - Semantic HTML tags can be assigned in designs to support products that work better with screen readers. - Figma emphasizes accessibility as an ongoing commitment rather than a one-time checklist. Users can consult Figma’s help center for instructions on using the new keyboard controls and enabling screen-reader support.

Read original(opens in new tab)
figma2 min readCurated summary

The Duolingo Method: Collaboration As A Core Practice | Figma Blog

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

Read original(opens in new tab)
figma3 min readCurated summary

Figma’s IPO: Design Is Everyone’s Business | Figma Blog

Figma’s IPO marks a new phase for the company, but not a change in its founding mission: narrowing the gap between imagination and reality. CEO Dylan Field argues that AI will make design more accessible and important, while emphasizing that Figma will prioritize decades-long growth over short-term efficiency or share-price performance. He sees Figma as a collaborative platform where more people can shape products and ideas. ## Figma’s IPO and Long-Term Mission - Figma went public to improve corporate governance, increase brand awareness, provide liquidity, strengthen its acquisition currency, and access capital markets. - Field especially values public ownership because it allows the broader Figma community to share in the company’s success. - He cautions investors that public-market performance is unpredictable and does not promise share-price growth. - Figma will prioritize supporting designers’ evolving needs and pursuing long-term growth over maximizing quarterly efficiency. - The company expects to take significant risks, including large platform investments and mergers and acquisitions. ## AI as a Strategic Investment - Figma is investing heavily in AI and plans to increase that investment further. - This spending may reduce efficiency for several years, but Field considers AI central to the future of design workflows. - Existing capabilities, including Figma Make and other AI features, are presented as only the beginning. - AI could help designers work more effectively and bring more people into the design process. ## Design as a Competitive Advantage - Creating a minimum viable product is easier than ever, making design, craft, and distinctive perspective more important differentiators. - Design is no longer an afterthought focused only on form and function; it can determine whether a product succeeds or fails. - As design becomes more central, companies will involve more types of contributors and encourage greater experimentation and creativity. - Figma must balance accessibility with professional power while supporting collaboration and decision-making across large organizations. ## The Evolution of AI Interfaces - Field compares current AI interfaces, which rely heavily on prompts, to the MS-DOS era of computing. - He expects new, domain-specific design patterns to make AI capabilities easier and more intuitive to use. - Just as graphical user interfaces expanded access to computers, well-designed AI interfaces could make advanced capabilities available to everyday users. ## Figma’s Role in the Future - Field describes Figma as a “peaceful garden” where individuals and teams can develop ideas together. - He believes tools alone do not change the world; people use them to create meaningful change. - Figma’s long-term ambition is to help more people participate in design and turn ideas into reality. Figma’s direction is therefore one of patient, ambitious investment: accept near-term inefficiency, expand access to design, and build AI-powered tools for a much broader creative community.

Read original(opens in new tab)
figma2 min readCurated summary

Figma Announces Pricing of Initial Public Offering | Figma Blog

Figma announced pricing for its initial public offering at **$33 per share**, valuing an offering of 36,937,080 Class A shares. Trading is expected to begin on the New York Stock Exchange under **“FIG”** on July 31, 2025, with closing scheduled for August 1. The IPO marks Figma’s transition from a design tool into a broader, AI-powered product development platform. ## IPO Details - Figma is offering **12,472,657 shares** of Class A common stock. - Existing stockholders are selling **24,464,423 shares**. - The offering’s public price is **$33.00 per share**. - Certain selling stockholders granted underwriters a 30-day option to purchase up to **5,540,561 additional shares** for over-allotments. - Figma will not receive proceeds from shares sold by existing stockholders. ## Trading and Underwriting - Shares are expected to trade on the **New York Stock Exchange** under ticker symbol **FIG**. - The offering is expected to close on **August 1, 2025**, subject to customary conditions. - Morgan Stanley, Goldman Sachs, Allen & Company, and J.P. Morgan are joint lead book-running managers. - BofA Securities, Wells Fargo Securities, and RBC Capital Markets are additional book-running managers. - William Blair and Wolfe | Nomura Alliance are serving as co-managers. - The SEC declared the related registration statement effective on July 30, 2025. ## Figma’s Platform and Evolution - Founded in 2012, Figma describes itself as a collaborative platform for digital product development. - The company has expanded beyond interface design into an AI-powered system supporting: - Ideation - Design - Building - Product shipping - Its central value proposition is helping teams collaborate more efficiently while maintaining alignment throughout the product lifecycle. Figma’s IPO makes its public-market debut with a $33-per-share offering and positions the company as a broader collaborative platform for designing and delivering digital products.

Read original(opens in new tab)
figma3 min readCurated summary

A Tale of Two Parameter Architectures—and How We Unified Them | Figma Blog

Figma’s component properties and variables both let users define a value once and apply it across a design, but they were originally built on separate architectures. This led to conflicting bindings, inconsistent rendering, and duplicated engineering effort. Figma unified the systems into one parameter architecture, improving consistency and creating a scalable foundation for future products. ## Two Different Parameter Systems - **Component properties**, introduced in 2022, addressed the gap between design and code. - They enabled **scoped parametrization**: parameters could be defined by a component and applied only to its internal layers. - This gave design-system authors a clear customization contract and mirrored how component properties work in code. - The model supported features such as: - Boolean properties - Text and instance customization - Component variants and states - Component properties helped power products including Figma Sites, Figma Make, and Code Connect. ## Variables and Global Parametrization - Variables provided a broader, more globally reusable parameter system. - They supported values such as colors and could define different values for contextual modes, such as light and dark themes. - Unlike component properties, variables were designed to be reused across many unrelated layers and components. - This made variables well suited to design tokens and system-wide configuration. ## Problems Caused by Separate Architectures - The two systems evolved independently despite having similar goals. - A variable and a component property could bind to the same layer property, producing inconsistent results in the editor. - Users had to learn different behaviors and rules for concepts that appeared similar. - Maintaining two implementations increased engineering complexity and slowed feature development. - Extending parametrization to other Figma products risked reproducing the same technical limitations. ## Unifying the Architecture - Figma built a single underlying parameter architecture to support both component properties and variables. - The unified system preserves the distinction between: - Parameters scoped to a component - Parameters reused globally across a project - It eliminates competing bindings and makes parameter behavior more predictable. - The change also improves developer velocity by allowing new capabilities to build on shared infrastructure. ## Broader Impact - Designers receive a more consistent mental model for configuring components and design systems. - Rendering behavior is more reliable when multiple parameter types interact. - Figma can extend parametrization across existing and future products without maintaining separate technical foundations. - The unified architecture supports Figma’s broader goal of connecting design-system behavior with code and interactive products. Figma’s recommendation in practice is to treat component properties and variables as complementary uses of one parameter model: use scoped properties for component contracts and variables for reusable, contextual design tokens.

Read original(opens in new tab)
figma2 min readCurated summary

Figma Announces Increase in IPO Price Range | Figma Blog

Figma announced an increased expected price range of **$30–$32 per share** for its proposed initial public offering. The company has amended its Form S-1 registration statement and plans to list Class A common stock on the New York Stock Exchange under **“FIG.”** The announcement follows the launch of Figma’s IPO roadshow. ## Updated IPO Terms - Figma plans to offer **12,472,657 shares** of Class A common stock. - Existing stockholders plan to sell an additional **24,464,423 shares**. - Selling stockholders may grant underwriters a 30-day option to purchase up to **5,540,561 additional shares** to cover over-allotments. - Figma will not receive proceeds from shares sold by existing stockholders. ## Underwriters - Joint lead book-running managers: - Morgan Stanley - Goldman Sachs - Allen & Company - J.P. Morgan - Additional book-running managers include BofA Securities, Wells Fargo Securities, and RBC Capital Markets. - William Blair and Wolfe | Nomura Alliance will serve as co-managers. ## Regulatory Status - The offering is being made through a preliminary prospectus. - Figma’s registration statement has been filed with the SEC but is not yet effective. - Shares cannot be sold, and purchase offers cannot be accepted, until the registration statement becomes effective and applicable securities-law requirements are satisfied. ## About Figma - Founded in 2012, Figma describes itself as an AI-powered platform for collaborative product development. - Its product supports the full workflow from ideation and design through development and shipping. - The company emphasizes collaboration, efficiency, and keeping product teams aligned. Figma’s revised price range signals increased expectations for its upcoming IPO, though the final offering price and completion of the listing remain subject to market conditions and regulatory approval.

Read original(opens in new tab)
figma2 min readCurated summary

The making of a product icon | Figma Blog

Figma product icons are the result of extensive exploration rather than a single inspired sketch. Designer Tim Van Damme combines consistent visual rules with product-specific research, then develops dozens or hundreds of variations before refining the final symbol. The process balances recognizability, scalability, and a distinct identity across Figma’s expanding product suite. ## Building a Consistent Icon System - Figma previously had no formal icon-design system, so Tim created unofficial guidelines to ensure the icons worked as a cohesive family. - Core principles include: - One-pixel-wide strokes - One-pixel-thick cutouts - Rounded caps - Balanced compositions that use the available space - Three standard sizes for different surfaces - Icons must work everywhere from toolbars to large marketing displays and billboards. - Designs are rejected when lines blur or visual elements become indistinguishable at smaller sizes. ## Finding the Product’s Core Idea - Each icon must follow Figma’s broader visual language while representing the identity of its specific product. - Tim collaborates with design and product teams to list concepts, themes, and associations connected to the product. - For Figma Community, ideas such as shared learning, connection, and knowledge exchange inspired experiments with people, trees, and books. - For Figma Buzz, themes including magic, creation, and AI image generation led to explorations involving glass orbs, stars, and bees. ## Exploring Through Extensive Iteration - Tim uses Figma’s variable-width strokes and simultaneous vector-layer editing to speed up experimentation. - He develops large families of related symbols, gradually adjusting shapes, proportions, movement, and composition. - Creative exploration can transform one idea into another—for example, trees into faces, faces into mandalas, or abstract shapes into interlocking forms. - For Figma Make, he explored motion and transformation through wheels, butterflies, compasses, and fidget spinners. - For Figma Buzz, he created hundreds of bee variations, changing wings, antennas, and line treatments before narrowing the options. The practical lesson is that effective product icons emerge from a structured but highly exploratory process: establish shared rules, identify the product’s essential meaning, and iterate freely until the symbol is both distinctive and immediately legible.

Read original(opens in new tab)
figma3 min readCurated summary

Figma Make Is Now Available to All Users | Figma Blog

Figma has moved Figma Make and other AI features out of beta and made them available to all users. Figma Make is positioned as a prompt-to-app tool that lets people create interactive, high-fidelity prototypes without extensive technical skills. The company argues that this speeds up exploration and alignment while enabling designers, engineers, researchers, and product managers to participate more directly in product development. ## Figma Make Becomes Generally Available - Users can create prototypes and web apps through natural-language prompts. - New capabilities include: - Importing an existing Figma library, including colors, typography, styling, and usage guidelines. - Connecting prototypes to backend data through a Supabase integration. - Figma’s other AI features, including Make and Edit Image and Boost Resolution, are also leaving beta. - Publishing Figma Make files remains in beta. ## Availability, Seats, and AI Credits - **Full seat users** receive the full Figma Make and AI experience, including private sharing and publishing capabilities. - **View, Collab, and Dev seat users** can create unlimited Make files in drafts and use the AI features available to their seats. - **Starter plan users** can create unlimited draft files and share up to three Make files with their team. - AI credits are included with all seats. - Full-seat monthly allocations are: - Professional: 3,000 credits, estimated at 50–70 Make prompts. - Organization: 3,500 credits, estimated at 60–80 prompts. - Enterprise: 4,250 credits, estimated at 80–100 prompts. - Figma plans to offer additional credits for purchase later. Full-seat limits will not initially be strictly enforced, while lower limits for Starter, View, Collab, and Dev users are enforced daily and monthly. ## Faster, More Collaborative Product Development - Figma says Make supports the broader development process, not just prototyping. - Designers can test complex interactions. - Engineers can produce high-fidelity design artifacts. - Product managers can build functional mockups to validate ideas. - The tool encourages teams to experiment, take risks, and discuss concrete artifacts rather than abstract descriptions. ## Making Prototyping More Accessible - Figma argues that language alone often fails to communicate how a product should look and feel. - Traditional prototypes can be time-consuming or inaccessible to people without design or development expertise. - Natural-language prompting allows more team members to turn ideas into realistic prototypes quickly. - Figma researcher Rie McGwier used Make to build a Survey Traffic Calculator for managing roughly 30 surveys across eight products. - The prototype modeled weekly active users, audience overlap, response rates, recontact windows, sampling requirements, and other constraints, producing a dashboard to help avoid oversampling. Figma’s recommendation is to use Make as a collaborative exploration tool: teams can rapidly turn ideas into working artifacts, test assumptions, and refine solutions before committing to full implementation.

Read original(opens in new tab)
figma2 min readCurated summary

Launching the roadshow for Figma’s proposed IPO | Figma Blog

Figma announced the launch of its roadshow for a proposed initial public offering of Class A common stock. The offering includes new shares from Figma and shares sold by existing stockholders, with an expected price of $25–$28 per share. Figma plans to list on the New York Stock Exchange under “FIG,” pending regulatory effectiveness. ## Proposed Share Offering - Figma will offer 12,472,657 shares of Class A common stock. - Existing stockholders will offer 24,646,423 additional shares. - Selling stockholders may grant underwriters a 30-day option to purchase up to 5,540,561 more shares for over-allotments. - Figma will not receive proceeds from shares sold by existing stockholders. - The expected IPO price is $25–$28 per share. ## Listing and Underwriters - Figma has applied to list its Class A common stock on the New York Stock Exchange under the ticker symbol **FIG**. - Morgan Stanley, Goldman Sachs, Allen & Company, and J.P. Morgan are joint lead book-running managers. - BofA Securities, Wells Fargo Securities, and RBC Capital Markets are book-running managers. - William Blair and Wolfe | Nomura Alliance are serving as co-managers. ## Regulatory Status - Figma’s registration statement has been filed with the SEC but is not yet effective. - The shares cannot be sold, and purchase offers cannot be accepted, until the registration process is complete. - The offering will be made only through a prospectus. ## Figma’s Business - Founded in 2012, Figma describes itself as a collaborative platform for digital product development. - It has expanded from a design tool into a connected, AI-powered platform supporting ideation, design, development, and product delivery. Figma’s announcement marks a formal step toward becoming a public company, but the IPO remains subject to SEC approval and final offering conditions.

Read original(opens in new tab)