<?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: Charlie Wong</title>
    <description>The latest articles on DEV Community by Charlie Wong (@charliewong).</description>
    <link>https://dev.to/charliewong</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%2F4233966%2F93dc4bb6-12ac-47ae-9e66-2b9206ab7fd3.png</url>
      <title>DEV Community: Charlie Wong</title>
      <link>https://dev.to/charliewong</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/charliewong"/>
    <language>en</language>
    <item>
      <title>I built a free pore-clogging ingredient checker that runs 100% in your browser</title>
      <dc:creator>Charlie Wong</dc:creator>
      <pubDate>Sun, 08 Nov 2026 18:31:09 +0000</pubDate>
      <link>https://dev.to/charliewong/i-built-a-free-pore-clogging-ingredient-checker-that-runs-100-in-your-browser-2gmb</link>
      <guid>https://dev.to/charliewong/i-built-a-free-pore-clogging-ingredient-checker-that-runs-100-in-your-browser-2gmb</guid>
      <description>&lt;p&gt;If you have acne-prone skin, you have probably Googled "is [ingredient] comedogenic" more times than you can count. I kept doing that too, so I built a small tool that does it in bulk: &lt;strong&gt;Pore Clogging Checker&lt;/strong&gt; - &lt;a href="https://porecloggingchecker.app" rel="noopener noreferrer"&gt;https://porecloggingchecker.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What it does&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Paste a product's full ingredient list (or upload a photo of the label and let OCR handle it), and the tool flags every ingredient on a 0-5 comedogenic scale. Ratings trace back to published dermatology literature - Fulton's 1989 comedogenicity study and related work - and every flag shows its source, so you can judge the evidence yourself instead of trusting a marketing "non-comedogenic" label.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it's built&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The interesting constraint was privacy: ingredient analysis runs entirely client-side, in the browser. Nothing you paste leaves your machine. The matching layer does exact, alias, and localized-name lookups across 9 languages, with a Levenshtein fallback for OCR noise - because ingredient lists on packaging are rarely typo-free. The whole app deploys as a Cloudflare Worker; there is no traditional server holding your data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why fungal acne is a different beast&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One thing we learned building this: "acne" isn't one problem. Fungal acne (malassezia folliculitis) reacts to a different set of ingredients - esters and fatty acids with certain chain lengths feed it, while classic pore-cloggers may be fine. Our dedicated fungal acne checker handles that separate rule-set, and there is a Korean-language version here: &lt;a href="https://porecloggingchecker.app/ko/tools/fungal-acne-checker" rel="noopener noreferrer"&gt;https://porecloggingchecker.app/ko/tools/fungal-acne-checker&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No signup, no paywall: &lt;a href="https://porecloggingchecker.app" rel="noopener noreferrer"&gt;https://porecloggingchecker.app&lt;/a&gt; - paste an ingredient list and see the flags. If you build skincare-adjacent tools too, I'd love to hear how you handle ingredient data quality; it's a messier dataset than it looks.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>privacy</category>
      <category>indiehacker</category>
    </item>
  </channel>
</rss>
