<?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 Howdyunnatidixit on Medium]]></title>
        <description><![CDATA[Stories by Howdyunnatidixit on Medium]]></description>
        <link>https://medium.com/@howdyunnatidixit?source=rss-e52a86fdf278------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8P-JEQkh9vlwgix1</url>
            <title>Stories by Howdyunnatidixit on Medium</title>
            <link>https://medium.com/@howdyunnatidixit?source=rss-e52a86fdf278------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:26:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@howdyunnatidixit/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[InclusiCare App : Where Telemedicine Meets Accessibility, Empowering Users with Disability — a UX…]]></title>
            <link>https://medium.com/@howdyunnatidixit/inclusicare-app-where-telemedicine-meets-accessibility-empowering-users-with-disability-a-ux-31b74a4ba0b6?source=rss-e52a86fdf278------2</link>
            <guid isPermaLink="false">https://medium.com/p/31b74a4ba0b6</guid>
            <dc:creator><![CDATA[Howdyunnatidixit]]></dc:creator>
            <pubDate>Thu, 22 May 2025 08:03:40 GMT</pubDate>
            <atom:updated>2025-05-22T08:03:40.233Z</atom:updated>
            <content:encoded><![CDATA[<h3>InclusiCare App : Where Telemedicine Meets Accessibility, Empowering Users with Disability — a UX case study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-jt9e7AdXRAs7n1xH_6WQQ.png" /></figure><h3><strong>Background:</strong></h3><p>I remember one time when I was traveling in a foreign country and I tried to order food at a restaurant. I didn’t speak the local language, and the waiter didn’t speak English very well. We ended up just pointing to pictures on the menu, and I ended up with a dish that I didn’t really enjoy. It was a frustrating experience, and I felt helpless and embarrassed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kTMczO0KJ1zM5sx_UCbM0A.jpeg" /><figcaption>Source-Frame order Youtube</figcaption></figure><p>Just as trying to order food in a foreign language can be frustrating and challenging for someone without a disability, <strong>imagine the struggles that people with disabilities face daily in trying to communicate their needs and wants.</strong></p><blockquote>A communication barrier results when people are unable to hear, speak, read, write or understand information as it is available to them.</blockquote><blockquote><strong>This Communication barriers can become a more significant obstacle for people with disability.</strong></blockquote><h4>Telemedicine’s Communication Hurdles:</h4><p><strong>How It Affects Healthcare for People with Disabilities</strong></p><p>Telemedicine, the cool way of getting healthcare from the comfort of your own home, has opened up a whole new world of possibilities for people with disabilities. No more battling traffic or waiting in crowded clinics! But sometimes, the virtual nature of telemedicine can make it tricky to communicate effectively, <strong><em>especially for people with disabilities</em></strong></p><blockquote><strong>Imagine already having less time with the doctor, and then having to face all these barriers just to communicate.</strong></blockquote><p>This communication gap can have a significant impact on the patients with disabilities. <em>If the doctors are unable to understand their symptoms or problems, the patients might end up with the wrong diagnosis or treatment .</em></p><p>Therefore, doctors need to get training on how to communicate effectively with people with disabilities. Moreover, <strong>the patients with disabilities should be provided with more options for communication when using telemedicine.</strong></p><h3><strong><em>The Problem</em></strong></h3><p>COVID-19 made telemedicine popular — and in many cases, necessary. Unfortunately, Apps and websites providing these Telemedicine services are inaccessible to those who need them most — <strong>people living with a disability</strong>. This has created a digital divide, leaving this segment of the population struggling to navigate the virtual healthcare.</p><h3>Solution preview</h3><p>I designed an accessible Telemedicine app called Inclusicare, for people with disabilities, that makes healthcare more accessible than before and curated based on each disability type.</p><p>Features provided in solution</p><h4><strong>1. Screen reader compatible</strong></h4><p><strong>Problem</strong>- Blind and visually impaired people rely on screen readers to read out text and visual information, but telemedicine apps in market are <strong>incompatible with screen reader</strong>.</p><p><strong>Solution</strong>- To make this app screen reader compatible, following steps were taken:</p><ul><li><strong>Added Logical hierarchy and structure- </strong>Made the headings, subheadings, and landmarks more organized to help people who use screen readers find their way around the app and understand what’s going on.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><ul><li><strong>Provided Descriptive Text Labels</strong>: Clear and concise text labels were provided describing the purpose and function <em>for all interactive elements, including buttons, links, form fields, and images</em>, enabling screen reader users to understand the app’s layout and interactions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><ul><li><strong>Provided Alternative Text for Images</strong>: Alternative text descriptions <strong>for all images and non-text content</strong> is provided. These descriptions provide a detailed and meaningful representation of images, allowing screen reader users to grasp the context and information conveyed by images.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><h4><strong>2. Followed</strong> <strong>WCAG Contrast Ratio Guidelines</strong></h4><p><strong>Problem-</strong>A lack of contrast between an app’s background and text color can make it challenging for those with poor eyesight to distinguish elements, including icons and placeholder text.</p><p><strong>Solution</strong>-To ensure that text was clearly distinguishable from its background. For normal text, a contrast ratio of at least 4.5:1 is maintained, while for large text, a contrast ratio of at least 3:1 is maintained.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><h4><strong>3. Colour blind friendly</strong></h4><p>Problem- It’s common to use red to represent errors, but some people who are colorblind will not be able to see it.</p><p><strong>Solution</strong>-Icons and text were also provided in addition to color clue to solve this problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><h4><strong>4. Compatible with keyboard navigation</strong></h4><p><strong>Problem- </strong>User who have mobility/dexterity challenges, they may use on keyboards or alternative input devices, but apps are not compatible with keyboard navigation</p><p><strong>Solution</strong> — App is made to be keyboard accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><h4>5. Provided Live Sign language interpreter for users who have hearing and speech impairment + Live captions are provided for users who are hard of hearing</h4><p><strong>Problem</strong>- User who are deaf/ mute use sign language to communicate, and most of the Doctors can’t interprete signlanguage, thus leading to communication barrier.</p><p><strong>Solution-</strong></p><ul><li>App provides custom feature for patients as per their need, and provide Signlanguage interpreter to ease the process for users with hearing impairment.</li><li>Live captions are provided during the call with Doctor.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><h4>6. Video and audio recordings of consultations, along with transcripts, are available for patient’s convenience in the format they prefer.</h4><p>Problem- Patients occasionally miss crucial information during calls and express the need to revisit specific details.</p><p>Solution- To address this concern, Video and audio recordings of consultations, along with transcripts, are made accessible to patients in the format of their preference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORg20Opq1VR2K6mNjjlqsw.png" /></figure><h3><strong>Design process</strong></h3><p>To solve accessibility problems that users experience with telemedicine apps, I followed Design thinking design process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_Ub_vfSi5kAK6pzuCtVgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yaH_WF3pIn_q376QWRNgJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9_e34AO2EYzPdZvwgtAJQ.png" /></figure><h3>Research</h3><p>Before diving into research, I started with creating a <a href="http://fc/">research plan</a> that outlined research goals, assumptions, questions, and methodologies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*66gugZ1CHfIHFYmAMxwZlw.png" /></figure><p>Data were generated using three research methods —</p><ul><li>Literature review</li><li>User interviews</li><li>Competitive analysis</li></ul><h3>Literature review</h3><p>Goals:-</p><ul><li>Understand about accessibility and scope of telemedicine.</li><li>Learn from existing research related to this topic.</li><li>Identify gaps in existing research</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dS8z6NVbjhC2RPaKEAI1ag.png" /><figcaption>Key insights from literature review</figcaption></figure><h3>User interview</h3><p>Armed with insights from literature review, I decide to conduct online user interviews, as I want to talk to real users and know their firsthand experience with telemedicine apps.</p><p>Here You can check <a href="http://dd/">interview guide</a>, and detailed <a href="http://sss/">research findings</a>.</p><p>Interviews generated a lot of information, so to make sense of it all, I created <a href="http://ff/"><strong>affinity map</strong></a>, which combines all the data points from my interviews to extract important patterns and insights.</p><h3>“Edit people to person in below image”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lm969JPyOZOeTKVINfadEQ.png" /><figcaption>Interviewee demographics</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8chQfpiphAzxkCHSgyZwWw.png" /><figcaption>Key insights from user interview</figcaption></figure><h3>Competitive analysis</h3><p>Goals:-</p><ul><li>To find strengths &amp; weaknesses of direct and indirect competitors.</li><li>Identify any gaps and opportunities that “Inclusicare app” might address.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*At5GDSNc541teUOkYawieQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K0RpwZmPiDwwRdN40qdGtQ.png" /><figcaption>Key insights from competitive analysis</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4bXHGxMt0k-Q6075Qi-HA.png" /></figure><blockquote>As I move forward in the design process, it’s natural to forget some of what I learned in the discovery phase about user, That’s where I use <strong>Personas (Someone with the shared characteristics of my interviewees)</strong> After having a clear portrait of who target users are, I created the user persona to represent their emotions, pain points, needs, goals, and motivation.</blockquote><h3>Meet Seema</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*owdN4un57u6x_n72" /><figcaption>Persona</figcaption></figure><h3>Framing the Problem</h3><p>With the Insights achieved from the research phase, I created <a href="http://cc/">POV (Point of View ) statements</a> that summarise user’s needs and later converted them into <a href="http://bb/">HMW (How Might We) questions </a>to kickstart brainstorming.</p><p>I decided to work on this <strong>How might we Question-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WC_34fJW1pIYs9OdrMPsOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hh3a5emrc5hRjgbb5rhoeQ.png" /></figure><h3>Brainstorming for solutions</h3><p>Lots of ideas were generated during brainstorming sessions. If it interests you, <a href="http://ff/">click here</a> to see all ideas generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*csK6boeaKYfwpGbNnU5pCA.png" /></figure><h4>Selecting top ideas from pool of ideas.</h4><p>It was a challenge to select just few ideas after brainstorming session, but I select ideas <strong><em>on the basis of it’s potential to impact my target users positively, backed up by my research, and it’s feasibility.</em></strong></p><h3>Project goal</h3><p>After clearly understanding users’ goals, I revisited the business goal &amp; wrote down some technical considerations. I write out project goals to understand the intersection between <em>business, user goals and technical goals.</em></p><p>This helped me gain complete clarity and align all parties involved<strong> before making feature decisions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8w8iwnTKmDNTruI7P-YRxQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ap2WAE2gP9BkXmMaRX1KbQ.png" /></figure><h3>Features Road map &amp; Prioritisation</h3><p>From here, I was able to create what’s called a <em>feature roadmap</em>, which is a checklist of features Inclusicare app will have and have ranked them in their order of importance.</p><blockquote>I avoid letting desires for features trumps over user needs.</blockquote><blockquote><strong>The features were prioritised based on impact vs cost.</strong></blockquote><p>The features are sorted into 4 categories, including–</p><ul><li><strong>Must-have (P1)</strong></li><li><strong>Nice-to-Have (P2)</strong></li><li><strong>Delightful (P3)</strong></li><li><strong>Can-wait (P4)</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVv00TK1Xhpmj2qpBck0OQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_TkDab8gUA9hqntoVpmitw.png" /></figure><h3>Information architecture</h3><p>Now comes next step<em>- sitemap.</em> This is how I organize our site/app structurally, labeling each page and where it exists in relation to others, I develop information architecture at this point:</p><blockquote>My method was to identify all of the items you’d see on a specific page, and indicate a clear call to actions. The two sitemaps below represent two different journeys a user can take when visiting the app. The first is the journey a user would make when booking appointment, and the other is journey a user would make while consulting.</blockquote><h4><strong>Information architecture of Booking journey</strong></h4><h4>Information architecture of Consulting journey</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ccvknT-VEXGs1m70ho3yBw.png" /></figure><h3>Sketching the ideas- Low fidelity wireframes</h3><p>Taking what I’ve learned throughout my process to this point, I sketched out the screens by using pencil and paper.</p><p>Doing this help me layout content quickly and try out multiple ideas without the barriers of technical tools. Then I took feedback and iterated it accordingly.</p><p>Below you can see paper sketches:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OTiG4rq9wj-FgEaR0Gbq3g.png" /></figure><h3>Mid fidelity wireframes</h3><p>Now that I had an idea of which direction I would pursue from sketching and feedback sessions, I converted Low fidelity sketches into Mid Fidelity digital wireframes in Figma to prepare for prototyping and testing in later stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dRzxEv3CcdRzFf-IA6Cc4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAhfNFt3eZz3MjZx2yCZJw.png" /><figcaption>Wireframing journey</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*trir8asJP26PqaLxu1B4Fw.png" /><figcaption>Wireframing journey</figcaption></figure><h3>Logo and Branding</h3><p>Before diving into the UI design, I took a step back to brainstorm the the brand’s attributes, and its overall identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnO5Kbf-Ofvd8oiBX4AqjA.png" /></figure><blockquote>I first came up with Brand name- <strong>InclusiCare </strong>which is combination of the words “inclusion” and “care,” <strong>e</strong>mphasising the app’s mission to provide inclusive and accessible telemedicine services for people with disabilities.</blockquote><p>Since <strong>brand value is to convey trust, inclusion, calmness and reliability</strong>, It was essential to bring a positive, trustful feeling to appeal to and encourage users. I then created a mood board in which I put ideas, concepts together to set the direction of the new branding.</p><p>I sketched lots of options for logos:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S-vqyWlzLujRidmYANmcrw.png" /></figure><blockquote>The <strong>blue colors</strong> is associated with trust, reliability, and inclusion, which are important qualities for a telemedicine app. The<strong> heart symbol</strong> represents compassion and care, while the <strong>shaking hands</strong> suggest representing Inclusicare’s commitment to providing assistance and support to people with disabilities.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/0*kSCVs5dfuAd7_Aca" /></figure><h3>UI kit</h3><p>Next, I created UI kit to act as a reference document and ensure consistency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BeepPJ83oMVtQqpxl-KPVA.jpeg" /></figure><h3>High Fidelity design</h3><p>With the visual style defined for the UI design and wireframes ready, it’s time to put things together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFjyTrPXLntXU2opmoQGbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zAjz8D6ApAJKgARwq0JqUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VLUxDg3kUQYtEYbmAJ3IA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DcASg6S6PSA0AdxDmmqYhQ.png" /></figure><h3>Turning wireframes into High fidelity Prototype</h3><p>You can check working prototype <a href="http://cc/">here</a></p><blockquote><em>I learnt that it’s better </em><strong>to test early and as often as possible. </strong>It reduces friction, eliminate errors, and uncover mistakes and false assumptions. Thus saves time, money, resources, and your sanity.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8keHjMgAmSWVdO-NleLhQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RfqLtLSNdvqMGd0Enry0yA.png" /></figure><h3>Usability testing</h3><p>With the Prototype ready, next is to test the product directly with customers to measure its effectiveness.</p><p>I started with preparing a <a href="http://dd/">Usability test plan</a> which includes objectives, success metrics, core tasks for users to complete and script for the moderated sessions.</p><p>Following my usability test plan, I conducted moderated usability test with participants <strong>( Sadly, I couldn’t recruit people with disability for usability testing due to unavailability )</strong></p><blockquote>Instead of explaining to them what my app does and how it works, I let them figure it out!</blockquote><h3>Affinity Map</h3><h4>Finding patterns to make improvements</h4><p>After the research, I transferred the information from interview session into the digital post-it note. Then, I created an affinity map to synthesize the finding. By doing this, I was able to document the research findings and uncover the issues in my designs and help to determine on the prioritization for revise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HXXDnrfsGuRrktvsRKFUGQ.png" /></figure><h3>Revise Design</h3><p>After identifying the pain points from the affinity map and considering how much work it would take and how much it would benefit users, <strong><em>I began by fixing the screens that were stopping users from finishing the main tasks. Then, I worked on improving the screens that users didn’t like.</em></strong></p><p>Refer to below image and annotations for understanding .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*eT6LE3uLHjDJlaop_XJmIg.jpeg" /></figure><h3>Final Prototype</h3><h3>Reflection</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31b74a4ba0b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QuickCompare: Changing the Way India Compares Grocery Prices]]></title>
            <link>https://medium.com/@howdyunnatidixit/quickcompare-changing-the-way-india-compares-grocery-prices-90219b1c01a9?source=rss-e52a86fdf278------2</link>
            <guid isPermaLink="false">https://medium.com/p/90219b1c01a9</guid>
            <dc:creator><![CDATA[Howdyunnatidixit]]></dc:creator>
            <pubDate>Fri, 02 May 2025 08:23:19 GMT</pubDate>
            <atom:updated>2025-05-02T08:23:19.925Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a <strong>live project </strong>— You can check out the website here → <a href="https://quickcompare.in/">quickcompare.in</a></p><p>Duration: 2 months</p><p>Role: Product designer</p><p>Team: Product designer, Developer, Founder</p><h3>Overview</h3><p>This project started as a personal exploration into the everyday problem of comparing grocery prices across quick commerce apps. While researching user frustrations, I got the opportunity to work with <strong>QuickCompare</strong> <strong>— a startup</strong> building a solution in the same space. I joined their team to help design and refine the app experience ahead of launch.</p><p>This live project involved <strong>working within real business and technical constraints</strong> to build a tool that helps users compare grocery prices across platforms with accurate, real-time data.</p><p>The app has now launched, and this case study reflects my contribution to shaping the product experience.</p><h3>About the Client</h3><p><strong>QuickCompare</strong> is an early-stage <strong>startup focused on simplifying grocery price comparison</strong> across India’s growing quick commerce market. When I joined, the team had a basic framework and early feature ideas in place, but the user experience needed clarity, consistency, and scalability.</p><p>I collaborated closely with the founder and developer to shape the product experience — from refining key user flows to designing new features that would support a successful launch.</p><h3><strong>Problem</strong></h3><p>In urban India, apps like Blinkit, Zepto, Instamart, and BigBasket often sell the same groceries — but at different prices. To get the best deal, shoppers switch between multiple apps, comparing prices item by item to save money. It’s a time-consuming, tedious and tiring process that leads many to give up and just order without comparing.</p><h3>The Users</h3><p>The primary users were working professionals, busy parents, and everyday shoppers in Indian cities who frequently use apps like Blinkit, Zepto, Instamart, and BigBasket for quick grocery deliveries.</p><p>They often juggle between apps to find better prices, but don’t always have time or energy for detailed comparisons.</p><h3>Solution</h3><p>We designed QuickCompare — an app that helps users<strong> instantly compare grocery prices </strong>across platforms, see <strong>which app delivers the fastest</strong>, check <strong>real-time stock availability</strong>, and <strong>open products directly in the app of their choice </strong>— all in one place.</p><h3>My Responsibilities</h3><ol><li>Designed key screens such as <strong>onboarding,</strong> <strong>home</strong>, and <strong>how users compare prices in the app</strong>.</li><li>Created a short <strong>launch video using Adobe After Effects </strong>to explain the app’s value.</li><li>Designed <strong>app store assets</strong> (screenshots and promotional banners) to support the launch</li><li>Designed the <strong>app’s loader screen</strong> to keep the experience smooth and branded</li><li>Conducted <strong>usability testing and iterated designs</strong> based on real user feedback</li><li><strong>Collaborated closely with the founder and developer</strong> throughout the project to align design with product goals and technical feasibility</li></ol><h3>Impact</h3><ol><li><strong>100K+ downloads</strong> on the Play Store</li><li>🔥 Ranked in the <strong>Top 5 Trending Apps</strong> in India after launch</li><li>Featured in <a href="https://www.thehindubusinessline.com/companies/quick-or-commerce-price-comparison-apps-put-consumers-loyalty-to-test/article69238360.ece">The Hindu Business Line</a></li></ol><h3>Research</h3><h3>Understanding the market</h3><p>In recent years, grocery shopping in India has shifted from monthly ordering to instant ordering. With platforms like Blinkit, Zepto, Instamart, and BigBasket, users now expect groceries to arrive within minutes — and often use more than one app.</p><p>These platforms compete on pricing , delivery speed, product variety, and app experience. Discounts change frequently. Prices vary across regions. And with no single leader in the space, users are constantly switching between apps based on what feels like the best deal.</p><p>To design something useful, I first needed to understand how users were actually shopping.</p><h3>Identifying key competitors</h3><p>To understand how others are solving this problem, I studied both <strong>direct and indirect competitors</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqaWfoda0YAjFUA3yxQRtQ.png" /><figcaption>Feature analysis</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yvquswbht_Prjj55FzRkMg.png" /></figure><h3>Key Takeways:</h3><p>I discovered that while the existing platforms highlighted many features important to people hoping to work at a listed location, these platforms were lacking in many ways.</p><p><strong>Gaps &amp; Limitations in Competitor Apps</strong></p><ol><li><strong>No real-time price or stock data</strong><br> Some apps display <strong>outdated prices</strong> or don’t clearly show when items are <strong>out of stock</strong>—causing frustration and wasted time.</li><li><strong>Most apps don’t show price comparisons upfront</strong><br> In most apps, users can’t see prices for the same product across platforms in one place. Instead, products are listed under each app separately — like one section for Blinkit, another for Zepto — and not grouped by item. To compare prices, users have to manually search for the same product in each app listing— which makes the whole process slow and frustrating.</li><li><strong>Cognitive load is high</strong><br> Users have to remember prices or manually go back and forth between listings.</li><li><strong>Missing delivery time info</strong><br> Most platforms don’t show which app can deliver the fastest for that product- which is important deciding factor when user make a purchase</li><li><strong>Forced ads break flow</strong><br> Non-skippable ads from third-party networks often block users from continuing, with no option to exit early.</li></ol><h3>Gathering data through user interviews</h3><p>To understand how people compare grocery prices across apps, I spoke with 4 users who regularly order from platforms like Blinkit, Zepto, Instamart, and BigBasket.</p><blockquote>Two of the interviews were conducted remotely, <strong>where participants shared their screens and walked me through their real process of comparing prices</strong>. The other two were conducted through <strong>open-ended conversations</strong> to understand their habits, frustrations, and decision-making.</blockquote><p>I wanted to learn:</p><ul><li>How they compare prices</li><li>What steps they take before placing an order</li><li>What makes the process feel easy — or frustrating</li></ul><p>After the interviews, I used <strong>affinity mapping </strong>to group similar behaviors, pain points, and frustrations. This helped me identify key patterns that would guide the design direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ebs9p3Ln6q2a0tN8S4HUGw.png" /><figcaption>Affinity mapping</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmqiD7_mqHvfC5WyOnBTvQ.jpeg" /><figcaption>Affinity mapping</figcaption></figure><h3>Key Insights from User Interviews</h3><p>Based on interviews, 5 key themes emerged from user behaviors and frustrations:</p><p><strong>1. Manual price comparison is mentally exhausting<br></strong> Users often switch between multiple apps, tabs, and even use calculators just to figure out which platform is cheaper — and it drains their time and energy.</p><blockquote>“I’m constantly flipping between apps and doing the math in my head. It shouldn’t be this hard to save a few rupees.”</blockquote><p><strong>2. Splitting the order manually is a major pain<br></strong> While users aim to save money by purchasing items from different apps, the process of splitting orders manually — considering delivery fees, minimum order values, and coordinating deliveries — is overwhelming.</p><blockquote><em>“I have to think: is it even worth splitting? Will I end up paying more in delivery charges? It’s just too much to calculate every time.”</em></blockquote><p><strong>3. Inaccurate prices quickly break trust<br></strong> In comparison apps, accuracy is everything. When users see outdated or wrong prices, they lose confidence — and stop using the app altogether.</p><blockquote>“I downloaded it to save money, but the prices were completely off. What’s the point of a comparison app if the info isn’t even accurate?”</blockquote><p><strong>4. Users prefer per-unit pricing for fair comparison<br></strong> Users appreciate when apps show unit-based pricing (Price per litre, kg, or piece). It helps them compare products of different sizes or quantities without doing the math themselves. When this isn’t shown, comparison becomes frustrating.</p><blockquote>“I have to buy diapers in bulk for my baby. When one pack has 76 Diapers and another has 228, seeing the price per diaper makes the decision so much easier.”</blockquote><p><strong>2. Price isn’t everything — trust plays a big role<br></strong> When price differences are small, users often stick with the app they trust — based on past delivery and return experience, or customer support.</p><blockquote>“I like BigBasket because they take returns easily and provide refunds even faster. Their customer support is great, so I feel safe ordering from them”</blockquote><h3><strong>User journey map</strong></h3><p>I created a <strong>user journey map</strong> to visualize how users currently compare grocery prices across apps. It shows where the process becomes confusing, repetitive, or frustrating — and helped me identify real opportunities to reduce effort and improve clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hfUNw-e_Sna73y8Ev8mgWw.png" /></figure><h3>User Needs Identified</h3><ol><li><strong>Spend less time and effort</strong> comparing grocery prices</li><li>Get <strong>real-time</strong> accurate prices , availability and delivery information.</li><li>Users need a simpler way to <strong>split their order across apps </strong>to get the best savings with minimum effort.</li><li>Users need a way to quickly identify which option gives them the best value, regardless of pack size or brand.</li></ol><h3>Framing the Problem</h3><p>With a clearer picture of user struggles, I turned the main pain points into “How Might We” questions. This helped me stay open to ideas — while making sure I was solving the right problem. From the options I explored, I chose to focus on the one that felt most impactful and aligned with user priorities.</p><blockquote>How might we make it easier and faster for shoppers to compare grocery prices online — so they can feel confident they’re getting the best deal?</blockquote><h3>Heuristic Evaluation of the Team’s Initial Wireframes</h3><p>When I joined the QuickCompare team, the product wasn’t live yet — but the team had already built a set of <strong>rough wireframes and early screen flows</strong> to visualize the core idea.</p><p>These screens served as a starting point, but hadn’t been tested or reviewed for usability. So before jumping into design work, I conducted a <strong>heuristic evaluation</strong> to identify usability issues, align the experience with user expectations, and prioritize what needed redesigning.</p><blockquote><strong>The home screen didn’t clearly communicate that QuickCompare was a price comparison app.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SpIzSSPWDxOs5foCZ8_GgQ.png" /><figcaption>Heuristic evaluation-Home screen</figcaption></figure><h4>📸 HEURISTIC ANALYSIS OF PRODUCT LISTING NEEDED?? Persona needed??</h4><h3>Developing a site map</h3><p>After deciding what features to prioritize and include for the MVP, I created a site map to help define the overall content structure of the app along with the relationships between different screens and features.</p><blockquote><em>The goal was to keep navigation simple and logical, helping users quickly compare prices without feeling confused or overwhelmed during the comparison</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gNvbNJhIbm1UUDIOE978Nw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FxnysVBI7MHJJLKCM9PC8Q.jpeg" /></figure><h3>Technical Constraints</h3><ol><li><strong>Prioritizing the Key Screens for Launch</strong></li></ol><p><strong>Because of the tight launch timeline, we concentrated on the highest-impact areas</strong>: designing the home screen, price comparison flow, and onboarding. Advanced features like sorting, filtering, and saved carts were intentionally set aside for future updates.</p><p>2. <strong>Speed over Perfect UX</strong></p><p>With limited time, we prioritized clear, usable flows over perfecting every microinteraction, animation, or screen detail. <strong><em>The goal was to deliver a simple, intuitive experience quickly, and keep improving it in later versions.</em></strong></p><h3>Early Sketches and Exploration</h3><p>I sketched different ideas to quickly explore options, get team feedback, and choose the best direction before moving forward.</p><p>📸📸</p><h3>Home screen</h3><p>The Client shared that users should immediately understand what the app is for when they land on the home screen.</p><blockquote><em>In the earlier wireframe version, it wasn’t clear that this was a grocery price comparison app. There was no messaging or visual cue to guide first-time users.</em></blockquote><p><strong>So I redesigned the home screen to:</strong></p><ul><li><strong>Add a clear message about what the app does</strong></li><li><strong>Highlight the main call-to-action</strong></li><li><strong>Make the experience feel purposeful from the start</strong></li></ul><p>This helped set the right expectation from the first moment and reduced user confusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rL8x2IBFRaTKRe9-_HqYAw.png" /><figcaption>Home screen exploration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wdNbGyk22Cg5kacnjBd7fA.png" /></figure><h3>Product listings</h3><p>Based on user insights, we knew that people wanted to compare grocery prices quickly, easily, and without confusion.</p><p>To support that, we made key design decisions on the <strong>product listing screen</strong>:</p><ul><li><strong>Prices across all apps are listed upfront</strong> under each item — no extra taps or digging</li><li><strong>Delivery time is shown clearly</strong> for each app, with color-coded icons (green = fastest) so users can decide faster</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/539/1*2Lt13YHDvtdoWrla8gb9ig.png" /><figcaption>Color coded Delivery time</figcaption></figure><ul><li><strong>Items are auto-sorted by lowest price</strong> — users don’t need to do any manual sorting to find the cheapest option</li><li><strong>Filters work as de-selections</strong> — all apps are selected by default, and users can easily remove any app they don’t want to compare</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*-lCtU__75Y9o7KHIYqN4xQ.png" /><figcaption>Color coding of Delivery time</figcaption></figure><h3>Product detail page</h3><blockquote>On the product details page, we noticed that users were trying to tap on the <strong>product image</strong> to go to the respective grocery app — instead of tapping on the <strong>price or app name</strong>.</blockquote><p>Since the image wasn’t clickable, this caused confusion and drop-offs.</p><p>So we updated the design to make the app cards clearly tappable — reducing frustration and making the flow feel smoother.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-h6s-9Sk0SK8vzwpBLicQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Ex5XjWlwAc5PJgNYfu34Q.png" /></figure><h3>Onboarding screens</h3><p>Before I started designing the onboarding flow and app store visuals, the founder shared <strong>4 key value props </strong>the app had to communicate clearly from the first screen:</p><ul><li><strong>Compare prices instantly</strong> — so users don’t have to switch between multiple apps</li><li><strong>Show real-time prices</strong> — not old or outdated data</li><li><strong>Tell what’s in stock</strong> — and where it’s not</li><li><strong>Highlight delivery speed</strong> — so users know who can deliver fastest</li></ul><p>These points helped me keep the onboarding simple, clear, and focused on what makes the app useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rypkHbA2J9yKmG2rsHZcxg.png" /></figure><h3><strong>The Launch Video</strong></h3><p>To support the app’s launch and clearly communicate its value, I created a short motion video using Adobe After Effects. The goal was to visually explain how QuickCompare works and why it saves users time — in under 30 seconds.</p><blockquote>I created several versions of the launch video, refining it through feedback to ensure the message was clear and engaging.</blockquote><blockquote><strong>The final version was used for app store listings and social media promotions.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*WTF2Pv4pk87_6tTkGnXW4w.gif" /></figure><h3>The Loader</h3><blockquote>Since price comparison takes a few seconds to fetch real-time data from multiple apps, we needed a loader screen to keep users informed and reduce drop-off.</blockquote><p>I designed a <strong>clean, branded loader screen that reassured users the app was working — and that prices would be shown shortly.</strong> It helped set expectations and made the short wait feel intentional, not broken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zh8t5_RRJs9i3u2mrxwhvg.gif" /></figure><h3>High Fidelity Prototype</h3><p>📸📸</p><h3>What I learned</h3><ol><li><strong>User Research in a Startup = Fast + Flexible</strong></li></ol><p>In a fast-moving startup, there’s <strong>rarely budget and time for big formal research.</strong> I learned <strong>how to get quick, useful insights</strong> by doing casual screen shares, lightweight interviews, and feedbacks— enough to move forward without getting stuck.</p><p>2. <strong>Progress Over Perfection</strong></p><p>I learned that <strong>showing rough ideas early, getting feedback, and improving step-by-step </strong>was much better than trying to design something perfect in isolation — <em>because isolation often leads to wasted time, missed feedback, and bigger rework later.</em></p><p><strong>3. MVP First — Polish later</strong></p><p>I learned that it’s better to <strong>launch a simple, working version first </strong>than get stuck perfecting every detail. Startups need to ship, test, and improve — not chase a “perfect” design that might never go live.</p><p>4. <strong>What you design isn’t always what can be built</strong></p><p>Working closely with developers taught me that technical limits are real. I learned to adapt my designs to what was feasible, without losing sight of the user experience.</p><p><strong>5. Business goals shape design decisions</strong></p><p>I realized that good UX isn’t just about making users happy — it also has to support business needs. I had to balance what users wanted with what the business needed to grow.</p><p><strong>6. Design for the Worst-Case Too</strong></p><p>It’s easy to design for the “happy path,” but real users don’t always behave the way you expect. <strong>I learned to think ahead and design for the rough situations, not just the perfect ones.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90219b1c01a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Total Price Comparison Feature for QuickCompare App]]></title>
            <link>https://medium.com/@howdyunnatidixit/designing-a-total-price-comparison-feature-for-quickcompare-app-39bda2e8ff77?source=rss-e52a86fdf278------2</link>
            <guid isPermaLink="false">https://medium.com/p/39bda2e8ff77</guid>
            <dc:creator><![CDATA[Howdyunnatidixit]]></dc:creator>
            <pubDate>Fri, 04 Apr 2025 10:17:42 GMT</pubDate>
            <atom:updated>2025-04-27T09:19:17.047Z</atom:updated>
            <content:encoded><![CDATA[<p>· <a href="#6f57"><strong>What is QuickCompare?</strong></a><strong><br>· </strong><a href="#579c"><strong>What Happened After We Launched QuickCompare?</strong></a><strong><br>· </strong><a href="#0df9"><strong>The Most Requested Feature</strong></a><strong><br>· </strong><a href="#9ecd"><strong>What Users Asked For vs. What They Actually Needed</strong></a><strong><br>· </strong><a href="#2e33"><strong>Evaluating the Effort vs. Impact</strong></a><strong><br>· </strong><a href="#e868"><strong>How Competitors Tackle this problem</strong></a><strong><br>· </strong><a href="#cf6c"><strong>Defining the Right Problem</strong></a><strong><br>· </strong><a href="#c0d0"><strong>Initial Ideas and Sketches</strong></a><strong><br>· </strong><a href="#08fb"><strong>Design Challenges We Faced</strong></a><strong><br>· </strong><a href="#2f96"><strong>The Goal</strong></a><strong><br>· </strong><a href="#f71a"><strong>Iterations and What Didn’t Work</strong></a><strong><br>· </strong><a href="#d575"><strong>The Final Version We Launched</strong></a><strong><br>· </strong><a href="#e99a"><strong>What We’d Improve Next?</strong></a><strong><br>· </strong><a href="#314a"><strong>What I Learned from This Project</strong></a></p><h3>What is QuickCompare?</h3><p>QuickCompare is a mobile app that helps users compare grocery prices across India’s top quick-commerce platforms — Zepto, Blinkit, Swiggy Instamart, Flipkart Minutes, and more.</p><p>Users can search for any grocery item and instantly see which app offers the best price — without switching between apps manually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*XgG_Z3i_xEoZBdgNibfT9w.png" /><figcaption><em>Search results page showing price comparison for the same item across multiple apps.</em></figcaption></figure><p>I worked on designing one of the most requested features:</p><p><strong><em>“Total price comparison for an entire grocery list”</em></strong></p><h3><strong>What Happened After We Launched QuickCompare?</strong></h3><p>When QuickCompare App<strong> </strong>launched, it struck a chord with Indian shoppers.</p><p>In a world where Zepto, Blinkit, Swiggy Instamart, and Flipkart Minutes promise groceries at your door in under 10 minutes, price became the real battleground. Every app had its own deals and discounts. Users could save a surprising amount — <em>if they knew where to look.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*2p4CycDqw7SiZIM0jG92Vg.png" /><figcaption>How Quick Compare works</figcaption></figure><blockquote><strong>Within days of launch, users were buzzing about how much they saved by comparing</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AAf1r3pOj6fr1F4Fq8DI_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WzJr_y8aLAFmsboSb2E4Aw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUxrMxXvC0gBGNcROnGr3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xf4jPpJPYuz-gIqF4yxy1g.png" /><figcaption>Reactions to QuickCompare App launch</figcaption></figure><h3><strong>The Most Requested Feature</strong></h3><p>As users began using QuickCompare regularly, one repeated request popped up across Reddit, Twitter, Instagram and feedback forms</p><blockquote><strong>“Can you show me the total price of all my items in one go? I want to know which app is cheapest for my whole list.”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y_tqtsTmip4FsCxwAV474A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cT6zUatKkRXoEN3l2xzbMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6IJlpMCKWpxsu8_jeVK5Uw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TlMjWrzTfCf1VC-3mRTnZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bsud-PzA3X7E_fZ6OQWX_Q.png" /></figure><p>This wasn’t just a casual request — it was repeated often, across channels, and became impossible to ignore.</p><h3><strong><em>What Users Asked For vs. What They Actually Needed</em></strong></h3><h4>Understanding the real problem</h4><p>We knew what users were asking for. But we needed to understand <strong>why</strong>.</p><p>Was this just a nice-to-have? Or a real problem worth solving?</p><p><strong>At first, the request sounded simple:</strong></p><blockquote>“Can you show me the total price comparison between apps for all my items? I just want to know where I’ll save the most.”</blockquote><p>Since many of our friends and family members were facing the same problem, we decided to do quick user interviews — and also observe a few of them over video calls.</p><blockquote>We asked them to share their screen and walk us through how they usually compare prices and make decisions across apps. Along the way, we asked questions to understand where they got stuck and what influenced their final choice.</blockquote><p>📸 <em>(Photo of participant and me)</em></p><h4><strong>That’s when we saw the real problem.</strong></h4><h4>🧠 In theory…</h4><blockquote>Users could save the most by buying each item from the app where it’s cheapest.</blockquote><blockquote>Example:</blockquote><blockquote>Let’s say <strong>Ravi</strong> is comparing prices for his 6-item grocery list:</blockquote><blockquote><strong>- Rice</strong> is ₹30 cheaper on <strong>Zepto</strong></blockquote><blockquote>-<strong>Detergent</strong> is ₹10 cheaper on <strong>Blinkit</strong></blockquote><blockquote><strong>-Oil</strong> is ₹15 cheaper on <strong>Instamart</strong></blockquote><blockquote><strong>-Snacks</strong> are ₹20 cheaper on <strong>Flipkart Minutes</strong></blockquote><blockquote><strong>Technically, he could split the order across all 4 apps and save ₹75 in total.</strong></blockquote><h4>😬 <strong>But in reality?</strong></h4><blockquote>That almost<strong> never happens.</strong></blockquote><h4>Why?</h4><blockquote>Because the hidden costs cancel out the savings. Each app comes with <strong>Delivery fee, Minimum cart value, handling charges.</strong></blockquote><blockquote>😢 <strong>And beyond the cost, there’s the effort:</strong></blockquote><blockquote>Placing separate orders</blockquote><blockquote>Paying separately for each app</blockquote><blockquote>Dealing with different delivery times</blockquote><h4>So how do users actually make decisions?</h4><p>It’s not just about the cheapest rice or oil.</p><p>We noticed something deeper:</p><blockquote>Users were trying to make <strong>one smart, final decision</strong> — not compare item by item, but decide <strong>where to buy their whole cart or best way to split the cart for max savings</strong>.</blockquote><p>They were already doing this.</p><p><strong>Mentally. Manually</strong></p><p>So we studied the patterns — and uncovered the hidden needs behind them.</p><p>👉 That’s when it all clicked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*79bxdCPhuNcNDQX0sqaB8g.png" /><figcaption><strong>What users do vs. what they actually need.</strong></figcaption></figure><h3><strong>Evaluating the Effort vs. Impact</strong></h3><p>Once we confirmed that Total Price Comparison was a real user need, we didn’t jump straight into building it.</p><p>In a startup, urgency alone doesn’t decide what gets built. Every new feature competes with existing priorities, time, and dev effort.</p><p>So we had to pause and ask:</p><blockquote><strong>Is this the right thing to work on right now?</strong></blockquote><p>To answer that, we listed all our potential features :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TtTbBr348RDFPlUfHJODEA.png" /><figcaption>All proposed features</figcaption></figure><p>Then we asked ourselves two questions:</p><ul><li><strong>How much value does this drive — today?</strong></li><li><strong>How much effort will it take to build, test, and ship?</strong></li></ul><p>That’s how we decided what to build first — and what to build next and mapped them using a simple <strong>Value vs. Effort matrix</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kCN_fuWTty-Nwg5c5H25jA.png" /><figcaption><strong>Value vs. Effort matrix</strong>.</figcaption></figure><p>Total Price Comparison clearly landed in <strong>High Value, High Effort</strong>.<br>We knew it would bring real clarity for users — but it wasn’t a quick win.</p><p>So we started with smaller, high-impact features that were faster to ship.<br>Once we created space, we turned our attention to :<br> 🛒 <strong>Helping users compare total prices in one go.</strong></p><h3>How Competitors Tackle this problem</h3><p>Before designing the feature, I looked at other grocery comparison apps in India to understand how they handled total pricing. The goal wasn’t to copy them — but to learn from their gaps and design something more helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TkBbw1mxcqe_t3h3Jk1cvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9afuSth0EYSwsHoHK5KOBw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9wdKdiL6wsl3X_eeQCBSg.jpeg" /><figcaption>From left to right: Shopswiftly, Pikeazy, Savvio</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OukmsmXvzcEAneQkSBaqAg.png" /><figcaption>Emoji legend</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qi1kacbak2H6mpEjEJrn-w.png" /><figcaption>Feature analysis</figcaption></figure><p><strong>Opportunities identified</strong></p><blockquote>Design total price comparison in a way that’s not just a total of items, but actionable and actually helps users decide where to buy.</blockquote><h3>Defining the Right Problem</h3><p>I framed a question to fuel my solution brainstorming later on:</p><blockquote><strong><em>How might we improve total price comparison to help users make an informed choice about where to buy groceries?</em></strong></blockquote><h3><strong>Initial Ideas and Sketches</strong></h3><p>With the problem clearly framed, I moved into exploring how the experience should work — both for users and the business. While brainstorming and sketching early ideas, we ran into a few core challenges that shaped our approach.</p><p>📸 Sketches photos</p><h3><strong>Design Challenges We Faced</strong></h3><h4>Challenge 1: Not All Apps Have the Same Items — So How Do You Compare the total?</h4><p>Not every app has every item in the user’s shopping list.</p><p>For example, if someone is comparing 3 apps:</p><ul><li>Item A might be available on all 3 apps</li><li>Item B only on 2 apps</li><li>Item C only on 1 app</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8_rPHYSxrdbtKJMK1_Q6w.png" /></figure><p>When this happens, the total price shown for each app ends up being based on <em>different sets of items</em>.</p><blockquote>This leads to an apples-to-oranges problem: the totals look comparable, but they’re not actually showing the total of same thing. For users, this makes it hard to trust the result</blockquote><blockquote>Designing around this inconsistency was one of the first major challenges we had to solve.</blockquote><h4>Challenge 2: Subscriptions Make Total Cost Unpredictable</h4><p>Even with the same cart, not every user sees the same total.</p><p>Some have <strong>subscriptions</strong> (like Blinkit Prime or Instamart Super) that unlock free delivery or extra discounts. Others see <strong>personalized offers</strong> based on their history, location, or time of day.</p><h4>Challenge 3: Building Fast Without Compromising What Matters</h4><p>As a growing startup, the challenge was striking a balance between:</p><ul><li>💡 Designing something helpful and clear</li><li>🕐 Shipping fast with limited time and resources</li><li>⚙️ Working within tech constraints of what data we had access to</li><li>How much complexity we could realistically handle in the first release.</li></ul><p>We didn’t just ask, “What’s the perfect experience?”<br> We had to ask, <strong>“What’s the clearest, leanest version we can ship right now that still solves the real problem?”</strong></p><h3>The Goal</h3><p><strong>Goal 1: Our goal was simple: clarity at a glance.</strong></p><p>We wanted users to stop guessing, and instead feel like, “Ah — this is where I should order from.”</p><p><strong>Goal 2: Design a clear, helpful solution we can ship fast within our data and tech constraints — then gather feedback and improve it</strong></p><p><strong>Goal 3: Increase app traffic, downloads, and retention</strong></p><h3><strong>Iterations and What Didn’t Work</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SyLy1v8X5wwjIPGztBx29A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vr94MB3JT0M_D1kIEKQD8g.png" /></figure><h3>The Final Version We Launched</h3><p>After multiple rounds of iteration, feedback, and team discussions, we arrived at a final version that addressed core user pain points — while working within technical and API constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*lRhohje1Jc7GXOtH5iBPJA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6bIL3bajMimWOrQUdRUmWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KL9LuOLXA4zDC7VTGRCa-Q.png" /></figure><p>📸 Add prototype</p><h3><strong>What We’d Improve Next?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MwklkSb21KYmgmc8S_YYQ.png" /></figure><h3><strong>What I Learned from This Project</strong></h3><p><strong>1. Not Every User Request Should Be Built</strong></p><p>I learned that while it’s important to listen to users, not every request makes sense for the product. Sometimes you have to step back, look at the bigger picture, and decide what actually helps both the user <em>and</em> the business grow.</p><p>2. <strong>Real Users Don’t Always Behave How You Expect</strong></p><p>Usability testing showed me that even simple screens can confuse users in ways I didn’t predict. Testing early and seeing real behavior helped me catch problems before they became bigger issues.</p><p><strong>3. Communicating Design</strong></p><p>I learned to communicate not just what I designed, but why I designed it that way, and how it solved the problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39bda2e8ff77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[InclusiCare App : Where Telemedicine Meets Accessibility, Empowering Users with Disability — a UX…]]></title>
            <link>https://medium.com/@howdyunnatidixit/inclusicare-app-where-telemedicine-meets-accessibility-empowering-users-with-disability-a-ux-9f8084bb280c?source=rss-e52a86fdf278------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f8084bb280c</guid>
            <dc:creator><![CDATA[Howdyunnatidixit]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 03:27:33 GMT</pubDate>
            <atom:updated>2024-11-11T07:22:23.912Z</atom:updated>
            <content:encoded><![CDATA[<h3>InclusiCare App : Where Telemedicine Meets Accessibility, Empowering Users with Disability — a UX case study</h3><h4>Background:</h4><p><strong>Picture this</strong>: you’re sitting in front of your computer, anxiously waiting for your virtual doctor’s appointment. Finally, the doctor appears on screen, but their attention seems to be elsewhere. You are already feeling the pressure of ticking clock by now. As you begin sharing your concerns, hoping for guidance, you notice a disconnect. Doctor is not interested in your big story and want you to speak just key words and finishes business with writing prescription with no/ less interaction with you? How does it feel? Personally, It make me feel like I’m wasting their time, and leaves me feeling unheard and hopeless. Later, The doubts start to creep in: Was the diagnosis accurate? Do I need to seek a second opinion?</p><p>These <strong>challenges of virtual appointments are amplified for people with disabilities</strong>. For example, video-based telehealth services remain inaccessible to many with communication-related disabilities (ie, people who are deaf, hard of hearing, deafblind, blind, low-vision, and speech disabled), as well as to those who have intellectual disabilities.</p><p><em>They face added challenges of communication barrier, anxiety, sense of isolation, pressure of navigating the technology to make their concerns clear to doctor and fear of misdiagnosis from misinterpretations due to communication barriers.</em></p><blockquote><strong>Imagine already having less time with the doctor, and then having to face all these barriers just to communicate.</strong></blockquote><h4>The Problem</h4><p>COVID-19 made telemedicine popular — and in many cases, necessary. Unfortunately, Apps and websites providing these Telemedicine services are inaccessible to those who need them most — <strong>people living with a disability</strong>. This has created a digital divide, leaving this segment of the population struggling to navigate the virtual healthcare.</p><h4>Who is my Target user?</h4><p>People with disabilities who are seeking telemedicine services.</p><h3>My Design process</h3><p>I follow double diamond design process</p><p>This is how I came up with the solutions, let me walk you through.</p><ol><li><strong>Discover</strong> — Research-Understanding Users and market</li><li><strong>Define-</strong> Frame the problems</li><li><strong>Develop</strong>- Generating ideas, Prioritisation, Information architecture</li><li><strong>Deliver</strong>- Prototype and test</li><li><strong>Design handoff to Developers</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SzQ3c5YvNkY8i1qU6IW5Kg.jpeg" /></figure><h3>Research- Understanding Users and market</h3><p>After identifying the problem, I began my design process with thorough research to understand the scope of the problem, the needs and motivations of my target users, and the solutions that competitors are offering.</p><p>Before diving into research, I created a research plan that outlined research goals, my assumptions, questions, and methodologies.</p><p><strong>My High level Research goals were to find out-</strong></p><ol><li>What challenges user with disability faces when using telemedicine apps.</li><li>What users feel when on a virtual call with Doctor and also while navigating the app?</li><li>What competitors offers and are doing to solve this problem? This will help me to find gaps and opportunities.</li></ol><h3>Secondary Research</h3><h4>Literature review</h4><p>My lack of domain knowledge about accessibility and scope of telemedicine, leads me to Literature review. I spent a lot of time buried in the academic research and literature to get more understanding of the wider challenges faced by people with disability.</p><h4>Insights from the Literature review</h4><ul><li>Telemedicine consultations in India increased by over <strong>1,000%</strong> during the COVID-19 pandemic.</li><li>A survey conducted by the Indian Telemedicine Association found that <strong>78% of people with disabilities</strong> in India believe that telemedicine can improve their access to healthcare.</li><li>Telehealth use differed by disability type with 43.3% of persons with mobility disabilities using telehealth, 42.1% of persons with cognitive disabilities, 36.8% of persons with visual disabilities, and 34.5% of persons with hearing disabilities</li><li>Doctors and healthcare staff are not well trained on how to communicate with people with disability.</li><li>A common problem is <strong>an app’s incompatibility with screen readers.</strong> <em>Many blind and visually impaired people rely on screen readers to read out text and visual information.</em></li><li><strong>Videos calls without captions or transcripts</strong>, <em>become inaccessible for people who are deaf or hard of hearing.</em></li><li>Many apps are also <strong>incompatible with keyboard navigation</strong>, and have menus that are hard to interact with <em>which creates pain points for users who cannot use a mouse — such as those with visual impairments or dexterity issues.</em></li></ul><blockquote>“I haven’t found any single application [that’s] fully digitally accessible,” says Cezary Tomczyk, a former Apple accessibility expert . He says he has tested dozens of telemedicine apps, and virtually all are digitally inaccessible.</blockquote><h4>Competitor Research</h4><p>Literature review helped me form a base knowledge about common problems people with disabilities face with telemedicine. Later I analyzed competitors to find their strengths, weaknesses, and trends. <em>These insights also help me identify any gaps and opportunities that </em><strong><em>Inclusicare</em></strong><em> app might address.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AX--ke611WhMLSOuoC-Tjg.png" /></figure><p><strong>Key Insights</strong></p><ol><li>Currently available telemedicine apps, both direct and indirect competitors, are designed for the general population. While they offer some accessibility features like voice recognition and screen magnification, their <strong>integration with assistive technologies like screen readers is inadequate and often disorganized.</strong></li></ol><blockquote>Inclusicare can take these limitation into consideration to help People with disabilities to easily navigate the app.</blockquote><h3>Primary Research</h3><p><strong>1-on-1 User Interviews</strong></p><p>Armed with insights from Secondary research, I decide to conduct user interviews, as I want to talk to real users and know their firsthand experience with telemedicine apps. I recruited total of 5 participants, out of which one was with disability.</p><p><strong>Barriers and Challenges : </strong>Recruiting participants with disabilities proved most challenging. Participants were not comfortable to share their experience, due to privacy issues, communication barrier. I was eventually able to secure the participation of <strong>one individual with mobility disability </strong>who provided valuable insights into the unique needs and challenges faced by them when accessing telemedicine services.</p><blockquote>Since I had limited access to participants with disabilities for my research, I supplemented my findings with data from interviews conducted by the National Center for Biotechnology Information (NCBI).</blockquote><p>Interviews generated a lot of information, so to make sense of it all, I created <strong>affinity map</strong>, which combines all the data points from my interviews to extract important patterns and thus insights.</p><p><strong>Insights from User interviews</strong></p><p><strong>User pains</strong></p><ul><li>People with disabilities feel worried and unsure of themselves when they have to talk to their doctor using telemedicine due to communication barriers.</li><li>People with communication disability depends on somebody else to convey their concerns to doctor.</li><li>Most of the users finds <strong>telemedicine app’s interface complicated</strong></li><li>Most Telemedicine apps, are <strong>not compatible with screen reader.</strong></li><li>Most telemedicine platforms <strong>do not have custom features</strong> <strong>to ease healthcare communications</strong> for persons who are deaf or blind or for persons with cognitive disabilities.</li><li>Users with disability may not be efficient in technology due to reasons like socioeconomic status and digital literacy</li></ul><p><strong>User needs</strong></p><ul><li>User needs an <strong>intuitive interface</strong> that enables them to take the benefits of Telemedicine <strong>considering their disability</strong></li><li>User needs simpler <strong>UI and UX</strong> experience</li><li>User needs product that is compatible with <strong>Screen reader and other assistive technologies</strong></li><li>User needs a customer support to help them when they are stuck in a process</li></ul><blockquote>“I honestly don’t know how other deafblind people are doing this. It just does not seem possible without help. Nothing is compatible with captions or a Braille display, and there are no words to even get on a display, since it’s all in voice,”</blockquote><blockquote>“The only thing that I see is that folks with disabilities are cared for last and are dying first.”</blockquote><blockquote>-User Quotes</blockquote><h3>Framing the Problem</h3><p>With the Insights achieved from the research phase, I created POV (Point of View ) statements that summarize my user’s needs and later converted them into HMW (How Might We) questions to kickstart brainstorming.</p><p>I decided to work on this How might we Question-</p><blockquote><strong><em>How might we improve the Telemedicine experience for Patients with Disabilities ensuring their specific needs are met?</em></strong></blockquote><p>As I move forward in the design process, it’s natural to forget some of what I learned in the discovery phase about user, That’s where I use Personas. After having a clear portrait of who target users are, I created the user persona to represent their emotions, pain points, needs, goals, and motivaiton.</p><p><strong><em>Meet Seema</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*owdN4un57u6x_n72" /></figure><h3>Brainstorming for solutions</h3><p>With the listed “How Might We” question, I started brainstorming session with pen and paper. As they say- No idea is good or bad, I follow this thought and focused on generating a large number of ideas without worrying about quality and feasibility.</p><h4>Selecting top ideas from pool of ideas.</h4><p>It was a challenge to select just few ideas after brainstorming session, but I select ideas on the basis of it’s potential to impact my target users positively, backed up by my research, and it’s feasibility.</p><h3>Project goal</h3><p>After clearly understanding users’ goals, I revisited the business goal &amp; wrote down some technical considerations. I write out project goals to understand the intersection between <em>business, user goals and technical goals.</em></p><p>This helped me gain complete clarity and align all parties involved<strong> before making feature decisions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ap2WAE2gP9BkXmMaRX1KbQ.png" /></figure><h3>Features Road map &amp; Prioritization</h3><p>I then <strong>created a list of features whcih I can include in my product, </strong>based on my user research, persona, business needs, technical considerations, and the market I have analyzed.</p><p>Then I p<strong>rioritize the features</strong> on the list based on their importance to business and users, it’s feasibility, desirability and viability.</p><blockquote>I avoid letting desires for features trumps over user needs.</blockquote><p>The features are sorted into 4 categories, including–<strong>Must-have (P1), Nice-to-Have (P2), Delightful (P3), and Can-wait (P4) features.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gkHW2bdLx-2i8ICH" /></figure><h3>Information architecture</h3><p><strong>Content Prioritisation — Card sorting</strong></p><p>At this point, I already know what features I am going to provide for my users. But to decide what content is the most important for users to access, how it should be organized, and how it can be placed strategically to guide the user from one screen to the next, I used Card sorting.</p><blockquote>Card sorting helps me step away from my own bias, and get a sense for how users will think about, so that I can organize and label content in a way that makes the most sense to them.</blockquote><p>After understanding patterns generated from card sorting, here comes the important part of building a skeleton for my app. I made several drafts and iterations before coming up with an ultimate sitemap.</p><p><strong>Information architecture-Booking journey</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QEc7ph3pu3IDvFc04lKsgw.png" /><figcaption><strong>Information architecture-Booking journey</strong></figcaption></figure><p><strong>Information architecture-Consulting journey</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TBxVW0NDiwT-9_X8B2utkw.png" /><figcaption><strong>Information architecture-Consulting journey</strong></figcaption></figure><h3>Sketching the ideas</h3><p>Taking what I’ve learned throughout my process to this point, I sketched out the screens. Doing this help me layout content quickly and try out multiple ideas without the barriers of technical tools. Then I took feedback and iterated it accordingly.</p><h3>Mid fidelity wireframes</h3><p>Now that I had an idea of which direction I would pursue from sketching and feedback sessions, I converted Low fidelity sketches into Mid Fidelity digital wireframes in Figma to prepare for prototyping and testing in later stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3AadZ-notsHxIWm5GOLhQ.png" /><figcaption>Mid fidelity Wireframe</figcaption></figure><h3>Logo and Branding</h3><p><strong>Introducing Inclusicare</strong></p><p>Before diving into the UI design, I took a step back to brainstorm the the brand’s attributes, and its overall identity.</p><p>I first came up with Brand name- <strong>InclusiCare </strong>which is combination of the words “inclusion” and “care,” <strong>emphasising the app’s mission to provide inclusive and accessible telemedicine services for people with disabilities.</strong></p><p>Since <strong>brand value is to convey trust, inclusion, calmness and reliability</strong>, It was essential to bring a positive, trustful feeling to appeal to and encourage users. I then created a mood board in which I put ideas, concepts together to set the direction of the new branding.</p><p>I sketched lots of options for logos, and later finalize this logo</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/0*kSCVs5dfuAd7_Aca" /></figure><blockquote>The <strong>blue colors</strong> is associated with trust, reliability, and inclusion, which are important qualities for a telemedicine app. The<strong> heart symbol</strong> represents compassion and care, while the <strong>shaking hands</strong> suggest representing Inclusicare’s commitment to providing assistance and support to people with disabilities.</blockquote><h3>UI kit</h3><p>Next, I created UI kit to act as a reference document and ensure consistency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wl3-1YXB9ObjexQxjMj8nA.jpeg" /></figure><h3>High Fidelity design</h3><p>With the visual style defined for the UI design and wireframes ready, it’s time to put things together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gCowni0_qFQkyiEkX3KBlw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i98TI6ilNca_XKgFQPX2aw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DGfM9sQhaPRSteM_7WprA.png" /></figure><h3>Turning wireframes into High fidelity Prototype</h3><p>It is time for testing my design choices and assumptions that have been made about the navigability, the screens, and the actions associated with different tasks. So I generated a prototype in Figma.</p><p>You can check working prototype <a href="http://cc/">here</a></p><blockquote><em>I learnt that it’s better </em><strong>to test early and as often as possible. </strong>It reduces friction, eliminate errors, and uncover mistakes and false assumptions. Thus saves time, money, resources, and your sanity.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fai8Du1CzBYc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dai8Du1CzBYc&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d8058213f81fd390d484be2110d975aa/href">https://medium.com/media/d8058213f81fd390d484be2110d975aa/href</a></iframe><p>With the Prototype ready, next is to test the product directly with customers to measure its effectiveness.</p><p>I started with preparing a Usability test plan which includes objectives, success metrics, core tasks for users to complete and script for the moderated sessions.</p><p>Following my usability test plan, I conducted moderated usability test with participants <strong>( Sadly, I couldn’t recruit people with disability for usability testing due to unavailability )</strong></p><blockquote>Instead of explaining to them what my app does and how it works, I let them figure it out!</blockquote><h3>Revise Design</h3><p>After identifying the pain points from the affinity map and considering how much work it would take and how much it would benefit users, <strong><em>I began by fixing the screens that were stopping users from finishing the main tasks. Then, I worked on improving the screens that users didn’t like.</em></strong></p><h3>Final Prototype</h3><p>After making all the changes, I’ve put together the last version of our plan.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f8084bb280c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>