<?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 Andres Mugueta on Medium]]></title>
        <description><![CDATA[Stories by Andres Mugueta on Medium]]></description>
        <link>https://medium.com/@andres.mugueta?source=rss-3869c56f1f36------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*F3rjjjL2QfD4fFZfyLdGpA.jpeg</url>
            <title>Stories by Andres Mugueta on Medium</title>
            <link>https://medium.com/@andres.mugueta?source=rss-3869c56f1f36------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:35:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andres.mugueta/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[Case Study: Redesigning IDEAS]]></title>
            <link>https://medium.com/@andres.mugueta/case-study-redesigning-ideas-51f48272112c?source=rss-3869c56f1f36------2</link>
            <guid isPermaLink="false">https://medium.com/p/51f48272112c</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Andres Mugueta]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 17:21:16 GMT</pubDate>
            <atom:updated>2026-09-18T17:21:16.152Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we redesigned a complex university LMS by applying Human Factors, error prevention principles, and defensive design to eliminate cognitive overload.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A7BlOU6WcKHu6IODcJwLaQ.png" /></figure><h3><strong>Project Overview</strong></h3><p>Learning Management Systems (LMS) in higher education are often designed around administrative constraints rather than student and professor mental models. The <strong>IDEAS platform </strong>(the virtual campus used by the National University of La Plata a.k.a UNLP) was a classic example: a feature-dense environment where critical actions were hidden behind ambiguous icons, tight click targets, and unorganized lists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_50TGPNa5gazpuofRTM1w.png" /><figcaption>Based on a review of the IDEAS platform’s screens, this study analyzes key interaction flows and how design decisions affect the user’s cognitive economy.</figcaption></figure><p>When an LMS fails in usability, the cost isn’t just user frustration: it’s missed assignment deadlines, mistaken course unenrollments, and severe academic anxiety.</p><p>This case study details the complete end-to-end UX/UI redesign of IDEAS, shifting its core architecture from a reactive system to a <strong>defensive, human-centered digital ecosystem</strong>.</p><ul><li><strong>Role:</strong> Lead UX/UI Designer &amp; UX Researcher.</li><li><strong>Scope:</strong> Information Architecture, Interaction Design, Heuristic Evaluation, Cognitive Walkthroughs, and Usability Testing.</li><li><strong>Context:</strong> Postgraduate Specialization in Human-Computer Interaction (UNLP).</li><li><strong>Tools:</strong> Figma, FigJam, Heuristic Evaluation Protocols, Maze / Usability Testing.</li></ul><h3><strong>The Core Problem: Slips vs. Mistakes in LMS Design</strong></h3><p>Most academic platform updates focus on visual refreshes (UI skins). However, our initial research revealed that the fundamental issues with IDEAS were rooted in <strong>Human Error Theory</strong> (James Reason / Don Norman).</p><p>Through cognitive walkthroughs and interviews with students and faculty, we categorized the usability breakdown into two distinct behavioral failure modes:</p><ol><li><strong>Slips (Execution Errors):</strong> Users knew what they wanted to do, but the interface triggered wrong actions. For example, clicking “Cancel” instead of “Save” because both buttons shared the same size, styling, and immediate physical proximity.</li><li><strong>Mistakes (Planning Errors):</strong> Users made wrong decisions because the system presented ambiguous information. For example, enrolling in the wrong course section due to flat data grids without clear visual hierarchy or filtering context.</li></ol><h3><strong>Strategic UX &amp; Interaction Principles</strong></h3><p>To address these vulnerabilities, we established three core design principles that guided the entire architecture:</p><h4>1. Defensive Design &amp; Error Prevention</h4><p>Preventing critical errors before they happen is far more effective than offering clear error messages afterward.</p><ul><li><strong>Separation of Destructive Actions:</strong> Destructive or irreversible buttons (like unenrollment or discarding changes) were physically separated from primary calls-to-action (CTAs) and given distinct visual weights.</li><li><strong>Explicit Confirmation &amp; Feedback:</strong> High-risk actions now require deliberate, unambiguous confirmation steps rather than single-click triggers.</li></ul><h4>2. Recognition Over Recall (Fitts’s &amp; Hick’s Laws)</h4><ul><li><strong>Eliminating Icon Ambiguity:</strong> Icon-only navigation bars were replaced with explicit text labels. Iconography now serves as a secondary visual anchor rather than the sole navigator.</li><li><strong>Expanding Touch &amp; Click Targets:</strong> Target sizes were increased to comply with accessibility standards (minimum 48x48 dp), drastically reducing mis-clicks on high-density screens.</li></ul><h4>3. Progressive Disclosure &amp; Information Architecture</h4><ul><li><strong>Breaking the “Wall of Links”:</strong> Unstructured lists (such as the 25+ unorganized links in the Help Center) were restructured using progressive disclosure (collapsible accordion categories and live predictive search).</li></ul><h3>Design Evolution &amp; Key Iterations</h3><p>We iterated through three main phases, testing each layout against strict usability heuristics and task-completion metrics</p><h4>Screen 1: “My Courses” Dashboard</h4><ul><li><strong>The Problem:</strong> The original dashboard relied on ambiguous icons without text labels, miniature action targets, and obscure notification badges that failed to communicate new course material clearly.</li><li><strong>The Fix:</strong> Redesigned course cards with clear hierarchy. Introduced explicit status badges (e.g., <em>“2 new announcements”</em>), larger click targets, and a dual layout switch (Grid vs. List) to support different user browsing preferences.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ViIccdQx-ZfxxmGn5HM9cA.png" /><figcaption>Each proposal addresses the previous findings using the same conceptual framework.</figcaption></figure><h4>Screen 2: Course Search &amp; Enrollment</h4><ul><li><strong>The Problem:</strong> A flat, unformatted data grid caused frequent accidental enrollments in wrong academic years or sections.</li><li><strong>The Fix:</strong> Implemented chained progressive filters (Faculty ➔ Department ➔ Course ➔ Year), a live search engine, and distinct visual tags indicating course status (Open, Enrolled, Closed).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HN5t5Xjf_LAYbmi4yVfXRg.png" /></figure><h4>Screen 3: Notification &amp; System Settings</h4><ul><li><strong>The Problem:</strong> “Save” and “Cancel” buttons were visually identical and placed side-by-side, frequently causing users to lose their configuration changes.</li><li><strong>The Fix:</strong> Established clear button hierarchy. “Save Changes” became a prominent primary CTA anchored at the bottom, “Cancel” was transformed into a secondary neutral button, and a global “Select All” toggle was added for bulk management.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YTIQypRmLx0RvWwGVUj1kw.png" /></figure><h4>Screen 4: Help Center &amp; Support</h4><ul><li><strong>The Problem:</strong> A overwhelming list of over 25 consecutive text links made finding help an exhausting task.</li><li><strong>The Fix:</strong> Categorized all support documentation into 6 expandable accordion sections, added a prominent real-time search bar, and formatted article previews for effortless scanning.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2YOfqXMo4_t8Ickz-4wyoQ.png" /></figure><h3><strong>Key Learnings &amp; Takeaways</strong></h3><ol><li><strong>Accessibility is Non-Negotiable in Education:</strong> University platforms serve extremely diverse student populations. <strong>Ensuring high contrast, clear focus states, and adequate touch targets isn’t an “extra”: it is fundamental infrastructure.</strong></li><li><strong>Design Systems Must Be Defensive:</strong> Good UI doesn’t just guide users toward success; it actively protects them from accidental failure.</li><li><strong>Hierarchy Drives Confidence:</strong> By replacing dense visual noise with structured progressive disclosure, students reported feeling more in control of their academic workload.</li></ol><p><em>Thank you for reading!</em></p><p>Designed by:<br>Santiago Andrés Mugueta — UX/UI &amp; Multimedia Designer</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51f48272112c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Designing Morfi]]></title>
            <link>https://medium.com/@andres.mugueta/case-study-designing-morfi-af79569273bd?source=rss-3869c56f1f36------2</link>
            <guid isPermaLink="false">https://medium.com/p/af79569273bd</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[food]]></category>
            <category><![CDATA[uxui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Andres Mugueta]]></dc:creator>
            <pubDate>Thu, 17 Sep 2026 11:59:23 GMT</pubDate>
            <atom:updated>2026-09-17T11:59:23.227Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>How we designed a budget-friendly culinary assistant that adapts to local ingredients and real-world availability, eliminating decision fatigue and food waste.</em></h3><h4><strong>Project Overview</strong></h4><p>Transitioning to independent living usually comes with an unexpected burden: deciding what to cook every single day. For young adults living alone, cooking often feels like an overwhelming chore rather than a rewarding habit. Existing culinary applications flood users with complex international recipes, expensive imported ingredients, and invasive ad banners, pushing beginners toward repetitive diets or costly delivery apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ww82gXuAQzIdLVcIwx4oOg.png" /></figure><p><strong>Morfi</strong> (from the Argentine slang <em>morfar</em>, “to eat”) is a mobile culinary assistant designed to simplify cooking for beginners. It bridges the gap between limited budgets, lack of time, and healthy eating by suggesting realistic step-by-step recipes based on what users already have in their kitchen.</p><ul><li><strong>My Role:</strong> End-to-End Product / UX/UI Design &amp; UX Research.</li><li><strong>Academic Context:</strong> UX/UI Design Personal Project.</li><li><strong>Timeline:</strong> 1st Delivery Cycle (Desk Research, User Interviews, Information Architecture, Wireframing).</li><li><strong>Tools:</strong> Figma, FigJam, UX Tweak, Maze, Whimsical</li></ul><h3><strong>The Core Problem</strong></h3><p>Young adults who move out on their own don’t suffer from a lack of desire to eat well; they face a friction-heavy ecosystem.<br>Through qualitative interviews, Desk Research, and community synthesis (analyzing spaces like r/ArgentinaCocina), we identified three primary friction points:</p><ul><li><strong>The Local Ingredient Gap:</strong> Popular cooking platforms feature recipes requiring specialized tools (e.g., food processors) or costly, hard-to-source ingredients.</li><li><strong>Planning &amp; Inventory Friction:</strong> The mental tax of figuring out meals on the spot leads to poor buying decisions, budget drain, and ingredient spoilage.</li><li><strong>Overwhelming Interfaces:</strong> Beginner cooks are deterred by dense text, poor visual legibility, and aggressive ad banners.</li></ul><p><strong>Point of View (POV):</strong> <em>“Young adults living independently need a quick, straightforward way to prepare accessible meals because their limited time, budget, and culinary skills make maintaining a balanced diet exhausting.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*au0lyXyXrW_xznrb1wqm_A.png" /><figcaption>Early low definition wireframes on paper.</figcaption></figure><h3><strong>Strategic UX &amp; Product Decisions</strong></h3><p>To address these challenges, we established three core product principles:</p><p><strong>1. Stock-First Recipe Engine (“Mi Cocina”)</strong> Instead of asking users to adapt to a recipe, Morfi adapts to the user’s pantry. By inputting available ingredients into the app, the engine filters for realistic, budget-friendly options.</p><p><strong>2. Scannable, Visual Guidance</strong> Text-heavy steps create anxiety during active cooking. We prioritized high-legibility cards paired with short visual GIFs to demonstrate basic techniques (chopping, searing, boiling) without cluttering the screen.</p><p><strong>3. Seamless Meal-to-Market Workflow</strong> When an ingredient is missing, users shouldn’t need a separate notes app. Missing items can be pushed straight to an integrated, editable shopping list with a single tap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLDWDodLp6hKGem26BPo3A.png" /></figure><h3><strong>Design Evolution &amp; Architectural Iterations</strong></h3><p>We structured the product architecture using Card Sorting tests and dendrogram analysis to optimize navigation.</p><ul><li><strong>Iteration 1: Streamlining the Navigation Structure</strong></li><li><em>Problem:</em> Early concepts grouped cooking history with current pantry inventory, confusing users during active tasks.</li><li><em>Fix:</em> Moved historical activity to the <strong>Profile</strong> tab, keeping <strong>Mi Cocina</strong> strictly dedicated to active inventory management and saved recipes.</li><li><strong>Iteration 2: Simplifying Meal Planning</strong></li><li><em>Problem:</em> Users found setting up weekly calendars too time-consuming when placed in deep sub-menus.</li><li><em>Fix:</em> Integrated daily and weekly meal views directly into a unified <strong>Planificar</strong> tab, linking it straight to the automatic <strong>Shopping List</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o5dT_maOTS4P2ldulMPzYA.png" /><figcaption>Card Sorting tests and dendrogram analysis were performed to find ways to optimize navigation</figcaption></figure><h3><strong>Key Features in High Fidelity</strong></h3><p><strong>1. “Mi Cocina” Inventory Matcher</strong> A dedicated space to input accessible local ingredients. The system surfaces instant recipe matches, highlighting what can be cooked immediately and what requires a quick trip to the store.</p><p><strong>2. Guided Step-by-Step Cooking Mode</strong> Large typography, clear timer integrations, and visual technique cues keep cooks focused on the stove without having to constantly unlock or scroll through their phones.</p><p><strong>3. Integrated Weekly Planner &amp; Auto-List</strong> Users can schedule meals across the week. The app automatically aggregates missing ingredients into a categorized grocery checklist, preventing impulse buys and food waste.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xxQSNJRKipACUb0Q48j5w.png" /></figure><h3><strong>Key Takeaways</strong></h3><ul><li><strong>Design for Local Context:</strong> Adapting product assumptions to regional reality (available ingredients, local kitchen tools) transforms a generic app into a useful daily tool.</li><li><strong>Reduce Active Cognitive Load:</strong> Cooking requires physical hands-on engagement; interfaces must minimize deep tapping and text reading while the user is at the stove.</li><li><strong>Utility Over Hype:</strong> While social features sound appealing, users derive the highest value from practical organization tools like inventory matchers and automated lists.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7yseC7-DzJfDdDOGXEUyA.png" /></figure><p>Designed by:<br>Santiago Andrés Mugueta — UX/UI &amp; Multimedia Designer</p><p><em>Thank you for reading! If you’d like to inspect the visual design and UI components, check out the project on </em><a href="https://dribbble.com/shots/27716984-Morfi-Foodie-mobile-app?utm_source=Clipboard_Shot&amp;utm_campaign=andres-mugueta&amp;utm_content=Morfi%20-%20Foodie%20mobile%20app&amp;utm_medium=Social_Share&amp;utm_source=Clipboard_Shot&amp;utm_campaign=andres-mugueta&amp;utm_content=Morfi%20-%20Foodie%20mobile%20app&amp;utm_medium=Social_Share"><em>Dribbble</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af79569273bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: Designing Miru]]></title>
            <link>https://medium.com/@andres.mugueta/ux-case-study-designing-miru-87b5ee7cdf87?source=rss-3869c56f1f36------2</link>
            <guid isPermaLink="false">https://medium.com/p/87b5ee7cdf87</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[self-care]]></category>
            <dc:creator><![CDATA[Andres Mugueta]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 22:23:51 GMT</pubDate>
            <atom:updated>2026-09-16T22:23:51.212Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How we designed </strong>a health &amp; self-care<strong> assistant that adapts to human behavior instead of punishing it, eliminating notification fatigue and post-action anxiety.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6iUh4z_UWo2jY7sjCcxQg.png" /></figure><h3><strong>Project Overview</strong></h3><p>Following a medical treatment or building a wellness habit (like skincare or reading) shouldn’t feel like a second job. Yet, most habit trackers enforce rigid schedules, spam users with invasive alarms, and induce guilt when a task is missed.</p><p><strong>Miru</strong> (from the Japanese <em>見る</em>, “to observe”, and a blend of <em>“My routine, my time”</em>) is a mobile assistance app designed to accompany health and self-care routines without cognitive overload. It learns from real-world behavior and adjusts its prompts to the user’s actual pace.</p><ul><li><strong>My Role:</strong> End-to-End Product / UX/UI Design, UX Research, &amp; Usability Testing.</li><li><strong>Timeline:</strong> 3 Iteration Cycles (Discovery, Testing, High-Fidelity Refinement).</li><li><strong>Tools:</strong> Figma, FigJam, User Interviews, Cognitive Walkthroughs, Think Aloud Testing.</li></ul><h3><strong>The Core Problem</strong></h3><p>People generally know <em>what</em> they need to do for their health and well-being. The problem isn’t a lack of intent - it’s <strong>hostile design environments</strong>.</p><p>Through<strong> qualitative research and semi-structured interviews with two distinct user groups</strong> (people with daily medical treatments vs. people building lifestyle habits), we uncovered three major pain points:</p><ol><li><strong>Alarm Fatigue:</strong> Intrusive, loud alarms create friction. Users dismiss them immediately just to stop the noise, missing the task entirely</li><li><strong>Post-Action Anxiety:</strong> The mental burden of asking <em>“Did I take my medicine 10 minutes ago or was that yesterday?”</em> causes more stress than the task itself.</li><li><strong>One-Size-Fits-All Logic:</strong> Treating a critical prescription the same way as “meditating for 5 minutes” fails both use cases.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLdc2pIA6PwqAMLEBdXb0g.png" /><figcaption>We created an affinity map based on the findings from the interviews, which lead us to “How Might We” questions, and the definition of the core principles that would guide the rest of the project.</figcaption></figure><h3><strong>Strategic UX &amp; Behavioral Decisions</strong></h3><p>To tackle these problems, we defined <strong>three core principles</strong> that guided every interface and interaction decision:</p><h4>1. Adaptive &amp; Respectful Reminders (Behavioral Design)</h4><p>Instead of firing static alarms, Miru observes user response patterns. If a user consistently ignores an 8:00 AM prompt but completes it at 8:45 AM, <strong>the system adapts and reschedules future prompts to match their real-world availability</strong>.</p><h4>2. Differentiated Confirmation Logic (Health vs. Wellness)</h4><p>Not all habits carry the same weight. We resolved the trade-off between <strong>low friction</strong> and <strong>medical accuracy</strong> by splitting the logic:</p><ul><li><strong>Wellness Habits:</strong> Low-effort, passive or single-tap confirmation.</li><li><strong>Medical Tasks:</strong> Require active confirmation to guarantee safety and automatically trigger <strong>inventory deduction</strong>.</li></ul><h4>3. Reducing Steps via Interactive Notifications</h4><p>Why force users to open the app just to log a completed action? We embedded interactive controls directly into notification banners, allowing users to mark tasks as “Done” in a single tap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qi0lJpJKV2wXtkEbrpZdJw.png" /></figure><h3><strong>Design Evolution &amp; Usability Iterations</strong></h3><p>We evolved the product across three key phases, leveraging heuristics, cognitive walkthroughs, and Think Aloud usability testing.</p><h4><strong>Iteration 1: Fixing Navigation &amp; Task Access</strong></h4><ul><li><strong>Problem:</strong> Early wireframes required navigating into secondary screens just to change a task status. The “Add Habit” button was buried at the bottom of a long list.</li><li><strong>Fix:</strong> Integrated a direct status toggle directly inside the <strong>Daily Timeline Card</strong> and placed a fixed <strong>Floating Action Button (FAB)</strong> always within thumb reach.</li></ul><h4>Iteration 2: Eliminating Input Errors</h4><ul><li><strong>Problem:</strong> Free-text input fields for time and medication dosages caused frequent typing errors during testing.</li><li><strong>Fix:</strong> Replaced free-text boxes with native time pickers and introduced <strong>barcode scanning and voice input</strong> for effortless data entry.</li></ul><h4>Iteration 3: Seamless Inventory Integration</h4><ul><li><strong>Problem:</strong> Managing medication stock felt like a disconnected, tedious chore.</li><li><strong>Fix:</strong> Automated stock control. Marking a medical task as completed automatically deducts the dose from the inventory, triggering a refill alert before supplies run out.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4X7KrHuDjBCcBp9L4LrKA.png" /></figure><h3><strong>Key Features in High Fidelity</strong></h3><h4>1. Chronological Daily Timeline</h4><p>A clean, visual overview showing what’s done and what’s left for the day, eliminating doubt and cognitive load.</p><h4>2. Flexible Data Entry (Barcode &amp; Voice)</h4><p>Add new habits or medications without typing long forms: just scan a medicine box or speak to the assistant.</p><h4>3. Customizable, Guilt-Free Tone</h4><p>Users can choose the voice tone of their alerts (motivational, neutral, or serene) and set preferred notification modes (sound, vibration, or silent). No punitive messages or broken streak warnings if a habit is skipped.</p><h3><strong>Impact &amp; Key Takeaways</strong></h3><ul><li><strong>Respecting Mental Space Matters:</strong> Designing “quiet” software that doesn’t scream for attention actually increases user retention and task completion.</li><li><strong>Context Over Features:</strong> Adding automated inventory tracking turned a passive reminder app into a reliable medical assistant.</li><li><strong>Flexibility Prevents Abandonment:</strong> Giving users autonomy over notification tones and interaction depth prevents the guilt cycle that leads to app deletion.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEQPWuWCHy135wvIZ8_Kig.png" /></figure><p>Designed by:<br>Santiago Andrés Mugueta — UX/UI &amp; Multimedia Designer<br>Agustina Córdoba — UX/UI &amp; Industrial Designer.</p><p><em>Thank you for reading! If you’d like to inspect the visual design and UI components, check out the project on </em><a href="https://dribbble.com/shots/27717376-Miru-Habits-and-lifestyle-app"><em>Dribbble</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87b5ee7cdf87" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>