Real Time Collaboration

figmaJun 12, 20182 min readCurated summary

A Sketch user's perspective on switching to Figma | Figma Blog

After using Figma for a month, Marco Pacifico argues that Sketch teams—especially distributed product teams—could gain substantially by switching. Figma combines Sketch-like design capabilities with prototyping, collaboration, developer handoff, version control, and cloud storage in one web-based tool. Its central advantage is reducing the syncing, uploading, and coordination overhead that slows design iteration. ## Web-Based Design and Real-Time Collaboration - Figma runs in browsers, with native apps available for offline work. - Work is automatically saved to a shared cloud space, eliminating manual file organization and updates. - A single URL serves as the source of truth for designers, developers, and stakeholders. - Teams no longer need to repeatedly upload screens, sync files, or distribute PNGs. - The author reports that Figma feels at least as performant as Sketch, including with large files. ## A Replacement for the Sketch Ecosystem The article presents Figma as combining the capabilities of several tools traditionally used alongside Sketch: - Sketch-like drawing tools and interface. - Clickable prototyping comparable to Craft and InVision. - Built-in comments, tagging, resolution tracking, and Slack integration. - Developer handoff with dimensions, styles, and downloadable assets. - Version history that allows users to restore or fork earlier designs. - Multiplayer editing with visible cursors and real-time drawing. - Live viewing of another collaborator’s screen and cursor. - Flexible components, intuitive constraints, and shared team libraries. - Dropbox Paper embedding. ## Faster Design Iteration - Designers can conduct reviews, make changes, and receive immediate feedback in the same file. - Iteration can shrink from days to minutes because teams avoid: - Re-uploading screens to InVision. - Reordering prototype screens after synchronization. - Waiting for teammates in other time zones to commit or upload work. - Recovering from broken third-party plugins after software updates. - Changes are visible immediately, so there is no separate synchronization step between the design file and prototype. ## A More Inclusive Design Process - The design file becomes a shared space where team members and stakeholders can discuss work directly. - Anyone with the link can participate through comments and collaborative review. - Real-time access makes design discussions more seamless and reduces barriers between distributed teammates. ## Practical Recommendation For teams currently assembling Sketch, Abstract, InVision, Craft, Zeplin, and collaboration tools into one workflow, the author recommends evaluating Figma as a unified alternative—particularly when rapid iteration and distributed collaboration are priorities.

Read original

Real Time Collaboration Figma Design Systems Prototyping+3

figmaMay 21, 20182 min readCurated summary

5 ways to use Figma that you probably never thought of | Figma Blog

Figma’s real-time collaboration makes it useful for far more than traditional interface design. The post highlights five applications that use shared editing to organize information, make decisions, divide repetitive work, encourage creative collaboration, and have fun. Its central conclusion is that Figma’s multiplayer capabilities can support nearly any activity involving visual thinking and teamwork. ## Affinity Diagrams for Organizing Ideas - Teams can collect large amounts of research or brainstormed ideas in one shared file. - Participants add concepts simultaneously, then group related items into themes. - This process helps clarify priorities and create structure for complex projects, even when collaborators work remotely. ## Real-Time Voting for Design Decisions - Teams can review multiple design options together and mark their preferences directly in Figma. - Instead of printing designs and using physical stickers, participants place circles or other markers beside favored concepts. - Seeing votes accumulate in real time makes individual preferences clearer and helps teams reach decisions faster. ## Design Assembly Lines for Repetitive Work - Large, repetitive tasks can be divided among several people working in parallel. - ClassPass used this approach to create more than 30 custom maps, with designers placing location pins for gyms and studios in different cities. - Multiplayer collaboration allows teams to complete simple production tasks quickly through coordinated effort. ## Collaborative Comic Creation - Figma can serve as a shared illustration environment where friends or colleagues draw and develop ideas together. - USC students Louis Harboe and Parker Malachowsky used it to turn a presentation about AI and healthcare into an accessible comic. - Reusable components such as speech balloons, caption boxes, and image panels helped organize the longer project. - Figma’s vector networks provided flexibility for drawing and editing illustrations. ## Games for Team Connection - Figma’s multiplayer features can also be used for recreational games and playful activities. - Collaborative play offers a way to lighten the mood and strengthen relationships when teams are not working. - This reflects the influence of cooperative multiplayer video games on Figma’s collaboration model. Figma’s shared canvas is valuable wherever people need to think visually together. Teams can use it not only for design production, but also for research synthesis, group decisions, repetitive workflows, creative projects, and informal team-building.

Read original

Real Time Collaboration Figma Vector Graphics Design Sprints+1

figmaFeb 14, 20182 min readCurated summary

With love, from Figma: @mentions and file sorting | Figma Blog

Figma’s February 2018 update introduced two features designed to reduce friction in design workflows: file sorting and @mentions. Users can now organize files by creation date or name, while comments can directly notify specific teammates by email and in-app notification. Together, the features make finding files and coordinating asynchronous feedback more efficient. ## Organizing Files with New Sorting Options - Figma file lists were previously sorted primarily by “Last Modified.” - Users can now sort files by: - Date created - File name alphabetically - Last modified date - These options make it easier to locate older files or maintain a more organized workspace. ## Directing Feedback with @Mentions - Figma introduced @mentions for comments, allowing users to tag a teammate by typing `@` followed by their name. - Mentions are useful for: - Drawing a product manager’s attention to a specific design change - Asking engineers questions about a prototype - Notifying designers that copy edits are complete - Mentioned users receive both an email and an in-app notification. - Users can reply directly to comment notification emails, and their response is added to the Figma comment thread. ## Improving Asynchronous Collaboration - Previously, commenters had to send a document link and tell recipients to search for the relevant comment. - @mentions eliminate that extra step by pointing teammates directly to the discussion requiring their attention. - The features were developed in response to repeated requests from Figma users. Refreshing open Figma tabs enables both updates. These additions provide simple, practical improvements for organizing files and ensuring feedback reaches the right collaborator.

Read original

Real Time Collaboration Figma User Experience Prototyping+3

figmaDec 13, 20172 min readCurated summary

Stitch Fix accelerates design sprints by collaborating in Figma | Figma Blog

Stitch Fix uses Figma to make design sprints faster, more collaborative, and easier to manage across departments. Its browser-based workflow gives everyone access to one shared source of truth, eliminating file handoffs and tool-installation delays. Real-time collaboration and reusable components let the team focus on solving UX problems instead of managing files or repeating production work. ## Sprinting in the Cloud - Stitch Fix brings designers, engineers, marketers, and project managers together to brainstorm, whiteboard, and prototype solutions. - Because Figma runs in the browser, participants can join shared files through a URL, regardless of whether they use Macs or PCs. - The team avoids exchanging files and installing separate applications for design, prototyping, and developer handoff. - Head of Product Design Ellen Beldner describes Figma as a replacement for the combined workflow of Sketch, InVision, and Zeplin. - A shared cloud file creates a single source of truth from the beginning of the sprint. ## Brainstorming and Critiquing in Tandem - Design sprints often reveal technical challenges or unexpected effects elsewhere in the user experience. - Figma’s Multiplayer feature allows team members to inspect and edit the same design simultaneously. - Instead of gathering around one computer or emailing exported files, teammates can review specific areas directly in the shared file. - Ellen can leave comments, provide immediate feedback, or draw mockups to explain suggested changes. - Designers can return to the same URL later to review detailed critiques without scheduling additional walkthrough meetings. - Working in one file prevents conflicting versions and helps the team stay aligned as prototypes become higher fidelity. ## Shared Components Reduce Busywork - Tight sprint schedules leave little time for repeatedly recreating common UI elements. - Figma’s shared components provide reusable instances of interface elements. - When the master component changes, all instances update automatically. - During a card-based design-system sprint, Stitch Fix used components to test different card combinations efficiently. - Team members could continue placing component instances while others worked on navigation and related areas. - This automation freed designers to focus on broader UX questions rather than repetitive production tasks. ## Practical Conclusion Stitch Fix’s experience suggests that browser-based collaboration, real-time feedback, and reusable components can significantly streamline design sprints. Teams seeking faster cross-functional iteration should prioritize a shared design environment that reduces tool friction and keeps everyone working from the same source.

Read original

Real Time Collaboration Figma Design Systems User Experience+4

figmaSep 27, 20172 min readCurated summary

Introducing Figma’s Live Embed Kit | Figma Blog

Figma’s Live Embed Kit lets anyone place continuously updated Figma designs and prototypes on websites or inside third-party tools. Embeds use a simple iframe and remain synchronized with the original file, eliminating repeated exports and uploads. Figma presents the kit as a way to improve team communication and signals future platform tools, including a planned API. ## Simple Embedding for Websites and Tools - Users can select **Share → Public embed** in a Figma file and copy the generated iframe code. - Developers can integrate Live Embeds into their own products using Figma’s embed documentation. - Third-party platforms such as Trello, JIRA, and Dropbox Paper can enable Figma embeds for their users. ## Always-Up-to-Date Designs - Because Figma runs on the web, embedded files stay synchronized with the source document. - Small changes—such as adjusting padding or replacing an icon—appear automatically in every embed. - Teams no longer need to re-export designs or upload updated files manually. ## Collaboration Use Cases - Internal wikis can display live designs alongside project and feature documentation. - Team messaging apps can let users share the latest design versions in conversations. - Blogs and project pages can show designs that remain current for readers. ## Broader Platform Direction - Figma aims to reduce the confusion caused by outdated files scattered across email, Slack, and file-sharing services. - The Live Embed Kit is described as an early step in expanding Figma’s platform. - Figma planned to release an API for retrieving additional information from files and incorporating it into new workflows. The kit is recommended for teams and developers that want design updates to flow automatically into the places where people communicate, document, and build products.

Read original

Real Time Collaboration Figma API Web Development+3

figmaMay 21, 20172 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

Real Time Collaboration Figma User Experience Slack+2

figmaSep 27, 20163 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

Real Time Collaboration Figma Operational Transformation Web Browser+3

figmaDec 2, 20152 min readCurated summary

Design Meet the Internet | Figma | Figma Blog

Figma’s 2015 launch post argues that creative software should become online, real-time, and collaborative, just as tools like Google Docs had done for documents. Enabled by WebGL, Figma aims to bring powerful vector design into the browser while solving designers’ fragmented collaboration workflows. The company introduced its preview release after three years of development and announced $18 million in funding. ## Why Design Tools Needed the Internet - Designers increasingly work across teams, sharing assets, refining marketing copy, and preparing specifications for engineers. - Unlike engineers, designers lacked integrated tools for designing, commenting, sharing, and storing work collaboratively. - The authors believed browser limitations had prevented creative applications from moving online. ## WebGL Makes Browser-Based Design Possible - Co-founders Dylan Field and Evan Wallace began exploring WebGL in 2011. - Wallace demonstrated that WebGL could reproduce server-side image processing directly in the browser. - This led them to pursue a browser-based creative tool supported by the Thiel Fellowship. - Building Figma required solving difficult problems involving: - Vector rendering - Font layout - Browser performance - Stability across many edge cases ## Introducing Figma - Figma is a browser-based vector interface design tool designed for team collaboration. - The team spent eighteen months using the product internally and working with alpha customers. - Collaboration features included: - Sharing designs through links - Providing contextual feedback - Establishing shared brand colors - Keeping design work accessible in one place ## Preview Release and Future Plans - Figma launched a preview release that invited teams to try the product and influence its roadmap. - Planned improvements for 2016 included: - A stronger Slack integration - Shared team asset libraries - Simultaneous multiplayer editing - The company had raised $18 million from Greylock, Index, OATV, and prominent angel investors. Figma’s launch positioned the browser as a viable platform for professional creative tools. Its practical recommendation was implicit: teams should adopt collaborative, web-based design workflows rather than rely on disconnected desktop applications.

Read original

Real Time Collaboration Figma Webgl Browser Based Design+2