<?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: cherry yan</title>
    <description>The latest articles on DEV Community by cherry yan (@cherry_yan_871261020c032a).</description>
    <link>https://dev.to/cherry_yan_871261020c032a</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%2F3736489%2Ff6c1848c-6245-4fbe-9ead-9d09e9927cfd.png</url>
      <title>DEV Community: cherry yan</title>
      <link>https://dev.to/cherry_yan_871261020c032a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cherry_yan_871261020c032a"/>
    <language>en</language>
    <item>
      <title>How I Built an AI Avatar Generator That Outputs Perfect Square Images</title>
      <dc:creator>cherry yan</dc:creator>
      <pubDate>Wed, 28 Jan 2026 04:52:36 +0000</pubDate>
      <link>https://dev.to/cherry_yan_871261020c032a/how-i-built-an-ai-avatar-generator-that-outputs-perfect-square-images-51pi</link>
      <guid>https://dev.to/cherry_yan_871261020c032a/how-i-built-an-ai-avatar-generator-that-outputs-perfect-square-images-51pi</guid>
      <description>&lt;h2&gt;
  
  
  Why I Built a Square Avatar Generator (and What I Learned)
&lt;/h2&gt;

&lt;p&gt;When building side projects or small tools, you often don’t realize how many &lt;em&gt;tiny&lt;/em&gt; problems add friction—until they stack up.&lt;/p&gt;

&lt;p&gt;One issue I kept running into was avatars.&lt;/p&gt;

&lt;p&gt;Most platforms (GitHub, social profiles, dashboards, comment systems) expect &lt;strong&gt;square images&lt;/strong&gt;.&lt;br&gt;&lt;br&gt;
But real user photos? Rarely square.&lt;/p&gt;

&lt;p&gt;Cropping manually works… until you have to do it over and over again.&lt;/p&gt;

&lt;p&gt;So I decided to solve it properly.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Real Problem with “Simple Cropping”
&lt;/h2&gt;

&lt;p&gt;At first glance, this feels like a solved problem:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Upload an image&lt;/li&gt;
&lt;li&gt;Crop to 1:1&lt;/li&gt;
&lt;li&gt;Done&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In practice, it breaks down fast:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Faces get cut off&lt;/li&gt;
&lt;li&gt;Important details fall outside the crop&lt;/li&gt;
&lt;li&gt;Automatic center-cropping fails on non-standard poses&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What I actually needed was:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Face-aware positioning&lt;/li&gt;
&lt;li&gt;Consistent square output&lt;/li&gt;
&lt;li&gt;No manual tweaking for every image&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That’s when I decided to experiment with an AI-based approach instead of traditional cropping.&lt;/p&gt;




&lt;h2&gt;
  
  
  From Manual Tools to AI-Based Generation
&lt;/h2&gt;

&lt;p&gt;Rather than just resizing or cropping, I explored using AI to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Detect the subject properly&lt;/li&gt;
&lt;li&gt;Reframe the image into a square&lt;/li&gt;
&lt;li&gt;Preserve facial proportions and composition&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The result is a workflow where you upload a photo and get a &lt;strong&gt;clean, square avatar&lt;/strong&gt; without thinking about margins, alignment, or cut-off edges.&lt;/p&gt;

&lt;p&gt;While working on this, I ended up turning it into a small standalone tool:&lt;br&gt;&lt;br&gt;
&lt;a href="https://squarefacegenerator.space" rel="noopener noreferrer"&gt;SquareFace Generator&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It’s focused on one thing only—turning photos into square avatars that actually look right.&lt;/p&gt;




&lt;h2&gt;
  
  
  What I Learned Building This
&lt;/h2&gt;

&lt;p&gt;A few takeaways from this mini project:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;“Small” UX problems are often under-engineered&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Cropping sounds trivial until quality actually matters.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;AI shines when rules break down&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Once images stop being predictable, heuristics fall apart fast.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Constraint-first tools are underrated&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Doing &lt;em&gt;one thing well&lt;/em&gt; is often better than shipping a toolbox.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;This wasn’t meant to be a startup idea—just a way to remove friction from my own workflow.&lt;br&gt;&lt;br&gt;
But it reminded me how many developer tools start exactly this way: scratching a very specific itch.&lt;/p&gt;

&lt;p&gt;If you’re building side projects, I’d highly recommend paying attention to the small annoyances you repeatedly ignore.&lt;br&gt;&lt;br&gt;
They’re often the best ideas hiding in plain sight.&lt;/p&gt;

&lt;p&gt;Happy building 👋&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>buildinpublic</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>I’m building a small tool to help people understand relationship misunderstandings</title>
      <dc:creator>cherry yan</dc:creator>
      <pubDate>Wed, 28 Jan 2026 04:49:30 +0000</pubDate>
      <link>https://dev.to/cherry_yan_871261020c032a/im-building-a-small-tool-to-help-people-understand-relationship-misunderstandings-4kfn</link>
      <guid>https://dev.to/cherry_yan_871261020c032a/im-building-a-small-tool-to-help-people-understand-relationship-misunderstandings-4kfn</guid>
      <description>&lt;p&gt;Hi DEV 👋&lt;/p&gt;

&lt;p&gt;I’m currently building a small side project called &lt;strong&gt;DecodeYou&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The idea came from personal experience.&lt;br&gt;
I’ve been in a long-distance relationship, and even when both people care a lot,&lt;br&gt;
misunderstandings still happen — not because of bad intentions,&lt;br&gt;
but because we interpret situations differently.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
the same action can feel “reasonable” to one person,&lt;br&gt;
and deeply hurtful to the other.&lt;/p&gt;

&lt;p&gt;Instead of giving advice or labeling people,&lt;br&gt;
DecodeYou focuses on helping users:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reflect before reacting
&lt;/li&gt;
&lt;li&gt;notice emotional and communication patterns
&lt;/li&gt;
&lt;li&gt;separate what &lt;em&gt;actually happened&lt;/em&gt; from what we &lt;em&gt;assumed it meant&lt;/em&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Right now the project is very early.&lt;br&gt;
I’ve open-sourced the repo to document the ideas and structure as I build.&lt;/p&gt;

&lt;p&gt;👉 GitHub repo: &lt;a href="https://github.com/cherryyan1987/cherryyan1987" rel="noopener noreferrer"&gt;https://github.com/cherryyan1987/cherryyan1987&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d really appreciate any feedback, thoughts, or even skepticism.&lt;br&gt;
Happy to learn from this community.&lt;/p&gt;

</description>
      <category>psychology</category>
      <category>relationships</category>
      <category>buildinpublic</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I built a global GLP-1 telehealth directory (and why it’s harder than it looks)</title>
      <dc:creator>cherry yan</dc:creator>
      <pubDate>Wed, 28 Jan 2026 04:45:09 +0000</pubDate>
      <link>https://dev.to/cherry_yan_871261020c032a/i-built-a-global-glp-1-telehealth-directory-and-why-its-harder-than-it-looks-5aad</link>
      <guid>https://dev.to/cherry_yan_871261020c032a/i-built-a-global-glp-1-telehealth-directory-and-why-its-harder-than-it-looks-5aad</guid>
      <description>&lt;p&gt;GLP-1 medications (like semaglutide and tirzepatide) have exploded in demand, but finding &lt;strong&gt;legitimate, accessible telehealth providers&lt;/strong&gt; is still surprisingly hard — especially outside the US.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;GLP-1 Patches&lt;/strong&gt;, a global directory of GLP-1 telehealth providers.&lt;/p&gt;

&lt;h3&gt;
  
  
  What problem I was trying to solve
&lt;/h3&gt;

&lt;p&gt;Most existing resources are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;US-only&lt;/li&gt;
&lt;li&gt;SEO farms or affiliate-heavy&lt;/li&gt;
&lt;li&gt;Opaque about pricing, prescriptions, or regions served&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you’re not in the US (or you’re comparing options), the information gap is huge.&lt;/p&gt;

&lt;h3&gt;
  
  
  What the directory includes
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Telehealth providers offering GLP-1 medications&lt;/li&gt;
&lt;li&gt;Regions served (US / international)&lt;/li&gt;
&lt;li&gt;Prescription model (subscription vs one-time)&lt;/li&gt;
&lt;li&gt;Transparency around eligibility and process&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No prescriptions. No medical advice. Just structured, comparable information.&lt;/p&gt;

&lt;h3&gt;
  
  
  The hard parts (that I underestimated)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Regulatory differences&lt;/strong&gt; across countries&lt;/li&gt;
&lt;li&gt;Providers changing terms quietly&lt;/li&gt;
&lt;li&gt;Avoiding becoming an affiliate spam site&lt;/li&gt;
&lt;li&gt;Balancing “useful” vs “compliance-safe” content&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Health + software is a very different beast.&lt;/p&gt;

&lt;h3&gt;
  
  
  Current state
&lt;/h3&gt;

&lt;p&gt;The project is still early, but already useful for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Users comparing GLP-1 access options&lt;/li&gt;
&lt;li&gt;Builders researching the space&lt;/li&gt;
&lt;li&gt;Anyone trying to understand how fragmented this market is&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;👉 Website: &lt;a href="https://glp-1patches.org" rel="noopener noreferrer"&gt;https://glp-1patches.org&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Feedback welcome
&lt;/h3&gt;

&lt;p&gt;If you’re building in healthtech, telemedicine, or regulated markets, I’d love feedback:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What would make this genuinely useful?&lt;/li&gt;
&lt;li&gt;What would you absolutely avoid adding?&lt;/li&gt;
&lt;li&gt;Any red flags you see immediately?&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>startup</category>
      <category>healthtech</category>
      <category>telehealth</category>
      <category>product</category>
    </item>
  </channel>
</rss>
