<?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 Carlota Antón on Medium]]></title>
        <description><![CDATA[Stories by Carlota Antón on Medium]]></description>
        <link>https://medium.com/@carlotaanton?source=rss-f06d8ca8c46b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cMjOyu5YGguB8F6LImQRqA.jpeg</url>
            <title>Stories by Carlota Antón on Medium</title>
            <link>https://medium.com/@carlotaanton?source=rss-f06d8ca8c46b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:38:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carlotaanton/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[Design System Challenges]]></title>
            <link>https://www.designsystemscollective.com/design-system-challenges-5a771d0b5db3?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a771d0b5db3</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Wed, 13 May 2026 04:22:14 GMT</pubDate>
            <atom:updated>2026-05-13T04:22:14.560Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="team working with post-its" src="https://cdn-images-1.medium.com/max/1000/1*9luaEC_sjvC2IKDCoXUIRg.jpeg" /></figure><h4>Who makes a great DS team player?</h4><p>This is the million-dollar question. Companies that lack the will or resources to hire specific profiles to build and maintain their DS are already paying the price, whether they realize it or not. And I can assure you it is expensive. Inconsistency is a tax that the company pays every single day in time, in money, and in team morale.</p><p>Not all profiles are suited to work for a design system. And it is not a matter of will or desire; certain traits make a profile more suitable than others.</p><p>This is like in sports, you might love shot put. You might train for it and be decent with dedication, but if you are built to do something else, it is better to invest in what you can excel at. If your body is built to throw a javelin, leave the shot put to someone else.</p><p>Systems are like that. Not everyone is good at it; that does not make someone better or worse. Like in sports, a javelin thrower is not better than a shot-putter and vice versa. It’s different trades.</p><p>Systems require a special kind of resilience, of attention to detail to the point close to obsession. The discipline to iterate until every piece clicks into place. Of looking at the same thing over and over again until you find a flaw. Patience to delve into the not-so-sexy bureaucratic parts of the design. Ability to iterate and evolve the same component to exhaustion. Watching color so closely, you become an expert on telling shades apart. Thinking about scaling, anticipating needs before they are even built. And this is key to not breaking too much under change. It’s about having a <strong>sixth sense</strong> for what works and what doesn’t. An intuition that operates even before seeing the layout, evaluating it simultaneously from a visual, interactive, accessible, and technical standpoint.</p><p>Working in systems is a lesson in humility. You are building the stage, not performing on it. If your goal is to be the star of every layout, the DS team is not for you. You have to find joy in the success of others using your tools.</p><p>I think all those traits are inherent of any good profile fit to work for the design system at a company. But now let’s take a look at the nitty-gritty of good trades to have as a designer and a developer.</p><h4>The profile of the designer:</h4><p>A good DS designer is not the one doing the prettiest screen, but instead the one who thinks about others.</p><p><strong>Abstraction above execution:</strong> They have to have an analytical mindset. They don’t see a blue button; they see the patterns, how they work holistically together with other elements. They see states, variables, interactions… They understand how it needs to behave for it to be effective, and most importantly, they know when it becomes a barrier for some.</p><p><strong>Systemic generosity:</strong> They need to design, thinking about how the other will use it and read it. Designing for those who will use your components without the benefit of your original context. And designing for clarity and understanding technical constraints to help devs build an aligned and robust version.</p><p><strong>Emotional detachment:</strong> Be willing to delete/modify your favorite work for the greater good of the system.</p><h4>The profile of the developer:</h4><p>A good DS dev is not an executor of tickets; it’s the guardian of the logic. It’s the one saying <em>‘give me some time to research how we can make it look/behave like this’</em>.</p><p><strong>Obsession for scalability and edge cases: </strong>They aren’t satisfied with a ‘visual match’; they demand architectural integrity. They make sure it comes with clean, sustainable code that doesn’t break other things. They ensure that systems behave well under pressure and carry all use cases and possible frictions in mind.</p><p><strong>Extreme visual sensitivity:</strong> They need to be someone understanding why the extra pixel matters, and that details make the difference. They are perfectionists.</p><p><strong>Assertive communication:</strong> Ability to raise when something doesn’t scale or work before kicking anything off, saving hours of labor. Open communication and a mentality to experiment to find alternative solutions.</p><p>And for the effective collaboration between these two pillars of the building of a design system, there needs to be shared curiosity and shared language. Both disciplines are building toward the same vision, yet they must also act as guardians of their respective crafts.</p><p>When a designer overlooks pattern consistency, they introduce friction that leads to developer frustration and systemic debt. Conversely, when a developer ignores edge cases or visual precision, the system fails to scale and the user experience degrades.</p><p>True synergy happens when both profiles can hold each other to the highest standards, fostering a culture of <strong>mutual accountability and blind trust</strong>.</p><p>As always, thank you for reading 💚</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a771d0b5db3" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/design-system-challenges-5a771d0b5db3">Design System Challenges</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>
        <item>
            <title><![CDATA[Radical hope]]></title>
            <link>https://medium.com/@carlotaanton/radical-hope-a1227384f2ed?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1227384f2ed</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Mon, 04 May 2026 16:48:50 GMT</pubDate>
            <atom:updated>2026-05-04T16:48:50.434Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="two thumbs up and a fire in the middle" src="https://cdn-images-1.medium.com/max/1024/1*dYGQKx2yXJQOxBav0AhRIw.png" /></figure><p>In this space of uncertainty that we live in worldwide, politically, economically, personally and at work, I want to shed some light 🕯️</p><p>This article is written through a design lens, as I am a designer myself, but I hope my fellow developers and POs also find some peace in it, as it applies to all of us building products.</p><p>Things are changing fast, at a pace that our reptilian biology is not ready to assimilate. We are forced to work at robotic speed, while detaching ourselves from the pain of seeing our colleagues being laid off in masses.</p><p>Contrary to what most social media posts say, we have no clue what the future holds for each of us. That is the only certainty. In these rapid-changing times… anything could happen.</p><p>The way we interact with information, how we are unlearning to search for things is already leaving a dent in our generation. <a href="https://gloriamark.com/attention-span/">Studies have been showing for a long time already</a>, how our attention span, capacity for concentration and ability to retain information are decreasing. This is just being accelerated by current trends.</p><p>Hold on, I promised I wanted to shed some light 🕯️</p><p>I don’t intend to be negative. But we first need to understand where we stand. A burst of toxic positivity is not going to help. A post about our perfect lives is not going to take away the weight we carry behind the curtains.</p><p>Mental health is <strong>declining</strong>, and we are seeing an <strong>increase in medical leaves due to burnout</strong>. Not to mention the huge numbers of people suffering in silence. <a href="https://www.who.int/news/item/28-05-2019-burn-out-an-occupational-phenomenon-international-classification-of-diseases"><strong>Burnout is real</strong></a><strong>. </strong>Data supports this reality: global studies by <a href="https://futureforum.com/research/future-forum-pulse-winter-2022-2023-snapshot/">Future Forum</a> show that 42% of the workforce is reporting burnout, an all-time high that signals a systemic failure in how we work. <strong>It is the consequence of companies built as delivery factories — rather than value-driven organizations — led by leadership that fails to lead intentionally. </strong>They have prioritized the <em>what</em> and the <em>when</em>, completely forgetting the <em>why </em>and the <em>how</em>. More than ever, knowing why and how we design/build in the first place is crucial. Leaders must lead by example, guarding the peace so their teams can create with as little noise as possible.</p><blockquote>Right now, most are failing dramatically.</blockquote><h4>And here comes the light 🕯️</h4><p>We are designing for others like us. We are bridging technology to all sorts of profiles. Those who know and those who don’t know how to use it, or even struggle to. We bring clarity to chaos. We have always been the guardians of pace; we bring calmness and certainty to our products. We shed light on dark, difficult paths to walk past. And that can’t be replaced. In a world that fragments our attention, a well-designed product isn’t just usable, but a sanctuary of clarity.</p><p>How many apps can a person/company need? Most tools that are now built at unprecedented speed for who knows who (because we also didn’t research well…) will eventually fall. Lean is going to show us in record speed how fast we can fail. The ‘move fast and break things’ era is hitting a wall. <strong>We are learning that if you move fast without a soul, you just break things faster.</strong> Only products built with purpose will survive the noise.</p><p>If the field ever falls, let it find us standing tall, proud of how we protected the human experience. But until then, don’t let the speed hollow out your craft. Keep your mastery, keep your curiosity, and above all, <strong>keep your criteria.</strong> Let’s see what happens, but let’s make sure we are the ones holding the light.</p><p>🔥🔥🔥🔥🔥🔥🔥</p><p>Thank you for reading 💚</p><p>— — — — —</p><p>Resources:</p><ul><li><a href="https://gloriamark.com/attention-span/">https://gloriamark.com/attention-span/</a></li><li>The Shallows: What the Internet Is Doing to Our Brains, Nicholas Carr</li><li><a href="https://www.worktime.com/blog/statistics/employee-burnout-statistics-trends-in-the-workplace#:~:text=Workplace%20burnout%20has%20reached%20a,show%20where%20employee%20burnout%20stands">Employee burnout statistics trends in the workplace</a></li><li><a href="https://www.forbes.com/sites/bryanrobinson/2025/02/08/job-burnout-at-66-in-2025-new-study-shows/">Job burnout at 66 in 2025</a></li><li><a href="https://www.glassdoor.com/blog/burnout-rising-2025/">Burnout rising 2025</a></li><li><a href="https://www.who.int/news/item/28-05-2019-burn-out-an-occupational-phenomenon-international-classification-of-diseases">Burnout an occupational phenomenon international classification of diseases</a></li><li><a href="https://futureforum.com/research/future-forum-pulse-winter-2022-2023-snapshot/">Future forum pulse winter 2022-2023 snapshot</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1227384f2ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design System Challenges]]></title>
            <link>https://www.designsystemscollective.com/design-system-challenges-d39ef075d0e2?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d39ef075d0e2</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Mon, 20 Apr 2026 10:31:11 GMT</pubDate>
            <atom:updated>2026-04-20T10:31:11.561Z</atom:updated>
            <content:encoded><![CDATA[<h4>Strategies for managing system entropy and maintaining a lean component library</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*XEILYxkE5PivoaY3SHm2Xg.jpeg" /></figure><p>A Design System is not a library; it’s a living organism. And like any living thing, if you don’t prune it, it will eventually choke on its own growth.</p><p>I like to compare a DS with a plant. If you managed to germinate the seed and grow the plant, now you need to constantly check on it and cut the things that no longer serve for its growth.</p><p>Like a plant, if you allow a DS to grow unwatched, you will end up with a lot of useless noise that is not helping the system, teams or the organisation. It’s most probably doing the opposite.</p><p>Let’s imagine we already have a system in place, and as a living organism it continues to evolve and grow. There will come a day when the system grows out of hand, and we find ourselves facing a monster. Now we have several components that are redundant and do the same thing; and other components might be dead but we saved them for the “what if we need it later”. The result of that happening is that we have now lost consistency and efficiency on the way.</p><p>Most of the time, we built some components that took a lot of time and logic… it hurts to just delete them. But if I learned something working alongside great DS devs was: If we are not using it ✂︎ let’s delete it. And it has been the best advice I have ever implemented in my workflow.</p><p>The DS needs to be clean, patterns have to be straightforward, designers should not have to doubt whether they need to use tabTable, tabDefault or tabWhatever.</p><blockquote>There is a big chance that if your designers are doubting what to apply where, it will transpire to the user.</blockquote><p>So it will be useful to include some sort of revisions in your flow when managing the DS. Ideally once a month: Go through the file and assess all the components.</p><p>These are the questions you need to have in mind for this assessment:</p><ol><li>Is there a component that you haven’t seen anyone using?</li><li>Are there any components that do the same action?</li></ol><p><strong>If the answer to either is ‘yes’, first check with the team.</strong> Contact the rest of the designers in the org and reseacrh whether a component is used, and where. The <strong>where</strong> is particularly important for the use case 2. Your job if you work on the DS is ensuring patterns make sense and are kept clean. And context is crucial for this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*sEAaTDQDJkQVwbb7tE6-PQ.jpeg" /><figcaption>rose pruning system</figcaption></figure><h4>USE CASE 1: <strong>The “what-if” trap</strong></h4><p><strong>Scenario:</strong> A component is gathering dust.</p><p><strong>The Lie:</strong> <em>“We might need it for that Q4 project.”</em></p><p><strong>The Reality:</strong> If it hasn’t been used in 6 months, it won’t be used.</p><p><strong>Verdict: ✂︎ Delete</strong></p><p>It won’t be used in a year, I promise you. Probably even longer. Delete it and keep the system clean and as concise as the system allows you to.</p><p>I like to also ask where they were used before to learn about past patterns and anticipate needs.</p><h4>USE CASE 2: The duplication whim</h4><p><strong>Scenario:</strong> You find 2 or 3 components that perform the exact/similar action with slight visual variations.</p><p><strong>The Lie:</strong> <em>“We need both ‘TabDefault’ and ‘TabAlternative’ because this specific page needs a different ‘vibe’.”</em></p><p><strong>The Reality:</strong> Inconsistency is the silent killer of user trust. If two components do the same thing, you don’t have a system; you have a collection of stickers.</p><p><strong>Verdict:</strong> <strong>✂︎ Align &amp; Merge</strong></p><p>Our main job here would be understanding if some fall into category 1, where we can just ✂︎ delete them, or if we need to align patterns.</p><p>If several components perform the same or similar action, it is most recommended to come up with a proposal for the team and align if possible. You might also need to check with tech if those components live together for a reason. Maybe they have peculiarities on the technical side, in which case might make sense that they stay alive.</p><p>In most cases, it will be just a duplication due to a visual whim. These ‘whims’ are the most expensive trade-offs in a Design System. They seem harmless at first, but they accumulate as technical debt that both design and tech will have to pay later. Design teams often create these exceptions instinctively, unaware of the hidden costs in efficiency and alignment. Our job will be to make a proposal to align, and…. ✂︎ delete anything that is redundant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*peUuBNZF5UfgLF1eHEk4Fw.jpeg" /></figure><p>So, take a look at your library today. What is actually growing, and what is just taking up space? Don’t be afraid of the scissors. Your system and your team will thank you for it.</p><p>Thank you for reading :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d39ef075d0e2" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/design-system-challenges-d39ef075d0e2">Design System Challenges</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>
        <item>
            <title><![CDATA[Design System Challenges:]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://www.designsystemscollective.com/design-system-challenges-66f02eeed91a?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/1582/1*LFHctrE3TNWM8vrIV_fpjA.png" width="1582"></a></p><p class="medium-feed-snippet">Freedom?</p><p class="medium-feed-link"><a href="https://www.designsystemscollective.com/design-system-challenges-66f02eeed91a?source=rss-f06d8ca8c46b------2">Continue reading on Design Systems Collective »</a></p></div>]]></description>
            <link>https://www.designsystemscollective.com/design-system-challenges-66f02eeed91a?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/66f02eeed91a</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-challenge]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[opinion]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Wed, 05 Feb 2025 09:46:55 GMT</pubDate>
            <atom:updated>2026-03-25T06:16:00.936Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Challenges of Design Systems:]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://www.designsystemscollective.com/challenges-of-design-systems-ed92f2898b1f?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/2000/1*9Woe4mNP8eKkBRKBcD8B9A.png" width="2000"></a></p><p class="medium-feed-snippet">Dedicated teams?</p><p class="medium-feed-link"><a href="https://www.designsystemscollective.com/challenges-of-design-systems-ed92f2898b1f?source=rss-f06d8ca8c46b------2">Continue reading on Design Systems Collective »</a></p></div>]]></description>
            <link>https://www.designsystemscollective.com/challenges-of-design-systems-ed92f2898b1f?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed92f2898b1f</guid>
            <category><![CDATA[design-system-tips]]></category>
            <category><![CDATA[design-system-operations]]></category>
            <category><![CDATA[uxui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Tue, 21 Jan 2025 12:56:47 GMT</pubDate>
            <atom:updated>2026-03-25T13:33:17.280Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Maturity of teams and its impact on Design Systems]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://www.designsystemscollective.com/maturity-of-teams-and-its-impact-on-design-systems-5ae4d738a584?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/1000/1*nl2T5CTujQaJI-_EAkLA8w.jpeg" width="1000"></a></p><p class="medium-feed-snippet">Understand better the level at which your organization operates and how it impacts the design systems.</p><p class="medium-feed-link"><a href="https://www.designsystemscollective.com/maturity-of-teams-and-its-impact-on-design-systems-5ae4d738a584?source=rss-f06d8ca8c46b------2">Continue reading on Design Systems Collective »</a></p></div>]]></description>
            <link>https://www.designsystemscollective.com/maturity-of-teams-and-its-impact-on-design-systems-5ae4d738a584?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ae4d738a584</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[designops]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Thu, 19 Dec 2024 17:25:35 GMT</pubDate>
            <atom:updated>2026-03-25T13:32:46.345Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to enrich the way you give feedback to the user]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/system-feedback-1f5043ffe6f2?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/2600/1*nmGqt8ONZ-6Bl2UXLpD6TA.png" width="4844"></a></p><p class="medium-feed-snippet">There is more than UI to your designs; these extra things will move the scale from having a nice app to a great one.</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/system-feedback-1f5043ffe6f2?source=rss-f06d8ca8c46b------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/system-feedback-1f5043ffe6f2?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f5043ffe6f2</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[in-app-feedback]]></category>
            <category><![CDATA[haptic-feedback]]></category>
            <category><![CDATA[micro-animation]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Tue, 19 Mar 2024 21:38:23 GMT</pubDate>
            <atom:updated>2026-03-25T13:40:40.297Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Naming conventions for flows and screens]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/naming-conventions-for-flows-and-screens-4ddc2e00c458?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/1225/1*k4Vbd2Pdn7wgR_1HQBfeKQ.png" width="1225"></a></p><p class="medium-feed-snippet">One of the most difficult things to understand when designing is navigation and how the screens react to it.</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/naming-conventions-for-flows-and-screens-4ddc2e00c458?source=rss-f06d8ca8c46b------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/naming-conventions-for-flows-and-screens-4ddc2e00c458?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ddc2e00c458</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[navigation]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 01:20:54 GMT</pubDate>
            <atom:updated>2024-02-20T09:27:49.410Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Quick Guide to error handling]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxplanet.org/quick-guide-to-error-handling-40f86e9d1962?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/2600/1*rYMvlRemfYay69CZ4uAxDw.png" width="4095"></a></p><p class="medium-feed-snippet">For mobile apps</p><p class="medium-feed-link"><a href="https://uxplanet.org/quick-guide-to-error-handling-40f86e9d1962?source=rss-f06d8ca8c46b------2">Continue reading on UX Planet »</a></p></div>]]></description>
            <link>https://uxplanet.org/quick-guide-to-error-handling-40f86e9d1962?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/40f86e9d1962</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[error-handling]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Tue, 19 Jul 2022 18:38:27 GMT</pubDate>
            <atom:updated>2026-04-18T15:39:51.486Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Ui color palette based on accessibility]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/trustyou-engineering/a-ui-color-palette-based-on-accessibility-c621bad4732c?source=rss-f06d8ca8c46b------2"><img src="https://cdn-images-1.medium.com/max/2347/1*0qncQevSJHB40_xVOegcfA.png" width="2347"></a></p><p class="medium-feed-snippet">TrustYou&#x2019;s new color palette</p><p class="medium-feed-link"><a href="https://medium.com/trustyou-engineering/a-ui-color-palette-based-on-accessibility-c621bad4732c?source=rss-f06d8ca8c46b------2">Continue reading on TrustYou Engineering »</a></p></div>]]></description>
            <link>https://medium.com/trustyou-engineering/a-ui-color-palette-based-on-accessibility-c621bad4732c?source=rss-f06d8ca8c46b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c621bad4732c</guid>
            <category><![CDATA[colors]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Carlota Antón]]></dc:creator>
            <pubDate>Sun, 23 Jan 2022 22:50:28 GMT</pubDate>
            <atom:updated>2022-01-27T08:54:36.521Z</atom:updated>
        </item>
    </channel>
</rss>