Figma

532 posts

figma2 min readCurated summary

Combine is taking on the design venture capitalist world | Figma Blog

Combine is a new seed-stage venture firm founded by former Facebook and Airbnb design leaders Soleio Cuervo and Adam Michela. Rather than relying on publicity, it plans to build an elite, design-focused portfolio and provide hands-on support through an in-house team of design partners. The firm’s model combines early investment with design-studio services, reflecting the growing importance of user experience in competitive software markets. ## A Quiet Venture Launch - Combine launched with little publicity, sharing only cryptic images of its warehouse office and no formal Medium announcement. - Despite its low profile, Silicon Valley insiders were watching closely. - The founders’ understated approach reflects their belief that reputation should come from past work rather than promotional claims. ## Founders with Deep Design Experience - Soleio Cuervo was Facebook’s second design hire. - He helped shape the company’s early design culture. - He led work on Facebook Messenger, Groups, and the original Like button. - Adam Michela joined Facebook after Cuervo’s departure. - He created Facebook’s first design system. - He later built a design system at Airbnb. - Their contrasting personalities complement each other: - Cuervo is an expressive, relationship-oriented connector. - Michela is a quieter, methodical operator. - Both share a strong interest in design and people, along with a reluctance to self-promote. ## A Venture Firm Built Around Design - Combine had raised more than $12 million for its first fund. - The firm planned to maintain a small, selective portfolio. - It intended to hire a team of highly experienced design partners. - These partners would work directly with portfolio companies on: - Branding and marketing - User research - Product design - Recruiting and team-building - The model resembles Andreessen Horowitz’s service-oriented venture approach, but with an unusually strong focus on design. ## The Growing Importance of Design - Combine was launching as startups increasingly compete through user experience. - Cloud infrastructure has made software cheaper and easier to build, giving consumers more alternatives. - As functional differences narrow, thoughtful design can become a company’s strongest competitive advantage. - Users increasingly blame a product—not themselves—when they cannot understand how to use it, making usability central to business success. Combine’s approach represents a shift from venture capital as primarily financial support toward venture capital as an active operating partnership. Its success would depend on whether elite design expertise can meaningfully improve early-stage companies and establish a repeatable model for design-driven investing.

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

Design conference Vectors sold out in two days | Figma Blog

Vectors, a new San Francisco design conference, sold out 300 tickets in just two days because it offered perspectives missing from conventional tech events. Rather than focusing on business trends, its program addressed vulnerability, unconscious bias, and inclusion. Organizer Gabriel Valdivia argues that diverse experiences improve design and that people with privilege should actively invite perspectives unlike their own. ## A Different Kind of Design Conference - Vectors was created as an alternative to typical technology conferences centered on “thought leaders” and commercial design topics. - Its talks focused on: - Vulnerability - Unconscious bias - Divergent perspectives - The event attracted enough interest to leave 150 additional people on the guest list. ## Diversity as an Invitation, Not a Label - Organizers deliberately avoided presenting Vectors explicitly as a “diversity” conference. - Traditional diversity initiatives can become limited to people who already identify with the issue. - Valdivia wanted people who were not already concerned about diversity—especially white men in tech—to attend and reconsider how they use their influence. - The goal was for privileged attendees to understand the practical value of including different perspectives. ## Experience Shapes Design - Valdivia describes his Cuban and Costa Rican background, including working low-wage jobs after immigrating to the United States. - Experiences such as cleaning car dealerships, working in a call center, and waiting tables exposed him to challenges many technology leaders may not have encountered. - He believes these experiences developed resilience and provide useful insight in product design. ## Small Inclusive Choices Create Value - Valdivia argues that products inevitably reflect their creators’ backgrounds. - Because many products disproportionately reflect white male perspectives, other useful viewpoints can remain overlooked. - At a previous startup, he added Spanish subtitles to a product video, making it accessible to Spanish-speaking audiences. - Such seemingly minor decisions can significantly expand a product’s usefulness and reach. Vectors’ success suggests that designers and technology professionals want more than conventional industry perspectives. Building better products requires actively including people with different backgrounds and turning their experiences into concrete design decisions.

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

How one designer escaped the export-upload abyss | Figma Blog

The post argues that traditional designer-developer handoff creates unnecessary work, outdated files, and communication problems. At Pivotal, designer Colby Sato replaced repeated image exports and uploads with Figma’s browser-based, collaborative workflow. This saved roughly two days per project and made design critiques more focused and efficient. ## The Export-and-Upload Problem - Colby exported design frames as images and uploaded them to Pivotal Tracker engineering cards. - He repeated this process 15–20 times per project as designs evolved. - Searching through hundreds of engineering cards was time-consuming. - Missed updates sometimes caused engineers to implement outdated designs. - The process wasted developer time and made collaboration frustrating. ## Figma as a Shared Source of Truth - Figma files were accessible in the browser, always current, and shareable through links. - Colby could add a Figma link when creating an engineering card instead of updating images repeatedly. - Comments attached directly to design frames provided functional context. - The workflow eliminated uncertainty about which design version engineers should use. - Colby estimated it saved him two days of work per project. ## More Effective Design Reviews - Pivotal’s weekly critiques had previously relied on post-it notes and verbal explanations. - Figma comments stayed attached to the relevant design, making feedback easier to understand. - Colby could observe where engineers were focusing in the file through their cursor activity. - He could redirect reviewers toward areas where feedback was most valuable. - Reviews became faster, more contextual, and more collaborative. Figma ultimately shifted Pivotal’s focus from tracking files and feedback to improving the product itself. The post recommends using a shared, continuously updated design workspace to reduce handoff friction and enable stronger collaboration between designers and engineers.

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

Tips for using Constraints in your workflow

Figma’s constraints feature helps designers build layouts that adapt across different screen sizes and contexts. By anchoring elements to edges, centers, or grids, designs can remain structurally consistent instead of requiring separate manual adjustments. The post presents five practical applications, from simple button placement to flexible navigation bars, table cells, and playful illustrations. ## Pinning Buttons to Corners - Set an action button’s constraints to the bottom and right sides of its parent frame. - This keeps floating action buttons in a consistent location as the screen expands. ## Combining Components and Constraints - Constrain important elements within a frame, then convert the frame into a reusable component. - Duplicate the component for different screen sizes. - Changes to the original—such as colors or text sizes—propagate to all instances, making responsive variations easier to manage. ## Building Flexible Navigation Bars with Grids - Nest a navigation bar frame at the bottom of a phone-screen frame. - Set its constraints to **left & right** and **bottom** so it stretches with the screen. - Apply a layout grid with the **stretch** type. - Place buttons in grid columns and center-constrain them so they reposition as the screen changes. ## Creating Reusable Table Cells - Group related content, such as an avatar and text, and constrain it to the center-left of the cell. - Group action text and a rounded rectangle into a button, then constrain it to the center-right. - The cell’s contents remain attached to their intended sides across different frame widths. ## Experimenting with Illustrations - Horizontal and vertical constraints can also be applied creatively to illustrations. - Stretching constrained artwork can produce humorous distortions and playful effects. Constraints are most useful when combined with components and grids. Setting them thoughtfully allows one design to adapt across many screen sizes while reducing repetitive layout work.

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

How Braintree Cut Time Spent on Design Critiques by 50% | Figma Blog

Braintree redesigned its critique process by replacing static presentations and follow-up meetings with real-time collaboration in Figma. Designers worked together in the same file during Slack audio calls, making and demonstrating changes immediately. This cut critique time by roughly 50% while also improving collaboration and simplifying developer hand-offs. ## Challenges with Traditional Critiques - Designers typically presented work, collected feedback, and worked alone afterward. - Feedback could be misunderstood or difficult to apply correctly. - Follow-up meetings were needed to review revisions and address new issues. - After PayPal acquired Braintree, multiple design teams, style guides, services, and developer groups increased coordination complexity. ## Finding Figma - Braintree’s Developer Experience team experimented with new critique methods. - Figma’s browser-based, collaborative files allowed designers to work together regardless of device or location. - Designers joined an audio Slack call and opened the same file instead of scheduling several in-person meetings. - Figma’s observation mode let one designer follow another’s screen and move through different frames in real time. ## Collaborative Work Instead of Static Feedback - Designers could duplicate an artboard and make changes while discussing the design. - Feedback became concrete and immediately understandable rather than being recorded as notes for later. - Team members brainstormed, explored alternatives, and combined the strongest elements of multiple designs. - Craig Wattrus estimated that critiques took 50% less time because collaborators could demonstrate ideas directly. - The process often produced better results than one designer working independently and applying feedback later. ## Faster Developer Hand-off - Designers shared a single link with developers instead of repeatedly exporting updated files. - Designers could explain interactions and demonstrate behavior directly in the shared file. - Developers received answers immediately, reducing long message exchanges. - Design and engineering teams needed fewer meetings to clarify how interfaces were intended to work. Braintree’s experience suggests that real-time, shared design files can turn critiques into productive collaboration sessions. Teams looking to reduce review cycles and improve design-to-development communication should consider working together directly in the design artifact rather than relying on presentation-based feedback.

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

Reflecting on Figma’s First Year | Figma Blog

Figma’s first year focused on proving that a browser-based design tool could deliver both powerful graphics performance and trustworthy collaboration. The company moved from being dismissed as a “toy” to becoming a serious platform through rapid feature releases, performance improvements, and better support for existing Sketch workflows. Its central insight was that multiplayer editing creates not only collaboration, but also a shared source of truth for entire product teams. ## Building a Browser-Based Design Platform - Figma faced major technical challenges in rendering complex graphics smoothly in a browser. - It also had to persuade designers that a web-based tool could be reliable enough for professional work. - The team spent its first year speaking with designers, engineers, and product managers to understand the needs of growing organizations. - Figma invested heavily in: - Faster file loading and rendering - Workflow improvements and polish - Continued refinement of Sketch import - Because releases came so quickly, the company collected its major updates in one anniversary retrospective. ## Collaborative Design and Multiplayer Editing - Public multiplayer editing launched on September 28, 2016, making Figma the first design tool to offer simultaneous editing. - Designers initially reacted both enthusiastically and skeptically to the idea of “pair design.” - After a year, teams were using multiplayer editing to: - Ship products under tight deadlines - Mentor designers remotely - Conduct more efficient design critiques - The larger benefit was a single source of truth: - Files could be shared through a persistent URL. - Updates appeared at the same location without requiring teams to synchronize assets manually. - Teams avoided overwritten files and outdated versions. - Different roles could work directly with the design: - Copywriters could test messaging. - Developers could inspect design attributes for implementation. - Product managers could monitor progress without relying on Slack updates. ## Components and Design Systems - As design became more central to product development, companies needed systems for maintaining consistent UI elements across teams and files. - Figma introduced components on December 8, 2016, allowing designers to synchronize reusable elements such as navigation menus and status bars. - Component overrides let designers customize individual instances—for example, changing color or typography—without disconnecting them from the underlying component. - This balanced flexibility with consistency, allowing teams to benefit from a broader design system while still adapting individual designs. Figma’s first-year progress suggests that browser-based design succeeds when performance, compatibility, and collaboration are treated as equally important. Its persistent shared files and emerging design-system features aimed to make the design process more connected across the entire product team.

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

Figma's two-factor authentication | Figma Blog

Figma introduced two-factor authentication (2FA) to give users additional protection if their passwords are compromised. Users can receive codes by SMS or an authenticator app, with recovery codes available if they lose access to their phone. After verification, 2FA remains valid for 21 days unless the user logs in from a new device or signs back in after logging out. ## Enabling Two-Factor Authentication - Users can activate 2FA from the account settings menu in Figma. - Supported verification methods include: - SMS login codes - Authenticator apps such as Google Authenticator - The feature works with all mobile phones. ## Recovery and Login Behavior - Figma provides recovery codes in the account settings. - Users are encouraged to record these codes in case they lose their phone. - 2FA is required when: - Logging in on a new device - Signing back in after logging out - Once authenticated, the verification remains valid for 21 days. Figma recommended enabling 2FA as an additional account-security measure and indicated that more security features were planned for the future.

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

Are hackathons the answer to the tech designer shortage? | Figma Blog

Hackathons could help address the tech industry’s designer shortage by connecting design students with engineers, rapid product development, and recruiting companies. However, traditional hackathons often make designers feel unwelcome because they emphasize coding and seem aimed exclusively at developers. Hack@Brown shows that deliberate outreach and inclusive programming can turn hackathons into an effective pathway into product design careers. ## Making Hackathons Welcoming to Designers - Many design students believe they do not belong at hackathons because they cannot code or view tech companies as “selling out.” - Hack@Brown changed its branding to appear more professional and appealing to designers. - Organizers introduced dedicated UX and UI prizes. - They contacted design clubs nationwide and paid travel costs for students to attend. - The event’s design team grew from four members to six, helping ensure designers’ concerns shaped the experience. ## The Missing Path into Tech Design - Engineers have established routes into technology through coding education, projects, and recruiting pipelines; designers often lack an equivalent path. - Even invited designers sometimes left after seeing recruiting booths focused on engineers, reinforcing the sense that they did not fit in. - Companies need to take responsibility for finding potential designers rather than waiting for them to enter traditional tech channels. - Personal mentorship can be decisive: Atty Eleti discovered his potential as a designer after encouragement from Figma engineer Jessica Liu and designer Alice Lee. ## Hackathons as a Recruiting Funnel - Hack@Brown grew from 15–20 designers in 2013 to more than 100 in 2017—about 20% of attendees. - Companies including Facebook, Kayak, LinkedIn, Dropbox, IBM, and GE were increasing designer recruitment. - Facebook representatives attended to identify students with potential and followed up with attendees, including campus visits. - Recruiters seek designers with a combination of skills that remains difficult to find because product design is still a relatively young field. - Hackathons give companies an opportunity to meet promising candidates early and show students that tech design offers substantial career opportunities. Companies and hackathon organizers should actively invite, support, and mentor designers. With inclusive branding, design-specific challenges, financial assistance, and visible designer participation, hackathons can become a meaningful bridge into tech careers rather than developer-only events.

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

Figma Mirror for Android | Figma Blog

Figma introduced Mirror for Android on May 9, 2017, bringing real-time mobile previews to Android users and designers. The app reflects selected Figma frames on an Android device and updates instantly as designs change on a computer. Figma also offered the same functionality through a mobile browser, making the feature accessible without installing the app. ## Real-Time Design Mirroring - Users can select a frame in a Figma file on their computer and view it immediately on an Android phone. - Design edits made on the computer are reflected instantly in the mobile preview. - The feature helps designers test how their work appears and behaves on an actual mobile device. - Mirror was already available for iOS before the Android release. ## Browser-Based Alternative - Users who do not want to install the Android app can visit `figma.com/mobile-app` in a mobile browser. - The browser version provides the same basic mirroring functionality. ## Support for Android Design - Android accounted for roughly 52% of the U.S. smartphone market and 82% of the global market at the time. - Figma included preset frame sizes for several popular Android devices, reducing the need to create device layouts from scratch. Figma Mirror for Android made mobile design testing more inclusive and convenient, while the browser option provided a no-download alternative.

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

New faces at the Figma helm | Figma Blog

Figma is entering a new phase as demand for design and collaborative tools grows across the technology industry. To support that growth, CEO Dylan Field announces Eric Wittman as the company’s first COO and Kris Rasmussen as Vice President of Engineering. Their experience scaling collaboration-focused businesses will help Figma expand its operations, revenue, technology, and team. ## Figma’s Growth Opportunity - Companies increasingly view design as central to creating products customers value. - Large organizations such as IBM and GE are expanding their design teams, while Facebook has pursued a high designer-to-engineer ratio. - Figma argues that the tools available to designers have not kept pace with this demand. - Improving collaboration remains the company’s guiding priority. ## Eric Wittman: Operations, Strategy, and Revenue - Wittman joins after leading Atlassian’s Developer Tools business, including Bitbucket. - As COO, he will focus on: - Recruiting and finance processes - Go-to-market strategy - Revenue and business operations - Company strategy and values - His career spans: - Customer support and product management at Macromedia, where he eventually led Flash product management - CEO of music player company Songbird - General manager of Developer Tools at Atlassian - Figma highlights his unusual combination of operational expertise and strong product enthusiasm. - Before the announcement, he had already helped Figma launch its pricing model and refine its strategic direction. ## Kris Rasmussen: Engineering Leadership - Rasmussen initially joined Figma as a part-time contractor but quickly became an influential, informal leader. - He is appointed Vice President of Engineering and will oversee major engineering initiatives and technical-team development. - His background includes: - Leading engineering at Asana during its early growth - Scaling engineering at Aptana, a web-application developer-tools company - Building personal projects involving 3D graphics - Figma values his ability to resolve disagreements, identify necessary actions, and combine technical skill with leadership. - His primary mission will be building a world-class engineering organization and infrastructure for collaborative design tools. ## Continued Hiring - Figma says it is still early in its development and expects significant opportunities and challenges ahead. - The company invites engineers, designers, writers, and product managers who are passionate about design to apply for open roles. Figma’s leadership changes are intended to turn growing demand for collaborative design software into scalable business and technical execution. Wittman will strengthen operations and commercial strategy, while Rasmussen will lead the engineering organization needed for Figma’s next stage.

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

Figma’s new icon | Figma Blog

Figma’s 2017 icon redesign reflects the company’s growth and broader design philosophy. Rather than treating the icon as a standalone mark, Figma built it around three ideas: fundamental design elements, playful experimentation, and modular systems. The result is a bright, flexible icon made from simple shapes that represents both Figma’s product and its approach to design. ## Celebrating the Fundamentals of Design - All designs can be reduced to basic elements such as points, lines, and shapes. - Figma’s own tools follow this principle: a relatively small set of carefully integrated functions can produce complex results. - The icon celebrates these foundational building blocks, echoing traditions associated with Bauhaus and other design movements. - Its simple forms represent Figma’s goal of empowering designers to create sophisticated work from elemental components. ## Encouraging Play - The icon’s bright colors and block-like shapes were inspired by children’s building blocks. - Figma views experimentation and play as important ways to discover new solutions. - An open, playful design process can produce more creative and unexpected outcomes. - The icon is intended to communicate the same openness and enjoyment that Figma hopes to enable in its users’ workflows. ## Design as a System - Digital products must work across many screen sizes, devices, operating systems, and connection conditions. - Modular systems and reusable components are therefore more effective than one-off designs. - Figma favors rules-based, vector design because it can adapt to different environments more reliably than fixed pixels. - The new icon is constructed from three simple shapes arranged on a modular grid, reinforcing the idea of flexible, reusable design components. - This concept connects to Figma features such as team libraries, which help designers build and maintain systems. The new icon extends Figma’s identity while expressing its core beliefs: strong design starts with fundamentals, creativity benefits from play, and digital work is most powerful when built as an adaptable system.

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

The 6 design trends John Maeda predicted in his State of the Union | Figma Blog

John Maeda’s 2017 *Design in Tech Report* predicted rapid growth and transformation in product design. The article argues that companies increasingly need designers because technology has become easy to build, making user experience and emotional relevance key differentiators. However, fragmented tools and outdated education remain major challenges. ## Designer Hiring Surges - Major corporations are expanding their product design teams. - Companies such as Facebook, Google, and Amazon reportedly hired 65% more designers in the previous year. - More than 35 design agencies were acquired by large companies over two years. - As app development becomes commoditized, design determines how useful and meaningful products feel to people. ## More Inclusive Design - Technology’s broader reach requires products designed for people from varied backgrounds and experiences. - Companies including Airbnb, Slack, Google, and Microsoft were highlighted as leaders in inclusive design. - Inclusion is becoming both a social responsibility and a product-quality requirement. ## Design Education Falls Behind - Many design programs remain focused on print-era disciplines such as traditional typography. - Schools often fail to teach digital product design for web and mobile platforms. - More than two-thirds of surveyed students said they learned digital skills independently through resources such as Lynda.com. - Maeda expects educational institutions to change slowly because their structures and processes evolve deliberately. ## Design-Focused Investment - Venture capital is showing greater interest in companies built around design. - Two VC firms were reportedly launching with design-focused investment strategies. - Designers themselves show entrepreneurial interest: 80% of those surveyed said they would start a company if they had sufficient funding. ## Growing Number of Design Tools - Product design tools remain fragmented, supporting different workflows rather than one unified process. - Many companies are attempting to streamline collaboration and production. - Maeda warned that increasingly sophisticated tools could create more opportunities for machine intelligence and eventually reduce demand for some design work. ## Emerging Specializations - Voice-interface design is growing alongside products such as Amazon Alexa. - Cybersecurity is creating demand for specialized designers. - China is expected to become increasingly influential in the global design landscape. The outlook for technology and product design is strong, but the industry must address outdated education and disconnected workflows. Designers, companies hiring them, and toolmakers all have opportunities—especially to create more unified, collaborative design processes.

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

Team Libraries in Figma | Figma Blog

Team Libraries bring shared, synchronized components to Figma, addressing the difficulty of maintaining design systems across separate files. The feature builds on Figma’s components, constraints, and web-based collaboration to create a single source of truth that teams can reuse and update efficiently. Its workflow—Publish, Insert, and Update—combines engineering-style structure with an accessible design workflow. ## The Problems with Traditional Design Tools - Many design tools were modeled on print and illustration software rather than interactive applications. - They lack meaningful support for application behavior, platform constraints, and reusable interface structures. - Copying symbols between files creates disconnected versions that must be updated manually. - Large organizations such as Facebook, Google, and Airbnb have had to build custom tools and dedicate staff to maintaining design systems. - Designers need synchronized, compounding component structures to create scalable systems. ## Bridging Design and Dynamic Interfaces - Figma’s earlier features established the foundation for reusable design systems: - Reliable vector editing - Constraints that reflect system behavior - Dynamic, reusable components - Team Libraries extend these capabilities across files and team members. - Because Figma operates online, shared components have effectively no synchronization delay. - Teams can reuse structured components across devices, platforms, layouts, and user flows. ## An Engineering-Inspired Design Workflow - Figma draws on software concepts such as modular composition and frameworks like React. - Structuring interfaces from discrete, clearly defined parts makes products easier to maintain. - The feature adapts engineering principles for designers rather than copying programming workflows directly. ## Publishing Components - Designers select components and choose **Add to Library** in the inspector sidebar. - Multiple components can be collected and reviewed before being published. - Permissions separate the source of truth from its consumers: - Editors of the source file can modify the original components. - Anyone with view access can use the published components. - This lets specialized teams control assets such as icons, colors, or brand guidelines while others reuse them without changing the rules. ## Inserting and Nesting Components - Published components are available in any file for users who can view the source file. - Users insert them through Figma’s components tool. - Components can be nested inside larger components or modules. - Nested structures allow teams to build complex views from reusable source elements while preserving a predictable single source of truth. ## Updating Shared Components - Changes are made to the original component and published again. - Figma provides a confirmation step and a visual diff showing what changed. - Deleting a component from the source file and publishing removes it from the team library. - The update process includes an additional safeguard because changes may affect multiple design explorations and could otherwise cause users to lose work.

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

Components in Figma | Figma Blog

Figma’s 2016 Components release applies software-engineering ideas such as composition, inheritance, and overrides to interface design. Components let designers reuse shared elements as linked instances, so updates remain consistent while local customizations are preserved. The result is a design workflow that supports both systematic reuse and creative flexibility. ## Designing with Components - Components help designers break complex interfaces into smaller, understandable parts. - Reusable elements can appear in multiple locations, at different sizes and with local modifications. - Unlike duplicated copies, component instances remain connected to their source. - Updates to the original component are automatically reflected across all instances, improving consistency and reducing repetitive work. - Examples include repeated address-book rows containing shared typography, spacing, icons, and graphics. ## Figma’s Design Goals Figma aimed to make Components: - Easy for new users to learn. - Powerful enough for advanced design systems. - Flexible throughout the design process. - Low-overhead, so systematic design improves speed without limiting experimentation. ## Creating and Using Instances - Any frame or selected object can be converted into a component through the toolbar. - Duplicating, copying, pasting, or Alt-dragging a component creates instances rather than independent copies. - Instances can move independently on the canvas while retaining their connection to the source component. - Changes made to the main component propagate immediately to its instances. - Certain internal properties, such as the position and size of nested objects, are restricted to make components easier to maintain. ## Style and Property Overrides - Instance changes are treated as overrides of the original component’s properties. - Designers can override fills, strokes, colors, widths, and properties of nested layers. - Overrides remain intact when the source component changes. - Properties that were not overridden continue to update from the source component. - Overrides can be removed with the “Reset Instance” action. ## Complex and Nested Components - Components can contain instances of other components. - Combining nested components makes it possible to build larger systems from smaller, reusable parts. - Designers can add instances to an existing component or create a new component from selected instances. - Nested components are intended to work like other Figma objects, keeping complex systems manageable. ## Constraints - Components can be combined with Figma’s Constraints feature. - Constraints allow elements to respond to changes in size and position. - Together, components and constraints support reusable designs that adapt more intelligently across layouts. Components provide a practical bridge between design and software development: create shared building blocks once, reuse them widely, and preserve controlled customization through overrides. Teams building consistent, evolving interfaces can use them to reduce duplication while keeping designs adaptable.

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

Multiplayer Editing in Figma | Figma Blog

Figma’s multiplayer editing release made real-time collaboration a core part of its design workflow. The company replaced a simple whole-document save-and-upload model after it caused overwrites, stale links, and confusing collaboration problems. Although multiplayer required major changes to conflict resolution, undo/redo, layout behavior, file formats, and performance, Figma concluded that it ultimately simplified the user experience. ## Why the Original Saving Model Failed - Early Figma downloaded documents locally, let users edit in the browser, and periodically uploaded the entire document. - This approach was easy to build and familiar to users of syncing services such as Dropbox. - In team settings, however: - Users could unknowingly overwrite one another’s work. - Shared links could display an outdated version while changes were still saving. - Version history preserved data, but did not prevent collaboration mistakes. - Alternatives such as “baton-passing,” where only one person could edit at a time, lacked the simplicity and flexibility Figma wanted. ## How Figma’s Multiplayer Engine Works - Each user’s changes are sent to the server and broadcast to other participants in real time. - Independent simultaneous changes can coexist. - When users modify the same property on the same object, Figma resolves the conflict by selecting the latest change. - Implementing this model required changing fundamental parts of the editor rather than adding multiplayer as a separate synchronization layer. ## Undo, Redo, and Conflict Resolution - Undo becomes ambiguous when other users modify the same objects afterward. - Figma adopted a guiding principle: undoing actions, copying something, and redoing back to the present should leave the document unchanged. - Redo therefore cannot simply reapply the original edits, since that might overwrite newer work by collaborators. - Conflict resolution also had to account for: - Related properties that must be changed together. - Actions that indirectly affect multiple objects. - Layout operations where apparently unrelated edits can interact. - These requirements led Figma to revise aspects of its layout system. ## Performance and File-Format Changes - Professional-quality multiplayer required extensive measurement and tuning. - Figma overhauled its file format because the previous representation was inefficient for transmitting small incremental messages. - The team expected additional challenges as new collaborative features were introduced. ## A Simpler Collaborative Experience - Multiplayer reduced UX complexity by eliminating workarounds for stale files, overwrites, and coordination. - Users can see collaborators’ mouse cursors and selections, providing immediate context about who is present and where they are working. - Cursors can also serve as lightweight communication tools, such as pointing at an object or getting someone’s attention. - Each participant appears as an avatar in the top-right corner. - Clicking an avatar lets one user present to another, making presentations opt-in rather than forcing a single presenter and synchronized viewing mode. Figma’s experience suggests that real-time collaboration is best treated as a foundational part of the editor. Despite the substantial engineering investment, multiplayer editing can make collaborative software both more powerful and easier to use.

Read original(opens in new tab)