<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Muhammad Mousa</title>
    <description>The latest articles on DEV Community by Muhammad Mousa (@muhammad_mousa_8429cfcc86).</description>
    <link>https://dev.to/muhammad_mousa_8429cfcc86</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3914622%2F8688794a-9cf7-4ba5-bf80-40936f1628c6.jpg</url>
      <title>DEV Community: Muhammad Mousa</title>
      <link>https://dev.to/muhammad_mousa_8429cfcc86</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muhammad_mousa_8429cfcc86"/>
    <language>en</language>
    <item>
      <title>Beyond Icon Export: Building Reusable Icon Systems Inside Figma</title>
      <dc:creator>Muhammad Mousa</dc:creator>
      <pubDate>Mon, 11 May 2026 19:35:25 +0000</pubDate>
      <link>https://dev.to/muhammad_mousa_8429cfcc86/beyond-icon-export-building-reusable-icon-systems-inside-figma-54f7</link>
      <guid>https://dev.to/muhammad_mousa_8429cfcc86/beyond-icon-export-building-reusable-icon-systems-inside-figma-54f7</guid>
      <description>&lt;p&gt;Over the past few months, I’ve been exploring a different way of thinking about icon workflows between design and development.&lt;/p&gt;

&lt;p&gt;Initially, I thought the main problem was simply exporting icons from Figma.&lt;/p&gt;

&lt;p&gt;But once projects and design systems start scaling, the real friction becomes something else entirely:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;keeping icon naming consistent&lt;/li&gt;
&lt;li&gt;managing reusable libraries across projects&lt;/li&gt;
&lt;li&gt;preserving stable codepoints&lt;/li&gt;
&lt;li&gt;avoiding fragmented handoff workflows&lt;/li&gt;
&lt;li&gt;exporting only what’s actually needed&lt;/li&gt;
&lt;li&gt;keeping outputs developer-friendly&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That realization pushed me to rethink the workflow around a more reusable system-oriented approach instead of a simple export flow.&lt;/p&gt;

&lt;p&gt;So I started evolving IconNova around a few core ideas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reusable SVG library workflows&lt;/li&gt;
&lt;li&gt;structured developer-ready outputs&lt;/li&gt;
&lt;li&gt;cleaner React / Vue / JSX / CSS handoff&lt;/li&gt;
&lt;li&gt;stable icon font generation&lt;/li&gt;
&lt;li&gt;favorites &amp;amp; reusable collections&lt;/li&gt;
&lt;li&gt;categorization and organization at scale&lt;/li&gt;
&lt;li&gt;smoother workflows directly inside Figma&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One thing I found especially interesting:&lt;br&gt;
the workflow slowly started feeling less like “asset export” and more like lightweight design infrastructure living inside Figma itself.&lt;/p&gt;

&lt;p&gt;We recently crossed 1,500+ users, and a lot of the recent improvements came directly from workflow feedback and edge cases shared by designers and frontend teams.&lt;/p&gt;

&lt;p&gt;I’m genuinely curious:&lt;/p&gt;

&lt;p&gt;How are teams here currently managing icon consistency and reusable workflows between design systems and production?&lt;/p&gt;

&lt;p&gt;Are you relying mostly on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;large icon libraries&lt;/li&gt;
&lt;li&gt;custom pipelines&lt;/li&gt;
&lt;li&gt;SVG-only workflows&lt;/li&gt;
&lt;li&gt;icon fonts&lt;/li&gt;
&lt;li&gt;or integrated tooling directly inside Figma?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Would love to hear what’s working well, and where the biggest friction still exists today.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.figma.com/community/plugin/1619361051850350459" rel="noopener noreferrer"&gt;https://www.figma.com/community/plugin/1619361051850350459&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>designsystem</category>
      <category>frontend</category>
      <category>figma</category>
    </item>
    <item>
      <title>Rethinking Icon Workflows from Figma to Production</title>
      <dc:creator>Muhammad Mousa</dc:creator>
      <pubDate>Tue, 05 May 2026 19:39:49 +0000</pubDate>
      <link>https://dev.to/muhammad_mousa_8429cfcc86/rethinking-icon-workflows-from-figma-to-production-1ni2</link>
      <guid>https://dev.to/muhammad_mousa_8429cfcc86/rethinking-icon-workflows-from-figma-to-production-1ni2</guid>
      <description>&lt;h1&gt;
  
  
  Rethinking Icon Workflows from Figma to Production
&lt;/h1&gt;

&lt;p&gt;Lately, I’ve been experimenting with different ways to handle icon workflows from Figma to production, especially when working on design systems.&lt;/p&gt;

&lt;p&gt;One thing I kept running into:&lt;/p&gt;

&lt;p&gt;Most setups either:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;rely on huge icon libraries&lt;/li&gt;
&lt;li&gt;or require multiple disconnected steps
(export → clean → generate fonts → integrate)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After a while, the process starts feeling fragmented.&lt;/p&gt;

&lt;p&gt;So I started exploring a more “all-in-Figma” approach with a plugin called IconNova.&lt;/p&gt;

&lt;p&gt;A few things stood out to me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generating ready-to-use outputs (React, Vue, JSX, Tailwind, fonts) in one flow&lt;/li&gt;
&lt;li&gt;Keeping everything offline (no data leaving Figma)&lt;/li&gt;
&lt;li&gt;Managing selection, favorites, and export without jumping between tools&lt;/li&gt;
&lt;li&gt;Exporting only what’s actually used instead of entire libraries&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The interesting part is that it started feeling closer to a real dev workflow rather than just a design tool.&lt;/p&gt;

&lt;p&gt;I’m curious how others are handling icon handoff today in real projects.&lt;/p&gt;

&lt;p&gt;Do you prefer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;icon libraries (Iconify, Hugeicons, etc.)&lt;/li&gt;
&lt;li&gt;custom pipelines&lt;/li&gt;
&lt;li&gt;or something more integrated inside Figma?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Would love to hear what’s working well, and what still feels painful in your workflow.&lt;/p&gt;

&lt;p&gt;If anyone’s curious, this is what I’ve been experimenting with:&lt;br&gt;
&lt;a href="https://www.figma.com/community/plugin/1619361051850350459" rel="noopener noreferrer"&gt;https://www.figma.com/community/plugin/1619361051850350459&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>designsystem</category>
      <category>handoff</category>
      <category>figma</category>
    </item>
  </channel>
</rss>
