<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ruben Cespedes on Medium]]></title>
        <description><![CDATA[Stories by Ruben Cespedes on Medium]]></description>
        <link>https://medium.com/@rubencespedes?source=rss-6368b49c65ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ks75xtR3O8ss3wTY0a2_UQ.jpeg</url>
            <title>Stories by Ruben Cespedes on Medium</title>
            <link>https://medium.com/@rubencespedes?source=rss-6368b49c65ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:34:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rubencespedes/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Unlimited AI was never real]]></title>
            <link>https://rubencespedes.medium.com/unlimited-ai-was-never-real-85c4fa3409dd?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c4fa3409dd</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[anthropic-claude]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 13:45:57 GMT</pubDate>
            <atom:updated>2026-09-28T13:45:57.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPkGjKI00CdxUVz-3gJBtg.jpeg" /><figcaption>Unlimited AI was never real</figcaption></figure><p>Last week I was three hours into a design project, finally getting the AI to give me something I actually liked, and then: <strong>limit reached, come back later.</strong></p><p>Right in the middle of a good idea, of course.</p><p>My first reaction was to feel ripped off. Then I remembered every client contract I’ve written with “unlimited revisions” in it. We all know what that means. Unlimited until somebody takes it too far.</p><p>AI plans work pretty much the same way.</p><p>Claude Pro, for example, has a limit that resets every five hours, plus a weekly cap on top of that. There’s no set number of messages, either. It depends on how long your messages are, what you attach, and which model you’re using, so two people on the same plan can hit the wall at totally different times.</p><p>These limits weren’t random. Back in 2025, Anthropic added weekly caps after finding people running Claude Code in the background around the clock. One person burned through tens of thousands of dollars of usage on a $200 plan. Honestly, kind of impressive. But you can see why that didn’t last.</p><p>Everyone’s doing it now. GitHub switched Copilot to credits this June, based on how much you actually use. ChatGPT gives you unlimited text chat, but with fine print about “abuse guardrails,” and images (hi, designers) still have limits.</p><p>It makes sense when you think about it. Every answer costs somebody real money in computing power. A flat monthly price only works if most people use less than they pay for. Most do. The rest of us hit the wall.</p><p>So I’ve stopped taking <strong>“unlimited”</strong> personally. I check my usage page before starting anything big, I don’t throw the most powerful model at every little task, and I read the fine print the way I’d read a brief.</p><p>The limit was always there. I just didn’t know where it was.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c4fa3409dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The AI subscription era might already be over]]></title>
            <link>https://rubencespedes.medium.com/the-ai-subscription-era-might-already-be-over-badc9d517e3c?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/badc9d517e3c</guid>
            <category><![CDATA[wwdc-2026]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[ai-siri]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 13:59:39 GMT</pubDate>
            <atom:updated>2026-06-09T13:59:39.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The AI subscription era might already be over" src="https://cdn-images-1.medium.com/max/1024/1*bP5ps4vhps2o9N60TFRAqg.jpeg" /></figure><p>Apple just made AI a default utility, and that changes everything.</p><p>With Siri AI announced at <a href="https://www.apple.com/apple-events/">WWDC 2026</a>, Apple didn’t just upgrade an assistant. They integrated intelligence directly into the OS, across every app, every device, on-device, private by default. No subscription. No app to download. No learning curve.</p><p>For most people? That’s enough.</p><p>And “enough, already on the device you own” is the most dangerous product move in tech right now.</p><figure><img alt="Apple Intelligence in more apps" src="https://cdn-images-1.medium.com/max/1024/1*rJ6RS3hX1M-45WgIiK8f0A.png" /></figure><p>As a product designer, I’ve watched companies race on model benchmarks for years. But the real competition was never about who has the smartest AI, it was about who gets there first at the <em>default</em> layer. Apple just won that race for the average consumer.</p><p>Google is next with local Gemini. After that, the list gets thin fast.</p><p>OpenAI and Anthropic are brilliant products built for power user, developers, designers, knowledge workers. But that was never going to be the mass market. The mass market doesn’t want to think about which AI to use. They want their phone to just <em>get it</em>.</p><p>The companies that should be worried aren’t the ones with worse models. They’re the ones whose entire growth strategy depended on regular people adopting standalone AI apps. That market is shrinking fast.</p><p>The next design challenge isn’t building a better chatbot. It’s figuring out what value you offer <em>above</em> the OS layer, because the baseline just got raised for everyone.</p><p><strong>Do you think standalone AI apps can survive in a world where the OS does it for free? Drop your thoughts below.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=badc9d517e3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built a Gym for Your Design Eye. Today It Opens Its Doors.]]></title>
            <link>https://rubencespedes.medium.com/i-built-a-gym-for-your-design-eye-today-it-opens-its-doors-b008a84a0497?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/b008a84a0497</guid>
            <category><![CDATA[design-education]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 13:00:35 GMT</pubDate>
            <atom:updated>2026-04-06T13:00:35.311Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="SpotTheUI | A/B Design Challenges" src="https://cdn-images-1.medium.com/max/1024/1*mVXIJMP0m3u4m8Uav_D5bw.jpeg" /></figure><p>Two years ago, I was reviewing a junior designer’s work and I said something that stuck with me: “The spacing feels off.” They looked at me and asked, “How do you know?” I didn’t have a good answer. I just… knew. And that bothered me.</p><p>Because if I couldn’t explain it, I couldn’t teach it. And if I couldn’t teach it, then design intuition was just something you either had or you didn’t. I refused to believe that.</p><p>So I started studying how designers actually develop their eye. Not through courses. Not through theory. Through repetition. Through seeing thousands of examples and learning to spot the difference between “good enough” and “great.” The same way a musician trains their ear or an athlete trains their reflexes.</p><p>That insight became an obsession. And that obsession became SpotTheUI.</p><p><strong>Today, SpotTheUI is officially live.</strong></p><p>SpotTheUI is a design training platform built around one simple mechanic: A/B challenges. You see two versions of a real UI element. One is stronger. You pick which one and learn why.</p><p>That’s it. No lengthy video lectures. No 40-hour certification programs. Just you, two designs, and your growing ability to spot what works.</p><p>Here’s what’s inside:</p><p>480 A/B challenges covering 12 core design principles, from visual hierarchy and spacing to typography, color theory, and contrast. Every challenge is categorized into one of 4 difficulty tiers so you can start where you are and progress at your own pace.</p><p><strong>Why I believe this matters.</strong></p><p>The design industry has a gap. We teach people tools (Figma, Sketch, Adobe) and we teach people theory (Gestalt principles, color wheels, grid systems). But we don’t train the thing that actually separates a good designer from a great one: the ability to look at a screen and immediately know what needs to change.</p><p>That skill lives in your eye. And like any skill, it gets sharper with practice.</p><p>I’ve watched designers go through these challenges and have genuine “aha” moments. Not because someone lectured them, but because they saw the difference for themselves. That’s the kind of learning that actually sticks.</p><p><strong>The best part? You can start right now for free.</strong></p><p>60 challenges are completely free. No credit card. No trial period. No “enter your email to unlock” nonsense. Just open it and start training.</p><p>I built it this way because I want you to feel the value before you spend a single dollar. If 60 challenges convince you this is worth your time, the full library of 480 is waiting for you.</p><p><strong>Who is this for?</strong></p><p>Junior designers who want to accelerate their growth. Senior designers who want to stay sharp. Developers who work with design systems and want to understand why certain choices get made. Product managers who review UI work and want a stronger vocabulary for feedback. Students who are learning design and want something more engaging than reading about principles in a textbook.</p><p>Honestly? It’s for anyone who looks at interfaces every day and wants to get better at understanding what makes them work.</p><p><strong>This has been the hardest and most rewarding thing I’ve ever built.</strong></p><p>Every challenge was carefully crafted. Every explanation was written to teach, not just to grade. Every difficulty tier was calibrated through testing and feedback. I didn’t want to build another content library. I wanted to build something that genuinely makes people better at design.</p><p>Today it’s live. Today you can try it.</p><p>Go train your design eye: <a href="https://www.spottheui.com/">https://www.spottheui.com/</a></p><p>And if you know a designer who’s trying to level up, send this their way. It might be exactly what they need.</p><p>Thank you for being here. This is just the beginning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b008a84a0497" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Is Helping Product Designers, But Let’s Stop Pretending the Workflow Is Smooth]]></title>
            <link>https://rubencespedes.medium.com/ai-is-helping-product-designers-but-lets-stop-pretending-the-workflow-is-smooth-22a2904f1796?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/22a2904f1796</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 16:35:31 GMT</pubDate>
            <atom:updated>2026-03-19T16:35:31.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="AI made this worse. A designer seating on a desk frustrated." src="https://cdn-images-1.medium.com/max/1024/1*d4mz8_EK9NO3RPOzNUeE-Q.jpeg" /></figure><p>I’ve been testing more AI tools in my product design workflow, and my experience has been mixed. I see the value right away. AI helps me move faster, explore ideas quicker, and get a starting point without staring at a blank screen. But I also keep running into the same issue. Simple things <strong>still break</strong>.</p><p>I tested <strong>Figma Make</strong> to code a design with the design system attached. I gave it a strong prompt, clear direction, and the context it needed. I expected the output to be close enough to build from, but it wasn’t. The result was broken.</p><p>I’ve seen similar issues even when using setups like <strong>Claude</strong> with MCP connected to a design system. You would think that giving AI access to the right components, patterns, and rules would lead to more reliable output. Not yet. The output still drifts. Spacing is off, components get used the wrong way, styles do not match, and the code looks okay until you inspect it and realize it starts falling apart fast.</p><p>That’s the part I think more designers need to say out loud. AI is helping, but it is also creating cleanup work. Sometimes you save time at the beginning, then lose it fixing things that should have been right from the start.</p><p><strong>I’m still optimistic</strong>. I do believe this gets better. The tools will improve, the integrations will improve, and design system understanding will improve. But right now, we are still in the stage where AI looks impressive while the workflow is not as smooth as people make it sound.</p><p>That’s my reality check. AI is useful. AI is promising. But for product designers, it still needs a lot of supervision. And I think that’s okay. We are early. The value is there, but so is the friction. The best thing we can do right now is stay honest about both.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22a2904f1796" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This changes how we design. And most people are not ready for it.]]></title>
            <link>https://rubencespedes.medium.com/this-changes-how-we-design-and-most-people-are-not-ready-for-it-973f4997d0f7?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/973f4997d0f7</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Wed, 18 Feb 2026 15:05:56 GMT</pubDate>
            <atom:updated>2026-02-18T15:05:56.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Introducing Claude Code to Figma" src="https://cdn-images-1.medium.com/max/1024/1*98hDcH9grMgMAmHLS63TrQ.jpeg" /><figcaption>Image source: Figma, “Introducing Claude Code to Figma,” Figma Blog</figcaption></figure><p><a href="https://medium.com/u/bf1152b11387">Figma</a> just introduced Claude Code to Figma. In simple terms, you can take UI generated in Claude Code and paste it straight into Figma as fully editable layers and frames. Not screenshots. Not flat images. Real, structured design files you can iterate on.</p><p>Let that sink in.</p><p>For years, our workflow has looked like this. Design in Figma. Hand off to engineering. Review builds. Go back and forth. Now we have a new entry point. UI can start in code and land back in the canvas for refinement.</p><p>As a designer, this makes me think hard about where decisions happen.</p><p><strong>Does this mean we design differently?</strong> Yes.</p><p>Not because AI replaces design. It does not. But because we can now react to something closer to production much earlier. Instead of designing abstract wireframes, we might critique generated real layouts. Instead of waiting for engineering to build a version, we can pull structured UI into Figma and shape it ourselves.</p><p>This shifts speed and ownership.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FriFFyTRljic%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DriFFyTRljic&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FriFFyTRljic%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/71f07f1d7f7ac42dd2bc1b22a4e4aaac/href">https://medium.com/media/71f07f1d7f7ac42dd2bc1b22a4e4aaac/href</a></iframe><p>I see three big impacts:</p><p><strong>First</strong>, faster iteration. You can generate a flow, drop it into Figma, and start improving hierarchy, spacing, accessibility, and alignment immediately.</p><p><strong>Second</strong>, tighter collaboration with engineers. The gap between what is designed and what is built gets smaller. That reduces misalignment and wasted cycles.</p><p><strong>Third</strong>, higher expectations. If UI can be generated fast, your value as a designer moves even more toward systems thinking, clarity, product strategy, and experience quality. Surface level layout work becomes less differentiated.</p><p><strong>Will every team adopt this tomorrow?</strong> No.</p><p>Some teams will experiment. Some will ignore it. But the ones who figure out how to combine code generation with strong design systems will move faster than the rest.</p><p>For me, this is not about replacing Figma. It is about expanding what the canvas can absorb. The canvas is no longer the starting point. It becomes the refinement engine.</p><p>If you are a designer, the question is not whether this will affect you.</p><p>The question is whether you will adapt your workflow before someone else does.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=973f4997d0f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Is Not Entry-Level Anymore (And That’s Not Up for Debate)]]></title>
            <link>https://rubencespedes.medium.com/ux-is-not-entry-level-anymore-and-thats-not-up-for-debate-af439d175dc7?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/af439d175dc7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 16:05:28 GMT</pubDate>
            <atom:updated>2025-12-16T16:05:28.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h2lz6Y2yA-G4ofF91QdZqA.png" /><figcaption>UX Design Industry</figcaption></figure><p>Let’s stop pretending.</p><p>UX is no longer a beginner-friendly role, and telling people otherwise is doing real damage.</p><p>The industry moved on. Most advice didn’t.</p><h3>The “junior UX” path is mostly gone</h3><p>There was a time when teams hired juniors and trained them. That time existed because teams were larger, timelines were looser, and mistakes were cheaper.</p><p>That world doesn’t exist anymore.</p><p>In 2026, teams are lean. Budgets are watched closely. And every hire is expected to contribute fast.</p><p>If you need months of hand-holding to understand UX fundamentals, you’re not a hire. You’re a risk.</p><h3>Entry-level designers aren’t competing with entry-level designers</h3><p>This is the part people avoid saying out loud.</p><p>Aspiring UX designers are now competing with designers who have already shipped products, survived reorgs, and worked under real pressure.</p><p>When hiring managers choose between potential and proof, they pick proof.</p><p>Every time.</p><h3>Tools won’t save you</h3><p>Knowing Figma is not a skill anymore. It’s the baseline.</p><p>UI execution is easy to replace. AI made that painfully obvious.</p><p>What’s rare is judgment.<br>What’s valuable is decision-making.<br>What gets you hired is knowing why something works and what breaks when it doesn’t.</p><p>Most portfolios show none of that.</p><h3>Skipping fundamentals is why most portfolios fail</h3><p>Here’s the uncomfortable truth.</p><p>Many aspiring designers want the UX title without learning UX.</p><p>No real research.<br>No systems thinking.<br>No understanding of accessibility.<br>No awareness of business constraints.</p><p>Just polished screens and borrowed frameworks.</p><p>That’s not UX. And hiring managers see through it instantly.</p><h3>Companies don’t want to “teach UX” anymore</h3><p>Not because they’re cruel. Because they’re under pressure.</p><p>Teams don’t have time to explain basic principles, justify obvious trade-offs, or fix avoidable mistakes.</p><p>If you can’t explain your thinking clearly, you slow the team down.</p><p>And slow teams get cut.</p><h3>This isn’t gatekeeping. It’s a warning.</h3><p>Calling UX “not entry-level” isn’t about ego. It’s about honesty.</p><p>UX today requires maturity.<br>Comfort with ambiguity.<br>And the ability to make decisions that affect real money.</p><p>That’s not beginner work.</p><h3>The part nobody wants to hear</h3><p>If you’re looking for a fast career switch, UX is the wrong place.</p><p>If you’re chasing titles, trends, or shortcuts, you’ll struggle.</p><p>But if you’re willing to study the discipline deeply, practice thinking instead of copying, and accept that this takes time, there is still room.</p><p>Just not for everyone.</p><p>And pretending otherwise helps no one.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="https://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af439d175dc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Bad UX Costs Billions: What the Amazon Settlement Means for Designers]]></title>
            <link>https://rubencespedes.medium.com/when-bad-ux-costs-billions-what-the-amazon-settlement-means-for-designers-8865067fe9c5?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/8865067fe9c5</guid>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[dark-patterns]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[amazon]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 15:17:45 GMT</pubDate>
            <atom:updated>2025-12-15T15:17:45.015Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="When Bad UX Design Cost Billions — Amazon &amp; Dark Patterns | When Bad UX Costs Billions: What the Amazon Settlement Means for Designers" src="https://cdn-images-1.medium.com/max/1024/1*PsX75gwFCDFlTG_5ALU9LA.png" /><figcaption>How design decisions impact the bottom line.</figcaption></figure><p>On <strong>September 25, 2025</strong> the Federal Trade Commission announced a <strong>$2.5 billion settlement with Amazon</strong> over how the company designed the enrollment and cancellation flows for Amazon Prime. The FTC alleged Amazon used what regulators call <strong>dark patterns</strong>, manipulative or deceptive interface designs, to push people into Prime subscriptions and make it hard to cancel. The deal includes a <strong>$1 billion civil penalty and $1.5 billion in refunds</strong> for consumers who were affected.</p><p>This isn’t a small legal case or a PR moment. It’s one of the clearest signals yet that design matters legally, financially, and ethically.</p><p>Here’s what happened and what it means for you as a designer.</p><h3>What the FTC said Amazon did</h3><p>The FTC’s complaint and settlement order focused on two core issues:</p><p><strong>Enrollment design:</strong> The interface made enrolling in Prime easy and obvious, but the terms (like recurring charges and auto-renewal) weren’t clearly disclosed before billing information was collected. The option to decline Prime was subtle or buried behind less noticeable elements.</p><p><strong>Cancellation friction:</strong> Once people were signed up, canceling was complex and confusing. In internal discussions, some Amazon teams reportedly referred to the cancellation flow as “The Iliad” because it forced users through many steps to cancel.</p><p>Part of the settlement requires Amazon to <strong>redesign these flows</strong>, including making it easy to cancel using the same method someone signed up with and providing clearer choices at every step.</p><h3>Why designers should care</h3><p>If you’re mentoring, building UX patterns, or shaping digital products, here are the core lessons from this case:</p><p><strong>1. Dark patterns are not a gray area anymore.</strong> Design tricks that push users into decisions they don’t want or make opting out hard are not just bad ethics. They are now part of legal scrutiny that can cost billions.</p><p><strong>2. Trust matters more than short-term metrics.</strong> It might feel tempting to boost conversions with subtle nudges or hidden defaults. But when users feel misled, trust evaporates. And trust is one of the hardest things to build, and easiest to lose.</p><p><strong>3. Clear choices are simple things, but they matter.</strong> A clear “no thanks” button. Plain language about cost and renewal. Cancellation flows that don’t feel like a maze. These choices respect users and protect your product from backlash.</p><p><strong>4. You might be legally responsible for design choices.</strong> The settlement hints that executives and teams can be named in these cases, and internal design decisions become evidence. How you think about choice architecture isn’t academic, it could be a legal risk.</p><h3>What we should aim for instead</h3><p>Instead of dark patterns, design experiences that:</p><p><strong>Inform users clearly</strong> about what they’re agreeing to before they act.<br><strong>Make opt-out and cancellation as easy as sign-up.<br>Test for user understanding</strong>, not just metrics. If users say “I didn’t know that,” that’s a red flag.</p><p>Good design shouldn’t trick people. It should help them make choices they understand and feel good about.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8865067fe9c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If Your Designs Look ‘Off,’ It’s Probably One of These Beginner UX Mistakes]]></title>
            <link>https://rubencespedes.medium.com/if-your-designs-look-off-it-s-probably-one-of-these-beginner-ux-mistakes-c6031aca2cf0?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6031aca2cf0</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Tue, 25 Nov 2025 15:10:45 GMT</pubDate>
            <atom:updated>2025-11-25T15:10:45.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="If Your Designs Look ‘Off,’ It’s Probably One of These Beginner UX Mistakes" src="https://cdn-images-1.medium.com/max/1024/1*huHKW4YqlFLQxQH1Lfgqhg.jpeg" /></figure><p>You can learn every tool, follow every YouTube tutorial, and copy as many Dribbble shots as you want… but if the fundamentals aren’t there, your work will still feel “off.” I see this all the time when I mentor new designers. The ideas are good. The effort is there. But a few small mistakes add up and make the design look confusing, unpolished, or amateur.</p><p>So instead of giving you a long list of theory, I want to walk you through the mistakes I spot most often and show you exactly how to fix them in a clear, practical way.</p><h3>1. Inconsistent Spacing</h3><p>Most beginner screens look messy because the spacing jumps around. <strong><em>Fix:</em></strong> Pick a spacing scale (4 or 8 px works great) and stick to it everywhere, buttons, cards, headings, everything.</p><h3>2. Weak Visual Hierarchy</h3><p>Everything looks the same, so nothing stands out. <strong><em>Fix:</em></strong> Decide what the user should see first. Use size, weight, color, and spacing to guide the eye.</p><h3>3. Random Alignment Choices</h3><p>Elements float without structure. <strong><em>Fix:</em></strong> Align everything with intention. Use a simple grid. Repeat it from screen to screen.</p><h3>4. Too Many Colors</h3><p>New designers tend to “decorate” instead of communicate. <strong><em>Fix:</em></strong> Start with one primary color, one accent, and neutrals. Build the UI on that foundation.</p><h3>5. Icons and Text That Don’t Match</h3><p>An icon says one thing, the label says another, and the user gets confused. <strong><em>Fix:</em></strong> Test every icon. If you remove the label, can someone guess what it means? If not, rethink it.</p><h3>6. Poor Contrast and Readability</h3><p>Light gray on slightly darker gray. Tiny fonts. Text that vanishes on mobile. <strong><em>Fix:</em></strong> Follow WCAG contrast rules. And bump up your font sizes; nobody complains about readable text.</p><h3>7. Overusing Effects (shadows, gradients, glassmorphism, animations)</h3><p>Effects become a distraction instead of a design choice. <strong><em>Fix:</em></strong> Add effects with intention. If it doesn’t clarify structure or hierarchy, remove it.</p><h3>8. Ignoring Real Content</h3><p>Designs look great with placeholders… until real text breaks everything. <strong><em>Fix:</em></strong> Use real content early. If you don’t have it, write a rough version yourself.</p><h3>9. Not Testing the Flow</h3><p>A pretty screen means nothing if the user can’t complete the task. <strong><em>Fix:</em></strong> Test with one person. Watch where they hesitate. That’s where you redesign.</p><p>If your work feels “off,” it’s rarely because you lack creativity. It’s usually because a few fundamentals are fighting each other. When you fix these small things, your designs look cleaner, clearer, and more professional almost instantly.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6031aca2cf0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why AI-First Design Feels Different (Coming From Someone Who Never Followed “Mobile-First”)]]></title>
            <link>https://rubencespedes.medium.com/why-ai-first-design-feels-different-coming-from-someone-who-never-followed-mobile-first-c836d7cbeb9f?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/c836d7cbeb9f</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Thu, 20 Nov 2025 14:46:07 GMT</pubDate>
            <atom:updated>2025-11-20T14:46:07.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Why AI-First Design Feels Different (Coming From Someone Who Never Followed “Mobile-First”)" src="https://cdn-images-1.medium.com/max/1024/1*lfiemfx6xGM1VdSp1JC13g.jpeg" /></figure><p>I’ve been designing long enough to remember when “mobile-first” was treated like religion. Every conference talk, every blog post, every kickoff meeting started with the same line: <em>“We have to design for mobile first.”</em></p><p>I never bought into it.</p><p>Not because mobile didn’t matter. It did. But back then, the idea of forcing every problem through a mobile lens felt like a trend, not a principle. I always designed desktop experiences first, then made sure they adapted well to mobile. And it worked. Users got strong, usable products across devices without compromising the complexity their workflows actually needed.</p><p>So when I hear people say we’re entering an “AI-first” era, part of me expects the same hype cycle. But this time feels different.</p><p>AI-first isn’t about screen sizes or responsive layouts. It’s about rethinking how people get things done.</p><p>Here’s why this shift matters more than the old mobile-first mindset:</p><p><strong>1. AI isn’t a smaller screen. It’s a new collaborator.</strong> With mobile, the conversation was about fitting the same information into less space. With AI, the conversation shifts to: <em>What can the system do for the user? What can it anticipate, simplify, or remove entirely?</em> That’s a much bigger design challenge.</p><p><strong>2. It forces us to define the real job sooner.</strong> When you work with AI, you can’t hide behind extra menus or complex flows. The model needs clarity. That makes us confront the core task earlier. And honestly, it makes our designs stronger.</p><p><strong>3. It changes what “good UX” means.</strong> For years, good UX was about clarity, consistency, and reducing friction. Now it also includes trust, transparency, and the relationship between the user and the system. You’re not just shaping an interface. You’re shaping behavior and expectations.</p><p><strong>4. It pushes us to design with context, not containers.</strong> Mobile-first treated screens as isolated endpoints. AI-first forces us to think about inputs, data, signals, patterns, and how the entire ecosystem supports the user. The experience becomes more connected and more adaptive.</p><p><strong>5. It opens the door for workflows that weren’t possible before.</strong> In my work across platforms and AIOps products, I’m seeing something interesting: users aren’t just switching between modes; they’re expecting the system to switch with them. Sometimes they want full control. Sometimes they want automation. Sometimes they need both at once. AI-first gives us room to build that flexibility in a natural way.</p><p>And that’s why I’m taking AI-first more seriously than I ever took mobile-first. Not because it’s trendy, but because it actually changes the foundation of how we design.</p><p>We’re not just rearranging UI. We’re rethinking the relationship between the user and the product.</p><p>If you’re navigating this shift in your own work, I hope this perspective helps you think about AI-first design in a more grounded way.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c836d7cbeb9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2025 Reality Check: Why Every Product Team Needs a Design System]]></title>
            <link>https://www.designsystemscollective.com/the-2025-reality-check-why-every-product-team-needs-a-design-system-f9ab274489d5?source=rss-6368b49c65ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9ab274489d5</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ruben Cespedes]]></dc:creator>
            <pubDate>Tue, 18 Nov 2025 16:35:15 GMT</pubDate>
            <atom:updated>2025-11-18T16:35:15.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The 2025 Reality Check: Why Every Product Team Needs a Design System" src="https://cdn-images-1.medium.com/max/1024/1*lGlrb3PX-E58NexVR_BpHQ.jpeg" /></figure><p>Designing in 2025 feels different. We’re not working on one screen anymore. We’re designing for phones, desktops, dashboards, watches, car displays, voice interactions, and now AI-generated layouts that change based on the user.</p><p>Everything moves fast. Teams move even faster. And if you don’t have a design system, things fall apart.</p><p>Let’s be real. AI didn’t replace designers. It increased the amount of work that comes at us. AI creates options in seconds, which means we have to review, refine, and guide a lot more than before. And all of that requires clear rules. Without a system, the output turns messy pretty quickly.</p><p>A strong design system gives your AI tools something solid to follow. Instead of generating random UI, the AI sticks to your patterns, spacing, colors, and components. You get speed without losing control.</p><p>Another big shift this year is how scattered product experiences have become. A user might start on mobile, jump to a dashboard, get a push notification, talk to a voice assistant, and finish the task on a tablet. If every touchpoint feels different, the whole product feels disconnected. A design system keeps the experience aligned so users don’t feel like they’re switching apps every time they switch devices.</p><p>And most teams are working fully remote or hybrid. People are in different time zones, working at different hours, with different communication styles. A design system removes guesswork. Instead of debating what a button should look like or how far components should be spaced, teams already have an answer. That clarity saves hours of meetings and endless back-and-forth during handoff.</p><p>Designers worry that systems limit creativity, but it’s actually the opposite. When the basics are solved, you don’t waste energy redrawing the same elements. You get more time to explore ideas, push the brand, and solve real problems. The system handles the foundation. You handle the thinking.</p><p>The last point is for your career. Design system experience matters in 2025. It shows that you understand how products scale, how teams work together, and how to keep a design language consistent across platforms. Hiring managers look for that now.</p><p>So here’s the reality: If your team wants to move fast, stay consistent, and actually use AI in a smart way, you need a design system. And if you’re a designer who wants to grow, learning how systems work will take you far.</p><p>Discover more UX and design insights! 🚀 Follow me on Instagram <a href="https://www.instagram.com/uiuxcreative/">@uiuxcreative</a> for tips and fun, or explore deeper at my website <a href="http://rubencespedes.com/">rubencespedes.com</a>. Join the design adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9ab274489d5" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/the-2025-reality-check-why-every-product-team-needs-a-design-system-f9ab274489d5">The 2025 Reality Check: Why Every Product Team Needs a Design System</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>