<?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 Ravi Kumar on Medium]]></title>
        <description><![CDATA[Stories by Ravi Kumar on Medium]]></description>
        <link>https://medium.com/@ravirafa?source=rss-c089f0d9c3ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Zv42Swf-1-K88OCa</url>
            <title>Stories by Ravi Kumar on Medium</title>
            <link>https://medium.com/@ravirafa?source=rss-c089f0d9c3ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:21:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ravirafa/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[Zombie UI: Why Every AI-Built Screen Looks the Same]]></title>
            <link>https://medium.com/design-bootcamp/zombie-ui-why-every-ai-built-screen-looks-the-same-8a2cb7d3f916?source=rss-c089f0d9c3ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a2cb7d3f916</guid>
            <category><![CDATA[ai-slop]]></category>
            <category><![CDATA[generative-ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ravi Kumar]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 21:56:30 GMT</pubDate>
            <atom:updated>2026-10-16T18:02:41.055Z</atom:updated>
            <content:encoded><![CDATA[<p>AI slop has reached our product screens. <em>Here is how designers can fix it and build with intent when generative tools do the first draft.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9YZ9zWV340GANE1R0agixw.png" /><figcaption>Zombie UI: Why Every AI-Built Screen Looks the Same</figcaption></figure><p><strong>TLDR</strong></p><p>AI lets us ship a screen in minutes, but it can’t decide what a product should feel like. I call the result zombie UI: interfaces that work, look polished and care about nothing. Here is why it happens, what the evidence says and four ways I fight it, with three prompts you can copy.</p><p>Open ten AI-generated apps and they could share one designer. Same rounded cards. Same gradient hero. Same neutral sans-serif. Same dashboard of identical tiles.</p><p>I call it <strong>zombie UI</strong>, a term I borrow from Katie Dill, head of design at Stripe. You may know its cousin: <strong>AI slop</strong>, low-effort, mass-produced AI output built for volume, not value. In a video, slop is easy to spot. In a product screen it hides behind clean corners, tidy spacing and a confident layout.</p><p><strong>Here is the lens I use:</strong></p><blockquote>Zombie UI is not ugly. It is uncared for.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HU0jN-Gv4wrvGavtQWq-IQ.png" /><figcaption>The Problem</figcaption></figure><h3>Zombies didn’t start with AI</h3><p>The term comes from post-war buildings, when builders copied modernism at speed and left the thinking behind. Our screens are getting the same treatment. A small team can now do what once took a much larger one. When speed arrives without direction, we get the digital version of zombie buildings: competent, functional, instantly forgettable.</p><h3>How to spot a zombie in your product</h3><p><strong>It is the most probable answer, not the right one.</strong> Language models return what has been popular. Dill’s example is a Korean barbecue restaurant whose website looks like it sells software. Ask an AI tool for a landing page for any local business and you can get the same: clean, correct and wrong for the place.</p><p><strong>It looks done before it is good.</strong> One prompt gives you rounded corners, soft shadows and a polished layout. It is the microwave burrito problem: ninety seconds from hungry to lunch, and you forgive a lot because the speed feels so good. Built does not mean done.</p><p><strong>It feels disposable.</strong> When building is fast, work gets treated as throwaway. Nobody asks who maintains it or who owns the quality.</p><h3>The receipts: zombie UI is measurable</h3><p><strong>Generic by default.</strong> In an October 2025 test of AI prototyping tools on a real redesign, the tools missed nuance in spacing, grouping and hierarchy, and without detailed specs they produced a similar generic look.</p><p><strong>Confident but wrong.</strong> A 2026 study of 120 interfaces from five generative UI tools found that the tools wrote convincing rationales that did not match what they built, and outputs converged on the same patterns.</p><p><strong>Invisible to some users.</strong> An accessibility audit found that general-purpose code tools repeatedly produce clickable div elements instead of buttons, with missing keyboard handling. For a screen-reader user, that component does not exist.</p><p><strong>A weak baseline.</strong> A 2026 scan of the top one million home pages found detectable WCAG failures on 95.9% of them. AI can scale that neglect at speed unless we set the standard first.</p><p>The pattern: AI optimizes for how a screen looks, not for who has to use it.</p><h3>Four ways to kill a zombie UI</h3><h3>1. Give it a point of view</h3><p>If you do not define one, the model gives you a generic one. Ask what this product should feel like, and what it should <em>never</em> feel like.</p><p><strong>Try this →</strong> Write a one-page design intent before opening any AI tool and paste it at the start of every session:</p><pre>DESIGN INTENT<br>Product: [name and what it does]<br>Users: [who, and what they care about]<br>Feels like: [3 words]<br>Never feels like: [3 words, e.g. generic SaaS]<br>One signature detail: [what only we would do]</pre><h3>2. Write the rules down</h3><p>A designer in the room used to fill in the blanks. Now building is distributed and agentic, so decisions have to be written down. The object of design is no longer the screen. It is the system.</p><p><strong>Try this →</strong> Give the model your tokens, type scale, spacing rules and component library. Build on accessible primitives such as Radix or React Aria. Set contrast to WCAG 2.2 success criterion 1.4.3: at least 4.5:1 for body text. Adjectives like “clean” produce generic output. Constraints produce <em>yours</em>.</p><p><strong>Then ban the tells.</strong> A blocklist alone invents new ones, so this prompt also forces specifics:</p><pre>ANTI-SLOP RULES<br>Use my DESIGN INTENT. Do not use: gradient hero, ✦ badge,<br>&quot;Elevate / Unlock / Transform&quot; headlines, Seamless / Powerful / Secure<br>cards, fake stars or stats.<br>Every headline must contain a fact only this product could say.<br>Swap the business name: if the line still works, rewrite it.<br>After building, mark any element you chose without a stated reason as [DEFAULT], and do not explain why.</pre><h3>3. Do not mistake done for good</h3><p>When a team can build twenty ideas in a week, quality control moves to after the build, where saying no is hardest. Someone has to be the editor. The best test is simple: use it the way a user would, and check that the same action carries the same label on every screen (Nielsen’s “consistency and standards” heuristic).</p><p><strong>Try this →</strong> Walk the whole flow before you judge any single screen. Run this after every generation:</p><pre><br>-------REVIEW PROMPT------<br><br>Audit this flow against the DESIGN INTENT.<br>List where hierarchy, spacing or grouping<br>fail the main user task.<br>Do not explain your design choices.<br>Show evidence in the UI.</pre><p>Ask for evidence, not explanations. <em>Design Theater</em> shows why: a tool’s rationale is not proof.</p><h3>4. Protect the strange</h3><p>AI can manufacture monotony. It is also the best creative catalyst designers have had.</p><p><strong>Try this →</strong> Reserve time in every project for one hand-crafted moment: an onboarding, an empty state, a signature interaction. Raise the ceiling, not only the floor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-ToDy_hs4uRushN-h0b0g.png" /><figcaption>Fix- Four ways to kill a zombie UI</figcaption></figure><h3>Not every AI screen is a zombie</h3><p>I am not against AI-built interfaces. For a quick prototype or an internal tool, a competent default is often enough. The trouble starts when the default ships as the product. Generation raises the floor. Design sets the ceiling.</p><h3>Give it a pulse</h3><blockquote>AI makes building cheap. It does not make judgment cheap.</blockquote><p>John Ruskin praised Gothic architecture because no two columns were alike. Each detail showed the hand and mind of its maker. Users still want that from our screens.</p><p>We have a choice in this building boom. Ship slop, or make something with a pulse.</p><p><strong>Want to stop AI slop without pasting these rules every time?</strong></p><p>The anti-slop-ui skill applies these rules every time you generate or review a screen. It asks for your design intent, bans the default tells, and returns an evidence-based review. A plain-text version of the prompt is included for other tools.</p><p>→ <a href="https://github.com/ravirafa/ai-native-workflows-product-design/tree/main/skills/anti-slop-ui">View the skill on GitHub</a></p><h3>Sources</h3><ul><li>Katie Dill, talk at the Lenny &amp; Friends Summit (origin of the term “zombie UI”): youtube.com/watch?v=GLvFTMtw4Jk</li><li>Nielsen Norman Group, “Good from Afar, But Far from Good,” October 2025: nngroup.com/articles/ai-prototyping</li><li>“Design Theater,” arXiv 2607.22928: arxiv.org/abs/2607.22928</li><li>Durgesh Pawar, “AI-Generated UI Is Inaccessible by Default,” Master.dev, April 2026: blog.master.dev/ai-generated-ui-is-inaccessible-by-default</li><li>WebAIM, “The WebAIM Million,” 2026: webaim.org/projects/million</li></ul><h3>Thanks for Reading!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a2cb7d3f916" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/zombie-ui-why-every-ai-built-screen-looks-the-same-8a2cb7d3f916">Zombie UI: Why Every AI-Built Screen Looks the Same</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Not Your Finger. It’s the Target.]]></title>
            <link>https://medium.com/design-bootcamp/its-not-your-finger-it-s-the-target-78b18bb7cb02?source=rss-c089f0d9c3ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/78b18bb7cb02</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[touch-target-size]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Ravi Kumar]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 17:59:13 GMT</pubDate>
            <atom:updated>2026-09-14T19:39:36.763Z</atom:updated>
            <content:encoded><![CDATA[<p>What WCAG, Apple, Google, and actual finger-measurement research say about — and why the number most designers quote is a myth</p><blockquote>A guide for product and interaction designers</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3eyC5GCshYhABx7yB6fzA.png" /><figcaption>It’s Not Your Finger. It’s the Target.</figcaption></figure><p>A button gets tapped. The wrong thing happens. The user tries again. This is a fat finger error — and the name already tells you where most teams look for the fix: the finger. This piece argues the fix lives somewhere else entirely.</p><h3>What a target size is</h3><p>Target size is the tappable area that responds to input — not the icon or label the user sees, but the invisible zone underneath it. A 24px icon sitting inside a 48px target has 12 pixels of room on every side that the user will never notice and their finger will always use.</p><p>When that zone is too small, or too close to a neighboring one, the tap lands in the wrong place. That’s the error. The finger didn’t fail. The target did.</p><p>This concept has a different name on every platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oI6944qj4Hdzsprs8xVa4g.png" /><figcaption>One Concept, Five Names</figcaption></figure><p>Apple calls it a hit target. Google calls it a touch target. WCAG calls it target size. Lighthouse called it a tap target (and filed the audit under SEO instead of Accessibility until 2024, when Lighthouse 12 moved it where it belongs). Designers tend to just say clickable area.</p><p>Five names, same problem.</p><h3>How big a finger is</h3><p>When a finger presses glass, the tip doesn’t make contact — the flattened pad does. That pad is wider than most people think.</p><p>MIT Touch Lab measured the average index finger contact patch at 16–20mm wide: roughly 45–57 CSS pixels at standard density. A thumb runs about 25mm, around 71 pixels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQnPUFSuyuGSV4_G66UWbg.png" /><figcaption><em>How Big Is a Finger, Actually</em></figcaption></figure><p>The “44px average finger” claim you see everywhere converts to about 15.5mm. That’s smaller than the low end of a real index finger and barely two-thirds the width of a thumb. The number didn’t come from measuring a finger — more on that below.</p><p>Accuracy also shifts across the screen. Steven Hoober’s research found people tap most precisely near the center. Corners are the worst zone, with the bottom corner needing almost twice the target size of the center. About half of users hold their phone one-handed, so this gradient affects most sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HiblO_rFLbA91t94Fmw-Vg.png" /><figcaption><em>Where Your Thumb Is Least Accurate</em></figcaption></figure><p>On a desktop, corners are the easiest place to click — a cursor can’t overshoot past the edge. On a phone held in one hand, corners are the hardest place to reach. A corner doesn’t justify a smaller target. It demands a bigger one.</p><h3>What the standards require</h3><p>Six sources publish target-size minimums. None of them agree, and the gap between the smallest and largest is more than 3×.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGfKWpVPxn2h4pb82TZn4A.png" /><figcaption><em>Touch Target Standards, Drawn to Scale</em></figcaption></figure><p>That range isn’t a mistake — it reflects context. Tapping a screen while driving is a different problem than tapping one in your hand. Android Auto’s minimum runs about 50% larger than Material’s phone standard for that reason.</p><p>The floor across all of them is higher than “make it bigger” usually implies.</p><h3>Where “44 pixels” comes from</h3><p>The standard explanation: the average finger is 44 pixels wide, so guidelines say 44×44. Clean story. Wrong on almost every count.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YKisfS_wqCIDiUugvqiHaw.png" /><figcaption><em>The Myth Behind “44 Pixels”</em></figcaption></figure><p>44 came from Apple’s original iPhone HIG — a design decision for a 3.5-inch screen held in one hand, not a measurement of anatomy. WCAG’s enhanced guideline (AAA, SC 2.5.5) later adopted the same figure. But the level most teams need to meet is SC 2.5.8, Level AA: <strong>24×24 CSS pixels</strong>, with a spacing exception that lets smaller targets pass when they’re far enough from neighbors. Links inside a sentence or paragraph are also exempt — WCAG recognises that reflowing text makes fixed target sizes impractical there.</p><p>44 is the stretch goal. 24 is the enforceable floor. <em>Apple’s HIG sets that enhanced bar at 44pt. Google Material at 48dp. Same intent, different platforms, different numbers.</em></p><p>And “pixels” is misleading. Apple’s unit is points. Android uses dp. WCAG uses CSS pixels. All three are density-independent — they stay the same physical size no matter how many hardware pixels the screen crams in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5o3lEbZ5Ne36_jjWywdQEw.png" /><figcaption>px · dp · pt — One Idea, Three Names</figcaption></figure><p>This is why “48dp” and “48px” aren’t interchangeable. At baseline density, 1dp equals 1px. At 2× density, the same 48dp target takes 96 hardware pixels. At 4×, 192. The spec never changes. The screen just draws more dots to fill it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iA1RekFuO38g73G7f_DXCw.png" /><figcaption><em>Same Spec. Same Size. Different Pixels.</em></figcaption></figure><p>44, 48, or 24-with-spacing — all reasonable defaults for their platform. The mistake is treating any of them as a fact about human fingers instead of what they are: engineering decisions that happen to be published.</p><h3>Why it’s an accessibility requirement, not just good practice</h3><p>Users with tremors, Parkinson’s, or limited hand mobility can miss a target by 20–30px even when aiming carefully. That’s why WCAG 2.2 made target size a Level AA requirement — enforceable under ADA, Section 508, and the European Accessibility Act. Sizing targets correctly is accessibility work, not just polish.</p><h3>Why taps miss</h3><p>Size gets blamed because it’s visible in a screenshot. It’s rarely the only reason.</p><p><strong>Too small.</strong> Smaller than a fingertip’s contact patch means some taps land outside the target no matter what.</p><p><strong>Too close together.</strong> Two targets can each pass the minimum and still cause errors if they’re packed tight. WCAG tests this with a 24px circle centered on each target — if the circles overlap, the spacing fails.</p><p><strong>Visual and target don’t match.</strong> A small icon inside a big target, or a big icon that only responds in its center — either way, users can’t see the real boundary.</p><p><strong>No affordance.</strong> Desktop has hover to reveal what’s clickable. Touch has nothing. If a control only looks interactive on mouse-over, it’s invisible on a phone.</p><p><strong>No feedback.</strong> No response to a tap means the user doesn’t know it worked, so they tap again — harder, faster, on the wrong thing. Analytics tools call this a rage tap.</p><p><strong>No recovery.</strong> A mis-tap that’s reversible costs nothing. One that deletes data or completes a purchase costs real damage. A delete button sitting in the easiest spot on the screen to reach makes this worse — move destructive actions out of easy reach, or put a confirmation in front of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tBiRVIcJI8epUPBslY_Pkg.png" /><figcaption>Why Targets Get Missed</figcaption></figure><p>Size is the cause you can screenshot. The other five cause just as many failures.</p><h3>Design the target, not the icon</h3><p>The fix isn’t a bigger icon. It’s a bigger target with the same icon inside.</p><p>A 24px icon doesn’t need to grow to meet a 48px minimum. It needs invisible, tappable padding. The design system keeps its small icon. The target underneath does the work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zVX1pV0ATifsR4uYsyrGJQ.png" /></figure><p>Same icon, four results. No padding: fails. Padded and centered: passes. Padded but pinned to one corner: fails (room is on the wrong side). Round target around a round icon: passes. Three variables — size, centering, shape — drive every outcome.</p><pre>.icon-button {<br>  width: 24px;<br>  height: 24px;<br>  position: relative;<br>}<br><br>@media (pointer: coarse) {<br>  .icon-button::after {<br>    content: &quot;&quot;;<br>    position: absolute;<br>    inset: -12px; /* expands target to 48×48 */<br>  }<br>}</pre><p>Padding fixes “too small.” It doesn’t fix “too close.” You need both.</p><p>A <a href="https://github.com/w3c/csswg-drafts/issues/4708">CSSWG proposal</a> for a native pointer-box-offset property has been open since 2020. Until it ships, pseudo-elements are the workaround.</p><h3>Before shipping</h3><p>Save this. Run it before every release.</p><p>One rule overrides all of them: test one-handed on a real device. Figma at 1× and a desktop browser can’t simulate the grip, the angle, or the thumb arc of a phone held in a moving hand.</p><p>Check Below <strong><em>‘target-size review skill’</em></strong> for your coding agent</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbOeLwGmhhOeYeflonRS-g.png" /><figcaption><em>The Target-Size Checklist</em></figcaption></figure><p>“Fat finger” is a phrase that puts the blame on the user. The problem is almost never the finger — it’s the target, the spacing, the feedback, or the recovery path. Get those right and the mis-taps go away.</p><p><strong>Want this checked automatically?</strong></p><p>A target-size review skill runs against code, design files, or written specs — flags undersized, uncentered, or poorly-spaced targets using the same standards cited above.</p><p><strong>→</strong><a href="https://github.com/ravirafa/ai-native-workflows-product-design/tree/main/skills/target-size-review"><strong> View the skill on GitHub</strong></a></p><p><em>If this changes how you spec your next control, share it — it helps other designers find it.</em></p><p><strong>Sources</strong></p><ul><li>W3C — SC 2.5.8 Target Size (Minimum), WCAG 2.2 — <a href="https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html">w3.org</a></li><li>W3C — SC 2.5.5 Target Size (Enhanced), WCAG 2.1 — <a href="https://www.w3.org/WAI/WCAG21/Understanding/target-size.html">w3.org</a></li><li>Smashing Magazine — Finger-Friendly Design, MIT Touch Lab data — <a href="https://www.smashingmagazine.com/2012/02/finger-friendly-design-ideal-mobile-touchscreen-target-sizes/">smashingmagazine.com</a></li><li>Nielsen Norman Group — Touch Targets on Touchscreens — <a href="https://www.nngroup.com/articles/touch-target-size/">nngroup.com</a></li><li>Google — Sizing, Design for Driving, Android Auto — <a href="https://developers.google.com/cars/design/android-auto/design-system/sizing">developers.google.com</a></li><li>W3C CSS Working Group — Issue #4708, pointer-box-offset — <a href="https://github.com/w3c/csswg-drafts/issues/4708">github.com</a></li><li>Steven Hoober — Designing for Touch, 4ourth Mobile — <a href="https://www.4ourthmobile.com/publications/designing-for-touch">4ourthmobile.com</a></li><li>Steven Hoober — Fitts’ Law in the Touch Era, Smashing Magazine — <a href="https://www.smashingmagazine.com/2022/02/fitts-law-touch-era/">smashingmagazine.com</a></li><li>Colin Contreary, Embrace — Rage Taps — <a href="https://embrace.io/blog/rage-taps/">embrace.io</a></li></ul><p><strong><em>Note:</em></strong></p><p><em>These visuals are designed to be saved and pinned into your design system docs.</em></p><p><em>Standards evolve — verify against current WCAG and platform docs before treating any number as final.</em></p><h3>Thanks for Reading!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78b18bb7cb02" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/its-not-your-finger-it-s-the-target-78b18bb7cb02">It’s Not Your Finger. It’s the Target.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Only MCP Servers a Product Designer Actually Needs]]></title>
            <link>https://medium.muz.li/the-only-mcp-servers-a-product-designer-actually-needs-1fab116c0dc0?source=rss-c089f0d9c3ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fab116c0dc0</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ravi Kumar]]></dc:creator>
            <pubDate>Wed, 08 Jul 2026 08:46:40 GMT</pubDate>
            <atom:updated>2026-07-11T11:27:20.051Z</atom:updated>
            <content:encoded><![CDATA[<p>What MCP actually is, and the specific servers that change what your coding agent gives you as a designer — not just as a developer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3BaRS8ADLvXsB2bq9egkQ.png" /><figcaption>The Only MCP Servers a Product Designer Actually Needs</figcaption></figure><p><strong>TLDR:</strong> MCP (Model Context Protocol) is what lets your coding agent connect to your real tools instead of guessing from memory. Most guides tell you to connect everything your team uses; most of that doesn’t actually change what you get as a designer. This article explains what MCP is in plain terms, then walks through the specific servers that make an agent’s design output grounded in your real product instead of a generic guess — what each one does, and exactly how it helps you.</p><h3>What MCP Actually Is</h3><p>MCP stands for Model Context Protocol. Anthropic introduced it in late 2024 as an open standard, and it’s since become the common way most coding agents connect to outside tools — Claude Code, Cursor, VS Code, whatever you’re using. It’s what lets that agent connect to a real tool and pull real information, instead of answering from whatever it happened to learn during training.</p><p>Here’s the difference it makes. Ask an agent to build a settings panel with no MCP servers connected, and it invents a plausible-looking toggle from memory — reasonable-looking, slightly different every time, and built from nothing that actually belongs to your product. Connect the right servers, and the same request triggers Figma MCP’s get_design_context to read the frame&#39;s structure and code, get_screenshot to see how it actually looks, and get_variable_defs to pull your real color and spacing tokens — then it reaches for your actual toggle component from your code library, and checks the current version of the framework you&#39;re building on. The output stops being a guess and starts being specific to you.</p><p>That’s the whole idea. An MCP server is a bridge between the agent and one real source of truth. The question worth asking isn’t “how many can I connect” — it’s which ones actually change what comes out the other end for a designer, specifically, versus which ones just add noise the agent has to sort through.</p><blockquote><em>An MCP server doesn’t make the agent smarter. It makes the agent’s guess unnecessary.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*weyl_1NguCXuqU2UeYH_2A.png" /><figcaption>What Actually Happens When You Connect an MCP Server</figcaption></figure><h3>The Servers That Actually Help a Designer</h3><h3>MarkItDown</h3><p><strong><em>Turns any document into clean Markdown so the agent can actually read it.</em></strong></p><p>Converts a PDF, PPTX, or DOCX into clean Markdown (.md) — structured text the agent can actually work with. Feed it a 40-page research report as a raw PDF, and the agent is working from a garbled dump — tables collapsed, headers merged into paragraphs, key sections easy to miss. Convert it with MarkItDown first, and the structure is preserved, so the agent’s summary is actually built from the right parts of the document. It’s cheaper too: a 25-page PDF runs about 15,000 tokens as raw text, roughly 7,000–8,000 as Markdown — a 30–50% reduction. It doesn’t change what the agent creates; it changes how reliably every other server here can work with what you hand it.</p><p><em>Connect: </em><a href="https://github.com/microsoft/markitdown"><em>github.com/microsoft/markitdown</em></a></p><h3>Notion or Google Drive</h3><p><strong><em>Pulls the actual brief into context — not your summary of it.</em></strong></p><p>Lets the agent open your actual brief instead of you retyping a summary of it. Ask it to design an empty state for checkout, and it fetches the PRD and notices a requirement buried on page four — “must support guest checkout” — that you’d have genuinely forgotten to mention, and designs for it without being asked, because it read the actual document instead of your memory of it.</p><p><em>Connect: </em><a href="https://github.com/makenotion/notion-mcp-server"><em>Notio</em></a><a href="https://github.com/makenotion/notion-mcp-server">n MCP</a> <em>or Google Drive via claude.ai connectors</em></p><h3>Mobbin</h3><p><strong><em>Real screens from real products — not the agent’s training average.</em></strong></p><p>Gives the agent access to real screens and flows from shipped products — over 600,000 of them — instead of letting it fall back on the generic average it learned in training. Ask for a chat widget, and instead of a plain rounded box, the first draft borrows Klarna’s inline-tile pattern — specific enough to react to, reject, or build on, instead of a generic default you’d have to rethink entirely.</p><p><em>Connect: </em><a href="https://mobbin.com/mcp"><em>mobbin.com/mcp</em></a><em> (beta, requires a paid plan)</em></p><figure><a href="https://muz.li/"><img alt="muzli new tab" src="https://cdn-images-1.medium.com/max/1024/1*4OmXLaKwVSCR5qmuLym0jQ.png" /></a></figure><h3>Figma</h3><p><strong><em>Your design system, your components, your canvas — connected in both directions.</em></strong></p><p>The one that matters most, because it covers more ground than any other server here. It gives the agent your real design system — your actual spacing and color tokens, your actual components — so generated work matches what you’ve already built instead of inventing new values. Through <strong>Code Connect</strong>, it links your Figma components directly to their real code equivalents. Without that link, ask for a profile card and the agent writes a brand-new avatar and layout from scratch, with its own sizing and spacing, never quite matching what’s already in the product. With five of your most-used components mapped — Button, Input, Card, Avatar, Badge — it imports the real thing instead, and you feel the difference across every screen it builds afterward.</p><p>It also works in the other direction. The agent can write directly to the Figma canvas — creating and modifying frames, components, variables, and auto layout from your coding tool. And it can capture the live UI of a running app or localhost and send it back to Figma as editable design layers — so what got built doesn’t live only in a browser, it’s on your canvas where you can inspect it, compare it to the original, and spot drift immediately.</p><p>This same connection covers your user flows and whiteboards too, through FigJam — the most common setup, since it rides along for free. If your team’s process diagrams and flows actually live in Miro or Lucid instead, connect whichever one is where the work already is; there’s no reason to run two.</p><p><em>Connect: </em><a href="https://www.figma.com/mcp-catalog/"><em>mcp.figma.com/mcp</em></a></p><h3>shadcn/ui or Storybook</h3><p><strong><em>Accessible component source your agent builds from — not invents from scratch.</em></strong></p><p>Gives the agent real, accessible component code to build from. Ask for a form with dropdowns and date pickers, and the difference is visible in the details — border radius that matches what’s already shipped, focus rings that are exactly the right shade. Every new form element arrives consistent with production instead of close-but-off. If your team runs a custom design system in Storybook rather than shadcn, that’s the equivalent connection — and it goes further, running your system’s own accessibility tests against what the agent generated before you ever see the result.</p><p><em>Connect: </em><a href="https://ui.shadcn.com/docs/mcp"><em>ui.shadcn.com/docs/mcp</em></a><em> or your published </em><a href="https://github.com/storybookjs/mcp"><em>Storybook MCP</em></a><em> route</em></p><h3>Context7</h3><p><strong><em>Current library docs at query time — not two-year-old syntax from training.</em></strong></p><p>Keeps the agent working from the actual, current version of whatever framework your project uses. Ask for a card with a hover animation, and the agent might write a Tailwind class from a version your project no longer has — the effect just silently doesn’t work, and you’d have no idea why. Context7 catches this before it happens, checking the installed version first so what it writes actually runs.</p><p><em>Connect: </em><a href="https://github.com/upstash/context7"><em>mcp.context7.com/mcp</em></a></p><h3>Playwright and Chrome DevTools</h3><p><strong><em>The agent checks its own work in a real browser before you have to.</em></strong></p><p>Let the agent check its own work in an actual browser. The agent builds a modal; ask it to verify with Playwright, and it catches that tabbing skips the close button entirely — a keyboard-accessibility bug caught in the same session it was introduced, not three days later in a bug report. Chrome DevTools does the same job on your real, currently open tab, better for figuring out why one specific thing looks wrong right now.</p><p><em>Connect: </em><a href="https://playwright.dev/docs/getting-started-mcp"><em>github.com/microsoft/playwright-mcp</em></a><em> and </em><a href="https://github.com/ChromeDevTools/chrome-devtools-mcp"><em>developer.chrome.com/docs/devtools/mcp</em></a></p><h3>GitHub</h3><p><strong><em>Ships the code and opens the PR — no separate handoff document.</em></strong></p><p>Where the finished work goes — but also where the agent checks what already exists. It reads the current codebase before generating anything new, so it doesn’t create a component your team already shipped or contradict a pattern that’s already live. Ask the agent to open a pull request for the redesigned empty state, and the description already reads “Implements Figma frame [link], using tokens X, Y, Z” — so the engineer reviewing it doesn’t have to ping you to ask why it looks the way it does.</p><p><em>Connect: </em><a href="https://github.com/github/github-mcp-server"><em>github.com/github/github-mcp-server</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-KzBUBl-puw3WJkQgN6xdQ.png" /><figcaption>Every MCP Server a Designer Needs</figcaption></figure><h3>Using Them Together</h3><p>Put together, this is what it looks like on something bigger than one component: designing a three-step checkout flow, the agent generates each screen from your Figma tokens and shadcn components, checks the current Tailwind syntax with Context7, verifies tab order across all three steps with Playwright, and opens one pull request for the whole flow — work that used to mean five separate handoffs now closes in a single session.</p><p>You don’t need all eight loaded at once — just the two or three the step in front of you calls for, pulled in a sensible order: real context first, generation second, verification before it ships. One practical note: several of these need someone with admin access to switch on — Figma’s org admin, Mobbin’s paid plan, GitHub’s repo permissions. If you can’t connect something yourself, that’s the first conversation to have.</p><blockquote><em>An MCP server doesn’t make the agent smarter. It makes the agent’s guess unnecessary — and that’s the part worth connecting.</em></blockquote><p><strong><em>Start with Figma. Add the rest as the work in front of you actually asks for it.</em></strong></p><p><strong>Sources</strong></p><ul><li>Model Context Protocol — Introduction <a href="https://modelcontextprotocol.io/introduction">modelcontextprotocol.io/introduction</a></li><li>Guide to the Figma MCP Server — Figma Help Center help.figma.com/hc/en-us/articles/32132100833559</li><li>Code Connect — Figma Help Center help.figma.com/hc/en-us/articles/23920389749655</li><li>Mobbin MCP — Mobbin mobbin.com/mcp</li><li>Chrome DevTools MCP — Google developer.chrome.com/docs/devtools/mcp</li><li>Playwright MCP — Microsoft github.com/microsoft/playwright-mcp</li><li>MarkItDown — Microsoft <a href="https://github.com/microsoft/markitdown">github.com/microsoft/markitdown</a></li><li><a href="https://mcpmarket.com/">https://mcpmarket.com/</a></li></ul><h3>Thanks for Reading!</h3><h3>💡 Stay inspired every day with Muzli!</h3><p>Follow us for a daily stream of design, creativity, and innovation.<br><a href="https://www.linkedin.com/company/muzli/"><strong><em>Linkedin</em></strong></a> | <a href="https://www.instagram.com/usemuzli/"><strong><em>Instagram</em></strong></a> | <a href="https://x.com/usemuzli"><strong><em>Twitter</em></strong></a></p><figure><a href="https://muz.li/"><img alt="Stay inspired every day with Muzli!" src="https://cdn-images-1.medium.com/max/1024/1*8L_711tWW8tSuAZXI73-2Q.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fab116c0dc0" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/the-only-mcp-servers-a-product-designer-actually-needs-1fab116c0dc0">The Only MCP Servers a Product Designer Actually Needs</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You’re Not Just a Designer Anymore. You’re an Agent Operator.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.muz.li/youre-not-just-a-designer-anymore-you-re-an-agent-operator-37425a3d4dca?source=rss-c089f0d9c3ae------2"><img src="https://cdn-images-1.medium.com/max/1621/1*tdeIbD480RIx-wUmQJdsWA.png" width="1621"></a></p><p class="medium-feed-snippet">What the OWASP Top 10 for Agentic Applications 2026 means for your workflow, your design system, and the prototypes you ship</p><p class="medium-feed-link"><a href="https://medium.muz.li/youre-not-just-a-designer-anymore-you-re-an-agent-operator-37425a3d4dca?source=rss-c089f0d9c3ae------2">Continue reading on Muzli - Design Inspiration »</a></p></div>]]></description>
            <link>https://medium.muz.li/youre-not-just-a-designer-anymore-you-re-an-agent-operator-37425a3d4dca?source=rss-c089f0d9c3ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/37425a3d4dca</guid>
            <category><![CDATA[agentic-coding]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[aiguardrails]]></category>
            <category><![CDATA[agent-security]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[Ravi Kumar]]></dc:creator>
            <pubDate>Fri, 03 Jul 2026 08:31:00 GMT</pubDate>
            <atom:updated>2026-07-11T11:32:39.749Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Ultimate Accordion Design Playbook]]></title>
            <link>https://medium.muz.li/the-ultimate-accordion-design-playbook-16179b9c8f69?source=rss-c089f0d9c3ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/16179b9c8f69</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[accordion]]></category>
            <dc:creator><![CDATA[Ravi Kumar]]></dc:creator>
            <pubDate>Mon, 16 Sep 2024 07:21:51 GMT</pubDate>
            <atom:updated>2026-07-10T18:45:26.567Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Unlock the Power of Interactive, Flexible, and Stylish Accordion</blockquote><figure><img alt="accordion overview, accordion design, accordion guideline, accordion features" src="https://cdn-images-1.medium.com/max/1024/1*HQkBUPwAR8lV_iHn0e92yw.png" /></figure><p>An accordion is a vertically stacked list of headers that reveal or hide associated sections of content. Accordion components are great for displaying content in a collapsible format, making them ideal for managing large amounts of information in a compact way. They typically consist of a series of expandable sections or panels.</p><h3><strong>Accordion Anatomy</strong></h3><figure><img alt="accordion design, accordion anatomy, accordion structure, accordion states, accordion guideline," src="https://cdn-images-1.medium.com/max/1024/1*DUVEIfZ-yQQfYyUnKPlQsA.png" /></figure><p>The accordion component is composed of several key elements:</p><p><strong>Header:</strong> The Header is the clickable area that users interact with to expand or collapse the accordion. It typically includes a title and may also feature additional elements like icons (e.g., chevron, status indicators, or settings icons) to provide context or functionality. The header ensures proper alignment and spacing of its elements for a clean and organized layout.</p><p><strong>Chevron Icon:</strong> A directional icon located at the end of the header, indicating the current state of the accordion (collapsed or expanded). It points down when collapsed and up when expanded.</p><p><strong>Additional Icon:</strong> An optional icon near the title within the header container, providing further context or functionality (e.g., a user avatar, status indicator, or settings gear).</p><p><strong>Content Panel/Container: </strong>The section that holds the detailed content of the accordion, revealed or hidden when the header is clicked. It ensures proper layout and organization of the content for clarity and readability.</p><p><strong>Divider: </strong>A visual separator between different accordion sections or headers, often a line or space that helps delineate sections and improve readability.</p><p><strong>Badge: </strong>A small visual indicator, typically placed near the header, showing additional information like counts or status. This enhances usability by providing extra data at a glance.</p><p><strong>Box:</strong> The outer container that surrounds the entire accordion component, including the header and content panel. It provides a structural framework and may include styling like borders, shadows, or background colors.</p><p>These elements work in tandem to provide an organized, visually appealing, and interactive user experience, allowing users to manage large amounts of information in a compact and efficient format.</p><h3><strong>Accordion States &amp; Behavior</strong></h3><figure><img alt="accordion design, accordion interactions, accordion states, expand and collapse states, accordion hover, focus" src="https://cdn-images-1.medium.com/max/1024/1*b9LJkBVcWF8iNn8h66xTVA.png" /></figure><p>The accordion component has several key states that define its interaction.</p><h4>Collapsed State</h4><p><strong>Default (Collapsed)</strong></p><p>Appearance and Behavior: The accordion header is visible with no content displayed. It typically features a collapsed icon (e.g., downward-facing arrow or plus sign) and is styled to indicate it can be interacted with.</p><p><strong>Hover (Collapsed)</strong></p><p>Appearance and Behavior: When the user hovers over the collapsed header, it visually changes (e.g., background color shift or border highlight) to indicate that it can be expanded.</p><p><strong>Pressed (Collapsed)</strong></p><p>Appearance and Behavior: The header shows a pressed effect (e.g., darker shade or inset shadow) when clicked, indicating that the section is in the process of expanding.</p><p><strong>Focused (Collapsed)</strong></p><p>Appearance and Behavior: The header features a focus ring or outline to indicate keyboard focus, helping users understand that the section can be expanded with a key press.</p><h4>Expanded State</h4><p><strong>Default (Expanded)</strong></p><p>Appearance and Behavior: The header is visible along with the expanded content. The icon (e.g., upward-facing arrow or minus sign) indicates the section is open and the content is fully displayed.</p><p><strong>Hover (Expanded)</strong></p><p>Appearance and Behavior: When hovering over the expanded header, visual feedback is provided (e.g., background color or shadow effect), indicating that the section can be collapsed.</p><p><strong>Pressed (Expanded)</strong></p><p>Appearance and Behavior: The header appears pressed when clicked, showing that the section is in the process of collapsing. The icon transitions to indicate the change.</p><p><strong>Focused (Expanded)</strong></p><p>Appearance and Behavior: The expanded header has a focus ring or outline, similar to the collapsed focus state, helping users navigate via keyboard while keeping the content visible.</p><h4>Disabled Accordion</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v1O5P0xrhrjlAINWs4If9Q.png" /></figure><p>A disabled accordion cannot be interacted with, expanded, or collapsed. It appears visually distinct, often grayed out, and does not respond to clicks or keyboard navigation. Its content and toggle icon are hidden, and it does not receive focus during navigation.</p><h3><strong>Accordion Variations</strong></h3><p>Accordions come in various styles to suit different user needs and content types. Here’s an overview of different accordion designs</p><h4>Text Accordion</h4><figure><img alt="default accordion, basic accordion, standard accordion, Text accordion" src="https://cdn-images-1.medium.com/max/1024/1*gHo20Qrpw1Br7qA49t32LA.png" /></figure><p>A text accordion, also known as a default, basic or standard accordion, features sections with text-based headers that users can click to expand or collapse. Each header is clearly labeled with text, making it easy for users to understand the content of each section. This design helps organize information efficiently and enhances readability by allowing users to view only the sections they are interested in.</p><h4>Icon Accordion</h4><figure><img alt="avatar accordion, image accordion, profile accordion, accordion design, icon accordion, icon" src="https://cdn-images-1.medium.com/max/1024/1*6HfnCn2YXaU1277b51_Xkw.png" /></figure><p>An icon accordion includes icons alongside the text or header of each section. The icons represent the content or function of the section, enhancing visual recognition. The accordion expands or collapses content as needed, with icons helping users quickly identify and navigate between sections. This design improves usability and provides a more engaging and intuitive interface.</p><h4>Image Accordion</h4><figure><img alt="avatar accordion, image accordion, profile accordion, accordion design, logo accordion," src="https://cdn-images-1.medium.com/max/1024/1*Hc3ujf3TXVHZw57Iq-wVJQ.png" /></figure><p>An image accordion features images within the header of each section, visually representing the content or purpose. This design is particularly useful for user profiles, team directories, or messaging apps where visual identification enhances the user experience. By making headers more engaging and easier to identify, it provides a more intuitive way for users to navigate and interact with the content.</p><h3><strong>Accordion Enhancements</strong></h3><h4>Expand Indicator Icon</h4><figure><img alt="accordion design, plus/minus icon, caret icons, chevron icon, arrow icon" src="https://cdn-images-1.medium.com/max/1024/1*aFTs19M6BgZFVEjPZUJIBw.png" /></figure><p>The expand indicator icon in an accordion automatically rotates to show the state of the section — down when collapsed and up when expanded. This icon is crucial for signaling whether content can be revealed or hidden. Common types of icons used include arrows (e.g., chevrons), plus/minus icons, and caret icons, each providing a clear visual cue about the accordion’s current state.</p><h4>Expand Indicator Icon Position</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqOYTmPXpzrUJAu1jHoQhg.png" /></figure><p>The expand indicator icon in an accordion can be positioned in several ways depending on the design and layout. It is often placed to the left of the header, making it immediately visible when the section header is clicked. Alternatively, it may be positioned to the right of the header, providing a clear visual cue after the header text. In some designs, the icon is integrated within the header, aligning with or adjacent to the text for a more compact appearance.</p><h4>Accordion Text Alignments</h4><figure><img alt="Accordion text alignments, Accordion alignments, Accordion text variations, header alignments," src="https://cdn-images-1.medium.com/max/1024/1*uLcKJjOGaE_xtVlyak3uXw.png" /></figure><p>In an accordion, text alignment within the header can vary to meet different design needs. Left-aligned text is placed at the left edge of the header, making it suitable for designs with icons or badges on the right. Center-aligned text is positioned in the middle of the header, ideal for minimalistic designs or short titles. Right-aligned text is aligned to the right edge, which works well for designs featuring icons or badges on the left and for supporting right-to-left language layouts.</p><h4>Accordion with Title</h4><figure><img alt="Accordion text, Accordion title, Accordion theme, Accordion topic, FAQ Accordion, Accordion design" src="https://cdn-images-1.medium.com/max/1024/1*dLTXVmWpGKoUSrKZCLOEtg.png" /></figure><p>A main title for an accordion is the primary heading that defines the overall theme of the content. It helps users quickly understand the purpose of the sections below. Positioned at the top, it’s more prominent than section headers, providing a clear sense of what information or settings are contained in the expandable sections, such as “Frequently Asked Questions” or “User Account Overview.”</p><h4>Accordion with Sub header</h4><figure><img alt="Accordion with Sub header, Accordion with Sub header, Accordion with label" src="https://cdn-images-1.medium.com/max/1024/1*bqx0ohZUKF2qfM6igi8xXQ.png" /></figure><p>A sub-header in an accordion provides additional context or information below the main header. This can help clarify the content of each section or offer more details without overwhelming the main header. If the sub-header text exceeds the width of the accordion, it may truncate and show a tooltip on hover for complete information.</p><h4>Accordion Text Display</h4><figure><img alt="truncated accordion, wrapped text accordion, text configuration, text setting, text display" src="https://cdn-images-1.medium.com/max/1024/1*T-zvzRmGQRdZIkXPtIWh2A.png" /></figure><p>Accordion Text Display focuses on how text is managed and presented within accordion headers. Key techniques include:</p><p>A <strong>truncated accordion</strong> uses ellipses to shorten titles that exceed a set length, maintaining a compact design. Full titles can be revealed through interactions like hovering or expanding.</p><p>In a<strong> wrapped text accordion,</strong> long titles automatically wrap to the next line, adjusting the container’s height to fit the full text. This approach ensures readability and accommodates extended titles while keeping the design responsive.</p><h4>Accordion with Show Number Prefix</h4><figure><img alt="Accordion with Show Number Prefix, bullet accordion, number accordion" src="https://cdn-images-1.medium.com/max/1024/1*BSuG5aSjX28TjQOOlJWLXw.png" /></figure><p>A number accordion uses numbers as prefixes in the headers to organize and sequence sections. Each header starts with a number, such as “1. Introduction,” “2. Features,” and “3. FAQs,” helping users easily navigate and identify the order of sections within the accordion.</p><h4>Accordion Spacing</h4><figure><img alt="accordion padding and margin, accordion spacing, modern accordion, clean accordion" src="https://cdn-images-1.medium.com/max/1024/1*uo9Xex1rex-XzOR5kGsHow.png" /></figure><p>Accordion Spacing involves adjusting the padding and margins within and around accordion components to achieve a clean and modern look. This includes setting section padding to keep content from touching the edges of each section, margins between individual accordion sections to ensure clear separation, and header spacing with adequate top, bottom, left, and right margins to enhance readability and prevent clutter. Proper spacing improves the visual appeal and usability of the accordion, creating a well-organized and balanced layout.</p><h4>Accordion Fluid</h4><figure><img alt="Accordion Fluid, Accordion Fluid class, container fluid, responsive accordion" src="https://cdn-images-1.medium.com/max/1024/1*r8e0rmAavYV_x1PtpsBXCw.png" /></figure><p>Accordion Fluid refers to an accordion design that adapts dynamically to fit its container, allowing it to resize fluidly based on available space. This approach ensures that the accordion maintains a responsive and flexible layout, adjusting both horizontally and vertically to accommodate varying screen sizes or container dimensions. Fluid accordions enhance usability by ensuring that content is always displayed effectively, regardless of changes in the viewing environment.</p><h4>Accordion Sizes</h4><figure><img alt="Accordion Sizes, Accordion type, Accordion Size variations, Accordion small, medium and large" src="https://cdn-images-1.medium.com/max/1024/1*m9f5HaYqkTTgdNgvk_F1QQ.png" /></figure><h4>Accordion with Border</h4><figure><img alt="Accordion with Border, borderless accordion, rounded accordion" src="https://cdn-images-1.medium.com/max/1024/1*HNmS119LxWUpANSx26oPOg.png" /></figure><p>An accordion with a border features sections enclosed by a border around the box. This design provides a clear visual boundary for each section, enhancing organization and focus. The rounded border creates a softer, more modern look, making the accordion visually appealing and easy to distinguish from surrounding elements.</p><h4>Floating Accordion</h4><figure><img alt="borderless accordion,  ghost accordion, bare accordion, floating accordion" src="https://cdn-images-1.medium.com/max/1024/1*8KIBdY4xLOTWgZxEJuJl0Q.png" /></figure><p>A Floating Accordion, also known as “borderless,” “bare,” or “ghost,” removes background and borders, offering a clean, unobtrusive design. This style is ideal for modals or when space is limited, providing a sleek appearance that integrates seamlessly with the surrounding content.</p><h4>Shadow on Accordion Box and Header</h4><figure><img alt="Shadow on Accordion Box and Header, accordion shadow, accordion UI enhancement" src="https://cdn-images-1.medium.com/max/1024/1*17M3u1PWQdBTScdVl0thJA.png" /></figure><p>Shadows enhance an accordion component by adding depth and emphasis. Applying a shadow to the accordion box makes it stand out from the background, creating an elevated effect. A shadow on the accordion header highlights its prominence and improves its visual distinction. These effects help make the accordion more engaging and visually appealing.</p><h4>Accordion Contextual Information</h4><figure><img alt="Badges, Alerts, Status, Metadata, and Progress on accordion, accordion badge and status, accordion advanced feature" src="https://cdn-images-1.medium.com/max/1024/1*bbNvqEx541ogUBsgsl8Etg.png" /></figure><p>Badges, Alerts, Status, Metadata, and Progress each enhance accordions by providing additional contextual information:</p><p><strong>Badges: </strong>Small visual indicators that display counts, notifications, or quick information, such as the number of unread messages or pending tasks. They offer a concise way to convey key details at a glance.</p><p><strong>Alerts:</strong> Visual or textual messages that highlight important notifications, warnings, or errors. Alerts are designed to draw attention to critical information, ensuring users are promptly aware of urgent issues or updates.</p><p><strong>Status: </strong>Indicators that show the current state or condition of each section, such as “In Progress,” “Completed,” or “Pending.” They help users quickly understand the progress or state of various items within the accordion.</p><p><strong>Unread Indicators:</strong> Highlight sections with unread or new content to help users quickly identify updates. Common indicators include badges with counts, background highlights, or small icons, enhancing usability by drawing attention to sections that need review.</p><p><strong>Metadata: </strong>Additional contextual information about each section, such as timestamps, labels, or data points. Metadata provides extra detail that helps users better understand or categorize the content.</p><p><strong>Progress:</strong> Displays progress indicators within each section, allowing users to track task completion or status. Common features include progress bars, progress circles, or status labels like “In Progress” or “Completed,” which help users monitor and manage ongoing tasks more effectively.</p><p><strong>Combination: </strong>Badges, alerts, status, and metadata can be combined in an accordion to provide users with a comprehensive overview of information, improving clarity and interaction.</p><h3><strong>Accordion Interactions</strong></h3><h4>Always Open</h4><figure><img alt="Always Open accordion, accordion interaction" src="https://cdn-images-1.medium.com/max/1024/1*k62mZGu_ykZ8-ZW8yZ5sOQ.png" /></figure><p>In this behavior, multiple sections of the accordion can be expanded at once, allowing users to view several or all sections simultaneously. This provides greater flexibility for users who want to access large amounts of content without closing any sections.</p><h4>Only One Expanded at a Time</h4><figure><img alt="one at a time, accordion interaction" src="https://cdn-images-1.medium.com/max/1024/1*D3qHvA-ZvLHfovKVZMxBog.gif" /></figure><p>In this interaction, only one section of the accordion can be open at a time. When the user expands a new section, the previously open section automatically collapses. This is ideal for keeping content organized and minimizing clutter, particularly when space is limited.</p><h4>By Default, One Open</h4><figure><img alt="By Default One Open, accordion interaction, accordion design" src="https://cdn-images-1.medium.com/max/1024/1*s3dVNBZKnN6hacIXHvR5Eg.png" /></figure><p>When the page loads, one section is expanded by default. This can guide users by highlighting the most important or commonly accessed information first. Other sections remain collapsed until the user manually interacts with them.</p><h4>Auto-Collapse</h4><figure><img alt="accordion animation, accordion interaction, accordion design, auto collapse" src="https://cdn-images-1.medium.com/max/1024/1*tyaQORS-K4RtDTWfstf28g.gif" /></figure><p>With this interaction, expanding one section automatically collapses all other open sections. It is similar to “one at a time” behavior but focuses on minimizing the need for user clicks by closing other sections immediately.</p><h4>Sequential Expansion</h4><figure><img alt="accordion interaction, accordion design, auto collapse, accordion animation" src="https://cdn-images-1.medium.com/max/1024/1*He4v4sNRbWRlcdWaZnIgKg.gif" /></figure><p>Sequential Expansion requires users to complete accordion sections in a specific order, often used in multi-step forms or onboarding processes. This method ensures a logical flow, making sure users address each section sequentially before moving to the next. It is effective in scenarios where each section builds upon the previous one, such as in detailed forms, surveys, or step-by-step tutorials.</p><h4>Accordion Control Button</h4><figure><img alt="Accordion Control Button, accordion interaction, accordion design, expand all button, collapse all button" src="https://cdn-images-1.medium.com/max/1024/1*hDfK3mzJdXbRKFO9Gu597w.gif" /></figure><p>The accordion control buttons include “Expand All” and “Collapse All”. The “Expand All” button, placed above the accordion, expands all sections to reveal all content. Conversely, the “Collapse All” button collapses all sections, hiding the content. Both buttons should be implemented with proper state management to ensure consistent and simultaneous expansion or collapse of all sections.</p><h4>Accordion with Tooltip</h4><figure><img alt="truncated accordion, accordion tooltip, accordion interaction," src="https://cdn-images-1.medium.com/max/1024/1*Kl2DdBQ_Tl3s9lQAXL7C9g.gif" /></figure><p>An accordion tooltip is a feature that provides additional context or information when a user hovers over or interacts with an accordion header or section. Tooltips can enhance the user experience by offering hints or explanations without cluttering the interface.</p><h3>Advanced Features</h3><h4>Nested Accordion</h4><figure><img alt="Accordion nested, accordion design , advanced feature, accordion interaction," src="https://cdn-images-1.medium.com/max/1024/1*c6DxSwfJONBFsPgnsaYVJA.gif" /></figure><p>A nested accordion includes an accordion within another accordion, allowing multiple layers of collapsible sections. This design helps organize complex, hierarchical content by expanding or collapsing top-level sections and revealing additional nested sections as needed.</p><h4>Accordion Reorder</h4><figure><img alt="Accordion Reorder, accordion rearrange, advanced feature, accordion interaction," src="https://cdn-images-1.medium.com/max/1024/1*5sNzUm9pToPjc_kbXl5mmg.gif" /></figure><p>Reordering Accordion allows users to rearrange accordion sections to better suit their needs. Users can drag and drop sections or use navigation buttons to adjust their order, enhancing flexibility and content organization. For example, in a project management dashboard, moving the “Urgent” section to the top helps prioritize critical tasks.</p><h4>Accordion with Actions</h4><figure><img alt="Accordion with Actions button, accordion interaction, accordion button, accordion configuration" src="https://cdn-images-1.medium.com/max/1024/1*fhIqNme-hl-2qz3YjAlWEA.png" /></figure><p><strong>Accordion Actions</strong> refer to the interactive elements that allow users to manipulate and interact with accordion components. Key actions include:</p><p><strong>Icon Button: </strong>Uses graphical icons to represent actions visually, such as a plus sign for “Create,” a pencil for “Update,” or a trash can for “Delete.” Icon buttons are compact and save space while conveying actions through universally recognized symbols.</p><p><strong>Text Button:</strong> Utilizes textual labels like “Create,” “Update,” or “Delete” to clearly indicate the action. Text buttons are straightforward and easily understood, making them suitable for explicit commands.</p><p><strong>Toggle Button:</strong> Provides an on/off switch to enable or disable features or settings within the accordion. It allows users to change the state of a section or its contents clearly.</p><p><strong>Radio Button:</strong> Allows users to select one option from a set of mutually exclusive choices. This is useful for scenarios where only one option can be chosen from several available within the accordion.</p><p><strong>Checkbox:</strong> Used for actions such as accepting terms or confirming selections. It allows users to toggle between checked and unchecked states to indicate agreement or completion.</p><blockquote><strong><em>Conclusion</em></strong></blockquote><p>Accordions are a powerful UI component for organizing and managing large volumes of information in a compact, user-friendly format. By allowing users to expand or collapse content sections as needed, accordions improve usability, reduce visual clutter, and enhance content discoverability. The design flexibility — ranging from simple text-based accordions to those featuring icons, images, and contextual information — ensures they can be adapted to suit various content types and user needs. By incorporating thoughtful design elements such as indicators, tooltips, and control buttons, and supporting various interaction patterns, accordions create an intuitive and engaging experience that helps users quickly find and focus on the information most relevant to them.</p><blockquote><strong><em>Sources:</em></strong></blockquote><p><a href="https://mui.com/material-ui/react-accordion/">https://mui.com/material-ui/react-accordion/</a></p><p><a href="https://www.nngroup.com/articles/accordions-on-desktop/">https://www.nngroup.com/articles/accordions-on-desktop/</a></p><p><a href="https://ant.design/components/collapse#collapse-demo-mix">https://ant.design/components/collapse#collapse-demo-mix</a></p><p><a href="https://rei.github.io/rei-cedar-docs/components/accordion/">https://rei.github.io/rei-cedar-docs/components/accordion/</a></p><p><a href="https://design.talend.com/?path=/docs/navigation-accordion--docsx">https://design.talend.com/?path=/docs/navigation-accordion--docsx</a></p><p><a href="https://blade.razorpay.com/?path=/docs/components-accordion--docs">https://blade.razorpay.com/?path=/docs/components-accordion--docs</a></p><p><a href="https://doc.wikimedia.org/codex/latest/components/demos/accordion.html">https://doc.wikimedia.org/codex/latest/components/demos/accordion.html</a></p><p><a href="https://horizon.servicenow.com/components/now-accordion">Accordion | Horizon Design System</a></p><h3>Thanks for Reading!</h3><figure><a href="https://muz.li/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MHhxzeSZ92yCM3yEhAtU-w.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16179b9c8f69" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/the-ultimate-accordion-design-playbook-16179b9c8f69">The Ultimate Accordion Design Playbook</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uncover the Full Potential of Perfect Tabs Design!]]></title>
            <link>https://medium.com/design-bootcamp/uncover-the-full-potential-of-perfect-tabs-af04eb6c9d99?source=rss-c089f0d9c3ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/af04eb6c9d99</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Ravi Kumar]]></dc:creator>
            <pubDate>Sat, 31 Aug 2024 20:50:37 GMT</pubDate>
            <atom:updated>2026-07-10T18:46:08.119Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Explore Advanced Features and Maximize Your Tabs Experience</blockquote><figure><img alt="Tabs design, tabs ux, tabs ui design, tabs bar, tab navigation" src="https://cdn-images-1.medium.com/max/1024/1*Q9A0w0cIaMs331uzJaMv3A.png" /></figure><p>Tabs are a powerful tool for organizing and navigating related content at the same hierarchical level. A tab bar, which includes multiple tabs, allows users to switch between different content areas or views effortlessly. This design simplifies navigation by providing quick access to relevant sections, minimizing visual clutter. Tabs are commonly used in web browsers, settings menus, data-driven applications, and SaaS products to group related information, enhancing the user experience with a clean and structured interface.</p><h3>Tabs Anatomy</h3><figure><img alt="Tabs Behavior and States, tabs states, tabs interactions, tabs behaviour, interaction, tabs design" src="https://cdn-images-1.medium.com/max/1024/1*anYzscU4QSj0xFwmqkq2bQ.png" /></figure><p>Tab Anatomy consists of several key components: The Text Label is the textual identifier on the tab, conveying the name or function of the tab’s content. The Tab Indicator visually highlights the active tab, often with an underline or color change. The Tab Separator distinguishes each tab from the others with a clear visual boundary. The Tab Content Area displays the content associated with the selected tab. An optional Dismiss Button may be present on some tabs to allow users to close or remove them. The Badge is an optional element that can appear on a tab to show notifications, counts, or status indicators. The Overflow Indicator is a visual element, such as an ellipsis or dropdown arrow, that signals the presence of additional tabs not currently visible and provides access to them when clicked.</p><h3>Tabs Behavior and States</h3><figure><img alt="Tabs Behavior and States, tabs stats, tabs interactions, tabs behaviour" src="https://cdn-images-1.medium.com/max/1024/1*q0nngrAqZ_8DTzYGIGEfXA.png" /></figure><figure><img alt="Tabs Behavior and States, tabs states, tabs interactions, tabs behaviour, interaction, tabs design" src="https://cdn-images-1.medium.com/max/1024/1*R-3hvFk0PH-0ZqYst8XkeA.gif" /></figure><p>Tabs play a crucial role in enhancing user interaction by defining clear and intuitive behavior patterns. Here’s how tabs typically behave and their associated states:</p><ul><li><strong>Default State:</strong> Inactive tabs appear muted, with their content hidden.</li><li><strong>Active State:</strong> The selected tab is highlighted, and its content is visible.</li><li><strong>Hover State: </strong>Inactive tabs may change color or show a tooltip on hover.</li><li><strong>Pressed State:</strong> Tabs show a visual change, like a color shift or shadow, to indicate they have been clicked.</li><li><strong>Disabled State</strong>: Non-interactive tabs are grayed out or marked as unavailable.</li><li><strong>Focus State</strong>: Focused tabs receive visual feedback for keyboard navigation.</li></ul><h3>Tabs Variations</h3><p>Tabs come in various designs and styles to meet diverse user needs and use cases. Here’s a closer examination of different tab designs and their specific applications:</p><h4>Text Tabs</h4><figure><img alt="base tabs, default tabs, contained tabs, label tabs, standard tabs" src="https://cdn-images-1.medium.com/max/1024/1*oSEI9lSA3w780W7CFoWYBQ.png" /></figure><p>Also known as base, default, contained, or standard tabs, these are designed to handle longer labels without truncation. They help organize related content within a single container, allowing users to easily switch between sections. By showing or hiding content based on user interaction, text tabs streamline the experience and keep the interface clean, ensuring that relevant information is accessible without causing visual clutter.</p><h4>Icon Tabs</h4><figure><img alt="icon tabs, image tabs, avatar tabs" src="https://cdn-images-1.medium.com/max/1024/1*rpaUaGFaCQKcLeo4m4HOsA.png" /></figure><p>Icon only tabs use visual icons without text for a sleek design. Choose clear, recognizable icons, provide visual feedback for active tabs, and ensure icons are consistent and accessible. They help users differentiate between sections by featuring distinct icons.</p><h4>Image Tabs</h4><figure><img alt="image tabs, avatar tabs, logo tabs, tabs design" src="https://cdn-images-1.medium.com/max/1024/1*Uz3p_-DJ9ylpidI81hhsuQ.png" /></figure><p>Image tabs enhance the visual appeal and usability of your interface. They help users quickly identify different sections or categories through images rather than text. Incorporating profile images alongside tab labels makes it easier to identify content or users. These are ideal for scenarios such as user dashboards or messaging app</p><h4>Combination Tabs</h4><figure><img alt="text and icon tabs, combination tabs, icon tabs" src="https://cdn-images-1.medium.com/max/1024/1*sK0qgSbBiXy8cg3J8voxcg.png" /></figure><figure><img alt="text and image tabs, combination tabs, image tabs" src="https://cdn-images-1.medium.com/max/1024/1*I-2ZuqPialUG9Y-57WVNdQ.png" /></figure><p>Combining images or icons with text in tabs enhances user experience by making interfaces more intuitive and engaging. This approach helps users quickly identify and navigate sections or categories. For example, profile tabs with pictures and names allow easy recognition of user profiles, icons with labels simplify finding content categories, and images with descriptions highlight product features. In dashboards, this combination makes it easier to switch between different views or data sets. Integrating visuals with text ensures navigation is both effective and user-friendly.</p><h3>Tab Enhancements</h3><p>Tab enhancements involve tailoring the appearance and behavior of tabs to improve usability, aesthetics, and alignment with user preferences or branding requirements. This process aims to create a more intuitive and visually appealing interface while ensuring that the tabs meet specific user needs and organizational standards.</p><h4>Tab Alignments</h4><figure><img alt="tab alignements,  tab positions," src="https://cdn-images-1.medium.com/max/1024/1*_RDMKrrICWILDKb56nwF_Q.png" /></figure><p>Tabs can be aligned to the start (left), center, or end (right) of the container. By default, tab items are aligned to the start (left). Center-aligned tabs are often used for top-level navigation on editorial websites, providing a balanced appearance. Right-aligned tabs are useful for aligning navigation elements with other content or controls positioned on the right side of the container.</p><h4>Tab Adjustments</h4><figure><img alt="tab adjustments, filled tabs, justified, tabs design, tab Enhancements" src="https://cdn-images-1.medium.com/max/1024/1*WKyC3ERWHzHwGvd6yFh1tg.png" /></figure><figure><img alt="tab adjustments, filled tabs, justified, tabs design, tab Enhancements" src="https://cdn-images-1.medium.com/max/1024/1*N_70NlnJglzuwq7sTWJQuQ.gif" /></figure><p>Tab adjustments offer flexibility in how tab controls are displayed and interact with available space. The fill option ensures that all horizontal space is equally distributed among the tab controls, allowing for a balanced appearance where each tab occupies an equal portion, though widths may vary based on content. On the other hand, the justified option ensures all tabs have equal width, creating a consistent layout where each tab control occupies the available space uniformly. This adjustment is ideal for symmetrical designs where tab labels may differ in length, providing a visually appealing and user-friendly interface.</p><h4>Tab Sizes</h4><figure><img alt="tab sizes, tabs variations, tabs styling, tab scale" src="https://cdn-images-1.medium.com/max/1024/1*cmc4J44Q5W2NDfeZ1009bA.png" /></figure><p>Tabs come in various sizes to meet different design needs and user preferences. Small tabs are compact and ideal for interfaces with limited space or for displaying many tabs without cluttering the view. Medium-sized tabs provide a balanced option, offering good visibility and space efficiency for most applications. Large tabs, with increased height and width, enhance readability and touch targets, making them suitable for interfaces where tab labels are longer or where a more prominent navigation element is needed. Choosing the right tab size affects both usability and aesthetics, balancing space conservation with readability and accessibility.</p><h4>Tab Quiet</h4><figure><img alt="Tab Quiet, tab divider, tab lines" src="https://cdn-images-1.medium.com/max/1024/1*3y-CRz-2qqr_jwO_eFuDNA.png" /></figure><p>By default, tabs include a divider that spans across all items, helping to anchor them to the page. This style is well-suited for top-level navigation at the top of a page. In contrast, quiet tabs do not have a visible divider between tab items, except for the indicator on the selected tab. Quiet tabs are ideal for sub-level navigation or within containers where a more discreet appearance is desired.</p><h4>Tab Fluid</h4><figure><img alt="tab fluid, tab height, tab padding" src="https://cdn-images-1.medium.com/max/1024/1*p2NKvdMAMoG76ZJyYhhpdQ.png" /></figure><p>Tabs can be set to a fluid height, allowing their vertical padding to adjust flexibly to fill the height of the containing element. This setting overrides the density option and is commonly used in headers to ensure that the tabs fit well within the available space.</p><h3>Tab Interactions</h3><p>Tab interactions refer to how users engage with tabs within an interface. This includes actions such as switching between tabs, opening and closing tabs, and responding to user inputs. Enhancing tab interactions aims to make these actions smooth, intuitive, and responsive, thereby improving the overall user experience.</p><h4>Tab Orientations</h4><figure><img alt="Tabs orientations, Vertical tabs, horizontal tabs, tabs design" src="https://cdn-images-1.medium.com/max/1024/1*orpXRj0l4i9J8uithw6N2w.png" /></figure><p>Tabs can be oriented in two main ways: horizontally or vertically. Horizontal tabs are placed across the top of a container or section, which is commonly used for tabbed navigation within a single page or view. This orientation allows users to switch between different sections or categories easily without needing to scroll. In contrast, vertical tabs are aligned along the side of a container or section, making them ideal for saving horizontal space or when the content within each tab requires more vertical room. Vertical tabs are often utilized in sidebars or when there are many tabs to display. The choice between horizontal and vertical tab orientation should be guided by the design requirements and the amount of content each tab needs to accommodate.</p><h4>Tab Positions</h4><figure><img alt="tab positions, vertical tabs, horizontal tabs, botto tabs, top tabs," src="https://cdn-images-1.medium.com/max/1024/1*nBxPcbk7Zw8LiN1AV21amg.gif" /></figure><p>Tabs can be positioned in various ways to enhance usability. The most common placement is at the top of the content area, ideal for standard navigation in websites, applications, and dashboards. Bottom-positioned tabs are often used in mobile apps, making them easy to reach with the thumb, and are great when the top space is reserved for other elements. Left-positioned vertical tabs provide more space for labels, making them suitable for dashboards or applications with numerous sections. Right-positioned vertical tabs, though less common, can balance other page elements and are useful when the main interaction occurs on the left side.</p><h4>Nested Tabs</h4><figure><img alt="Nested tabs, Secondary, Sub tabs, tab in tab, Tab nested view" src="https://cdn-images-1.medium.com/max/1024/1*8Hmi40OvD-zrb3Bx2Vn29A.png" /></figure><figure><img alt="Nested tabs, Secondary, Sub tabs, tab in tab, Tab nested view" src="https://cdn-images-1.medium.com/max/1024/1*6_SwExKiGKCTr5cBlXwHGA.png" /></figure><figure><img alt="Nested tabs, Secondary, Sub tabs, tab in tab, Tab nested view" src="https://cdn-images-1.medium.com/max/1024/1*EG50DGNEGeRbOSOeKD0YDQ.png" /></figure><p>Nested tabs help organize complex content by grouping related sections within a parent tab. This approach is ideal for interfaces with multiple sub-categories. By maintaining clear hierarchy and using scoped tabs, nested tabs keep interfaces uncluttered while allowing users to navigate layered content easily. This enhances user experience by efficiently managing space and simplifying navigation through related options. Nested tabs also known as Secondary and Sub tabs.</p><h4>Tabs Tooltip</h4><figure><img alt="Tabs tooltip, tooltip on tabs, truncation text in tabs, tabs hover" src="https://cdn-images-1.medium.com/max/1024/1*xpf_htfBAVntx3nfmEADPw.gif" /></figure><p>Tooltips provide additional information when hovering over a tab, displaying full labels or brief descriptions. They’re especially helpful for truncated text or icon-only tabs, enhancing usability by offering quick insights without requiring extra clicks.</p><h4>Scrollable Tabs</h4><figure><img alt="Scrollable Tabs, tab Scroll" src="https://cdn-images-1.medium.com/max/1024/1*KOB2xFAzW7QvN2mJ9RiPmg.gif" /></figure><p>When your page has more tabs than can fit or needs to adjust to a new browser size, line and contained tabs should become scrollable. Left and right arrows will appear, allowing users to navigate through off-screen tabs.</p><h4>Overflow Tabs</h4><figure><img alt="Tab overflow, tab dropdown, more option in tabs, extra items, tabs pop over" src="https://cdn-images-1.medium.com/max/1024/1*RjJch_gNgMPhQPbOh-OyVQ.gif" /></figure><figure><img alt="Tab overflow, tab dropdown, more option in tabs, extra items, tabs pop over" src="https://cdn-images-1.medium.com/max/1024/1*aQ_o11uC4yvZt0ZWS7s5Ig.png" /></figure><p>Overflow tabs are a design solution for managing a large number of tabs within a limited space. When there are more tabs than can be displayed at once, some tabs are hidden and accessible through an overflow menu or dropdown. This approach helps maintain a clean and organized interface while allowing users to access all available options. Overflow tabs are particularly useful in scenarios where screen real estate is constrained or when dealing with dynamic content.</p><h4>Dismissible Tabs</h4><figure><img alt="Dismissible Tabs, closable tabs, tab interaction, tab cross icon" src="https://cdn-images-1.medium.com/max/1024/1*ctv74K-ATI_eUy7m4lI4bA.gif" /></figure><p>When dismissible is enabled, a close icon appears on each tab, allowing users to hide it. The remove button can be configured for individual or specific tabs to enable dynamic removal. Dismissible tabs are also known as closable tabs.</p><h4>Rearrangeable Tabs</h4><figure><img alt="Rearrangeable Tabs, tab interactions, tabs drag and drop, reorder tabs" src="https://cdn-images-1.medium.com/max/1024/1*VLnqAksr6lbIKV7cQKPUJA.gif" /></figure><p>Enabling drag-and-drop functionality allows users to reorder tabs by dragging and dropping them according to their preferences. This feature can also be applied to rearrange other elements and can be customized to fit various needs. It offers greater flexibility and personalization, helping users organize their workspace or navigation in a way that best suits their individual requirements.</p><h3>Additional Functions</h3><p>Additional functions in tabs improve navigation by organizing related features, reducing clutter, and allowing easy switching between sections, enhancing workflow and user experience.</p><h4>Tab Badges</h4><figure><img alt="Tab Badges, Tab counter, show value in tabs, count show in tabs" src="https://cdn-images-1.medium.com/max/1024/1*P0lAfex8-OwKcWJm89sv7Q.png" /></figure><p>Add badges to tabs using a Boolean property to control visibility. Badges can also show item counts after the text to indicate the number of items and should be visible based on the status of the containing data view.</p><h4>Tab Alerts</h4><figure><img alt="tab alerts, semantic color, tab status, error tabs, success tabs, tab notifications" src="https://cdn-images-1.medium.com/max/1024/1*bdtrQfzePX9Nd4Hk4Pm7jA.png" /></figure><p>Tabs can display statuses like error, success, and pending to quickly convey the state of their content. Error tabs use red backgrounds or error icons to signal issues, success tabs feature green backgrounds or checkmarks to indicate completed actions, and pending tabs show yellow or orange backgrounds with progress indicators to represent ongoing tasks. These visual cues help users easily understand and manage different states within the interface.</p><h4>Unread Tabs</h4><figure><img alt="unread tabs, tab alert, tab update, content update" src="https://cdn-images-1.medium.com/max/1024/1*ytwv1KgYLkJuHAC6r7TfDQ.gif" /></figure><p>Unread tabs can be visually distinguished to alert users to new or updated content. This can be achieved with a red dot to signal that a tab has unread information, helping users quickly identify which tabs have new or important updates.</p><h4>Tab with Action</h4><figure><img alt="tab with action, action button in tabs, CTA in tabs" src="https://cdn-images-1.medium.com/max/1024/1*1i6Z09uXshflPgm3DQUTbQ.png" /></figure><figure><img alt="tab with action, action button in tabs, CTA in tabs" src="https://cdn-images-1.medium.com/max/1024/1*_rfejewKC2UM6SRzGXs00Q.gif" /></figure><p>Placing an action button on the right side of tabs, especially beside the last tab label, offers a practical and convenient location for additional functionalities without disrupting the main navigation. This setup is ideal for tasks like adding new tabs, managing existing ones, or accessing extra features. The action button can be text-only, icon-only, or a combination of both, depending on the design and functionality needs. This ensures that the button is prominent and easily accessible while keeping the primary tab navigation clear. By making the button visually distinct yet cohesive with the tab design, you enhance usability and maintain a seamless user experience without cluttering the interface.</p><blockquote><strong><em>Conclusion:</em></strong></blockquote><p>Tabs are essential UI components that enhance content organization and navigation, especially in SaaS applications. They allow users to switch between content sections, improving the user experience by reducing visual clutter and maintaining a clear structure.</p><p>Tabs come in various designs like text, icon, image, and combination tabs, adapting to diverse needs. Key states, such as active, hover, and disabled, provide feedback that enhances interaction, while features like tooltips, badges, and alerts boost usability.</p><p>Enhancements like scrollable, overflow, and rearrangeable tabs offer control over navigation. Nested tabs manage multi-level information, while dismissible tabs allow users to remove unneeded sections. Customizable alignments, sizes, and orientations ensure tabs fit specific design requirements, making them versatile tools that improve navigation and user experience.</p><blockquote><strong><em>Sources:</em></strong></blockquote><ul><li><a href="https://experience.sap.com/fiori-design-web/tab-bar-web-component/">https://experience.sap.com/fiori-design-web/tab-bar-web-component/</a></li><li><a href="https://tegel.scania.com/components/tabs">https://tegel.scania.com/components/tabs</a></li><li><a href="https://spectrum.adobe.com/page/tabs/">https://spectrum.adobe.com/page/tabs/</a></li><li><a href="https://www.lightningdesignsystem.com/components/tabs/">https://www.lightningdesignsystem.com/components/tabs/</a></li><li><a href="https://www.delldesignsystem.com/components/tabs/">https://www.delldesignsystem.com/components/tabs/</a></li><li><a href="https://carbondesignsystem.com/components/tabs/usage/">https://carbondesignsystem.com/components/tabs/usage/</a></li></ul><h4>Thanks for Reading!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af04eb6c9d99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/uncover-the-full-potential-of-perfect-tabs-af04eb6c9d99">Uncover the Full Potential of Perfect Tabs Design!</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>