<?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 Anna John on Medium]]></title>
        <description><![CDATA[Stories by Anna John on Medium]]></description>
        <link>https://medium.com/@ajohndesign08?source=rss-ba6713d07f4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sx_l6SfUk0iYN1cw</url>
            <title>Stories by Anna John on Medium</title>
            <link>https://medium.com/@ajohndesign08?source=rss-ba6713d07f4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:37:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajohndesign08/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[Just Enough Design]]></title>
            <link>https://medium.com/@ajohndesign08/just-enough-design-623284f1d44a?source=rss-ba6713d07f4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/623284f1d44a</guid>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[boltnew]]></category>
            <dc:creator><![CDATA[Anna John]]></dc:creator>
            <pubDate>Tue, 17 Jun 2025 00:58:19 GMT</pubDate>
            <atom:updated>2025-06-17T00:58:19.753Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What do you do when your entire product needs to go mobile in three weeks, and the foundation is a patchwork of legacy code?</strong></p><p>In my early days at Brevity, I wore multiple hats — designing, testing, and shaping product decisions in a five-person startup. The pace was intense, and our priority was clear: ship a working desktop-first product fast. There was little time for long-term UX thinking, and design systems took a backseat to daily fire drills. It was challenging to work without structure, but I enjoyed the scrappy energy and the opportunity to influence every part of the product from the ground up.</p><p>But everything shifted a few months ago. We saw a clear rise in mobile usage — especially from reps on the move, between sales calls, or reviewing practice sessions on the go. Customer expectations were evolving, and it became obvious: mobile responsiveness wasn’t just a UX upgrade, it was critical to meeting users where they are and driving product growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HBhBxkuEbWLEU1V9Qz8tdg.png" /></figure><h3>Prioritizing Under Pressure</h3><p>When my manager set a three-week timeline to make the platform mobile-responsive, I knew this wasn’t going to be a typical design sprint. The technical foundation was a mix of legacy decisions, ad hoc implementations, and partial MUI integration. Mid-sprint cleanup of the entire front end wasn’t feasible.</p><p>The challenge wasn’t only about execution, it was about prioritization under pressure.</p><p>Rather than begin with a full-system audit, I zoomed in on value-critical screens, the ones users rely on most.</p><h4>Triage by Importance</h4><ul><li><strong>High</strong>: Screens essential to the product’s core value such as primary workflows and main engagement touchpoints.<br> <em>For example, in Brevity: Assignments Page, Practice Page, Dashboard.</em></li><li><strong>Medium</strong>: Supporting screens used regularly by specific roles or in secondary workflows.<br> <em>In Brevity: Teams (used by admins to manage participants and settings).</em></li><li><strong>Low</strong>: Rarely used or static pages that don’t directly impact core user outcomes.<br> <em>In Brevity: Settings, Profile, and other informational pages.</em></li></ul><p>This prioritization helped focus design time where it mattered and gave engineers a clear scope to work with asynchronously.</p><h3>Laying the Groundwork: Atomic Design in Action</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w86H3kxDTO6ICado" /><figcaption>Image from UX Planet</figcaption></figure><p>To align efficiently with engineering, I collaborated early with our frontend lead to identify what could be translated from desktop to mobile with minimal friction.</p><p>The complexity across critical pages made it clear: mobile responsiveness couldn’t be treated as a series of isolated fixes. We needed a scalable foundation.</p><p>That’s where <strong>atomic design</strong> came in. It is a method of breaking the interface down into reusable building blocks: from simple elements like buttons and icons (<em>atoms</em>), to small functional units like cards and drawers (<em>molecules</em>), and then full sections and screens (<em>organisms and templates</em>).</p><p>I wasn’t building a design system for documentation’s sake, but as a practical tool for alignment, speed, and long-term maintainability.</p><h3>Starting with One High-Impact Screen</h3><p>To avoid overhauling the full interface at once, I started with the Assignments page, a high-traffic, business-critical screen.</p><p>This screen allowed me to define and test layout decisions, interaction patterns, and responsive behaviors in a real-world context.</p><p><strong>Design System Schema</strong></p><ul><li><strong>Tokens</strong>: Typography, spacing, color, breakpoints, elevation</li><li><strong>Atoms</strong>: Buttons, icons, labels</li><li><strong>Molecules</strong>: Drawer headers, action cards</li><li><strong>Organisms</strong>: Assignment lists, tab structures</li><li><strong>Templates &amp; Pages</strong>: Full layouts composed from system parts</li></ul><p>Material 3 and Apple’s Human Interface Guidelines informed accessibility and scalable behavior logic.</p><h3>System-Level Thinking for Mobile UX</h3><figure><img alt="Behavior change in Brevity’s Practice View from Desktop to Mobile" src="https://cdn-images-1.medium.com/max/1024/1*eoFeO98hG6Abug7i5KcMNg.png" /></figure><p>Designing for mobile is not about shrinking layouts, it’s about reimagining interactions under constraints like limited space and touch input.</p><p>For example, on desktop, users could open sliders at once (e.g., Milestones, Transcript, Settings). On mobile, this became overwhelming.</p><p>I replaced this model with a single-drawer interaction, allowing only one panel to be open at a time, improving clarity and task flow.</p><p>Implementing this required consistency in spacing, interaction behavior, and naming, reinforcing the need for a robust design system.</p><h3>When in Doubt, Prototype and Prove</h3><p>Some proposed interactions were initially met with hesitation from engineering due to implementation complexity.</p><p>To validate ideas, I used <a href="https://bolt.new/">bolt.new</a> in conjunction with Figma prototypes to generate working HTML/CSS examples. This reduced ambiguity and facilitated alignment on complex behaviors like animations and layout transitions.</p><p>This also strengthened design-engineering collaboration by providing immediate, testable outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*Amll90l0nHRIIndziPQuag.gif" /><figcaption>Using bolt.new for prototyping</figcaption></figure><h3>Scaling Beyond the Sprint</h3><p>After completing the Assignment and Practice pages, extending the system to Courses, Dashboard, and Teams became significantly more efficient.</p><p>Although the original timeline was ambitious, it set the momentum we needed. I helped establish a scalable mobile foundation that now positions us to support product growth well beyond Q2 2025.</p><p>Engineering implementation time on subsequent pages was reduced considerably due to the clarity and reusability of the system.</p><h3>Key Learnings</h3><ul><li>Mobile UX requires rethinking, not just resizing, interfaces.</li><li>Early collaboration with engineers accelerates delivery.</li><li>Prototyping tools like bolt.new help communicate complex behaviors quickly.</li><li>Design systems are most effective when built from live use cases, not isolated theory.</li></ul><p>The internal response has been positive: engineers report fewer blockers, and stakeholders see greater clarity in the UI. One team member noted, “It feels like we’ve finally caught up to how people actually want to use the product.”</p><h3>Quick Practice Guide: Starting Your Mobile-Responsive Design &amp; Design System Journey</h3><p>Whether you’re the first designer at a startup or part of a growing product team, here’s a practical checklist for managing mobile responsiveness and building foundational systems under pressure:</p><ol><li><strong>Prioritize Value, Not Perfection<br></strong> Identify the key user journeys. Triage screens by impact (High / Medium / Low).</li><li><strong>Start with a Foundational Schema<br></strong> Define tokens (spacing, typography, color, breakpoints).<br>Organize components using atomic structure (atoms → molecules → organisms → templates).</li><li><strong>Audit with Implementation in Mind<br></strong> Understand how your product is built (e.g., MUI, Tailwind, custom).<br>Collaborate early with engineers to ensure design feasibility.</li><li><strong>Embrace Mobile-First Thinking<br></strong> Avoid shrinking layouts. Use drawer patterns, simplify multitasking, and prioritize touch interactions.</li><li><strong>Validate Often, Even Without Full Data<br></strong> Use tools like LogRocket to observe usage patterns.<br>Rely on UX best practices and test assumptions with prototypes.</li><li><strong>Use Tools That Bridge Design and Code<br></strong> Tools like bolt.new, Figma Dev Mode, and Storybook streamline communication.<br>Short demos can accelerate alignment.</li><li><strong>Document Lightly, Scale Naturally<br></strong> Avoid over-documentation early. Focus on naming clarity, reusable patterns, and lightweight guidance.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=623284f1d44a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>