<?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 Sonal Solaskar on Medium]]></title>
        <description><![CDATA[Stories by Sonal Solaskar on Medium]]></description>
        <link>https://medium.com/@solaskarsonal?source=rss-8671974d8e7f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KQJvE9PtnlX5Ca8nEv4Q4g.jpeg</url>
            <title>Stories by Sonal Solaskar on Medium</title>
            <link>https://medium.com/@solaskarsonal?source=rss-8671974d8e7f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:58:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@solaskarsonal/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[Improving Trust and Feedback in Instagram Instants]]></title>
            <link>https://medium.com/@solaskarsonal/improving-trust-and-feedback-in-instagram-instants-c4285cf39d4d?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4285cf39d4d</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[instagram]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Thu, 21 May 2026 15:36:40 GMT</pubDate>
            <atom:updated>2026-05-22T03:06:48.255Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iUgedPXJeFSdnjmfcMrFaQ.png" /><figcaption><strong>Improving Trust and Feedback in Instagram Instants</strong></figcaption></figure><p>Instagram Instants is built around a simple promise: share everyday photos in the moment, with no edits and no pressure. That idea is appealing because it lowers the bar for posting and encourages more authentic sharing with close friends. But in its current form, the feature creates confusion at the exact moment users need clarity most.</p><p>This case study looks at the interaction problems in the current experience and explores how a few small design changes can make Instants feel more understandable, trustworthy, and still fast. The goal was not to turn it into a heavy camera app, but to preserve its spontaneity while reducing accidental actions and unfamiliar behavior.</p><h3>What Instants is trying to do</h3><figure><img alt="Instagram Instants Preview Images Posted by Instagram on X." src="https://cdn-images-1.medium.com/max/1024/1*fy-WoguhC4q2kZdS5H294A.jpeg" /><figcaption><strong>Instagram Instants © </strong><a href="https://x.com/instagram?lang=en"><strong>Instagram</strong></a></figcaption></figure><p>The appeal of Instants is obvious. It encourages users to capture and share raw, unedited moments without overthinking them, which is a strong fit for casual, close-friends communication. It removes the pressure to polish a photo before posting, which makes the feature feel lighter and more human.</p><p>That idea is worth protecting. The challenge is that the current UX does not support the emotional promise of the product very well. A feature designed for immediacy still needs clear feedback, familiar interactions, and a reliable way to recover from mistakes.</p><h3>The Problems I Found</h3><p>There were several main issues that stood out while reviewing the feature.</p><figure><img alt="The Problems I Found with Instagram Instants" src="https://cdn-images-1.medium.com/max/1024/1*69Pe8xk9xXFjy2Bd7ueT5Q.png" /><figcaption><strong>The Problems I Found with Instagram Instants</strong></figcaption></figure><ol><li><strong>Capture Flow: </strong>Unlike most camera experiences, Instants skips the preview step and sends the photo immediately after tapping the shutter.</li><li><strong>Feedback: </strong>There is no strong confirmation that the image was sent.</li><li><strong>Undo: </strong>While there is an undo option, it appears only for a few seconds and is hard to notice, and deleting a mistaken post later requires several hidden steps.</li><li><strong>Browsing behaviour,</strong> which feels unfamiliar because it does not follow the same gestures users are used to in Stories or other Instagram surfaces.</li></ol><p>The remaining issues were around <strong>onboarding, visibility, and placement:</strong> captions are not well introduced, there is no clear view of who saw an instant, and the feature sits in a part of DMs where it can be accidentally tapped. Taken together, these problems make the feature feel inconsistent and less trustworthy than it should.</p><h3>Design goals</h3><p>I used five design goals to guide the redesign:</p><ul><li>Keep the feature fast and lightweight.</li><li>Add a clearer recovery path for mistakes.</li><li>Make feedback visible at every important step.</li><li>Match the interaction model people already know.</li><li>Clarify where content lives and who can see it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvaxH26qHB_uOLSlNMyJiA.png" /><figcaption><strong>Redesigned Flow for Instagram Instants</strong></figcaption></figure><p>These goals helped keep the redesign focused. Instead of changing everything, I looked for the smallest changes that would make the biggest difference in clarity and confidence.</p><h3>Capture Flow</h3><h4>Current flow</h4><p>In the current flow, the user opens the camera and taps the shutter. The photo is sent instantly, with no preview, no send confirmation, and no clear moment to stop and reconsider. That makes the interaction feel abrupt, especially for a feature that is supposed to be casual and low-pressure.</p><p>This is different from most camera-based patterns people already know. In other apps, the normal expectation is: capture the image, review it, then decide whether to send, edit, or discard it. Instants removes that familiar pause entirely, which is where much of the confusion starts.</p><figure><img alt="Current Capture Flow for Instants" src="https://cdn-images-1.medium.com/max/1024/1*Hwfb2TPMFv2pT1h7UzjjHg.png" /><figcaption><strong>Current Capture Flow for Instants</strong></figcaption></figure><h4>My first redesign idea</h4><p>My initial idea was to add a preview screen with <strong>Send</strong> and <strong>Discard</strong>, and then still keep an <strong>Undo</strong> timer after sending. But once I looked at that more closely, it felt redundant. If the user already sees the photo and chooses to send it, then asking them to undo a few seconds later can feel like they are making the same decision twice.</p><figure><img alt="Image illustrating wireframes of my initial ideas for Capture Flow for Instants" src="https://cdn-images-1.medium.com/max/1024/1*d_pINz_j5pvDxh4TxGM0tg.jpeg" /><figcaption><strong>Wireframes of my</strong> <strong>Initial ideas for</strong> <strong>Capture Flow for Instants</strong></figcaption></figure><p>That made the capture flow feel overdesigned. I wanted to improve control, but not at the cost of making the feature feel less immediate. Since Instants is meant to feel quick and spontaneous, I needed to decide whether the redesign should prioritize pre-send control or post-send recovery.</p><h4>Option 1: Preview + Send/Discard</h4><p>In this version, the user taps the shutter and then sees the captured image before anything is shared. They can either send it or discard it, which gives them a clear decision point before the action becomes final. This is the safer and more familiar option because it matches the way camera and sharing flows usually work.</p><p>The downside is that it slows the experience down a little. It feels more like a traditional camera app and less like an instant-sharing tool, which slightly weakens the core idea of the product.</p><h4>Option 2: Instant send + Undo timer</h4><p>In this version, the user taps the shutter and the photo is sent right away, just like the current behavior. The difference is that the system then shows a visible undo timer, so if the user tapped too quickly or changed their mind immediately afterward, they still have a small recovery window.</p><p>This option keeps the action aligned with the purpose of Instants. It preserves the sense of immediacy and makes the feature feel more true to its name, while still giving users a short safety net for mistakes.</p><h4>Final choice</h4><p>I chose the <strong>Undo timer</strong> approach because it feels more true to Instants. The product’s identity is built around quick, raw sharing, so I did not want to add a preview step that made it feel too much like a standard camera workflow. The undo timer gives users just enough protection without taking away the feeling of speed.</p><figure><img alt="Redesigned Capture Flow" src="https://cdn-images-1.medium.com/max/1024/1*0BQ_22WkQOCQnHH1puKBnQ.png" /><figcaption><strong>Redesigned Capture Flow</strong></figcaption></figure><h3>Send Feedback</h3><h4>Current flow</h4><p>After the photo is sent, there is very little visible feedback. There is no strong toast or animation to confirm that the action worked, which can leave the user uncertain. That uncertainty is especially problematic because the action is fast, and fast actions need clear confirmation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzurDpfBwTCKs5peuMok6Q.gif" /><figcaption><strong>Current Feedback Flow</strong></figcaption></figure><p>When a system doesn’t show completion clearly, users are left wondering whether they mis-tapped, whether the photo actually sent, or whether they still have time to recover. In a feature like this, that hesitation is avoidable and should be designed out.</p><h4>Redesigned flow</h4><p>The redesigned version adds a small “Image sent” toast as soon as the capture is shared. It is subtle, but it gives the user an immediate signal that the action succeeded. That one moment of feedback makes the experience feel much more intentional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCJ20hqwsCMJyt1_s4-euQ.gif" /><figcaption><strong>Prototype for Redesigned Feedback Flow</strong></figcaption></figure><p>This also creates a natural bridge into the undo state. The send confirmation tells the user what happened, and the undo timer tells them what they can still do about it.</p><h3>Undo and Recovery</h3><h4>Current flow</h4><p>The current undo experience is difficult to rely on. The undo button only appears for a short time, and the user does not have a strong visual sense of how long it will remain available. If they miss it, the delete flow is buried behind several additional steps in the gallery.</p><p><strong>Delete Flow:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2f1oAy-Ma6gWpIIfJuavLQ.png" /><figcaption><strong>Delete Flow for Instagram Instants</strong></figcaption></figure><p>That creates a high-cost mistake. A user can accidentally send a photo in one tap, but then needs to perform a complicated sequence to reverse it. That mismatch makes the whole feature feel less forgiving than it should.</p><h4>Redesigned flow</h4><p>In the redesigned version, the undo state is made visible through a progress bar. Instead of a disappearing toast with unclear timing, the user can see exactly how much time remains before the undo option disappears. This makes the recovery window feel real and usable.</p><p>If the user misses that window, the delete option still exists in the archive, but it is surfaced more clearly and consistently. The goal is not to remove the safety net, but to make it understandable enough that users trust it.</p><h3>Browsing Behaviour</h3><figure><img alt="Wireframes of the redesigned browsing behaviour for Instants" src="https://cdn-images-1.medium.com/max/1024/1*5GH0m8XprwV6P70aReKYyA.jpeg" /><figcaption><strong>Wireframes of the redesigned browsing behaviour for Instants</strong></figcaption></figure><h4>Current flow</h4><p>Browsing Instants currently feels unfamiliar because the gestures do not match what people already expect from Instagram. Tapping on an instant moves to the next image instead of expanding it, and swiping opens the Instants camera instead of continuing the browsing flow.</p><p>This may seem small, but it matters because users bring existing mental models into a product. When the system behaves differently from what they expect, they have to slow down and relearn the interaction, which adds friction in a place that should feel effortless.</p><figure><img alt="Current Browsing Behaviour of Instants" src="https://cdn-images-1.medium.com/max/1024/1*ltLFiWcwp3It1KLtEIYgwA.png" /><figcaption><strong>Current Browsing Behaviour of Instants</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkKMSMM8igWPMDiIN2SYEQ.gif" /><figcaption><strong>Current Browsing Behaviour of Instants</strong></figcaption></figure><h4>Redesigned flow</h4><p>The redesigned version follows the same interaction patterns users already know. Tapping expands the content, swiping moves to the next instant, and the camera becomes available through an explicit control instead of a gesture that interrupts browsing.</p><figure><img alt="Redesigned Browsing Behaviour of Instants" src="https://cdn-images-1.medium.com/max/1024/1*oe9HU5cA1_RfMtJnD7wWAg.png" /><figcaption><strong>Redesigned Browsing Behaviour of Instants</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkqjdcYDlYM7FFoZ3IJnxw.gif" /><figcaption><strong>Redesigned Browsing Behaviour Prototype of Instants</strong></figcaption></figure><p>This makes the feature easier to learn and easier to trust. The user no longer has to think about how the feature works; they can focus on the content itself.</p><h3>Caption Onboarding</h3><h4>Current flow</h4><p>There is no strong onboarding for captions in the current version. That means users may not realize the feature exists, or may not understand how to use it. When an optional capability is hidden, it tends to stay underused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Le_s4CK5tQroRyScsDFZLA.png" /><figcaption><strong>Current Caption Flow for Instants</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uq-WbHwx7sYkiS5YUImJw.gif" /><figcaption><strong>Current Caption Flow for Instants</strong></figcaption></figure><p>This is especially important because captions add context to a moment. Without them, the feature loses some of the expression that makes sharing more personal.</p><h4>Redesigned flow</h4><p>The redesigned version makes caption support more discoverable by adding a dedicated button directly on the instant, modeled after the familiar “text” control found in Instagram Stories. That makes the feature easier to discover without cluttering the experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OajfJHIrAvBXzbSQ664iAA.png" /><figcaption><strong>Redesigned Caption Flow for Instants</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWouoIego0tLXlf2ekzgDg.gif" /><figcaption><strong>Redesigned Caption Prototype for Instants</strong></figcaption></figure><p>The intent is not to make captions feel mandatory. It is simply to make them visible enough that users understand they are available.</p><h3>Placement in DMs</h3><p>The current placement of Instants in DMs creates accidental taps because it sits where the user naturally scrolls through chats. That means the feature interrupts the main task of the screen instead of supporting it.</p><p>This is a classic placement problem: even a well-designed interaction can feel annoying if it lives in the wrong part of the interface. In this case, the location makes the feature more distracting than useful.</p><p>That said, insights from the Instants designer on X clarify the feature’s original intent and its current rollout alongside Instagram Stories in specific regions. By moving the entry point away from the main chat list, this placement effectively reduces accidental actions and makes the overall DM environment feel much more intentional and composed.</p><figure><img alt="Image showcasing the placement of Instants in Instagram App: Current vs. Original Idea" src="https://cdn-images-1.medium.com/max/1024/1*TIb3ylvcrLl3gAODpdUm2w.png" /><figcaption><strong>Placement of Instants in Instagram App: Current vs. Original Idea © </strong><a href="https://x.com/instagram?lang=en"><strong>Instagram</strong></a><strong>, </strong><a href="https://x.com/me____likex"><strong>Melike Turgut</strong></a></figcaption></figure><h3>What changed</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rlsAjjS4MzsG7zCnACesuQ.gif" /><figcaption><strong>Final Redesign for Instagram</strong></figcaption></figure><p>The final redesign keeps Instants fast, but makes it easier to understand and harder to misuse. The main changes are:</p><ul><li>Clearer send feedback.</li><li>A visible undo timer.</li><li>More familiar browsing gestures.</li><li>Caption onboarding.</li></ul><p>The result is a feature that still feels spontaneous, but no longer feels surprising in the wrong way. It keeps the spirit of Instants intact while reducing the friction that gets in the way of using it comfortably.</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4285cf39d4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[M-Indicator: Reducing Confusion & Cognitive Load Through Mental Model Alignment in Mumbai’s Metro Navigation]]></title>
            <link>https://medium.com/@solaskarsonal/m-indicator-reducing-confusion-cognitive-load-through-mental-model-alignment-in-mumbais-metro-e844efbd6c1b?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e844efbd6c1b</guid>
            <category><![CDATA[travel-app]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Wed, 06 May 2026 11:59:20 GMT</pubDate>
            <atom:updated>2026-05-06T12:02:34.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYoBOHlbtJ4Eln0b6APY4g.png" /><figcaption><strong>Reducing Confusion &amp; Cognitive Load Through Mental Model Alignment in Mumbai’s Metro Navigation</strong></figcaption></figure><h3>Problem Statement:</h3><p>M-Indicator is one of Mumbai’s most trusted commute apps used daily by millions for local train schedules, bus routes, and city navigation. When Mumbai’s new metro lines began opening across South Mumbai, M-Indicator added it to the metro section to the app. On paper, this made sense. In practice, it broke the experience entirely.</p><p>The metro flow was built as if it were a standalone product dropped inside a familiar app. It had its own logic, its own structure, and its own interaction patterns none of which matched what M-Indicator users already knew. For first-time metro riders, especially those unfamiliar with the new line names and stations,<strong> the app offered no guidance, no location detection, and no path to actually plan a journey.</strong> What it did offer, before anything else, was a button to buy a QR ticket for a train the user hadn’t selected yet, on a route they hadn’t figured out, to a destination they hadn’t entered.</p><h3>What Makes a Good Navigation Flow in a Multi-Modal Transit App?</h3><p>A well-designed transit navigation experience should:</p><ul><li>Open every mode with the <strong>same interaction pattern</strong> so users never have to relearn how the app works</li><li>Detect the <strong>user’s location automatically</strong> as the starting point, removing the first step of manual input</li><li>Keep all functionality in-app sending users to Google Maps or an external browser is a trust-breaking moment that signals the product isn’t complete</li></ul><h3>Issues With Current Experience:</h3><p>The current M-Indicator metro section was audited by using it exactly the way a first-time metro rider would — arriving at the airport, needing to get to CSMT, opening the app expecting it to work the way it always had.</p><p><strong>No source-destination prompt: </strong>Every other section of M-Indicator whether local trains, buses, express routes opens with a “source / destination” input. The metro section does not. Instead, it presents a list of metro line names tied to area names that are unfamiliar to anyone who hasn’t already memorised the new network. A user landing here has no obvious next step.</p><figure><img alt="Image showing comparison of other modes and metro with respect to source-destination prompt" src="https://cdn-images-1.medium.com/max/1024/1*eFVCS6e2ed9smfFzHJF3sA.png" /><figcaption><strong>No source-destination prompt for metro section</strong></figcaption></figure><p><strong>Location detection absent from the metro flow:</strong> M-Indicator already detects your location for local trains and uses it to surface your nearest station automatically. The metro flow ignores this entirely. A user at the airport must manually figure out which metro line serves that area, find the right station name, and type it in — steps that every other mode eliminates by default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eq5qDL3FcdGUxMkTQmojsw.png" /><figcaption><strong>Location detection absent from the metro flow</strong></figcaption></figure><p><strong>“Buy QR Ticket” appears before route selection:</strong> The most prominent action on the metro screen is a ticketing button. The user hasn’t chosen a route, hasn’t seen timing options, hasn’t confirmed which line to take. Asking someone to buy a ticket before they know what train they’re taking is the equivalent of a restaurant asking you to pay before showing you the menu. It creates immediate confusion about what the correct first step even is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhGR2GKz-xreYdOUPE6lmQ.png" /><figcaption><strong>“Buy QR Ticket” appears before route selection</strong></figcaption></figure><p><strong>FAQs are embedded mid-task:</strong> Informational content about how the metro works, fare structure, line details appear inside the active task flow. For a user trying to navigate, this is noise in the wrong place. FAQs belong in a help section, not between the user and their destination.</p><p><strong>The metro map exits the app:</strong> Tapping the metro map button opens Google Maps. A user who came to M-Indicator because they trust it is now in a different app entirely, with no way to get back to their journey planning. If a familiar app forces you to use a more familiar app, something in the design has broken down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p6zF6gUt_gHDSUIq-Iv31A.png" /><figcaption><strong>The metro map exits the app</strong></figcaption></figure><h3>Goals/Objectives of the Redesign</h3><ul><li><strong>Unify the interaction model</strong> across all transport modes such that metro should feel like local trains, not a separate product</li><li><strong>Detect location upfront</strong> so the user’s starting point is known before they do anything</li><li><strong>Lead with source and destination</strong> as the first and only prompt. The same pattern users already know</li><li><strong>Bring the metro map in-app</strong> so users never need to leave M-Indicator to understand the network</li><li><strong>Move ticketing to after route confirmation, </strong>it should be the last step, not the first</li><li><strong>Remove FAQs from the task flow</strong> entirely and relocate them to a help section</li></ul><h3>Approaching the Redesign</h3><p>Before touching any screens, I spent time understanding why the inconsistency existed and what it was actually costing users.</p><p>I used M-Indicator the way a first-time metro rider would — not as someone auditing it, but as someone genuinely trying to get from the airport to CSMT on a new metro line. That ten minutes of confusion wasn’t frustration at the metro. It was the specific disorientation of an app behaving differently than it had trained me to expect. That distinction matters: the problem wasn’t that the metro was new. The problem was that the design didn’t transfer what the user already knew.</p><p>I then compared the metro flow against the local train flow step by step.</p><p><strong>The local train flow:</strong> location detected → nearest station surfaced → enter destination → see routes and timing → optional next steps.</p><p><strong>The metro flow:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m42c6sxMnOuWdxEhe7Dmrw.jpeg" /></figure><p>These weren&#39;t variations of the same pattern. They were two completely different products wearing the same app&#39;s branding.</p><p>Users spend most of their time in other apps and arrive with pre-formed mental models.¹ M-Indicator had already done the hard work of building one. The redesign didn&#39;t need to create anything new but it needed to apply what already existed to a mode that had been left out.</p><p>I sketched the redesigned flow focusing on one question: at each step, does this feel like M-Indicator or does it feel like something else? Every point where the answer was &quot;something else&quot; was a point to fix.</p><h3>Redefined Flow</h3><p>The original metro flow had no consistent entry point and no clear path from intent to action. The redesigned flow mirrors the local train model exactly.</p><p><strong>Original flow:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-nhcR5pXjqJBu12JBjlIw.png" /><figcaption><strong>Current M-Indicator Metro Flow</strong></figcaption></figure><p><strong>Redesigned flow:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8NI8GfRx8xctzSNyZt6V8Q.png" /><figcaption><strong>Resigned M-Indicator Metro Flow</strong></figcaption></figure><p>The redesign introduces no new patterns. It applies the pattern users already trust to the one mode that was missing it.</p><h3>Redesigned Experience</h3><h4>Location Detection and Source-Destination First</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zPeqT6Go6YhHMGouyWgO1Q.png" /><figcaption><strong>Location Detection and Source-Destination First</strong></figcaption></figure><p>The redesigned metro section opens identically to the local train section. <strong>Location is detected automatically and the nearest metro station is surfaced as the default starting point.</strong> The user sees a familiar “from / to” prompt — the same one they’ve used for buses and trains — and can either confirm the detected location or change it manually.</p><p>This removes the first and most disorienting step of the original flow: figuring out which station corresponds to where you are. For a user at the airport who doesn’t know which metro line serves it, this step alone resolves the confusion that sent them hunting through a list of unfamiliar line names.</p><h4>Route Options With Timing and Interchange Information</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kk4hpRDddDrc8XEWBz5GIA.png" /><figcaption><strong>Route Options With Timing and Interchange Information</strong></figcaption></figure><p>After entering source and destination, the redesign surfaces route options the same way local trains do with estimated travel time, number of interchanges, departure windows, and platform information. For a city building a new metro network, interchange information is particularly important: many journeys require switching lines, and a user who doesn’t know the network needs to see this clearly before committing to a route.</p><h4>In-App Metro Map</h4><p>The metro map is brought entirely in-app. Instead of redirecting to Google Maps, tapping the map opens a native view that shows the full network so the user never leaves M-Indicator.</p><p>This matters beyond the convenience of staying in one app. Sending users to Google Maps breaks the session — they lose their entered route, their timing context, and their confidence in the product. An in-app map keeps the journey planning intact.</p><h4>QR Ticket After Route Confirmation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r1PWoR6sa7BLevSY15Iifw.png" /><figcaption><strong>QR Ticket After Route Confirmation</strong></figcaption></figure><p>Ticketing moves to the final step. Once the user has selected a route and confirmed their journey, a “Buy QR Ticket” option appears — at the moment it’s actually relevant. The action is the same. Its position in the flow is what changes.</p><h4>FAQs Removed From Task Flow</h4><p>All informational content is relocated to a help section accessible from the metro home screen. During an active journey-planning session, FAQs are noise. A user trying to find their train doesn’t need to know the metro’s fare structure mid-task — they need their next step. Clearing the task flow of non-essential content reduces cognitive load at exactly the moment it needs to be lowest.</p><h3>Final Design and Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*te8m-sPwG4N4RKGjXBjj-w.png" /><figcaption><strong>Final redesigned flow for metro section</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*nHSfWqBZi7s74ZHmpCsoqQ.gif" /><figcaption><strong>Prototype for M-Indicator Metro Flow</strong></figcaption></figure><h3>Design Decisions</h3><p><strong>Why lead with location detection?</strong> Because the mental model M-Indicator’s users already have begins with the app knowing where they are. Removing this step from the metro flow didn’t simplify the experience but it broke the pattern users relied on. Reinstating it costs nothing and immediately resolves the first moment of confusion.</p><p><strong>Why mirror the local train flow exactly?</strong> Users who open M-Indicator for metro navigation have already internalised how the app works.¹ The fastest way to make a new feature usable is to make it feel like a feature they already know. Designing a separate interaction model for metro even a well-designed one would mean asking users to relearn an app they thought they knew. The redesign avoids that cost entirely.</p><p><strong>Why does moving the QR ticket button matter so much?</strong> Because sequence communicates meaning. When the first thing a user sees is a “Buy QR Ticket” button, the implicit message is: this is where you start. A user who hasn’t chosen a route yet, who doesn’t know which line to take, who is standing in an unfamiliar transit environment — that user does not know what to do with a ticketing button. It doesn’t just fail to help; it actively disorients. Moving it to the end of the flow means it appears at exactly the moment it becomes meaningful and reduces the cognitive load throughout the flow.²</p><p><strong>Why remove FAQs from the task flow?</strong> This is a principle of progressive disclosure.³ Information should appear when the user needs it, not whenever it exists. FAQs are useful but their moment is before the journey or after a failed attempt, not mid-task when the user is actively trying to navigate. Embedding them in the flow is the design equivalent of a waiter explaining the kitchen process while you’re trying to order.</p><p><strong>The consistency argument beyond UX.</strong> There’s a product maturity point here too. M-Indicator has spent years building commuter trust across local trains and buses. When the metro feature was added without applying that same interaction model, it implicitly told users: we built this differently. For a city introducing a new transit system to millions of first-time users, that inconsistency has real consequences — people assume the new mode is harder to use than it is, because the app made it harder than it needed to be. Consistency isn’t just good UX. It’s how the product supports the city’s infrastructure rollout.</p><h3>Conclusion</h3><p>When you introduce a new feature into an existing product, you’re not starting from zero. You’re inheriting the trust, the habits, and the mental models that every previous feature has built. The fastest way to make something new feel usable is to make it feel familiar.</p><p>The M-Indicator metro redesign added nothing new. No novel interaction patterns, no new visual language, no features that didn’t already exist somewhere in the app. What it did was apply what already worked to a mode that had been left out.</p><p>[1]: Laws of UX: <em>Jacob’s Law<br></em><a href="https://lawsofux.com/jakobs-law/">https://lawsofux.com/jakobs-law/</a></p><p>[2]: Think Design: <em>Cognitive Load in UX Design</em><br><a href="https://think.design/blog/cognitive-load-in-ux-design/">https://think.design/blog/cognitive-load-in-ux-design/</a></p><p>[3]: NN Group: <em>Progressive Disclosure</em><br><a href="https://www.nngroup.com/articles/progressive-disclosure/">https://www.nngroup.com/articles/progressive-disclosure/</a></p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e844efbd6c1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reducing Rider Distrust Through Route Transparency in Ride-Hailing Apps]]></title>
            <link>https://medium.com/@solaskarsonal/reducing-rider-distrust-through-route-transparency-in-ride-hailing-apps-e095e1572f8d?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e095e1572f8d</guid>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[uber]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 14:49:55 GMT</pubDate>
            <atom:updated>2026-05-06T12:03:32.725Z</atom:updated>
            <content:encoded><![CDATA[<h3>Uber: Reducing Rider Distrust Through Route Transparency in Ride-Hailing Apps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rtIxFVNvf6pgPHcMdaoJkw.png" /><figcaption><strong>Reducing Rider Distrust Through Route Transparency in Ride-Hailing Apps</strong></figcaption></figure><h3>Problem Statement:</h3><p><strong>Uber</strong>, one of the world’s most widely used ride-hailing platforms, gives riders no control over the route taken to their destination. Once a ride is confirmed, the app auto-selects a route with no traffic context shown, no alternatives offered, and no way to change it without either speaking to the driver or paying for an extra stop. For riders, especially women traveling alone, introverts, or those unfamiliar with a city this creates a quiet but consistent wall between them and any sense of agency over their own journey.</p><h3>What Makes a Good Routing Experience?</h3><p>A well-designed routing experience should:</p><ul><li>Show riders the route being taken <strong>before</strong> they confirm the ride, not after they’re already moving</li><li>Surface real traffic conditions so ETAs feel honest, not optimistic</li><li>Offer a small set of route options so riders can make an informed choice</li><li>Remove the need for riders to speak to drivers about navigation — protecting both parties from an uncomfortable mid-ride negotiation</li><li>Lock the agreed route in before the ride begins so neither side faces ambiguity, complaints, or fare disputes later</li></ul><h3>Issues With Current Experience:</h3><figure><img alt="Researching Issues with the current Uber interface" src="https://cdn-images-1.medium.com/max/1024/1*IE_HXIQnl7MobG17_cj69Q.png" /><figcaption><strong>Researching Issues with the current Uber interface</strong></figcaption></figure><p>The current Uber interface was researched through Reddit threads across multiple subreddits, where a consistent pattern of frustration emerged across hundreds of comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*hTdRX2p7uSGGZ2kIp5aYeQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*-HM6K9slq3e5fteSKMhkXA.jpeg" /><figcaption><strong>Lack of route choices at booking</strong></figcaption></figure><p><strong>Route is constrained at booking.</strong> Riders confirm a ride without a choice to what route the driver will take and there is no traffic overlay</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKNonaFZy2xRtsjWwHpjWQ.png" /><figcaption><strong>ETA is consistently downplayed</strong></figcaption></figure><p><strong>ETA is consistently downplayed.</strong> Multiple users noted that Uber shows optimistic times that don’t account for real traffic conditions. One thread explained this structurally Uber uses Google Maps Routes Preferred API, and its priority is speed for driver throughput, not accuracy for rider expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JkNHASyzvq8-CR9A-e9mYQ.png" /><figcaption><strong>Workarounds cost extra.</strong></figcaption></figure><p><strong>Workarounds cost extra.</strong> The most common solution riders discovered — adding a fake stop along the desired route to force the app down that path adds both steps and charges. It’s a workaround that penalises the rider for a limitation that shouldn’t exist.</p><p><strong>Verbal route suggestions are unreliable.</strong> Riders who politely asked drivers to take a different route reported mixed results. Several threads mentioned language barriers with foreign-born drivers, and others noted that drivers who deviate from the Uber-assigned route risk complaints and fare penalties even when the rider asked them to.</p><h3>Goals/Objectives of the Redesign</h3><ul><li><strong>Shift the route decision to before the ride begins</strong> when the rider has full autonomy and zero social pressure</li><li><strong>Surface real traffic data at booking</strong> so ETAs are honest and riders can make genuinely informed choices</li><li><strong>Offer 2–3 route options</strong> mapped to how people already think: fastest, shortest, or familiar</li><li><strong>Eliminate the need for mid-ride negotiation</strong> between rider and driver</li><li><strong>Protect drivers</strong> from complaints by locking in the agreed route before either party is in the car</li></ul><h3>Approaching the Redesign</h3><p>Before jumping into solutions, I spent time understanding the problem properly.</p><p>I studied Reddit threads across subreddits to understand how riders actually experienced the problem not just what they wished the app did, but what they were already doing to cope. This surfaced the <strong>fake-stop workaround, the language barrier pattern, and the ETA frustration as recurring, cross-demographic pain points</strong>, not isolated complaints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*tZbwI47xdya6dcTzKBOHMA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*hTdRX2p7uSGGZ2kIp5aYeQ.jpeg" /><figcaption><strong>Gap between Google Maps and Uber mental models.</strong></figcaption></figure><p>I then looked at how Google Maps handles route selection. Riders already have a strong mental model from a product they use every day. The gap between what <strong>Google Maps allows (tap to switch routes in seconds) </strong>and what <strong>Uber allows (nothing)</strong> was the clearest articulation of the design failure.</p><p>I mapped the existing user flow to find where the decision point currently sits — mid-ride, under social pressure, in an enclosed space — and identified that simply moving that decision earlier would resolve most of the friction without requiring a technically complex change.</p><p>Finally, I sketched the redesigned flow and worked through the route-selection screen, focusing on information hierarchy: what a rider needs to see, in what order, to make a confident choice in under ten seconds at the booking stage.</p><h3>Redefined Flow</h3><p>The original flow handed all route decisions to the driver. The redesigned flow introduces a single new step at the right moment before confirmation.</p><p><strong>Original flow:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zCNLytEWY0sGY95EwIofA.png" /><figcaption><strong>Original flow for Uber Route selection flow</strong></figcaption></figure><p><strong>Redesigned flow:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYCs7wcmNq_0NNDB5BAsjw.png" /><figcaption><strong>Redesigned flow for Uber Route selection flow</strong></figcaption></figure><p>The critical shift is not a new feature, it’s moving when the decision happens. Before confirmation, the rider has full agency and no pressure. When people feel they made a choice, they tolerate bad outcomes better. A rider stuck in traffic on a route they picked is frustrated at traffic. A rider stuck in traffic on a route they never saw is frustrated at Uber.</p><h3>Redesigned Experience</h3><p>Before committing to high-fidelity solutions, I used wireframes to map out the information hierarchy for route selection. This iterative sketching process led to a critical design crossroads between two distinct architectural approaches:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFjHh6SH8v-ICvpf8jgH7w.jpeg" /><figcaption><strong>Wireframes for the redesign</strong></figcaption></figure><ol><li>Introduce an isolated, sequential step where riders evaluate traffic, time, and fare options before transitioning to the vehicle selection screen.</li><li>Integrate the route options directly into the booking interface, allowing riders to compare paths and pricing simultaneously.</li></ol><p>I ultimately moved forward with the second option. The first approach violated the principle of cognitive efficiency; it forced riders to rely on their short-term memory by navigating back and forth between screens to compare different route-fare combinations. By merging these variables into a single view, I reduced the friction of choice.</p><h3>Final Flow Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e96iCZKZD2SpEfe0LoyQaA.png" /><figcaption><strong>Uber Ride Hailing Redesign</strong></figcaption></figure><h4>Route Selection at Booking</h4><p>After entering pickup and destination, riders see 2–3 route options before confirming. Each option shows estimated time, distance, and a simplified traffic state. Options are labelled in terms riders already use — faster, shorter, matching the mental model from Google Maps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u9_oA9cgZfjsRwVe7vZkjQ.png" /><figcaption><strong>Route Selection at Booking</strong></figcaption></figure><p>The choice of 2–3 routes is deliberate in a way that the goal isn’t to overwhelm riders with every possible path, it’s to give them enough to make a confident, informed choice without turning the booking screen into a navigation app. More than three options would shift the cognitive burden onto the rider without solving the trust problem.</p><h4>Simultaneously Compare Prices and Paths</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNiBQrVt6Vo7myHIr3rlTQ.png" /><figcaption><strong>Simultaneously Compare Prices and Paths</strong></figcaption></figure><p>By consolidating route options and pricing into a single view, the redesign allows riders to simultaneously compare costs across different paths and vehicle types, ensuring financial transparency before confirmation.</p><h4>Honest ETA with Traffic Context</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xZ8goUbzl8JtZHntyN0mog.png" /><figcaption><strong>Honest ETA with Traffic Context</strong></figcaption></figure><p>The redesign replaces single-point ETAs with a range tied to the selected route and current traffic. A rider who sees “8:43–8:47 pm” arrives at the same time as before but feels informed rather than misled. The violation of expectation, not the delay itself, is what erodes trust.</p><h4>Small UI Changes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZB0ixh8YwX6MHDJ7cIjuA.png" /><figcaption><strong>Small UI Changes</strong></figcaption></figure><p>Changed the position of <strong>‘shorter/faster/cheaper’</strong> labels from the map interface directly into the selection drawer, increasing visibility and aligning with the rider’s mental model during the decision-making stage.</p><h3>Design Decisions</h3><p><strong>Why 2–3 options, not more?</strong> Research showed riders weren’t frustrated by having too few choices, they were frustrated by having no information about the one choice made for them. The fix is legibility, not volume. Three options with clear labels take under five seconds to scan and choose.</p><p><strong>Why allow price and path comparison together?</strong> By showing multiple paths alongside their specific fares, the app removes the guesswork. Riders can immediately see if a faster highway route justifies a higher price or if a shorter, cheaper path through local streets is worth the extra minutes. This combined transparency empowers riders to make a trade-off that fits their current priority whether that is saving money or saving time.</p><p><strong>Why show traffic at booking, not just ETA?</strong> Because ETA alone is a number with no context. Traffic state gives riders the reasoning behind the number which is what they actually need to decide whether to take a different route, leave earlier, or switch to another option. Norman’s Visibility Principle applies here: users need to understand the system’s state, not just its output.¹</p><p><strong>What about the business side?</strong> Uber’s routing is optimised for driver throughput faster routes mean more rides per hour, which benefits both drivers and the platform. Giving riders route choice means some will pick longer paths, which creates some routing inefficiency. That’s a real tradeoff. But the research also shows the current design is generating its own cost: fake-stop fare disputes, mid-ride conflict, and riders who quietly stop trusting the app. Route transparency traded for reduced churn and fewer support escalations is a legitimate business case, not just a user experience preference.</p><h3>Conclusion</h3><p>A route map inside a ride-hailing app isn’t just a utility, it’s a trust interface. When riders can’t see where they’re going or why, they don’t sit comfortably in that uncertainty; they fill it with distrust.</p><p>Riders who feel in control don’t escalate. Drivers who follow a locked-in route don’t get flagged. The tension that used to happen inside the car now resolves before anyone gets in it</p><p>The fix here wasn’t technically complex. It was about recognising where anxiety enters the experience and placing a decision point there instead. Control, offered early, is a form of care. When the route is agreed before anyone gets in the car, the ride itself becomes what it was supposed to be just a ride.</p><p>[1]: principle.design: <em>Don Norman’s Principles of Design</em> <a href="https://principles.design/examples/don-norman-s-principles-of-design">https://principles.design/examples/don-norman-s-principles-of-design</a></p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e095e1572f8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cost of Deceptive Patterns: How Amazon India’s UX Erodes Trust]]></title>
            <link>https://medium.com/@solaskarsonal/the-cost-of-deceptive-patterns-how-amazon-indias-ux-erodes-trust-680fb5dff684?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/680fb5dff684</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[deceptive-patterns]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 16:52:07 GMT</pubDate>
            <atom:updated>2025-12-18T10:42:42.441Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Deceptive Patterns in Amazon India’s UX" src="https://cdn-images-1.medium.com/max/1024/1*Ip_Pe8Cto5wf5euEGhwM1g.png" /><figcaption><strong>Deceptive Patterns in Amazon India’s UX</strong></figcaption></figure><h3>Disclaimer</h3><p>This case study was written in August 2025 before the new Amazon App Update.</p><h3>Introduction</h3><p>Earlier this week, an Amazon order was marked <em>“Delivered”</em> on the app, despite never reaching my doorstep. In situations like these, customer support becomes a critical trust-recovery touchpoint. Expecting a quick resolution, I opened the Amazon India app to contact customer service.</p><p>What should have been a simple interaction turned into a <strong>30-minute navigation effort</strong> through layered menus, ambiguous issue categories, and circular flows. The once easily discoverable <em>“Chat with Us”</em> option was now buried deep within the interface, transforming a high-intent support task into a cognitively demanding experience.</p><p>This moment prompted a deeper investigation into Amazon India’s customer service flow and revealed a broader pattern of intentional friction embedded within the app’s support experience.</p><h3><strong>What are Deceptive patterns?</strong></h3><p>A deceptive pattern is a design pattern that prompts users to take an action that benefits the company employing the pattern by deceiving, misdirecting, shaming, or obstructing the user’s ability to make another (less profitable) choice.¹</p><p>Common examples include:</p><ul><li><strong>Hidden costs</strong> revealed only at checkout</li><li><strong>Forced continuity</strong> where free trials automatically convert to paid subscriptions</li><li><strong>Trick questions</strong> with confusing wording</li><li><strong>Roach motel</strong> designs that make it easy to get in but hard to get out</li></ul><h3>Why Deceptive Patterns Are Harmful</h3><p>Deceptive patterns create several critical problems. They erode user trust by making customers feel deceived and manipulated, leading to long-term brand damage. They cause significant user frustration and anxiety, particularly when people need urgent help. They violate ethical design principles by prioritizing profit over people. Perhaps most concerning, they disproportionately affect vulnerable users who may not recognize the manipulation.</p><h3>The Specific Deceptive Pattern: Hiding Customer Service</h3><p>Amazon India’s customer service interface exhibits a specific type of deceptive pattern: <strong>intentional obstruction</strong>. This occurs when a company deliberately makes it difficult for users to access support, hoping they’ll give up before reaching a human representative or resolving their issue.</p><h4>How It Manifests in Amazon India</h4><p>Based on extensive user research and app analysis, here’s how Amazon obscures its customer service:</p><figure><img alt="Looped Pathways in Amazon Support Discovery" src="https://cdn-images-1.medium.com/max/1024/1*XH1AsdCq_xGpdJKRxohEwg.png" /><figcaption><strong>Looped Pathways in Amazon Support Discovery</strong></figcaption></figure><p><strong>1. Deeply Nested Navigation</strong></p><ul><li>Customer Service is buried under several screens which are not intuitive.</li><li>The “Need More Help” option is hidden after navigating through multiple menus</li><li>No direct “Contact Us” visible on the main menu</li></ul><figure><img alt="Amazon Customer Service Flow Loop" src="https://cdn-images-1.medium.com/max/1024/1*MY_G-v8XEtHYRfYOxiEKGw.png" /><figcaption><strong>Amazon Customer Service Flow Loop</strong></figcaption></figure><p><strong>2. The “Customer Service Maze”</strong> Once you reach the support section, users encounter:</p><ul><li>8+ numbered options before finding actual human contact</li><li>Forced interaction with FAQ articles and automated solutions</li><li>“Browse more articles” redirects that loop users back</li><li>Even direct searches and querying with Rufus AI loop users back</li></ul><figure><img alt="Locating customer service via Rufus AI &amp; Search Bar" src="https://cdn-images-1.medium.com/max/1024/1*_c65cshYVBH6XN7YgS69xA.png" /><figcaption><strong>Locating Customer Service via Rufus AI &amp; Search Bar</strong></figcaption></figure><p><strong>3. Misleading Labels</strong></p><ul><li>“Need More Help” suggests limited support availability</li><li>No clear “Contact Support” or “Chat with Us” button</li><li>Video tutorials and self-serve solutions presented as primary options</li></ul><h3>User Impact: Real Reviews, Real Frustration</h3><p>Users<strong> </strong>across platforms reported identical issues with locating customer service on Amazon India’s app, indicating this is a systemic design problem, not isolated user error. Users described clicking on “first link” in results page, only to be taken back to menu in a circular loop. Many eventually gave up and searched Reddit or YouTube for video tutorials on <em>how to find chat support</em> on Amazon. One user’s tweet</p><blockquote><strong><em>@amazonIN has made it impossible to find the ‘contact us’ or ‘chat with us’ on the customer service tab?</em></strong></blockquote><p>reached over <strong>17k likes</strong> showing just how the design became progressively worse.</p><figure><img alt="User Reviews Across Google Play &amp; X" src="https://cdn-images-1.medium.com/max/1024/1*AcRN-TBc-ISc3anhF1KYRw.png" /><figcaption><strong>User Reviews Across Google Play &amp; X</strong></figcaption></figure><h3>How It Used to Be: A Comparison</h3><h4>Earlier Versions (2024 and before)</h4><p>In previous iterations of the Amazon India app, customer service was accessible and user-friendly:</p><ul><li><strong>Direct access</strong>: “Customer Service” or “Help” clearly visible in the main menu</li><li><strong>Two-tap access</strong>: Home → Customer Service → Chat/Call</li><li><strong>Clear labeling</strong>: Buttons explicitly said “Chat with us” or “Talk to us”</li><li><strong>Prioritized human contact</strong>: Self-serve options were available but didn’t gate access to support</li></ul><figure><img alt="Locating Amazon ‘Chat with us’ Option in Dec 2024" src="https://cdn-images-1.medium.com/max/1024/1*Q__pMzkdbMA3vzgg3vzjkg.png" /><figcaption><strong>Locating Amazon ‘Chat with us’ Option in Dec 2024. </strong><a href="https://youtube.com/shorts/Qzmyw_aXfJ4?si=ncFoBdnwXR5z3JiS"><strong>Image Source</strong></a></figcaption></figure><h4>Current Version (2025)</h4><p>The transformation is dramatic. The chat option is now hidden behind 4–5 layers of navigation and forced self-serve options. No clear “Customer Service” in main menu exists anymore. Users must navigate through “Your Account” to find support, which is counterintuitive. Circular loops redirect users away from human contact through “browse more articles” flows. The search bar itself has been questioned by users: <em>“Where is this option?”. </em>Users need to resort to YouTube or Reddit to navigate the “Chat with us” option by clicking irrelevant options in orders section.</p><figure><img alt="Reddit Threads For Locating Customer Service" src="https://cdn-images-1.medium.com/max/1024/1*e1lHW8Ybyaq8PPTX2aKTrg.png" /><figcaption><strong>Reddit Threads For Locating Customer Service</strong></figcaption></figure><p>The change is prominent even in website interfaces of Amazon, where in 2019 it was visible up top but now has shifted to the bottom of the menu overlay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9r_zB00u18yA4ORvW0SMMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z1bq86nRKH4Z_tFwilqjdA.png" /><figcaption><strong>Amazon Website in 2019 (Picture 1) vs. 2025 (Picture 2). </strong><a href="https://www.versionmuseum.com/history-of/amazon-website#google_vignette"><strong>Image Source</strong></a></figcaption></figure><h3><strong>Additional Deceptive Pattern: The Amazon Prime “Roach Motel”</strong></h3><p>Amazon India employs another notorious deceptive pattern with its Prime membership: the <strong>Roach Motel</strong>. This pattern makes it easy to sign up but deliberately difficult to cancel.</p><h3>How It Works:</h3><p><strong>Signing up for Prime:</strong></p><ul><li>One-tap enrollment with “Start Free Trial”</li><li>Prominent placement across the app</li><li>Benefits highlighted clearly</li></ul><p><strong>Canceling Prime:</strong></p><ul><li>Hidden deep in settings: Account → Prime Membership → Manage → End Membership</li><li>Multiple confirmation screens with guilt-inducing messages</li><li>Benefits reminder screens that try to change your mind</li><li>Confusing options: “End now” vs “End on [date]” vs “Remind me later”</li><li>Deceptive patterns in wording: “Are you sure you want to give up these benefits?”</li></ul><h3>The Combined Effect</h3><p>When users can’t find customer service to cancel Prime AND face the <strong>roach motel </strong>when they finally do, the frustration compounds. This creates a deliberately hostile user experience for anyone trying to manage their subscription.</p><h3>The Consequences</h3><figure><img alt="Consequences of Deceptive Patterns" src="https://cdn-images-1.medium.com/max/1024/1*AtoOzxqZqDu15mx6nChqkQ.png" /><figcaption><strong>Consequences of Deceptive Patterns</strong></figcaption></figure><p><strong>1. Brand Distrust:</strong> Users who feel manipulated lose faith in Amazon as a customer-first company. The gap between Amazon’s marketing promises and actual experience creates cognitive dissonance.</p><p><strong>2. Customer Churn: </strong>Frustrated users may switch to competitors like Flipkart, Myntra, or direct brand websites where support is more accessible.</p><p><strong>3. Negative Word-of-Mouth:</strong> Reddit threads, YouTube tutorials, and App Store reviews document the problem, damaging Amazon’s reputation. Social media amplifies individual frustrations into collective awareness.</p><p><strong>4. Vulnerable Users Suffer Most:</strong> Elderly users, non-tech-savvy customers, and those facing urgent issues are disproportionately affected.</p><p><strong>5. Support Staff Overwhelmed:</strong> When users finally reach support, they’re already frustrated and angry, making interactions more difficult for customer service representatives.</p><h3>Why This Matters</h3><p>This isn’t just about bad UX, it’s about ethics in design. When a company with Amazon’s resources and UX expertise creates such convoluted flows, it’s not accidental. It’s a deliberate choice that prioritizes cost savings over customer experience.</p><p>The irony is that Amazon built its empire on customer obsession and convenience. This dark pattern represents a departure from those founding principles, potentially damaging the very trust that made Amazon dominant.</p><h3>The Ethical Design Alternative</h3><p>Good UX should:</p><ul><li>Make important features easily discoverable</li><li>Respect users’ time and intelligence</li><li>Build trust through transparency</li><li>Prioritize user needs alongside business goals</li><li>Be accessible to users of all technical abilities</li></ul><p>Amazon’s current customer service design violates all of these principles.</p><h3>Conclusion</h3><p>Deceptive patterns like Amazon India’s hidden customer service may offer short-term cost savings, but they come at a significant long-term cost: eroding the trust and loyalty that took years to build. In an increasingly competitive market, where user experience is a key differentiator, these manipulative practices could drive customers toward more transparent alternatives.</p><p>[1]: NNGroup: <em>Deceptive Patterns in UX: How to Recognize and Avoid Them</em><br><a href="https://www.nngroup.com/articles/deceptive-patterns/">https://www.nngroup.com/articles/deceptive-patterns/</a></p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=680fb5dff684" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Puch AI — Democratizing Artificial Intelligence in India]]></title>
            <link>https://medium.com/@solaskarsonal/puch-ai-democratizing-artificial-intelligence-in-india-bd5bdbeaccbe?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd5bdbeaccbe</guid>
            <category><![CDATA[ux-casestudies]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[puch-ai]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Mon, 12 May 2025 07:42:35 GMT</pubDate>
            <atom:updated>2025-05-12T07:44:15.568Z</atom:updated>
            <content:encoded><![CDATA[<h3>Puch AI — Democratizing Artificial Intelligence in India</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SH5fN7wrX2zYhLFZtd3kNQ.png" /><figcaption><strong>Puch AI — Democratizing Artificial Intelligence in India</strong></figcaption></figure><h3>Executive Summary</h3><p>This case study dives into <strong>Puch AI</strong>, India’s first homegrown artificial intelligence platform, built to break down barriers around technology access. By focusing on user-friendly design, regional language support, and seamless voice interaction, Puch AI shows how thoughtful UX can make AI accessible and useful for everyday Indians — regardless of tech background, literacy level, or language.</p><h3>Introduction</h3><p><strong>Puch AI has been all over the Indian tech space</strong> — from <strong>X (formerly Twitter)</strong> to <strong>LinkedIn</strong>, it’s been grabbing attention. Curious about the hype, I decided to test it out. I was genuinely surprised by how intuitive and approachable its UX was, especially considering how complex AI can be. That inspired me to take a closer look — and ultimately redesign its official landing page. <strong><em>This case study features my visual redesign of Puch AI, but you can view the official website at </em></strong><a href="https://puch.ai/"><strong><em>puch.ai</em></strong></a><strong><em>.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_a450akK70pHycVwRHV8Pw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-96QPB_9RRuqRjKvvmh9g.png" /><figcaption>Redesigns for Puch.AI</figcaption></figure><p>In a country of over <strong>1.4 billion people</strong>, speaking <strong>22 officially recognized languages</strong> and hundreds of dialects, designing inclusive technology is no small task. But Puch AI offers a compelling example of how user-centered design can meet that challenge head-on. Let’s look at how it navigates India’s unique digital landscape and turns complex AI into a tool anyone can use.</p><h3>The Challenge: AI Accessibility in India</h3><h4>Digital and Linguistic Diversity</h4><p>India’s tech adoption story is layered and complex:</p><ul><li>Digital literacy ranges from highly tech-savvy to first-time smartphone users</li><li>A rich mix of languages and dialects across regions</li><li>Uneven access to internet and smart devices</li><li>Cultural and regional factors influencing how people use technology</li></ul><p>For many Indians, the idea of using AI feels far out of reach — not because they don’t need it, but because <strong>the design of traditional AI tools doesn’t account for their context</strong>.</p><blockquote><strong><em>Up to 70% of potential users in India lack the technical familiarity to use most AI interfaces.¹</em></strong><em><br> </em>[McKinsey Global Institute, 2024]</blockquote><h4>Technical Barriers</h4><p>AI tools have traditionally assumed a certain level of technical comfort:</p><ul><li>Understanding of complex terms</li><li>Comfort with advanced UIs</li><li>Text-heavy interaction assuming full literacy</li><li>Reliable high-speed internet</li></ul><p>But for AI to serve developing nations like India, it has to <strong>start from the ground up</strong>, not get adapted from Western-first models.</p><blockquote><em>“Design must match the real-world capabilities of users, not idealized versions of them.”²<br> </em>[World Economic Forum, 2023]</blockquote><h3>Puch AI’s User-Centered Design Approach</h3><h4>Platform Overview</h4><p>Puch AI solves these problems with <strong>four standout features</strong>:</p><ul><li><strong>WhatsApp Integration</strong> — No new apps to download</li><li><strong>Multilingual Support</strong> — Talk in your preferred language</li><li><strong>Voice-First Interaction</strong> — Speak instead of typing</li><li><strong>Real-Time Fact-Checking</strong> — Trustworthy answers in seconds</li></ul><h4>Design Philosophy</h4><p>At the core of Puch AI’s UX is simplicity and familiarity:</p><ul><li><strong>Use what people already use</strong> (WhatsApp)</li><li><strong>Design for the many, not the few</strong></li><li><strong>Let language flow naturally</strong></li><li><strong>Make AI helpful in real life, not just technically impressive</strong></li></ul><h3>UX Features Analysis</h3><h4>WhatsApp as Access Point</h4><p>WhatsApp is used by over <strong>535 million Indians</strong>, making it the most accessible app for mass communication. Puch AI smartly embeds its interface within WhatsApp to remove the barrier of downloading or learning a new app. This leverages an already-established trust and habit, creating a smoother, low-effort entry point for new AI users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NpVMaQnF2wz5jdQoPxGTxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YoTAD-DL5zTWWG6oQutEgQ.png" /><figcaption>WhatsApp as Access Point</figcaption></figure><p>This approach directly addresses several UX challenges:</p><ul><li>No additional app downloads required</li><li>Familiar interface requiring minimal new learning</li><li>Low data consumption compared to web-based alternatives</li><li>Works on entry-level smartphones</li></ul><h4>Multilingual Capabilities</h4><p>Puch AI responds in <strong>over 22 Indian languages</strong>, allowing users to interact in their native tongue. This approach broadens AI’s reach to people excluded by English-only systems. Puch AI’s use of <strong>Indic NLP</strong> allows questions to be asked and answered naturally, improving usability and trust. Its ability to detect and respond in the user’s preferred language addresses one of India’s most significant technological barriers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n1CoNpcOX5t8KkqJ99vGZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dn_qFdLoy0y8DsoYLTtIAw.png" /><figcaption>Multilingual Capabilities</figcaption></figure><p>Language-aware AI systems that adapt to the user rather than requiring the user to adapt to them can reduce abandonment rates by up to 70% in multilingual markets³. Puch AI exemplifies this principle by enabling seamless language switching and maintaining context across languages.</p><h4>Voice-First Interaction Design</h4><p>Puch AI’s support for voice messages and responses addresses literacy barriers while accommodating cultural preferences for spoken communication. Voice interfaces dramatically increase AI accessibility for semi-literate or illiterate populations, with studies showing 85% successful task completion rates compared to just 25% for text-based interfaces among these users.⁴</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJmzmo-y8FQ4tR6CekqfCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MfGhg11DEpYnWX9KvQJlg.png" /><figcaption>Voice-First Interaction Design</figcaption></figure><p>The voice interface features:</p><ul><li>Natural language processing optimized for Indian accents and speech patterns</li><li>Support for code-switching (mixing languages within conversations)</li><li>Adjustable speech rates for different user preferences</li><li>Low-bandwidth voice processing suitable for 2G and 3G networks</li></ul><h4>Fact-Checking Capabilities</h4><p>Puch AI emphasizes <strong>real-time fact-checking</strong>, helping users cut through misinformation — a prevalent issue in India’s digital media landscape. This makes the AI not just a knowledge tool, but also a <strong>trusted source of truth</strong>.</p><p>Misinformation spreads widely in India because of language diversity and limited media literacy. To counter this, AI-powered fact-checkers must be quick, culturally sensitive, and accessible in regional languages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ENEG9m5Y9xfNO390scu1A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqOZVaFMFCI_-9NUS6jZmA.png" /><figcaption>Fact-Checking Capabilities</figcaption></figure><p>Puch AI’s backend is tuned to access structured knowledge bases and deliver verified answers, especially useful in domains like public health, government schemes, or legal help.</p><p>The UX design emphasizes:</p><ul><li>Clear visual distinction between verified and unverified information</li><li>Transparent sourcing of factual claims</li><li>Simplified explanations of complex topics</li><li>Cultural sensitivity in presenting contradictory information</li></ul><h3>Successful Strategies</h3><ol><li><strong>Meet Users Where They Are</strong>: Leveraging existing platforms rather than requiring new behavior</li><li><strong>Minimize Cognitive Load</strong>: Progressive disclosure of features as users become comfortable</li><li><strong>Prioritize Value Over Features</strong>: Focusing on core utilities that provide immediate benefits</li><li><strong>Design for Constraints</strong>: Optimizing for low-bandwidth and entry-level devices</li><li><strong>Cultural Contextualization</strong>: Adapting responses to regional customs and communication styles</li></ol><h3>My Redesign</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FBwmupKyNQ5Ftcrg3nZrshX%2FPuch%3Fnode-id%3D47-684%26t%3DH4h5KApiY8qcxwzC-1%26scaling%3Dscale-down-width%26content-scaling%3Dfixed%26page-id%3D0%253A1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FBwmupKyNQ5Ftcrg3nZrshX%2FPuch%3Fnode-id%3D47-684%26t%3DH4h5KApiY8qcxwzC-1%26scaling%3Dscale-down-width%26content-scaling%3Dfixed%26page-id%3D0%253A1&amp;image=https%3A%2F%2Fwww.figma.com%2Ffile%2FBwmupKyNQ5Ftcrg3nZrshX%2Fthumbnail%3Fnode-id%3D47-684%26in-better-link-exp%3Dtrue%26t%3DH4h5KApiY8qcxwzC-1&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c29cdbd0c7b1893c2110da64066bdde/href">https://medium.com/media/2c29cdbd0c7b1893c2110da64066bdde/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FBwmupKyNQ5Ftcrg3nZrshX%2FPuch%3Fnode-id%3D10-147%26t%3DH4h5KApiY8qcxwzC-1%26scaling%3Dscale-down-width%26content-scaling%3Dfixed%26page-id%3D0%253A1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FBwmupKyNQ5Ftcrg3nZrshX%2FPuch%3Fnode-id%3D10-147%26t%3DH4h5KApiY8qcxwzC-1%26scaling%3Dscale-down-width%26content-scaling%3Dfixed%26page-id%3D0%253A1&amp;image=https%3A%2F%2Fwww.figma.com%2Ffile%2FBwmupKyNQ5Ftcrg3nZrshX%2Fthumbnail%3Fnode-id%3D10-147%26in-better-link-exp%3Dtrue%26t%3DH4h5KApiY8qcxwzC-1&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/b583ce1ee3b12ca4436b54d113a742ca/href">https://medium.com/media/b583ce1ee3b12ca4436b54d113a742ca/href</a></iframe><p>Check out the <a href="https://www.figma.com/proto/BwmupKyNQ5Ftcrg3nZrshX/Puch?node-id=47-684&amp;t=H4h5KApiY8qcxwzC-1&amp;scaling=scale-down-width&amp;content-scaling=fixed&amp;page-id=0%3A1">dark mode prototype</a> &amp; <a href="https://www.figma.com/proto/BwmupKyNQ5Ftcrg3nZrshX/Puch?node-id=10-147&amp;t=H4h5KApiY8qcxwzC-1&amp;scaling=scale-down-width&amp;content-scaling=fixed&amp;page-id=0%3A1">light mode prototype</a>.</p><h3>Conclusion</h3><p>Puch AI demonstrates how thoughtful UX design can democratize advanced technology across diverse populations. By prioritizing accessibility through familiar platforms, language support, voice interaction, and reliable information, it has created a model for AI deployment that truly serves the needs of all users, regardless of their technical background or linguistic preferences. The success of Puch AI offers valuable lessons for technology designers seeking to create truly inclusive digital experiences.</p><p>[1]: McKinsey Global Institute. (2024): <em>Notes from the AI frontier: Tackling digital and AI challenges in emerging economies</em></p><p>[2]: World Economic Forum. (2023): <em>Artificial Intelligence for India</em></p><p>[3]: MIT Technology Review. (2023): <em>How voice assistants are breaking down language barriers</em></p><p>[4]: Journal of AI Research. (2024): <em>Multilingual Voice Interfaces in Developing Regions</em></p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd5bdbeaccbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving CityFurnish’s Contact Us Experience: A UI/UX Redesign Case Study]]></title>
            <link>https://medium.com/@solaskarsonal/improving-cityfurnishs-contact-us-experience-a-ui-ux-redesign-case-study-d91053973e0b?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d91053973e0b</guid>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Mon, 28 Apr 2025 05:45:31 GMT</pubDate>
            <atom:updated>2025-04-28T05:46:33.996Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Beqfs18zs3ggp3QvlJ6q1g.png" /><figcaption>Improving CityFurnish’s Contact Us Experience.</figcaption></figure><h3>Problem Statement:</h3><p><a href="https://cityfurnish.com/">CityFurnish</a>, a furniture and appliance rental platform catering to working professionals — particularly those who have relocated from Tier 2/3 cities to Tier 1 metros — aims to offer convenience and flexibility in setting up modern living spaces. However, its current <a href="https://cityfurnish.com/pages/contact-us">Contact Us</a> page depends heavily on traditional support methods such as phone calls and emails, often resulting in slower response times and increased strain on customer support teams. Given that the Contact Us page serves as a crucial touchpoint for users seeking help or information, its current form does not align with the expectations of a digitally savvy audience.</p><h3>What Makes a Good Contact Us page?</h3><p>A well-designed Contact Us page should:</p><ul><li>Be immediately visible in the main navigation or footer for easy access — hiding this essential feature diminishes customer trust and satisfaction</li><li>Respect user convenience by not requiring account creation for basic inquiries (while account login makes sense for order-specific questions)</li><li>Provide clearly organized navigation with multiple communication channels that users can quickly identify and select based on their needs</li><li>Enhance the experience with contextual support elements like relevant FAQs or smart suggestions that may address common questions before contact is needed</li><li>Feature prominent calls-to-action that guide users to alternative support options when standard channels don’t meet their specific requirements</li></ul><h3>Issues With Current Interface:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fMgIq9_iWLQWTtyW" /><figcaption>Researching Issues with the Current CityFurnish Contact Us Page</figcaption></figure><p>The current interface had several issues in regards to contact us page:</p><ul><li>The <strong>Contact Us page was difficult to find</strong>, as it was buried towards the bottom of the side menu, reducing its visibility and accessibility.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eXODvpOU-bE_dLP5UzKYoA.png" /><figcaption>Nested Contact Us Page in CityFurnish’s Existing Inteface.</figcaption></figure><ul><li>Before logging in, the ‘Chat Now’ and ‘Raise a Service Request’ buttons redirected users to the Service Request page rather than opening a chat interface, <strong>leading to confusion and breaking user expectations.</strong></li><li>The <strong>Chat Bot floating action button (FAB) was non-functional</strong> unless the user logged in, offering no feedback or guidance, which caused a disjointed experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFk-cs6BnwIkqlzBqGV1KA.png" /><figcaption>Chat Bot FAB Authentication Issue.</figcaption></figure><ul><li>While office addresses were provided, there were <strong>no clickable links for mobile users</strong> to easily open the locations in their map applications, missing an important convenience opportunity.</li><li>The <strong>FAQ section lacked relevant questions that users typically have</strong> when seeking customer service support, limiting its usefulness.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*4GFYa6IVnGqrHo8ing7NpA.png" /><figcaption>Inadequate FAQ: Missing Common Customer Service Questions.</figcaption></figure><ul><li>After logging in and interacting with the chatbot, clicking the ‘X’ button <strong>triggered repeated prompts asking for feedback,</strong> making the experience frustrating and disruptive for users trying to exit the conversation smoothly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_P5bKE4QC66CO-PPBRoyA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*90rdaJ1EcXDwdx-Zn7WxXQ.png" /><figcaption>Issues with Exit Process: Repeated Feedback Prompts Disrupting User Experience.</figcaption></figure><h3>Goals/Objectives of the Redesign</h3><ul><li><strong>Streamline the information architecture</strong> to make support pathways clear and easy to navigate.</li><li><strong>Design intuitive, scannable support options</strong> that help users quickly find what they need.</li><li><strong>Focus on a mobile-first</strong>, human-centered design that ensures a smooth and responsive user experience across devices.</li><li><strong>Emphasize self-service tools</strong> such as FAQs, guided troubleshooting, and chatbot support to reduce reliance on direct calls and emails.</li><li><strong>Craft an effortless user journey</strong> that enables customers to resolve common issues efficiently without human intervention.</li></ul><h3>Approaching the Redesign</h3><p>Before jumping into design, I</p><ul><li>Studied CityFurnish’s current website to understand their brand style</li><li>Identified common customer queries in the furniture rental business</li><li>Looked at successful self-help contact pages for inspiration</li><li>Redefined the user flow</li><li>Made paper wireframes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqXSOxPWZjtZwLcdqflrGQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VbSSG5EIlaTk2Z0ZjTm5Jg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-YY8cOhUFnb1PR7bjP8DHg.jpeg" /><figcaption>My Approach to the Redesign.</figcaption></figure><h3>Redefined Flow</h3><p>I restructured the Contact Us experience as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UzGSzNPZq0Cw73Dk" /><figcaption>Redefined User Flow.</figcaption></figure><ul><li>Ask the user what help they need (via quick chips like “Track Order”, “Rental Extension”, “Refund”, etc.)</li><li>Based on the choice, display the most relevant action or contact option</li><li>Offer an AI chatbot for instant support and escalation</li><li>If unresolved, provide a clean handoff to human agents (via call or email)</li></ul><h3>Redesigned UI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wixxrbNykvF6_bRjqMJgiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1W8azVEY7WQo3h8V_wnD_g.png" /><figcaption>City Furnish Redesigns for Website and Mobile Interfaces.</figcaption></figure><h4>Design Decisions:</h4><ul><li><strong>Making Contact Information Readily Accessible:</strong> NNGroup’s¹ usability testing and eye-tracking studies reveal that users searching for “Contact Us” information typically look in the top-right corner or footer of websites. I’ve implemented a clearly visible icon to facilitate quick access to contact details.</li><li><strong>Moving the Search Bar:</strong> Although cityfurnish already had a search bar in the navigation, I moved it below with specific placeholder text as most users are conditioned to use search as their first action when looking for help. And the primary objective is reducing dependency on phone calls and emails. A good search function can immediately surface relevant FAQs, articles, and solutions without human intervention.</li><li><strong>Added Knowledge Base:</strong> Users can quickly navigate through most common help categories where they’ll find articles to help with their issues.</li><li><strong>Information Architecture Change:</strong> I changed the Information Architecture of the website to include the direct contact details &amp; address after the self help options.</li><li><strong>Added Direct Links:</strong> Users who are looking for physical addresses would find it useful to have direct links to the address via google maps, etc. This would spend their time manually typing in the address.</li><li><strong>Prominent Chatbot Button:</strong> Added a prominent chat bot floating action button that is easily accessible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fHKb6TUBoYPDz3lb" /><figcaption>Example Interface for Chatbot.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ZDOaNVmiWpXvb1Z" /><figcaption>Example Interface for Chatbot Escalation.</figcaption></figure><p>To scale support without overwhelming agents, I integrated a lightweight AI chatbot prototype. It:</p><ul><li>Handles <strong>FAQs</strong>, such as “How do I return a product?”</li><li><strong>Escalates</strong> to human support when needed</li><li>Learns from user interactions to <strong>improve over time</strong></li><li>Uses a friendly, conversational tone to keep users engaged</li></ul><h4>Design Decisions</h4><ul><li><strong>Option to Upload Images:</strong> Button to add images in case the user wants to report any damage.</li><li><strong>Chatbot Escalation Example: </strong>Consumers begin to resist chatbot customer service due to limited escalation options. With 60% of chatbots² providing no way to connect with a human agent during the conversation, customers must independently contact support lines to escalate issues. This disrupts their workflow, particularly when they simply need clarification on specific details in the chatbot’s response.</li></ul><h3>Conclusion</h3><p>A Contact Us page is more than a form — it’s a <strong>customer trust-building tool</strong>. Through this redesign, I aimed to create a <strong>seamless, modern, and assistive support experience</strong> that reflects the reliability and friendliness of CityFurnish.</p><p>This case study not only sharpened my visual and UX design thinking, but also deepened my understanding of how micro-interactions and automation (like AI chatbots) can enhance user satisfaction.</p><p>[1]: NNGroup: <em>‘Contact Us’ Page Guidelines</em> <a href="https://www.nngroup.com/articles/contact-us-pages/">https://www.nngroup.com/articles/contact-us-pages/</a></p><p>[2]: Forrester: <em>Predictions 2019: This Is The Year To Invest In Humans, As Backlash Against Chatbots And AI Begins </em><a href="https://www.forrester.com/blogs/predictions-2019-chatbots-and-ai-backlash/">https://www.forrester.com/blogs/predictions-2019-chatbots-and-ai-backlash/</a></p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d91053973e0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[McDelivery Coupon Redemption Flow Redesign: A UX Case Study]]></title>
            <link>https://medium.com/@solaskarsonal/mcdelivery-coupon-redemption-flow-redesign-a-ux-case-study-b1604e0a1288?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1604e0a1288</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[mcdelivery]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Thu, 03 Apr 2025 16:13:18 GMT</pubDate>
            <atom:updated>2025-04-03T16:32:24.369Z</atom:updated>
            <content:encoded><![CDATA[<h3>Streamlining McDelivery’s Coupon Experience: A User-Focused Redesign</h3><figure><img alt="McDelivery Coupon Redemption Flow Redesign" src="https://cdn-images-1.medium.com/max/1024/1*OXAXnQXIzRWPHoUpXZ2_GQ.png" /><figcaption>McDelivery Coupon Redemption Flow Redesign</figcaption></figure><h3>Introduction</h3><p>As a UX designer, I set out to improve the coupon redemption experience in the McDelivery app. This case study explores the problems with the current system and presents a solution that makes finding and applying coupons more intuitive and satisfying for users.</p><h3>Research Process</h3><p>To understand best practices in coupon redemption UX, I conducted competitive analysis across popular apps including <em>Swiggy, Amazon, BlinkIt, Zomato, FlipCart, and Myntra</em>. This revealed several consistent patterns in successful coupon experiences:</p><ul><li>Prominent coupon placement on cart pages</li><li>Dedicated coupon listing pages</li><li>Logical sorting by availability and discount value</li><li>Clear visual distinction for unavailable coupons</li><li>Search functionality for coupon codes</li></ul><h3>The Coupon Redemption Task Flow</h3><p>After analyzing multiple food delivery and e-commerce apps, I identified a common task flow for coupon redemption:</p><figure><img alt="Coupon Redemption Task Flow" src="https://cdn-images-1.medium.com/max/1024/0*qmdTdIzccVqbdK5_" /><figcaption>Coupon Redemption Task Flow</figcaption></figure><p>The task flow follows these key steps:</p><ol><li>User starts at the Cart Screen</li><li>Proceeds to Coupon Listing</li><li>Makes a decision to Apply/Browse Coupons</li></ol><h4>Takes one of two paths: Search/Paste a specific Coupon Code or Browse a List of Available Coupons</h4><ol><li>Applies the selected coupon</li><li>Confirmation that the coupon is applied to cart</li></ol><p>This standardized flow provides users with flexibility while maintaining clarity throughout the process.</p><h3>Common Pain Points in Coupon Experiences</h3><p>Through my research, I identified several frustration points that repeatedly appear in coupon redemption flows:</p><ol><li>Manual coupon entry instead of one-click application</li><li>Unclear distinction between available and unavailable coupons</li><li>Hidden or missing coupon code fields</li><li>Inadequate indication of discounted items and conditions</li><li>Discrepancies between applied discounts and final payment totals</li></ol><h3>The McDelivery App: Current Issues</h3><p>After selecting McDelivery for redesign, I identified specific problems with its coupon system:</p><ol><li>No clear visual distinction between available and unavailable coupons</li><li>Lack of coupon sorting options</li><li>Promo code field not prominently visible near checkout</li><li>Ineligible coupons not visually disabled</li><li>Confusing “Promo Not Applied” messaging despite coupons appearing active</li><li>Poor visibility of discounts in cart totals</li><li>Applied discounts not clearly displayed near final checkout amount</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dOL-nCEo4qlMsmIu" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2Qmpivvki9M-GI0e" /></figure><h3>My Redesign Solution</h3><figure><img alt="Final Screens for the checkout flow" src="https://cdn-images-1.medium.com/max/1024/0*QWS4v4VCyGQwVT4Q" /><figcaption>Final Screens for the checkout flow</figcaption></figure><h4>Cart Page and Coupon Listing Improvements:</h4><ol><li><strong>Accessible Search Field</strong>: Added a prominent input field for searching or pasting coupon codes</li><li><strong>Tabbed Organization</strong>: Implemented tabs to categorize different offer types (discounts, freebies, etc.)</li><li><strong>Clear Visual Hierarchy</strong>: Visually disabled inapplicable coupons for instant understanding of what’s available</li><li><strong>Enhanced “Offers &amp; Savings” Section</strong>: Improved with:</li></ol><ul><li>Convenient manual coupon input field</li><li>Showcase of best available coupons for current order</li></ul><figure><img alt="Cart Page and Coupon Listing Page Redesign" src="https://cdn-images-1.medium.com/max/1024/0*jcXAImUO0VFulXSh" /><figcaption><strong>Cart Page and Coupon Listing Page Redesign</strong></figcaption></figure><h4>Offer Applied Card Redesign:</h4><p>The original offer card was redesigned to be more informative, clearly showing:</p><ul><li>Applied coupon details</li><li>Resulting discount amount</li><li>Total payable amount with savings calculation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8vlfTz4LIrK3iTup" /><figcaption>Redesigned the offer card to provide clearer, more detailed information about applied discounts.</figcaption></figure><figure><img alt="Clearly reflected coupon code effects in the total payable amount so users can see their savings and understand how the total is calculated." src="https://cdn-images-1.medium.com/max/1024/0*xniUxePLKcGSL6Dr" /><figcaption>Clearly reflected coupon code effects in the total payable amount so users can see their savings and understand how the total is calculated.</figcaption></figure><p>This redesign ensures users can easily understand how discounts affect their final payment, creating a more transparent and satisfying checkout experience.</p><h3>Conclusion</h3><p>By addressing the key pain points in the McDelivery coupon redemption flow, this redesign creates a more intuitive, efficient, and satisfying user experience. The improvements focus on clarity, accessibility, and transparency — three essential elements for a successful coupon system. The redesigned flow follows established patterns that users are familiar with while eliminating confusion points, ultimately leading to higher coupon usage and customer satisfaction.</p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1604e0a1288" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QuickCompare: Reimagining Comparison Shopping]]></title>
            <link>https://medium.com/@solaskarsonal/quickcompare-reimagining-comparison-shopping-da78adceb7b8?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/da78adceb7b8</guid>
            <category><![CDATA[quick-commerce]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Mon, 03 Mar 2025 07:37:49 GMT</pubDate>
            <atom:updated>2026-05-06T12:04:06.547Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>QuickCompare: </strong>Reimagining Comparison Shopping into Intelligent Shopping.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rA7FAJoNd1PdWe3_vUCWDg.png" /><figcaption>Reimagining Comparison Shopping into Intelligent Shopping.</figcaption></figure><h3>CaseStudy Background</h3><p><a href="https://quickcompare.in/">QuickCompare</a> is a price comparison platform operating in the competitive Indian e-commerce ecosystem. The platform allows users to compare prices of everyday products across multiple delivery services including Instamart, Blinkit, Zepto, DMart, and BigBasket.</p><p>In urban India, quick commerce has seen explosive growth, with multiple platforms competing for market share through aggressive pricing, delivery speed, and subscription benefits. This fragmentation creates significant complexity for consumers trying to optimize their shopping experience. Users frequently toggle between 3–5 different apps to check prices, availability, and delivery times before making purchase decisions.</p><p>QuickCompare initially launched as a simple price aggregator but upon exploring the platform, I discovered that direct price comparison alone was insufficient for delivering meaningful value. This redesign aims to transform QuickCompare from a basic comparison utility into an intelligent shopping companion that considers all factors affecting the shopping decision.</p><h3>User Research and Insights</h3><p>In-depth interviews and usability testing with 10 users revealed several key insights:</p><ol><li><strong>Decision Complexity:</strong> Users reported regularly comparing products across 3+ platforms before making purchase decisions, with price being the primary factor but delivery speed gaining importance for urgent needs.</li><li><strong>Hidden Cost Frustration:</strong> Most users expressed significant frustration with discovering additional fees only at checkout, with 41% reporting they had abandoned purchases entirely upon discovering these hidden costs.</li><li><strong>Cross-Platform Optimization:</strong> Users reported they would distribute purchases across platforms to optimize savings if it were easy to do so, but only few actually did this regularly due to the complexity involved.</li><li><strong>Mental Model Mismatch:</strong> The platform’s organization around individual products contradicted users’ task-oriented approach of “completing a shopping list” rather than optimizing individual purchases.</li><li><strong>Time Value Variability:</strong> Users displayed significant variability in how they valued delivery time:</li></ol><ul><li>For urgent needs (e.g., missing ingredient for cooking), most users were willing to pay 10–20% more for sub-10-minute delivery</li><li>For regular restocking, only a small portion of users considered delivery time important. This context-sensitivity was not supported by the current design</li></ul><h3>Problems Identified</h3><h4>1. The Invisible Fee Trap</h4><p><strong>Problem:</strong> Base prices are displayed without factoring in small cart fees that apply when orders fall below minimum thresholds.</p><blockquote><strong>Example:</strong> A user comparing detergent prices sees a product listed for ₹564 on DMart appearing to be the cheapest option. However, after selecting this item, they discover at checkout that a ₹49 small cart fee applies, making the actual cost ₹613 — more expensive than alternatives on other platforms that had no hidden fees.</blockquote><p><strong>Impact:</strong> Users make decisions based on incomplete cost information, leading to frustration when unexpected charges appear at checkout. This damages trust in the platform and reduces return usage.</p><h4>2. Subscription Blindness</h4><p><strong>Problem:</strong> The platform doesn’t account for user subscriptions (Swiggy One, Zepto Pro, etc.) that eliminate delivery fees.</p><blockquote><strong>Example:</strong> A Swiggy One member comparing prices for groceries sees Instamart products as more expensive than Blinkit alternatives. However, their subscription provides free delivery on Instamart, making it actually cheaper when total costs are calculated. The current design gives no visibility to this crucial variable.</blockquote><p><strong>Impact:</strong> Subscribers cannot see their actual best options based on their membership benefits, forcing them to perform mental calculations or abandon the comparison tool entirely.</p><h4>3. The Time-Money Disconnect</h4><p><strong>Problem:</strong> Delivery times are displayed but not factored into the comparison algorithm or presented in a way that facilitates time-value decisions.</p><blockquote><strong>Example:</strong> When comparing identical packets of Surf Excel Matic Liquid, the platform shows one option at ₹564 with next day delivery with DMart Now and another at ₹575 with 6-minute delivery from Swiggy Instamart. For a user with immediate needs, the faster delivery represents significant added value, but the platform provides no mechanism to prioritize or visualize this tradeoff.</blockquote><figure><img alt="Lack of Time-Value Consideration." src="https://cdn-images-1.medium.com/max/977/1*aiDMcjEDAWr_ZP9P1-cnjw.png" /><figcaption>Fig.1: Lack of Time-Value Consideration.</figcaption></figure><p><strong>Impact:</strong> Users cannot easily identify the optimal price-time tradeoff for their specific needs, often requiring them to manually evaluate multiple factors across different screens.</p><h4>4. Single-Item Tunnel Vision</h4><p><strong>Problem:</strong> Only individual product comparisons are available, not full shopping cart optimization. (<a href="https://quickcompare.in/"><em>QuickCompare is currently working on adding a cart feature).</em></a></p><figure><img alt="Cart Comparison Feature" src="https://cdn-images-1.medium.com/max/903/1*dlQIQKtgwDHeTHGVfDvVyw.png" /><figcaption>Fig.2: Cart Comparison Feature</figcaption></figure><blockquote><strong>Example:</strong> A user wanting to purchase detergent, snacks, and vegetables needs to compare each item individually without seeing whether distributing their purchases across platforms (e.g., detergent from Blinkit, snacks from Instamart, vegetables from Zepto) would optimize their overall spending.</blockquote><p><strong>Impact:</strong> Users must manually calculate the best distribution of items across platforms, a complex task that few actually complete, resulting in suboptimal purchasing decisions and wasted money.</p><h4>5. Measurement Mayhem</h4><p><strong>Problem:</strong> Search results mix different product types, sizes, and units without proper categorization.</p><blockquote><strong>Example:</strong> Searching for “Detergent 2L” returns 5L bottles, powder detergents measured in kg, and even unrelated products like cooking oils, forcing users to manually filter through irrelevant or non-comparable items.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*2F8uA5NdddgApmnHBaxLmg.png" /><figcaption>Fig. 3: Mix of results for a search “Detergent 2L”. The search result includes mostly detergents varying across quantity beyond 2L and even includes different product, i.e Mustard Oil.</figcaption></figure><p><strong>Impact:</strong> The cognitive load increases significantly when trying to make like-for-like comparisons, resulting in poor decision-making or abandonment of the comparison process entirely.</p><h4>6. Filter &amp; Sort Deficiency</h4><p><strong>Problem:</strong> Basic functionality for sorting by unit price or filtering by product attributes is missing.</p><blockquote><strong>Example:</strong> When comparing detergents, users cannot filter by or sort by price per liter, delivery times, making meaningful comparisons much more difficult than necessary.</blockquote><p><strong>Impact:</strong> Users face unnecessary cognitive load when making comparisons, often resorting to mental shortcuts that lead to suboptimal purchasing decisions.</p><h3>Design Solutions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V4G6vFVdPWVXCfUaCtI93w.jpeg" /><figcaption>Fig. 4: Approaching The Redesign</figcaption></figure><h4>1. Total Cost Intelligence</h4><p>The redesign implements “True Cost” display that accounts for all variables affecting final price:</p><ul><li>Base product prices are shown alongside the total cost including any applicable small cart fees</li><li>Threshold warnings alert users when they’re close to minimum order values, with suggestions for additional items to avoid fees.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p1_re2HH9YL91y4tvdbrMw.png" /><figcaption>Fig. 5: Threshold warnings alert for products on Swiggy Instamart.</figcaption></figure><h4>2. Time-Value Optimization Engine</h4><p>The redesign introduces intelligent time-price balancing:</p><ul><li>Delivery platforms are organized by delivery time (5 mins, 6 mins, 18 mins, 23 mins)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rTVqk0_LX_lX-CIUuIHeTA.png" /><figcaption>Fig. 6: Time-Price tradeoff for total cart value</figcaption></figure><ul><li>The cart view allows users to see how delivery time affects their total shopping experience</li><li>This acknowledges that the “best” option varies based on urgency and context</li></ul><h4>3. Multi-Platform Cart Genius</h4><p>The redesign introduces a revolutionary unified cart experience:</p><ul><li>As demonstrated, users can build a complete shopping list and see it optimized across platforms.</li><li>The QuickCompare Cart calculates the most cost-effective distribution of items.</li><li>Users can clearly see total costs across each platform.</li><li>The interface shows potential savings compared to single-platform shopping.</li><li>This transforms comparison from an item-level to a cart-level activity, matching users’ actual shopping goals.</li></ul><figure><img alt="Cart Page for QuickCompare Redesign." src="https://cdn-images-1.medium.com/max/1024/1*Q9EhSZha3Pax9X5y2d8aXw.png" /><figcaption>Fig. 7: Cart Page</figcaption></figure><h4>4. Standardized Product Architecture</h4><p>The redesign creates clarity through consistent categorization:</p><ul><li>Products are organized into clear categories with standardized attributes</li><li>Units are normalized (L/kg/g) for fair comparison</li><li>Quantity information is consistently displayed.</li><li>This eliminates the cognitive load of mentally converting between different measurement units.</li></ul><figure><img alt="Quantity Standardization." src="https://cdn-images-1.medium.com/max/1024/1*Lz5Oy076jDUhf-WVIlXKEw.png" /><figcaption>Fig. 8: Quantity Standardization.</figcaption></figure><h4>5. Precision Filter Framework</h4><p>The redesign implements intuitive filtering and sorting:</p><ul><li>The “Sort By Price” button enables quick price-based organization</li><li>Category filters like “Combo Packs” help users find specific product types</li><li>Size and quantity filters allow for like-for-like comparisons</li><li>This dramatically reduces the effort required to find truly comparable products</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rk8IgB6ZGdeXqIY_RRSTiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0KRC5jO8-IIkQW8Vi1JoAw.png" /><figcaption>Fig. 9 &amp; 10: Results for different filters ‘Get It Now’ &amp; ‘Combo Packs’.</figcaption></figure><h3>Business Impact Through UX Excellence</h3><p>The redesigned QuickCompare transforms key UX improvements into significant business value:</p><h4>1. Competitive Moat Creation</h4><p>The sophisticated UX creates substantial data advantage as each user interaction strengthens the platform’s understanding of pricing patterns and user preferences, creating a self-reinforcing competitive advantage.</p><h4>2. User-Centric Growth Engine</h4><p>The improved user experience drives organic growth metrics such as:</p><ul><li><strong>Reduced Acquisition Costs:</strong> High satisfaction leads to word-of-mouth referrals, reducing the cost of acquiring new users.</li><li><strong>Increased Engagement:</strong> A more valuable tool encourages deeper platform engagement, with users initiating their shopping journey on QuickCompare.</li></ul><h4>3. Strategic Market Positioning</h4><p>The redesign positions QuickCompare as an essential intermediary in the e-commerce ecosystem:</p><ul><li><strong>Platform Independence:</strong> By being platform-agnostic, QuickCompare becomes a trusted advisor in the fragmented quick commerce spacer.</li><li><strong>Network Effects:</strong> Each new platform integration and each new user improves the data quality for everyone.</li></ul><h3>Final Words</h3><p>The QuickCompare redesign demonstrates how addressing fundamental user pain points can transform a basic utility into an essential shopping companion. By evolving from simple price comparison to intelligent shopping optimization, the platform delivers exponentially more value to both users and business stakeholders.</p><p>This redesign acknowledges that shopping decisions are multi-dimensional, balancing price, time, convenience, and platform preferences. By helping users navigate this complexity, QuickCompare becomes an indispensable tool in the Indian e-commerce ecosystem.</p><p>Most importantly, this redesign achieves the rare alignment where business success directly correlates with user value. By helping users make truly optimal shopping decisions — incorporating all relevant factors beyond just base price — QuickCompare creates a sustainable competitive advantage while genuinely improving the lives of its users.</p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da78adceb7b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hidden Constraints: How Swiggy’s Address Change Limitation Creates User Friction]]></title>
            <link>https://medium.com/@solaskarsonal/hidden-constraints-how-swiggys-address-change-limitation-creates-user-friction-cce2643c2545?source=rss-8671974d8e7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cce2643c2545</guid>
            <category><![CDATA[swiggy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sonal Solaskar]]></dc:creator>
            <pubDate>Wed, 26 Feb 2025 06:55:22 GMT</pubDate>
            <atom:updated>2025-04-28T07:07:42.889Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*09ZVgHF0bkgr1WXycoJgSQ.png" /></figure><h3>The Problem</h3><p>Swiggy, a popular food delivery platform, has more than 14 million users in India, allows users to change their delivery address after an order is placed. But most users are unaware of this feature and the fact that they can only change it once. While this limitation is documented in their guidelines, the user interface fails to adequately communicate this constraint during the order process, creating potential frustration and financial consequences for users.</p><h3>User Scenario</h3><p>A customer placed an order but needed to modify the delivery address. The reasons could be various:</p><ul><li>Accidentally selecting the wrong saved address.</li><li>Using an outdated address stored in their profile.</li><li>Exploring the order interface and triggering an address change unintentionally.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FnelSMLi03VPaiN46KjJwg.png" /><figcaption><em>Fig. 1. Users unaware of address change option and its rules.</em></figcaption></figure><p>In my particular case, I was exploring the page after placing the order and changed the delivery address, only to realize afterward that I couldn’t modify it again. Fortunately, the two addresses were in close proximity, and the delivery driver accommodated the situation. However, this positive outcome relied entirely on driver cooperation rather than system design.</p><h3>Where The Interface Falls Short</h3><ul><li><strong>Insufficient Warning</strong>: Despite documenting the “one-change only” policy in their guidelines, Swiggy provides no prominent banner, alert, or confirmation message informing users of this limitation during the address change process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*OoDRE6aQuc5J_W4orORG4Q.png" /><figcaption><em>Fig.2. Edit address option at the end of the screen.</em></figcaption></figure><ul><li><strong>Hidden Consequences</strong>: Users are unaware of the implications of their actions. The interface doesn’t communicate that <strong><em>changing an address is an option</em></strong> and an one-time, irreversible action.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*oFqpGqXERXh0SQcufWVqDA.png" /><figcaption>Fig. 3. User Testimonials.</figcaption></figure><ul><li><strong>Costly Mistakes</strong>: When users need to make additional changes, their only options are to:</li></ul><ol><li>Cancel the order entirely and reorder (<em>incurring potential cancellation fees</em>).</li><li>Hope for driver cooperation (<em>unpredictable and inconsistent</em>).</li><li>Accept delivery at incorrect address.</li></ol><ul><li><strong>Poor Information Architecture</strong>: The order details section, where users would need to change their address, is <strong>buried beneath excessive scrolling</strong> and numerous advertisements. This placement makes it difficult for users to locate and modify their delivery information in a timely manner.</li><li><strong>Financial Impact on Users</strong>: Due to the lack of awareness about this feature limitation, users frequently find themselves in situations where they must cancel orders and reorder, resulting in financial losses. These negative experiences <strong>create significant frustration and erode trust in the platform</strong>.</li></ul><h3>Reimagining Address Changes</h3><p>This interface is redesigned to:</p><ol><li>Improve information architecture by placing critical order details above advertisements and making them immediately accessible.</li><li>Adding a clear warning banner before address changes are confirmed.</li><li>Implementing a confirmation modal explaining the one-time change limitation.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*11Oklb-128xxuavg5ot4nA.png" /><figcaption>Fig. 4. Comparison of Swiggy screen and my redesign.</figcaption></figure><h3>Why Small UX Details Matter Big Time</h3><p>While users rarely change their address after placing an order, it’s still an UX issue with the lack of directions and incomplete information. This case study highlights how seemingly minor UX oversights can create significant friction points in the customer journey. By failing to properly communicate critical limitations at the right moment in the user flow, Swiggy creates unnecessary confusion, financial impact, and frustration for their customers.</p><p>The lesson learnt: Important restrictions should be surfaced within the interface at the moment of relevance, not buried in guidelines or terms of service. Additionally, critical functionality should be readily accessible rather than hidden beneath non-essential content.</p><p>Did you like this post? Here’s how you can support me:</p><ul><li>👏 Give me a clap &amp; <a href="https://medium.com/@solaskarsonal">follow me!</a></li><li>👩‍💻 Connect with me on <a href="https://www.linkedin.com/in/sonal-solaskar/">LinkedIn</a>!</li><li>👩‍🎨Follow me on <a href="https://x.com/solaskarso/">X</a> and <a href="https://www.behance.net/sonalsolaskar">Behance</a>!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cce2643c2545" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>