<?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: Simran Singh</title>
    <description>The latest articles on DEV Community by Simran Singh (@simran_singh_836b353245fb).</description>
    <link>https://dev.to/simran_singh_836b353245fb</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4045090%2Fcd79ecad-58ac-4e03-b8ac-40498f4e57de.jpg</url>
      <title>DEV Community: Simran Singh</title>
      <link>https://dev.to/simran_singh_836b353245fb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/simran_singh_836b353245fb"/>
    <language>en</language>
    <item>
      <title>The Small Emoji Problem in Web Development That Takes More Time Than It Should</title>
      <dc:creator>Simran Singh</dc:creator>
      <pubDate>Mon, 12 Oct 2026 05:49:51 +0000</pubDate>
      <link>https://dev.to/simran_singh_836b353245fb/the-small-emoji-problem-in-web-development-that-takes-more-time-than-it-should-3c7a</link>
      <guid>https://dev.to/simran_singh_836b353245fb/the-small-emoji-problem-in-web-development-that-takes-more-time-than-it-should-3c7a</guid>
      <description>&lt;p&gt;Have you ever needed an emoji for a project, only to spend the next few minutes looking for the right version? Sometimes you just need a PNG for your UI. Other times, you need an SVG, a Unicode value, an HTML entity, or an encoded version. And somehow, finding all of these can mean opening multiple websites just to get one little thing.&lt;/p&gt;

&lt;p&gt;It's not a big problem, but it's the kind of small task that interrupts your workflow, especially when you're already juggling design and development work.&lt;/p&gt;

&lt;p&gt;We wanted to make that a little easier, so here's an emoji resource where you can find everything in one place:&lt;/p&gt;

&lt;p&gt;🔗 &lt;a href="https://radianui.com/resources/emoji" rel="noopener noreferrer"&gt;https://radianui.com/resources/emoji&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can search for emojis, download SVGs and PNGs in different sizes, and copy useful formats like Unicode, Unicode escapes, HTML entities, HTML code, shortcodes, and URI-encoded values. No need to keep switching between websites just to find the format you need.&lt;/p&gt;

&lt;p&gt;Of course, copying an emoji directly works perfectly fine most of the time. But when you need a specific format, having everything together can save you a few extra steps.&lt;/p&gt;

&lt;p&gt;How do you usually handle emojis in your projects? Do you copy them directly, use a library, or search for the formats whenever you need them?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>tools</category>
      <category>productivity</category>
      <category>react</category>
    </item>
    <item>
      <title>Free Country Flags for React Projects</title>
      <dc:creator>Simran Singh</dc:creator>
      <pubDate>Wed, 30 Sep 2026 04:48:06 +0000</pubDate>
      <link>https://dev.to/simran_singh_836b353245fb/free-country-flags-for-react-projects-pm8</link>
      <guid>https://dev.to/simran_singh_836b353245fb/free-country-flags-for-react-projects-pm8</guid>
      <description>&lt;p&gt;If you’re building something with countries, you’ll probably need flags at some point. And then comes the usual process: find a flag set, download a bunch of SVGs, rename files, organize them, and figure out how you want to use them in your app.&lt;/p&gt;

&lt;p&gt;There’s a free country flags library that saves you from doing all that. It includes flags for countries around the world, with SVG, PNG, and React-ready usage so you can drop them into a project without much setup.&lt;/p&gt;

&lt;p&gt;Useful for country selectors, location fields, dashboards, travel apps, international products, or anywhere else you need country flags.&lt;/p&gt;

&lt;p&gt;🔗 &lt;a href="https://radianui.com/resources/flags" rel="noopener noreferrer"&gt;https://radianui.com/resources/flags&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Free resource, no need to spend an afternoon collecting flags one by one.&lt;/p&gt;

</description>
      <category>react</category>
      <category>tools</category>
      <category>design</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Calling a Figma file a "design system" is why frontend devs end up rewriting CSS</title>
      <dc:creator>Simran Singh</dc:creator>
      <pubDate>Wed, 16 Sep 2026 06:46:17 +0000</pubDate>
      <link>https://dev.to/simran_singh_836b353245fb/calling-a-figma-file-a-design-system-is-why-frontend-devs-end-up-rewriting-css-4ij5</link>
      <guid>https://dev.to/simran_singh_836b353245fb/calling-a-figma-file-a-design-system-is-why-frontend-devs-end-up-rewriting-css-4ij5</guid>
      <description>&lt;p&gt;Most team confusion starts when a Figma library gets labeled as a "design system."&lt;/p&gt;

&lt;p&gt;To keep it simple:&lt;/p&gt;

&lt;p&gt;UI Kit: Visual assets and static Figma components.&lt;/p&gt;

&lt;p&gt;Design System: Tokens, production code, strict rules, and maintenance setup.&lt;/p&gt;

&lt;p&gt;If you are handed a UI kit and expected to magically ship a scaled app, you end up writing custom CSS hacks and duplicating component logic just to bridge the gap.&lt;/p&gt;

&lt;p&gt;Here's a quick resource that breaks down the actual technical differences, when to push back, and what devs should expect from a real system:&lt;/p&gt;

&lt;p&gt;(&lt;a href="https://radianui.com/blog/design-system-vs-ui-kit" rel="noopener noreferrer"&gt;https://radianui.com/blog/design-system-vs-ui-kit&lt;/a&gt;)&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>frontend</category>
      <category>design</category>
      <category>css</category>
    </item>
  </channel>
</rss>
