<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>React-Components on No Semicolons</title><link>https://nosemicolons.com/tags/react-components/</link><description>Recent content in React-Components on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 20 Jun 2026 10:27:44 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/react-components/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation UX Disaster: How Generated Frontend Components Break User Experience (And 5 Design Patterns That Actually Work)</title><link>https://nosemicolons.com/posts/ai-code-generation-ux-disaster-frontend-components/</link><pubDate>Sat, 20 Jun 2026 10:27:44 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-ux-disaster-frontend-components/</guid><description>&lt;p>Ever copied an AI-generated React component, dropped it into your app, and immediately thought &amp;ldquo;this feels&amp;hellip; wrong&amp;rdquo;? You&amp;rsquo;re not alone. I&amp;rsquo;ve been there countless times, staring at perfectly valid code that somehow creates the digital equivalent of a door that opens into a wall.&lt;/p>
&lt;p>The rise of AI frontend development has been incredible for productivity, but there&amp;rsquo;s a UX disaster hiding in plain sight. Most AI-generated UI components are technically correct but experientially broken. They follow code patterns without understanding human patterns.&lt;/p></description></item></channel></rss>