<?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 Barkatullah Mohammed on Medium]]></title>
        <description><![CDATA[Stories by Barkatullah Mohammed on Medium]]></description>
        <link>https://medium.com/@khaleelforever?source=rss-1d2612161dfa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Z4wR8YY0PbKVI8exZX15SQ.jpeg</url>
            <title>Stories by Barkatullah Mohammed on Medium</title>
            <link>https://medium.com/@khaleelforever?source=rss-1d2612161dfa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:55:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@khaleelforever/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[20 Days of Designing with AI: What’s Actually Working in My Workflow]]></title>
            <link>https://medium.com/@khaleelforever/20-days-of-designing-with-ai-whats-actually-working-in-my-workflow-ca649f3775eb?source=rss-1d2612161dfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca649f3775eb</guid>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Barkatullah Mohammed]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 14:29:26 GMT</pubDate>
            <atom:updated>2026-10-19T14:29:26.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B2FCTBLNOsl8N6C0ByGKtg@2x.png" /></figure><p>For the past 20 days, I’ve been running an experiment.<br>Not to see whether AI can generate a pretty screen. We already know it can.</p><p>I wanted to understand how far AI can fit into a real product design workflow, from strategy and information architecture through design systems, prototyping, and eventually something a developer can actually build.</p><p>I’m still experimenting.<br>But the workflow has now settled into something I genuinely trust.<br>Here’s what’s working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jKFgE6R38wMmzcq2jBbW1A@2x.png" /></figure><h3><strong>1. Show references. Don’t describe a vibe.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DAkGytO_SPRU-WYapRg5dg@2x.png" /></figure><p>“Make it premium.”<br>“Make it modern.”<br>“Make it feel innovative.”<br>Those prompts usually get you the average of the internet.<br>A strong reference gives AI direction.</p><p>I’ve found it works far better to point at a product I admire and say:</p><blockquote><em>Study how it structures information, communicates value, and tells the story. Don’t copy the UI.</em></blockquote><p>The more concrete the benchmark, the less time I spend translating vague adjectives into something useful. Good designers aren’t just creating anymore. They’re curating.</p><h3>2. Structure first. Pixels later.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8r1PQikcjmJdLiCgMWihog@2x.png" /></figure><p>This was easily the biggest lesson.<br>Early on, I’d get screens that looked polished but still felt wrong.<br>The issue wasn’t the visual design.<br>It was the hierarchy.<br>The order of information matters more than the quality of the UI.<br>So I started locking the structure before touching the visuals:</p><blockquote><strong>Audience → Problem → Solution → How it Works → Proof</strong></blockquote><p>Once the content structure and flows were clear, the visual design became dramatically faster. AI is good at generating layouts.It’s much less reliable at deciding what deserves attention first.</p><h3>3. Build a design system so AI has guardrails.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UOQTwqRSsST7A7R92yTdDA@2x.png" /></figure><p>I built an atomic design system in Figma with tokens, components, patterns, and reusable foundations.</p><p>Then I stopped asking AI to invent screens from scratch.</p><p>Instead, I asked it to work within the system.</p><p>That changed everything.</p><p>The design system became a guardrail.</p><p>It prevented AI from making decisions I never agreed to:</p><ul><li>random colours</li><li>inconsistent spacing</li><li>rogue typography</li><li>unnecessary component variations</li><li>patterns that don’t exist elsewhere in the product</li></ul><p>Without a system, AI creates.</p><p>With a system, AI contributes.</p><p>That’s a big difference.</p><h3>4. Prototype one flow at a time.</h3><p>I stopped asking AI to design an entire product.<br>Now I focus on one flow, get it right, then move on.<br>Smaller chunks make problems easier to identify and decisions easier to build upon.</p><p>I’ve also started describing each flow in plain language before designing it.</p><p>That’s become a useful test.</p><p>If I can’t explain the flow simply, I probably don’t understand it well enough yet.</p><p>AI exposes ambiguity surprisingly quickly.</p><h3><strong>5. Design the edge cases, not just the happy path.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NM1uORr91o_VOz-dIcd0Uw@2x.png" /></figure><p>This is where I think most AI-generated design work falls apart.</p><p>AI loves an ideal scenario:</p><ul><li>perfect data</li><li>perfect content length</li><li>successful actions</li><li>no interruptions</li><li>no unexpected behaviour</li></ul><p>Real products don’t work like that.</p><p>Every AI-generated screen eventually ends up in Figma, where I work through the uncomfortable questions:</p><ul><li>What happens when there’s no data?</li><li>What happens when something fails?</li><li>What if the network is slow?</li><li>What if the user arrives here for the first time?</li><li>What if names are ridiculously long?</li><li>What happens when users do things in the wrong order?</li></ul><p>Ironically, this is now where most of my design time goes.</p><p>AI gets me to the first 80%.</p><p>Designing for reality is still the remaining 20%.</p><h3>6. AI gets you to competent. Taste gets you to distinctive.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPQB9YqPhTy4bjRTYSZ8Rw@2x.png" /></figure><p>Some of my design feedback has been remarkably simple:</p><blockquote><em>“This is very mid.”</em></blockquote><blockquote>The design wasn’t bad.</blockquote><blockquote>It was clean.</blockquote><blockquote>Logical.</blockquote><blockquote>Usable.</blockquote><p>And completely forgettable.</p><p>AI is incredibly good at producing competent first drafts.</p><p>Getting from competent to distinctive still requires human judgement.</p><p>Knowing:</p><ul><li>what deserves emphasis</li><li>what feels excessive</li><li>what creates emotional impact</li><li>what should be removed</li></ul><p>The gap between bad and decent is shrinking fast.</p><p>The gap between decent and memorable still comes down to taste.</p><h3>7. Know when to go back.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WIqie_Hs1z0vdsW5R6PWew@2x.png" /></figure><p>Not every iteration is progress.</p><p>Several times I explored a new direction, compared it honestly with the previous version, and reverted.</p><p>That’s not failure.</p><p>That’s design.</p><p>AI makes experimentation cheap.</p><p>The danger is that it also makes endless iteration feel productive.</p><p>Sometimes the best design decision is simply:</p><blockquote><em>The previous version was better.</em></blockquote><h3>What I’d tell anyone starting</h3><ul><li>Use real references over adjectives.</li><li>Fix the structure before polishing the visuals.</li><li>Use a design system as the guardrail.</li><li>Work in small steps and judge each one.</li><li>Design the edge cases, not just the happy path.</li><li>Treat AI as a fast collaborator, not the decision-maker.</li></ul><h3>What’s next</h3><p>The design phase is in good shape, so I’m moving on to building the front end in code and testing the UI with real interaction. This is where I find out how well the workflow holds up when designs meet a browser, real devices and real users. I’ll share what I learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uTXF2XiCJe5AcmJCam1w1Q@2x.png" /></figure><p>If you’re bringing AI into your own design process, I’d love to hear what’s working for you, and what isn’t.</p><p><strong>A note on the tools</strong></p><p><strong>Claude</strong> was my main thinking partner for structure, flows, copy and plans, and for turning ideas into quick prototypes. <strong>ChatGPT</strong> helped me generate design options from my design-system files. <strong>Figma</strong> held everything together: the design system lives there, and it’s where every screen gets refined and every edge case gets designed.</p><p>The tools will keep changing. The process is what made them useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca649f3775eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ Designing with Discipline: How to Maintain Branches in Figma Like a Pro]]></title>
            <link>https://medium.com/@khaleelforever/%EF%B8%8F-designing-with-discipline-how-to-maintain-branches-in-figma-like-a-pro-c056e1942b55?source=rss-1d2612161dfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/c056e1942b55</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[review]]></category>
            <dc:creator><![CDATA[Barkatullah Mohammed]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 04:40:24 GMT</pubDate>
            <atom:updated>2025-06-10T03:59:19.015Z</atom:updated>
            <content:encoded><![CDATA[<h3>Designing with Discipline: How to Maintain Branches in Figma Like a Pro</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RYtLhsSnZYLUeK3lzf1Ehw.png" /></figure><p>Designing in Figma can be exhilarating — real-time collaboration, powerful components, and an intuitive interface. But when you’re working on large-scale design systems or in fast-moving product teams, things can get chaotic fast. That’s where <strong>Figma branches</strong> come in.</p><p>If you’re treating Figma branches like temporary scratchpads or skipping them altogether, you’re missing out on one of the most powerful tools for maintaining design quality and team alignment.</p><p>In this post, I’ll break down how to properly maintain Figma branches during the design process so you can design with confidence — and avoid chaos.</p><h3>What is a Branch in Figma?</h3><p>Branches in Figma work similarly to branches in Git: they allow you to make changes to a file without immediately affecting the main design system or project file. You can explore ideas, test redesigns, or develop new components — all in isolation.</p><p>Once you’re happy with your changes, you can <strong>merge them back</strong> into the main file (often called “main” or “master”).</p><h3>Why Use Branches?</h3><ul><li>✅ <strong>Safe experimentation</strong>: Try new ideas without disturbing production designs.</li><li>✅ <strong>Parallel workflows</strong>: Designers can work on different features simultaneously.</li><li>✅ <strong>Better reviews</strong>: Changes are isolated and easy to review before merging.</li><li>✅ <strong>Cleaner design history</strong>: Avoid messy file versions and overwritten components.</li></ul><h3>A Smooth Branching Workflow</h3><p>Here’s a sample workflow for maintaining branches effectively:</p><p><strong>Start from Main</strong></p><ul><li>Always create your branch from the latest version of the main file.</li><li>Name it clearly: feature/redesign-login, bugfix/button-alignment, etc.</li></ul><p><strong>Design in Isolation</strong></p><ul><li>Make your changes in the branch only. Keep components linked to main wherever possible.</li><li>If creating new components, prefix them or organize them in a frame titled Branch Components to avoid confusion.</li></ul><p><strong>Document Your Changes</strong></p><ul><li>Use sticky notes, comments, or a changelog frame in the branch.</li><li>Summarize what’s new or changed. It helps reviewers a lot.</li></ul><p><strong>Test for Impact</strong></p><ul><li>Double-check affected components and flows.</li><li>Run prototype tests if needed within the branch.</li></ul><p><strong>Request Review (if in team)</strong></p><ul><li>Share the branch link for peer review.</li><li>Use Figma’s built-in review tools or comment threads.</li></ul><p><strong>Merge Thoughtfully</strong></p><ul><li>Only merge once your changes are stable and reviewed.</li><li>Clean up unused components or draft work before merging.</li></ul><p><strong>Post-Merge Cleanup</strong></p><ul><li>Archive the branch or delete it after merging.</li><li>Update the design documentation or design system if applicable.</li></ul><h3>Best Practices for Branch Maintenance</h3><ul><li><strong>Branch small, branch often</strong>: Avoid giant branches that are hard to review.</li><li><strong>Stay in sync with Main</strong>: If Main has been updated while you’re in a branch, consider rebasing (i.e., duplicating a new branch and copying your changes).</li><li><strong>Use naming conventions</strong>: Example — feat/, fix/, exp/ for feature, fix, and experimental.</li><li><strong>Limit scope</strong>: Keep each branch focused on a specific problem or feature.</li><li><strong>Communicate changes</strong>: Let your team know what you’re working on.</li></ul><h3>Real Example: Button Component Update</h3><p><strong>Scenario</strong>: You want to update all button variants with a new hover effect.</p><ol><li>Create a branch: feat/button-hover-states</li><li>Update the button component set.</li><li>Test the change across multiple mockups or flows using Swap Instance.</li><li>Add a comment frame summarizing the update and potential impact.</li><li>Get feedback from the design lead.</li><li>Merge and notify devs or update the design documentation.</li></ol><p>Outcome? A seamless upgrade without breaking live designs.</p><h3>Final Thoughts</h3><p>Branching in Figma isn’t just a feature — it’s a <strong>discipline</strong>. By following a thoughtful branching strategy, you not only improve your team’s collaboration but also protect the integrity of your design system.</p><p>So the next time you’re about to tweak a component or revamp a screen, don’t dive into the main file. <strong>Branch first. Design better.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c056e1942b55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reviewing Your Design Post-Development]]></title>
            <link>https://medium.com/@khaleelforever/reviewing-your-design-post-development-50e21df68977?source=rss-1d2612161dfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/50e21df68977</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[bugs]]></category>
            <dc:creator><![CDATA[Barkatullah Mohammed]]></dc:creator>
            <pubDate>Sat, 21 Sep 2024 10:05:54 GMT</pubDate>
            <atom:updated>2025-06-10T04:01:10.811Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZkbyjJIV8uey0H84XBgKA.png" /></figure><p><strong>Introduction</strong></p><ul><li><strong>Relatable anecdote:</strong> “When I first started my design journey, I was eager to dive into creating stunning visuals. However, I quickly realized that the gap between my initial concepts and the final product could be significant. As a novice designer working with a development team, I often found myself unsure about how to effectively review my designs post-development.”</li><li><strong>Thesis:</strong> “This article will guide you through the process of reviewing your designs after they’ve been developed, even if you have limited technical knowledge. By understanding the basics of developer tools and following a structured approach, you can ensure that your designs are implemented accurately and meet your intended goals.”</li></ul><p><strong>Understanding the Importance of Post-Development Review</strong></p><ul><li><strong>Addressing design drift:</strong> “Design concepts can evolve during development. Post-development review helps identify any discrepancies between your original vision and the final implementation.”</li><li><strong>Enhancing user experience:</strong> “A thorough review ensures that your design functions as intended, providing a seamless and enjoyable user experience.”</li><li><strong>Identifying and fixing bugs:</strong> “By carefully examining the developed product, you can uncover and address any technical issues or errors that may have arisen during implementation.”</li></ul><p><strong>A Structured Approach to Post-Development Review</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jn5bCwrl1mtaOLAxAdNtfA.png" /></figure><ul><li><strong>Step 1: Familiarize yourself with developer tools:</strong> “Chrome Developer Tools (DevTools) is a powerful tool for inspecting and debugging web pages. Start by learning the basics of the Elements, Console, and Network tabs.”</li><li><strong>Step 2: Conduct a visual inspection:</strong> “Compare the developed design to your original mockups. Pay attention to elements like fonts, colors, spacing, and alignment. Use DevTools to inspect individual elements and verify their styles.”</li><li><strong>Step 3: Test responsiveness:</strong> “Ensure your design adapts well to different screen sizes and devices. Use DevTools’ responsive design mode to simulate various screen widths and orientations.”</li><li><strong>Step 4: Check for functionality:</strong> “Test all interactive elements, such as buttons, links, and forms. Verify that they work as expected and provide the desired user interactions.”</li><li><strong>Step 5: Optimize</strong> <strong>Performance:</strong> “Use DevTools’ performance profiling tools to measure page load times and identify any performance bottlenecks. Optimize images, minimize code, and reduce HTTP requests to improve performance.”</li><li><strong>Step 6: Prioritize issues:</strong> “Document any discrepancies or bugs you find. Prioritize them based on their severity and impact on the user experience.”</li><li><strong>Step 7: Collaborate with developers:</strong> “Communicate effectively with your developers to discuss the identified issues and propose solutions. Together, you can determine the best course of action for addressing them.”</li></ul><p><strong>Conclusion</strong></p><ul><li><strong>Recap:</strong> Summarize the key steps involved in post-development review.</li><li><strong>Benefits:</strong> Emphasize the benefits of conducting thorough reviews, such as improved design quality, enhanced user satisfaction, and strengthened collaboration with developers.</li><li><strong>Continuous improvement:</strong> Encourage designers to make post-development review a regular part of their workflow to ensure ongoing design excellence.</li></ul><p>By following these steps and leveraging the power of developer tools, you can become a more confident and effective designer, capable of delivering high-quality products that meet your users’ needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50e21df68977" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revolutionizing the Shopping Experience: Exploring GAP’s Interactive Fitting Room Technology]]></title>
            <link>https://medium.com/@khaleelforever/revolutionizing-the-shopping-experience-exploring-gaps-interactive-fitting-room-technology-2e645e75ffa0?source=rss-1d2612161dfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e645e75ffa0</guid>
            <category><![CDATA[inovation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[fashion]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[investing]]></category>
            <dc:creator><![CDATA[Barkatullah Mohammed]]></dc:creator>
            <pubDate>Sat, 01 Jul 2023 14:57:06 GMT</pubDate>
            <atom:updated>2023-07-01T14:57:06.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zpFBgVdTF9kMYH71srj0FA.png" /></figure><p>In a world where technology continues to shape our daily lives, the retail industry is behind in embracing innovative solutions. GAP, a renowned clothing brand, has introduced a groundbreaking feature that transforms its stores&#39; traditional fitting room experience. <strong>By incorporating interactive screens into their fitting rooms, GAP has revolutionized how customers try on clothes and find their perfect fit</strong>. This article delves into the fascinating concept of GAP’s interactive fitting room technology and its impact on the shopping experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GPUR0ujcQ8PuhDxOarrZDg.jpeg" /></figure><p><strong>Interactive fitting rooms emerged as a solution to improve the customer experience and connect online and in-store shopping.</strong> GAP recognized the importance of a smooth transition between these two channels and invested in developing technology to enhance the process of trying on clothes. This resulted in the creation of their interactive fitting room feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7M5MPHkDlhWIzcBE1EL9nw.jpeg" /></figure><p>GAP’s interactive fitting room technology centers around a screen inside the fitting room. <strong>As customers try on clothes, the screen displays the selected items, visually representing their outfits. </strong>This visual aid allows customers to see how different pieces of clothing complement each other and make informed decisions about their purchases.</p><p>One of the standout features of GAP’s interactive fitting room is the ability to request different sizes without leaving the fitting room or seeking assistance from a salesperson. <strong>Customers can select the “bigger” or “smaller” size option for any particular item by simply interacting with the screen.</strong> This feature not only saves time but also offers a level of convenience and autonomy that was previously unavailable in traditional fitting rooms.</p><p><strong>While the technology empowers customers to control their fitting room experience, it doesn’t replace the role of sales associates.</strong></p><p>When a customer selects a different size through the interface, the request is transmitted to the sales associates, who promptly retrieve the requested items. <strong>This integration ensures that customers receive the correct sizes without any delays, enhancing their overall shopping experience.</strong></p><p>GAP’s interactive fitting room technology offers numerous benefits that enhance the customer’s shopping journey. Firstly, it provides convenience by eliminating the need for customers to search for sizes themselves or wait for a salesperson to assist them. The ability to request different sizes instantly through the interface saves time and effort, making the fitting room experience more efficient.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e645e75ffa0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>