Figma Plugin for Better Feedback on Web Design Projects ๐Ÿ”— **Source:** [Figma Plugin for Better Feedback on Web Design Projects](https://www.youtube.com/watch?v=f2LC8PXgvYw) > [!note]+ Document Notes > tags: [figma, design-collaboration, adim, web-design] > author: Adim > source: YouTube > reference: https://www.youtube.com/watch?v=f2LC8PXgvYw > date created: 2024-12-19 10:30 > > # ๐Ÿท๏ธ Title: Figma Plugin for Better Feedback on Web Design Projects > <!-- deep-read:sections start --> ## ๐Ÿงฐ Action Inbox - [H1] Install Adim Figma plugin from plugin manager โ€” 02:46 #design-workflow - [H2] Test version control functionality for design iterations โ€” 05:23 #version-management - [H3] Evaluate centralized feedback system vs native Figma comments โ€” 01:15 #collaboration ## ๐Ÿงญ Table of Contents - [๐Ÿ“ Summary](#-summary) - [๐Ÿ“– Main Content](#-main-content) - [๐Ÿ—’๏ธ Notes](#๏ธ-notes) - [๐Ÿ“š References](#-references) - [๐Ÿ—ฃ๏ธ Paraphrase](#๏ธ-paraphrase) - [๐Ÿ“ฐ Newsletter](#-newsletter) - [โœ… Action Items](#-action-items) - [๐Ÿงช Hypotheses](#-hypotheses) - [๐Ÿ“Š Methodology](#-methodology) - [โ“ Questions](#-questions) - [๐Ÿ”ฎ Future Research](#-future-research) - [๐Ÿ’ก Implications](#-implications) - [๐Ÿง  Learning Styles Assessment](#-learning-styles-assessment) - [๐Ÿ“Š Accessibility Assessment](#-accessibility-assessment) - [๐ŸŒ DEIB Assessment](#-deib-assessment) - [โœ… Logical Validity](#-logical-validity) - [๐Ÿ›ก๏ธ DARVO Analysis](#-darvo-analysis) - [๐ŸŽฏ Conclusion](#-conclusion) ### ๐Ÿ”— References - [Figma Plugin Manager](https://figma.com/plugins) - [Adim Platform](https://adim.com) ## ๐Ÿ“ Summary - Adim released their first Figma plugin enabling designers to push designs directly from Figma to Adim for enhanced collaboration - Plugin addresses limitations in native commenting systems through deeper functionality, centralization, and version control - Key stakeholders include design teams, clients, and project managers needing better feedback workflows - Trade-off involves adding another platform to workflow but gains advanced collaboration features - Bottom line: Plugin bridges gap between design creation and comprehensive project management ## ๐Ÿ“– Main Content Adim has launched their first Figma plugin to address critical limitations in native design collaboration tools. The plugin allows users to transfer designs directly from Figma into Adim's specialized collaboration platform, solving three core problems with existing systems. First, native commenting systems lack depth in functionality. While Figma has basic commenting, Adim provides advanced features like status tracking, task prioritization, user assignment, and integrations with project management tools (Jira, ClickUp, Slack). The platform also supports internal notes visible only to team members, not clients. Second, centralization remains a major challenge. Comments left in native tools stay isolated within those platforms, creating information silos across projects. Teams cannot view all tasks in one location, leading to scattered feedback that often falls through cracks. Third, version control proves nearly impossible in Figma alone, requiring manual duplication that creates organizational chaos. The Adim plugin tracks design versions automatically, showing progression from creation to handoff. The plugin includes a rebuilt graphics collaboration interface flowing top-to-bottom rather than page-by-page navigation, making feedback collection more systematic and precise. ## ๐Ÿ—’๏ธ Notes #### โฑ๏ธ [00:00](https://youtu.be/f2LC8PXgvYw?t=0) โ€” [H1] Adim Figma Plugin Launch - Key idea: First official Figma plugin release enables direct design transfer to Adim platform - Evidence: "Introducing the first Adim Figma plugin" #### โฑ๏ธ [00:25](https://youtu.be/f2LC8PXgvYw?t=25) โ€” [H2] Why Not Use Figma's Native Comments - Key idea: Two fundamental limitations exist across all native commenting systems - Evidence: "why would I do that if Figma already has its own comment system? for two reasons" #### โฑ๏ธ [00:35](https://youtu.be/f2LC8PXgvYw?t=35) โ€” [H3] Depth of Functionality Gap - Key idea: Adim provides significantly more advanced collaboration tools than native platforms - Evidence: "functionality that is provided through aiming...is way deeper when it comes to communication and visual collaboration" #### โฑ๏ธ [01:00](https://youtu.be/f2LC8PXgvYw?t=60) โ€” [H3] Advanced Feature Set - Key idea: Platform includes status tracking, prioritization, assignments, and integrations - Evidence: "they include the statuses, prioritization, assignment to different users, uh alignment into a bunch of other platforms" #### โฑ๏ธ [01:15](https://youtu.be/f2LC8PXgvYw?t=75) โ€” [H3] Internal Task Management - Key idea: Teams can create internal notes invisible to clients and stakeholders - Evidence: "allows you to make tasks internal so that not everyone can see them...Leave notes for each other that uh clients or stakeholders cannot see" #### โฑ๏ธ [01:35](https://youtu.be/f2LC8PXgvYw?t=95) โ€” [H2] Centralization Problem - Key idea: Native comments stay isolated within their platforms, creating information silos - Evidence: "When you leave a comment inside these uh native commenting features...the comment lives there and it stays there" #### โฑ๏ธ [02:05](https://youtu.be/f2LC8PXgvYw?t=125) โ€” [H3] Comments Fall Through Cracks - Key idea: Isolated comments function more like personal notes than actionable feedback - Evidence: "It is designed to fall between the cracks...They consider that when they leave a comment and no one else will see them" #### โฑ๏ธ [02:20](https://youtu.be/f2LC8PXgvYw?t=140) โ€” [H2] Version Control Challenges - Key idea: Figma lacks proper version control, requiring manual duplication that creates chaos - Evidence: "Very hard to do in Figma. In fact, impossible if you just need to duplicate different elements and the whole thing becomes a mess" #### โฑ๏ธ [02:46](https://youtu.be/f2LC8PXgvYw?t=166) โ€” [H1] Plugin Installation Process - Key idea: Access plugin through right-click menu or manage plugins section - Evidence: "To turn on the plug-in, I'm just going to rightclick here and then I'm going to go to plugins" #### โฑ๏ธ [03:25](https://youtu.be/f2LC8PXgvYw?t=205) โ€” [H2] Project Creation Workflow - Key idea: Select specific frames or entire design to create projects in Adim - Evidence: "I need to select what I'm going to push through. And I'm just going to select this frame" #### โฑ๏ธ [04:15](https://youtu.be/f2LC8PXgvYw?t=255) โ€” [H3] Multiple Page Management - Key idea: Can add multiple design pages to single project for comprehensive review - Evidence: "And then I have multiple pages. So I'm just going to click on this one and add a design" #### โฑ๏ธ [04:35](https://youtu.be/f2LC8PXgvYw?t=275) โ€” [H2] Version Control Implementation - Key idea: Add version button tracks design iterations and revision rounds - Evidence: "there's an add version button here...allowing me to track the progress and how many revision rounds we had per design" #### โฑ๏ธ [05:23](https://youtu.be/f2LC8PXgvYw?t=323) โ€” [H1] Rebuilt Collaboration Interface - Key idea: New top-to-bottom flow replaces page-by-page navigation for better feedback precision - Evidence: "This is the rebuilt graphics uh collaboration system...redesigned to have it flow from top to bottom" #### โฑ๏ธ [06:45](https://youtu.be/f2LC8PXgvYw?t=405) โ€” [H3] Client Communication Benefits - Key idea: Version tracking helps communicate iteration limits to clients - Evidence: "we're already on the 17th version. Uh maybe it's time to wrap it up...maybe after two or three, that's the right time to start flagging" ## ๐Ÿ“š References - [Figma Plugins](https://figma.com/plugins) - [Adim Platform](https://adim.com) - [Jira Integration](https://atlassian.com/software/jira) - [ClickUp Integration](https://clickup.com) ## ๐Ÿ—ฃ๏ธ Paraphrase - Adim created a Figma plugin that transfers designs into their collaboration platform, solving depth limitations in native commenting by providing advanced project management features, integrations, and internal task capabilities - Native commenting systems create information silos where feedback stays trapped in individual platforms, preventing centralized task management and causing important comments to be overlooked or forgotten - Version control becomes manageable through automated tracking instead of manual duplication chaos, while a redesigned interface guides reviewers through systematic top-to-bottom feedback collection ## ๐Ÿ“ฐ Newsletter ๐ŸŽจ **New Figma Plugin Revolutionizes Design Collaboration** Design teams finally have a solution for scattered feedback! Adim's new Figma plugin bridges the gap between design creation and comprehensive project management. **What's the big deal?** Native commenting systems fall short with limited functionality and isolated feedback that gets lost between platforms. This plugin transfers your Figma designs directly into Adim's advanced collaboration environment. **Key benefits:** - Advanced project management features (status tracking, prioritization, assignments) - Centralized feedback across all projects in one dashboard - Automated version control to track design iterations - Internal notes invisible to clients - Integrations with Jira, ClickUp, and Slack **Try it now:** Search "Adim" in your Figma plugin manager and start streamlining your design feedback workflow. Resources: [Figma Plugins](https://figma.com/plugins), [Adim Platform](https://adim.com), [Design Collaboration Best Practices](https://figma.com/best-practices) ## โœ… Action Items #### DevRel - Developer advocacy: Create integration tutorials showing Figma-to-development handoff workflows - Education: Develop workshop curriculum on design collaboration tool selection - Developer experience: Document API endpoints for custom Figma plugin development - Developer marketing: Partner with design tool influencers for plugin demonstrations - Community management: Establish feedback channels for plugin feature requests #### Community - Maintainers: Provide plugin development templates and governance guidelines - Contributors: Create first-issue programs for plugin enhancement contributions - Sponsors: Develop transparent ROI reports for design tool investments - Ecosystem: Coordinate with other design tool integrations for interoperability #### WordPress - Design: Audit design collaboration workflows in WordPress core development - Documentation: Create design handoff guidelines for theme and plugin developers - Community: Integrate design collaboration training into WordCamp curricula - Meta: Evaluate design review processes for WordPress.org properties ## ๐Ÿงช Hypotheses - Teams using integrated design collaboration tools will reduce feedback cycle times by 40-60% compared to native commenting systems - Centralized design feedback systems will decrease project communication overhead and missed requirements by eliminating information silos - Automated version control in design workflows will improve client relationships through transparent iteration tracking - Top-to-bottom feedback interfaces will increase comment completion rates and reduce reviewer fatigue compared to free-form canvas navigation ### ๐Ÿ“Š Methodology - A/B testing comparing feedback cycle completion times between native Figma comments and Adim plugin workflows - Survey analysis of design team communication overhead before and after centralized feedback implementation - Client satisfaction measurement tracking version transparency and iteration discussions ### โ“ Questions - How do centralized design feedback systems impact cross-functional team collaboration beyond design reviews? - What integration patterns emerge when design collaboration tools connect with development workflows? - How might AI-powered feedback analysis change design iteration processes in collaborative platforms? ### ๐Ÿ”ฎ Future Research - Integration patterns between design collaboration platforms and development handoff tools - Impact of automated version control on design decision documentation and team learning - Effectiveness of structured feedback flows versus free-form collaboration in creative processes ### ๐Ÿ’ก Implications - Practice: Design teams need evaluation frameworks for collaboration tool selection and workflow integration - Policy: Organizations should establish design feedback governance including version limits and approval processes - Security: Design collaboration platforms require access controls for internal notes and client-visible content - Education: Design curricula should include collaborative workflow management alongside individual design skills - Funding: Design tool budgets should account for integration costs and workflow transition time ### ๐Ÿง  Learning Styles Assessment Reading level estimate: 9.2 (Flesch-Kincaid Grade Level) #### ๐Ÿ‘€ Visual learners - Present: Screen recordings of plugin installation and workflow demonstration - Improve: Architecture diagrams showing information flow between Figma and Adim #### ๐Ÿ”Š Aural learners - Present: Video narration explaining plugin benefits and workflow steps - Improve: Audio-only version focusing on decision frameworks for tool selection #### ๐Ÿ—ฃ๏ธ Verbal learners - Present: Clear definitions of collaboration concepts and feature comparisons - Improve: Story-driven examples of before/after workflow transformations #### ๐Ÿงฉ Kinesthetic learners - Present: Step-by-step installation and setup walkthrough - Improve: Hands-on checklist for evaluating collaboration tool effectiveness #### ๐Ÿง  Logical learners - Present: Structured comparison of native vs integrated collaboration features - Improve: Decision tree for selecting appropriate design collaboration workflows #### ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Social learners - Present: Emphasis on team collaboration and client communication benefits - Improve: Discussion prompts for team evaluation of current collaboration pain points #### ๐Ÿง˜โ€โ™€๏ธ Solitary learners - Present: Individual plugin setup process and personal workflow optimization - Improve: Self-assessment worksheet for collaboration tool needs analysis #### ๐ŸŒฟ Naturalistic learners - Present: Workflow ecosystem thinking and tool integration patterns - Improve: Collaboration tool lifecycle analysis and sustainable workflow design ### ๐Ÿ“Š Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure and descriptive video narration - Improve: Alt text for plugin interface screenshots and workflow diagrams #### Keyboard navigation - Present: Focus on Figma's accessible plugin interface - Improve: Document keyboard shortcuts for plugin navigation #### Contrast and readability - Present: High contrast plugin interface elements - Improve: Ensure text overlays meet 4.5:1 contrast requirements #### Text resizing and reflow - Present: Plugin interface scales with Figma's zoom settings - Improve: Test readability at 200% zoom for all interface elements #### Media and captions - Present: Video demonstration with clear narration - Improve: Add captions and provide transcript for screen reader users #### Forms and interactions - Present: Clear plugin installation and setup process - Improve: Error handling guidance for plugin configuration issues ### ๐ŸŒ DEIB Assessment #### Cultural breadth - Present: Focus on universal design collaboration challenges - Improve: Include examples from different cultural design approaches and global team structures #### Inclusive language - Present: Gender-neutral terms and clear technical language - Improve: Define technical jargon and avoid design industry idioms #### Neurodiversity support - Present: Structured workflow presentation and clear step-by-step processes - Improve: Provide alternative navigation options for different cognitive preferences #### Representation - Present: Focus on functional benefits rather than specific user types - Improve: Include diverse team structure examples and accessibility considerations #### Psychological safety - Present: Supportive tone encouraging experimentation with new tools - Improve: Address concerns about workflow disruption and change management ### โœ… Logical Validity #### Strong reasoning - Deductive strength: Native commenting limitations lead to collaboration problems, therefore specialized tools provide better outcomes - Inductive strength: Plugin features address specific pain points observed across design teams - Causal reasoning: Centralized feedback directly reduces information silos and missed requirements - Analogical strength: Version control benefits in development apply similarly to design workflows #### Fallacies - Appeal to novelty: Location 00:00, "first Adim Figma plugin" - newness doesn't guarantee effectiveness - False dilemma: Location 01:35, implies only two solutions exist (native comments vs Adim) - other collaboration tools available #### Tone of voice - Overall tone: Confident and promotional with technical demonstrations, maintains professional credibility through specific feature explanations ### ๐Ÿ›ก๏ธ DARVO Analysis - Deny: No significant denials or minimization present - Attack: No attacks --- ## Full Transcript [00:00] Another<br>[00:03] week, another release, and this time I<br>[00:05] have something big for you. Introducing<br>[00:08] the first Adim Figma plugin. The plug-in<br>[00:10] allows you to drive designs directly<br>[00:13] from Figma into Adarim so that you can<br>[00:15] collaborate on those designs over there.<br>[00:18] Now, why would I do that if Figma<br>[00:19] already has its own comment system? for<br>[00:21] two reasons and these are the two things<br>[00:23] that are shared across all of those<br>[00:25] native communication systems or<br>[00:27] commenting system that are out there.<br>[00:29] Number one is depth. The functionality<br>[00:32] that is provided through aiming because<br>[00:33] this is our focus for the past few years<br>[00:36] uh is way deeper when it comes to<br>[00:39] communication and visual collaboration<br>[00:41] compared to any of the native platforms<br>[00:44] that are out there. This is because this<br>[00:46] is our focus. So we give you much more<br>[00:48] advanced tools. For example, they<br>[00:49] include the statuses, prioritization,<br>[00:52] assignment to different users, uh<br>[00:54] alignment into a bunch of other<br>[00:56] platforms that you may be using like<br>[00:57] Jira, ClickUp or anything or Slack or<br>[00:59] anything like this. Uh it also allows<br>[01:01] you to make tasks internal so that not<br>[01:04] everyone can see them as you're working<br>[01:05] on some of the different elements. Leave<br>[01:07] notes for each other that uh clients or<br>[01:10] stakeholders cannot see just internal<br>[01:11] team members and a bunch and this is<br>[01:13] just scratching the surface. there's a<br>[01:15] bunch more uh attached to Adorim that<br>[01:17] just does not exist in uh Figma. And<br>[01:19] number two, centralization. When you<br>[01:21] leave a comment inside these uh native<br>[01:24] commenting features, whether this is on<br>[01:25] Figma or inside WordPress or inside Wix<br>[01:29] or anything uh really, the comment lives<br>[01:32] there and it stays there. And because<br>[01:35] there's no connectivity to any of the<br>[01:37] other projects that we're doing, there's<br>[01:38] no way to look at all of the tasks in<br>[01:41] one centralized location. It is designed<br>[01:44] to fall between the cracks. So really<br>[01:47] how people use this mostly is as notes.<br>[01:49] They consider that when they leave a<br>[01:51] comment and no one else will see them.<br>[01:53] Maybe sometime someone will just pass by<br>[01:56] and see that comment in there but<br>[01:57] generally it's not something that you<br>[01:59] can rely on. Um, also when it comes to<br>[02:01] execution, because there's no proper<br>[02:04] tracking across multiple projects,<br>[02:06] you're expected to go into each one of<br>[02:08] the projects to see the comments for<br>[02:09] each of them instead of using our board<br>[02:11] systems or the inbox or uh the the<br>[02:14] multiple ways that we allow people to<br>[02:16] centralize this those communications.<br>[02:18] Now, I'll give you a third one because<br>[02:20] this is a bonus one, which is version<br>[02:22] control. Very hard to do in Figma. In<br>[02:24] fact, impossible if you just need to<br>[02:26] duplicate different elements and the<br>[02:28] whole thing becomes a mess. But with the<br>[02:29] Adim Figma plug-in, you can now<br>[02:31] understand how many versions were<br>[02:33] created for each design as it gets from<br>[02:36] creation into handoff and feedback. So<br>[02:39] each platform serves its own purpose.<br>[02:42] Now, I'm not even mentioning what's<br>[02:43] coming with the graphics AI and how all<br>[02:45] of this uh uh connected to Figma is a<br>[02:48] huge game changanger, but that's<br>[02:49] something that I'll talk about in<br>[02:50] hopefully a month or so. So, let's dive<br>[02:53] straight in. To turn on the plug-in, I'm<br>[02:54] just going to rightclick here and then<br>[02:56] I'm going to go to plugins. If I don't<br>[02:57] have it installed yet, I'm going to<br>[02:58] click on manage plugins. And you can<br>[03:00] find this there just by typing Adarim.<br>[03:02] Once you install it once, then you<br>[03:03] should be able to see it right here on<br>[03:05] the top. I'm going to choose Adarim<br>[03:07] here. You can see that I'm already<br>[03:08] logged in and connected to my uh uh<br>[03:10] playground workspace. And I want to<br>[03:12] create a project in Adarim with this uh<br>[03:14] project that we have right here. So for<br>[03:16] this, I need to select what I'm going to<br>[03:18] push through. And I'm just going to<br>[03:19] select this frame. If I'm not going to<br>[03:21] select a specific frame, it's going to<br>[03:22] bring in the entire design into one<br>[03:24] slide, which is a use case. Uh but uh if<br>[03:27] you want to bring in specific frames,<br>[03:29] you just need to select it. And then<br>[03:30] you're going to click on here and add<br>[03:32] new project.<br>[03:35] Now we have a project called collabite<br>[03:36] selection model, which is exactly what<br>[03:38] this thing is. And then I have multiple<br>[03:41] pages. So I'm just going to click on<br>[03:42] this one and add a design.<br>[03:45] And I'm going to click on this one and<br>[03:47] add a design. And click on this one. Add<br>[03:50] a design.<br>[03:52] And that's it. I'm set up. Now you can<br>[03:54] also see that there's an add version<br>[03:55] button here. So let's say that something<br>[03:57] has changed and then I want to push it<br>[03:59] again as a new version allowing me to<br>[04:02] track the progress and how many revision<br>[04:04] rounds we had per design. So I can just<br>[04:06] select it again and then choose which uh<br>[04:08] page I want this to be associated with<br>[04:11] and uh click on add version which is<br>[04:13] just going to add this as version two of<br>[04:15] the same page. Let's see an example.<br>[04:17] Just going to do this on this and put it<br>[04:19] on the first one actually as a new<br>[04:21] version.<br>[04:25] Yeah. So you can see that now we have<br>[04:26] version two here. Only thing left to do<br>[04:29] is click on share so we can go and see<br>[04:30] the project right inside.<br>[04:33] Now I'm taking the opportunity to show<br>[04:35] you an interface that you haven't seen<br>[04:36] before. This is the rebuilt graphics uh<br>[04:39] collaboration system uh which uh instead<br>[04:42] of having it page by page, it is<br>[04:44] redesigned to have it flow from top to<br>[04:46] bottom which leans into the intent of<br>[04:48] giving feedback in a much more precise<br>[04:50] way than needing to go in and out of<br>[04:53] different pages as well as navigating<br>[04:54] aimlessly on an open canvas that there<br>[04:57] could be things in different places.<br>[04:58] What is the order or anything like this?<br>[05:01] So now you have it flown so the people<br>[05:03] you're inviting to give feedback can go<br>[05:04] from the top to the bottom and add<br>[05:07] comments to each element right here.<br>[05:10] Now I mentioned that I pushed a second<br>[05:12] version to the first design and we can<br>[05:15] see right here that we have version two.<br>[05:17] We can navigate between the different<br>[05:18] versions and see how the design<br>[05:20] progressed over time. Also, this is a<br>[05:22] great way of communicating to clients or<br>[05:24] stakeholders that we can might say,<br>[05:26] "Listen, man, we're already on the 17th<br>[05:28] version. Uh maybe it's time to wrap it<br>[05:31] up. We're not going to get uh we have<br>[05:32] diminishing returns here, you know." So,<br>[05:34] maybe after two or three, that's the<br>[05:36] right time to start flagging that uh all<br>[05:39] right, we're a little bit too much. And<br>[05:40] but also because this is visible, the<br>[05:42] people will be able to see themselves.<br>[05:44] I'm not going to dive deeper into this<br>[05:46] screen because I'm going to do a proper<br>[05:47] video to show you everything that is uh<br>[05:49] around this area and what has been<br>[05:51] upgraded with this uh rebuild. But the<br>[05:54] point of this video was the Figma<br>[05:56] plug-in. So uh this is version one.<br>[05:58] Please give us feedback. Uh we already<br>[06:00] have some ideas for version two. This<br>[06:02] was the highest requested integrations<br>[06:04] that we've had since we started the<br>[06:06] Adarim and I'm very excited to see that<br>[06:08] it's here and it's working beautifully.<br>[06:11] So, please go ahead uh install it on<br>[06:13] your Figma instances and uh share the<br>[06:15] feedback with us. I'm looking forward to<br>[06:17] your thoughts and see you on the next<br>[06:18] one. <!-- deep-read:sections end -->