<?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 Vanshika on Medium]]></title>
        <description><![CDATA[Stories by Vanshika on Medium]]></description>
        <link>https://medium.com/@vanshika.2511?source=rss-8f746b724032------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XrNEary02ktoFoPeHL9pow.png</url>
            <title>Stories by Vanshika on Medium</title>
            <link>https://medium.com/@vanshika.2511?source=rss-8f746b724032------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:34:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vanshika.2511/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[From “Not For Me” to “Hotstar Knows Me”: Designing Content Reactions]]></title>
            <link>https://blog.hotstar.com/from-not-for-me-to-hotstar-knows-me-designing-content-reactions-369b4f71125a?source=rss-8f746b724032------2</link>
            <guid isPermaLink="false">https://medium.com/p/369b4f71125a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-feedback]]></category>
            <dc:creator><![CDATA[Vanshika]]></dc:creator>
            <pubDate>Sun, 23 Nov 2025 11:11:12 GMT</pubDate>
            <atom:updated>2025-11-23T11:11:12.168Z</atom:updated>
            <content:encoded><![CDATA[<p>Building meaningful user feedback mechanisms that actually improve recommendations</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LV1oiH9Ozaut-OTwGVmmdw.png" /></figure><p>Personalisation is a tough nut to crack. Despite having one of the largest curated media libraries in the world, we continue to tune how personalisation can work better for our customers. Here, we discuss how customer input forms a key component in making better recommendations and how we set about asking you, our customer, to help us make a real connection with you, for your content.</p><h3>The “Content Paradox” Problem</h3><p>Despite offering <strong>over 7000 content pieces in 11 languages, 30+ genres and channels</strong> on JioHotstar, we have repeatedly received feedback from our customers that <strong>there is not enough relevant content for them</strong>. This indicates a <strong>disconnect between the product and the users</strong>, and shows that JioHotstar needs to understand people’s taste better.</p><h4>The Core Issue</h4><p>Our recommendation algorithm was making educated guesses based on watch time, not actual enjoyment.</p><p>Think about it, how many times have you watched a series to its bitter end, or finished a movie just to see how badly it could end? Take a look at this example:</p><p><em>Shreya binged an entire season of a drama series and even though she didn’t like it much, she ended up finishing it just to know the ending. She doesn’t want to watch any more TV series like this one again though.</em></p><p>In such a scenario, the recommendation system will take their watch time as a positive signal, assume that the person liked the content and will suggest similar content to them not fully understanding if the person actually enjoyed it or not.</p><h3>The Problem Statement</h3><p>To solve this and understand our customers better, we needed to explicitly understand what they like and dislike, which leads us to our <strong>problem statement:</strong></p><blockquote>How might we enable customers to meaningfully express their content reactions so they receive better recommendations and develop deeper platform engagement?</blockquote><p>Let’s dig into this problem statement and focus on the key problems to solve:</p><ol><li><strong>Expression:</strong> How can people meaningfully communicate their feelings?</li><li><strong>Encouragement:</strong> How do we motivate authentic feedback?</li><li><strong>Investment:</strong> How do we create lasting engagement through quick wins?</li></ol><h3>What do people want to express?</h3><p>We started by studying how people naturally talk about content. You know that moment when your group chat goes off after someone watches something amazing (or hilariously terrible)?</p><ul><li>“This is cinema!” → Pure love and recommendation-worthy</li><li>“It was fine, I guess” → Lukewarm, forgettable</li><li>“Meh, not really my thing” → Personal preference, not necessarily bad</li><li>“What did I just watch?!” → Strong dislike, avoid similar content</li><li>“I’m obsessed!” → Rewatchable, share with friends</li></ul><h4>The emotional spectrums we discovered</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_V0h-OtH0DNz7scFCgRSw.png" /></figure><h3>How can they meaningfully express these signals?</h3><p>Before diving into the designs, we uncovered a crucial pattern in how people actually discover content:</p><ul><li>People often find new shows and movies based on what their friends and social circle are watching and liking</li><li>Viewers also gravitate towards content trays like ‘Latest and Trending’ or the ‘Top 10’ list which highlight popular content among other users.</li><li>Social validation plays a crucial role in discovering and deciding what to watch.</li></ul><p>All this social validation was happening <em>outside</em> JioHotstar. We were losing the most powerful recommendation engine: peer influence, to WhatsApp groups and Instagram stories.</p><p><strong>The breakthrough realisation:</strong> If we could capture these social signals on our platform, we wouldn’t just improve individual recommendations, we’d create a network effect where every user’s feedback improves everyone else’s experience.</p><p>This social insight fundamentally changed our design approach. We needed something that felt like <strong>talking to a friend</strong>, not filling out a survey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*31bP86KBoEc7IBi6_Z9qtA.png" /><figcaption>Types of Ratings</figcaption></figure><p><strong>Star ratings?</strong> Too clinical, they’re for critics writing reviews, not friends sharing opinions.</p><p><strong>Thumbs up/down?</strong> Too binary, doesn’t capture the nuance of “it was well-made but not my taste.”</p><p><strong>Text reviews?</strong> Too effortful, most people don’t have the time to write paragraphs, they react.</p><p><strong>Emoji reactions?</strong> They mirror exactly how people communicate about content naturally:</p><ul><li>Emotionally expressive → Just like your WhatsApp reactions</li><li>Universally understood → No language barriers in emotional expression</li><li>Low cognitive load → One tap, like reacting to a friend’s story</li><li>Socially familiar → Feels like every other social platform you use</li></ul><p>So, emoji reactions seemed like the right choice and we settled on 5 emojis for people to express their reactions to a content. This is the first iteration we tested with our users:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ds0rooug8t8fg9wgKRPILQ.png" /></figure><h3>The User Testing Reality Check</h3><p>Until now, we were designing based on insights from secondary research and our intuition of what felt right for the users. This is where our user research team came in. The nuanced insights we gathered through the user study made us revisit our decisions:</p><ul><li><strong>FOMO:</strong> “If I select ‘Hate’, will I miss out on similar good content?” Users were hesitant about the Hate reaction, fearing that this would remove all similar recommendations.</li><li><strong>Word extremity:</strong> Words like ‘Hate’ felt too harsh for a bad movie, and discouraged them from rating the content negatively even if they didn’t like the content.</li><li><strong>Decision paralysis:</strong> ‘Neutral’ became an easy way out for users when they were unsure or didn’t want to think. It didn’t lead to concrete inputs for us to improve their recommendations.</li></ul><p>Based on these insights, we narrowed it down to three well-understood options:</p><ul><li><strong>Love-</strong> More like this, recommend to similar users</li><li><strong>Like- </strong>Decent content, mild positive signal</li><li><strong>Dislike- </strong>Personal taste mismatch, no judgment on quality</li></ul><p>After finalising the three reactions, something still felt off. The term <strong>‘Dislike</strong>’ seemed too strong and might deter users from selecting it.</p><p>We began brainstorming for a better alternative. After considering options like ‘Boring,’ ‘Pass,’ and ‘Meh, ‘<strong>Not for me</strong>’ seemed like the best choice. It conveyed a personal preference without being too strong. The copy matters as much as the functionality.</p><h4>Our Final Trio</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*e1YTzrRwNsKyCu-eXHv5Eg.png" /><figcaption>Final Reactions for Content Rating</figcaption></figure><p>Now that we have our perfect star-cast, let’s move on to the second part of the problem statement:</p><blockquote>How might we<strong> encourage and enable customers </strong>to meaningfully express these reactions?</blockquote><p>To encourage and enable customers, it is crucial to answer the question:</p><h3>When and How to ask for Rating?</h3><p>People open JioHotstar to sit back and relax so asking them to rate shouldn’t be a hindrance in users’ journeys or feel like an extra task to them.</p><p><strong>Core principle:</strong> Prompt naturally, never interrupt the entertainment experience. How can we ensure we follow this key principle and position these reactions?</p><h4>Our Three-Point Strategy</h4><p><strong>1. Post-Content Prompt (Primary)</strong> <br>Right when credits roll, emotions are fresh, context is clear, no interruption to the next choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*TXjss1nSCADOVvCrXlhDYA.gif" /><figcaption>Landscape Player at the End of Content</figcaption></figure><p><strong>2. Content Detail Page (Persistent and Deterministic)</strong><br>Always available for second thoughts or delayed reactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*7lrcV1nheUxkJuzygKeSbA.gif" /><figcaption>Content Details Page</figcaption></figure><p><strong>3. Homepage Gentle Reminder (Recovery)</strong> <br>Unobtrusive nudge for missed opportunities: “How did you feel about that show you watched last night?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5pc1DjKHwAbPdBHaP63_A.png" /><figcaption>Content Rating Prompt on Home Page</figcaption></figure><h3>The Magic of Micro-Interactions</h3><p>Animation helps in building user attention and curiosity while creating a sense of delight. Each emoji needed a personality that felt human and delightful.</p><p>Working with our team of motion designers we iterated on:</p><ul><li>Eye expressions that convey genuine emotion</li><li>Subtle movements that feel natural, not robotic</li><li>Animation timing that feels responsive, not laggy</li></ul><p>We iterated continuously on every element until we were able to achieve this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c37xdb8kDwJhfUcKly1aUw.gif" /></figure><p>Since it was important that the rating prompt can’t be obtrusive at all and shouldn’t hinder user’s other flows, it became even more crucial to grab users’ attention with subtle animations so they discover the feature easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rUJmvUVBAd1kK3roT3Fc9w.gif" /></figure><h3>Closing the Loop with Quick Wins</h3><p>When we talk about retention, that is, encouraging customers to interact with the feature repeatedly, we need to keep in mind <strong>what value our customers are getting</strong> from it and <strong>how to clearly communicate these benefits to them </strong>bringing us to the third part of the problem statement:</p><blockquote>How might we help our customers to <strong>build a deeper investment</strong> in the product</blockquote><p>Showing content based on users’ ratings can make them feel that Hotstar is already listening to them, providing immediate reward. Once users rate a content, they see a content tray on the homepage, featuring content similar to what they reacted positively to, called the “Because You Loved” tray.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MaJRcAYgQ7e8WFXyhaIP8Q.png" /><figcaption>Recommendation tray on homepage based on what people rated</figcaption></figure><p>When users see their ratings translate to better content suggestions within hours, they understand the value exchange and engage more.</p><h3><strong>The Impact</strong></h3><h4><strong>Adoption Beyond Expectations</strong></h4><p>We initially assumed getting users to take actions outside their primary entertainment flow would be challenging. We were wrong. When people experienced tangible quick wins, like improved recommendations, they willingly engaged with the rating feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Upo5e7dW9Qie6wuT4rhIAA.png" /></figure><p><strong>The Trust-Engagement Loop: </strong>Users who rated content showed meaningful engagement with the “Because You Loved” tray, proving the value exchange was working. This created a virtuous cycle: better ratings → better recommendations → more rating behavior.</p><p><strong>Content Discovery Transformation: </strong>Users who embraced rating began exploring substantially more diverse content titles, moving beyond their typical viewing patterns. The platform successfully broke them out of content silos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0VA2qGkea11iqj3raSFgg.png" /></figure><p><strong>Quality Engagement Increase: </strong>People who rated content spent significantly more time watching content per session, indicating they were finding genuinely engaging content.</p><p><strong>Platform-Wide Impact:</strong> The individual behavior changes aggregated into meaningful platform improvements, validating that better individual recommendations create better overall user experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eD1CIOKOJ1R1Rc3eGCTMNg.png" /></figure><p>On an entertainment platform where people come to relax, asking for feedback seemed counterintuitive but they experienced delight and immediate personal value which helped build rating habits.</p><p>The success we had with Content Rating has given us confidence to continue weaving the social fabric on JioHotstar. Watch out this space for more updates.</p><p><em>Passionate about breaking the barriers and building world class experiences at scale? Join us: </em><a href="https://www.jiohotstar.design/"><em>https://www.jiohotstar.design/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=369b4f71125a" width="1" height="1" alt=""><hr><p><a href="https://blog.hotstar.com/from-not-for-me-to-hotstar-knows-me-designing-content-reactions-369b4f71125a">From “Not For Me” to “Hotstar Knows Me”: Designing Content Reactions</a> was originally published in <a href="https://blog.hotstar.com/">JioHotstar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI/UX Case Study — Enabling users to book tickets seamlessly with least friction]]></title>
            <link>https://medium.muz.li/ui-ux-case-study-enabling-users-to-book-tickets-seamlessly-with-least-friction-fce2c5f1d2db?source=rss-8f746b724032------2</link>
            <guid isPermaLink="false">https://medium.com/p/fce2c5f1d2db</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Vanshika]]></dc:creator>
            <pubDate>Tue, 01 Jun 2021 10:02:29 GMT</pubDate>
            <atom:updated>2022-02-19T17:23:13.993Z</atom:updated>
            <content:encoded><![CDATA[<h3>UI/UX Case Study — Enabling users to book tickets seamlessly with least friction</h3><h4>In this article, I’ll explain how I approached redesigning the redBus search results page and its booking flow.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ck5ZVkk8eObRNUoyNXyhhg.png" /></figure><h3>What is redBus?</h3><p>redBus is a renowned <strong>online bus ticketing platform</strong> that provides ticket booking facility and helps the users in booking the seats of their choice.</p><h3>Why the Redesign?</h3><p>Once, I was trying to book a bus ticket on redBus for the very first time. Although, being a tech-savvy person, I was able to book the tickets successfully. But since redBus has a wide variety of users who might not be tech-savvy, I felt the design could be a lot more easy to understand and straight forward.</p><p>Here are some of my observations, and in this case study I’m going to elaborate on them.</p><ul><li><strong>Visual clutter</strong> makes it difficult to comprehend the important information.</li><li><strong>Lack of visual hierarchy</strong> results in overlooking of important data such as bus type, change of date, sorting options, etc.</li><li><strong>Sorting options</strong> don’t look like they are clickable. There isn’t enough emphasis on them to make sorting options stand out.</li><li><strong>The newly introduced filters</strong> look like product cards/pop-up ads rather than filters. I asked some users to use the website. I observed that they didn’t even click on those filters because they confused them as ads.</li><li><strong>The transition between booking flows</strong> is not flexible. When I reached the payment options page while booking the seats, it didn’t allow me to go one step back and change my boarding point without loosing my current selections. I was directed all the way back to the search results page where I had to select the bus and seats all over again. It became a frustrating task.</li></ul><p>Also, the UI looked pretty outdated. It surely needed a makeover. So I decided to revamp the interface and simplify the ticket booking flow.</p><h3><strong><em>Let’s get started!</em></strong></h3><h4>Competitive Analysis</h4><p>Before starting the project, I did competitive analysis to identify existing design patterns. I studied user flow of all kinds of booking websites, be it bus/ flight ticketing, hotel booking, e-commerce, etc. to understand the decision making factors of a user, in a better way. Some of the websites were</p><ul><li><a href="http://omio.com/">Omio.com</a></li><li><a href="http://momondo.com/">Momondo.com</a></li><li><a href="http://airbnb.com/">Airbnb.com</a></li><li><a href="http://agoda.com/">Agoda.com</a></li><li><a href="http://makemytrip.com/">Makemytrip.com</a></li></ul><p>Although, these platforms share similarities in terms of functionality, but they still differ in the way they shape search and booking experience.</p><h4>User Research</h4><p>In order to gain some perspective, I asked some of my friends (existing users as well as the ones who had never used redBus before) to use the website and these are the common pain points that they shared :</p><p>1. There is an <strong>over-abundance of content</strong> on the Search Results Page which is <strong>distracting </strong>them<strong> while making a decision</strong>.</p><p>2. The information placement was scattered and <strong>not one particular thing was catching their attention.</strong></p><p>3. They found the <strong>UI outdated</strong> as compared to the other ticketing websites they had been using all along and most of them voted in favour of a UI makeover.</p><p>After ascertaining that other users had similar pain points as mine, I started working on possible solutions for the booking flow and an aesthetically pleasing UI.</p><h4><strong>Wire-frames and Iterations</strong></h4><p>When I started approaching the design problem, I sketched out some options of how I could improve the existing design and resolve the above mentioned problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DNIYR3Vvz_M9s7_DJ3YIA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnC9xWgJwXygyu3V-dT1hA.jpeg" /><figcaption>Initial sketches and flows</figcaption></figure><p>Once I finalised the user flow and IA, I proceeded to UI design and iterated a lot more on the visual language of the website. I have iterated every component and screen several times. I have attached a link to my <a href="https://www.figma.com/file/Am1mQsLiYfh127Ph83DkT0/%F0%9F%9A%8D-Red-Bus-Redesign?node-id=323%3A2">Figma file</a> here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWShaB9eNwOZvGI8Dmb5oA.png" /><figcaption>There is no such thing as “too many iterations” :P</figcaption></figure><h3>Search Results Page</h3><p>The purpose of the search results page :</p><ul><li>To let the users <strong>scan through the list of buses and related data points (Bus type, timings, price, etc.)</strong></li><li>To let the users make a decision while giving them options to filter the results according to their preference.</li></ul><p>Being a <strong>content heavy page</strong>, the search results need to be structurally organised with the right amount of emphasis for different pieces of information.</p><h4><strong>Problem 1 : Lack of hierarchy </strong>and the<strong> scattered placement of information</strong></h4><p>This increases <strong>cognitive load</strong> on the user. They might find it <strong>difficult to scan through</strong> different sections of the screen at a glance and find a particular result they were looking for. This makes the decision making process a little longer for the user.</p><h4><strong>Solution</strong></h4><ul><li><strong>Fixed width layout<br></strong>The existing design has a full width layout which doesn’t allow a more structured format of information. This means that the user has to look from the extreme left side of the screen to the extreme right. <br>Instead, I made it a centre aligned fixed-width layout so that it’s<strong> easy for the user to scan through options, irrespective of the screen size.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRIx6PHGuwX9YLDVNBiKHg.png" /><figcaption>Layout of search results page (old and new)</figcaption></figure><h4>Problem 2 : Inability to quickly change search parameters</h4><p>The search bar isn’t given enough prominence. In the current design state, the <strong>search input fields are not in an active state </strong>unless you click on “modify”. This increases the number of clicks and makes the process over complicated.</p><h4>Solution</h4><ul><li>I placed the search input fields in a separate bar that’s fixed to the top of the screen to give it <strong>more hierarchy.</strong></li><li>Also, I added <strong>an input field for “Number of Passengers” in the search bar.</strong> The results will show buses only with the required or more seat availability. In the current state, the search results page shows total number of seats available in the bus, on every card. This data is not relevant to the users and should be filtered out before showing the search results themselves.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8gYLK6KBv_9h_AX3IFdvKQ.png" /><figcaption>Search Bar (old and new)</figcaption></figure><h4>Problem 3 : Lack of affordance in the filters</h4><p>RedBus has introduced new filters for users’ benefit but do users even click on them?</p><p>In the original redBus design, <strong>the cards on top look like pop-up ads/banners, which users refrain from using</strong>, but in actuality they are filters.</p><p>Also, it is not possible to select more than one of these new filters at a time, yet the results show most of the buses with more than one of these features, which <strong>leads to conflict between user action and results.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ztY0TtjEcOBdOryQjXPZA.png" /></figure><h4><strong>Solution :</strong></h4><p><strong>I placed the new filters along with the other existing filters</strong> to avoid any confusion regarding their use and purpose. I also gave them a little more emphasis by separating them from the existing filters, to give them more priority.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HufBVsiW0PGK1P-U66hdTA.png" /><figcaption>Filters (before and after)</figcaption></figure><p>I redesigned the way the filters look. The new visual style makes it easier for the users to comprehend information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5y2ZyJLMhxfyrPPwWWbGDg.png" /><figcaption>Filters (before and after)</figcaption></figure><h4>Problem 4: The sorting options don’t look clickable</h4><p>The sorting options <strong>lack affordance. </strong>They are in the same text format as the other information and don’t look like they are <strong>clickable </strong>which might give a lot of users the<strong> impression that the function of sorting options doesn’t exist on redBus.</strong></p><h4><strong>Solution :</strong></h4><ul><li>I put the sorting options into a separate bar to give them enough <strong>emphasis</strong> and attain <strong>hierarchy</strong>, so that they look clickable. This lets the users know that they can refine the results according to their preference.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VpvZ3FEgJuODZ3i2up7Gdw.png" /><figcaption>Sorting Options (before and after)</figcaption></figure><ul><li>As the sorting options are to be frequently used on a booking platform, I avoided putting them in a drop-down format and used a<strong> tabs format to reduce the number of clicks and make it faster to sort between multiple options.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JzOMGzBw_EsQeKkJ_zxgig.png" /></figure><h4><strong>Problem 5: Visual clutter and lack of reading pattern in Bus Details Cards</strong></h4><p>The information on the Bus Cards is very scattered and doesn’t follow a proper reading pattern. That makes it difficult to efficiently find and focus on important data points like Bus timings, operator’s name, pricing, etc., without feeling lost in information-overload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UeWR6nILac_4HviUwyxIkA.png" /></figure><h4><strong>Solution</strong></h4><p>First of all, I decided to retain<strong> only the most essential information</strong> on the cards. To do this, I removed some irrelevant information like number of seats from the card. Instead of this, <strong>I introduced an input field for the number of passengers in the search bar itself, </strong>to refine the search results in a better way.<strong> </strong>This would filter out the number of search results and would show the buses only with required or more seat availability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ai1NMHr_2p9izUuTI6GbMA.png" /></figure><p>Below, you can see the original and redesigned version of the bus card. I designed the layout in a proper hierarchical manner and highlighted important information to make it easier for the users to scan through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsGi6wZPaefXGteO_dKqxw.png" /><figcaption>Bus details card</figcaption></figure><p>The key factor in designing these bus cards is <strong>Information Architecture, </strong>like designing any other feature.</p><p>Let me breakdown how I redesigned the IA to make sure that the users don’t miss out on important data points.</p><ul><li>I made a list of all the data points that the users need on these cards.</li><li>I grouped the data points in different categories based on their context.</li><li>Ranked the data groups according to priority and ranked the pointers further inside each data group.</li><li>I replaced the tertiary information like icons for amenities (which were not self explanatory) to the drop-down text links under “Amenities and Bus photos” section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_q0AtDYyRfo6Zkwf0fgolQ.png" /><figcaption>Information Architecture of Bus Cards</figcaption></figure><p>While diving deeper into the process and trying out so many iterations, I gained an insight :</p><blockquote>Attaining good Information Architecture and Visual Hierarchy is the most fundamental yet the trickiest part of designing a solution.<br>These two things play an integral role in optimising the process of conveying information to the user in an effective and efficient way.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HqPpTj30S5Ot8zeU9ytwxw.png" /><figcaption>Iterations of bus details cards</figcaption></figure><h4><strong>Different states of the bus cards</strong></h4><p>Here is how the cards will look in different journey scenarios :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VevjTExxson0MvAs96glPQ.png" /><figcaption>Different states of bus details cards</figcaption></figure><h4><strong>Drop down links on the bus detail cards</strong></h4><p>I redesigned the drop down links and arranged the information in a more structured and comprehensible manner.</p><p>Here are the original and redesigned versions of the drop down link of Boarding and Dropping points :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DW6onG9K096YvUHYVuj5Yg.png" /><figcaption>Drop down link of boarding and dropping points</figcaption></figure><p>I followed the similar visual language for all the drop down links. Below, you can see the redesigned version of all the drop down links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4kJB8sR2gjeYz75PzNyWkg.png" /><figcaption>Drop down links of all the bus features</figcaption></figure><h3>Tickets Booking Flow</h3><p>After the users selects a bus, they proceed to the following steps :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hxjlh4XA0pj98FVAu-ztRw.png" /></figure><h4>Problem 1 : Inconsistency in pageview of multiple steps of the booking flow</h4><ul><li>The seat selection has a <strong>drop down format.</strong></li><li>Passenger details are showed in a<strong> side sheet.</strong></li><li>Payment options are on a <strong>new page</strong> altogether.</li></ul><p>This creates inconsistency in user flow and doesn’t contribute to a good experience.</p><h4>Solution</h4><p><strong>De-cluttering the Seat Selection Process : </strong>In order to solve these issues, I decided to unify the all the steps of the booking flow by <strong>redirecting them to a new page</strong> with only the most essential information which is relevant to complete the booking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWyDXw4UeNZa00ccnoWOWw.png" /><figcaption>Seats selection layout</figcaption></figure><h4><strong>Problem 2 : Complex transition between different stages of the booking flow</strong></h4><p>Let me explain this with an example :</p><blockquote>Jane has booked 3 tickets from Chennai to Bangalore, added passenger details and proceeded to payment options to complete the booking. Before making the payment, she realises that she put wrong boarding point by mistake and the contact number has a fault too. Now, she wants to fix these two things and complete her payment quickly. What should she do?</blockquote><p>The current design will make her <strong>click on the back button and redirect her all the way back to the search results page</strong>, where she will have to select a bus, the seats and other details all over again. This results in user frustration.</p><h4><strong>Solution</strong></h4><p>To facilitate smooth transition between different stages of the flow, I have taken the following measures :</p><ul><li><strong>Integrated the booking details at every step.<br></strong>I decided to design a “Trip Details” card fixed to the right side of each screen of the booking flow which has integrated information such as number of seats, boarding/dropping points, passenger details, to ensure that the users have the summary of their selections in front of them, at all times.</li><li><strong>Provided CTA for every section of the Trip Details card,</strong> so that the users can go one step back and change or add to whichever information they want, <strong>without losing the ongoing progress in the booking flow</strong>. <br>For instance, when a user is on payments option page, they can change the Boarding points/Dropping points or add/remove a passenger without having to click on the back button.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_-OjVWqzh5GyPIDHxgQUA.png" /><figcaption>Newly added “Trip Details” card</figcaption></figure><h4>Passenger Details and Payments Options page :</h4><p>There was nothing wrong with the “passenger details” and “payment details” steps, so I retained the original Information Architecture there. But, I changed the visuals to match the new visual language that I have created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xEfeoAeEvpFCjORG_rMH0Q.png" /><figcaption>Passenger details page</figcaption></figure><h4>Designing Trip Details Card</h4><p>I came across a challenge while designing the trip details card. There was a lot of information that had to be fixed on the right side of the screen, which increased the height of the card. At the same time, <strong>I had to make sure that the card is fixed and not being cut, irrespective of the height of the browser.</strong></p><p>To resolve this, I reduced the height of the card to make sure that it is always in the viewport of the screen. And, to avoid any chances of the card content being cut, I provided <strong>internal scrolling</strong>.</p><p>Now, the card will adapt to all the screen sizes and heights because of internal scrolling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bA3nFLxEG_wLQSKMRS2CHQ.png" /></figure><h3>redBus Phone App</h3><p>I have tried to resolve the same pain points in redBus App. There was no major flaw that stood out while using the app, however, there are some things that could be improved. Further, I will talk about few of the such things in detail.</p><p>And, I revamped the interface of the app as well. I followed the same visual language for redBus app that I did for the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zs9_0SbZDWMH2RCPJWLixQ.png" /><figcaption>Home screen of redBus app</figcaption></figure><h3>Search Results Page</h3><h4>1. Sort and Filter</h4><p>I observed that the filters and sorting options could be simplified. <br>As sorting options are used very frequently, I wanted to provide that function on the screen upfront so that the <strong>users don’t have to leave the search results page while switching between preferences</strong>. So, I again provided tabs for sorting.</p><p>The flaw with filter cards on app remains the same as those on website. They look like banners/ads. The bus cards (search results) are supposed to be the primary feature on search results page but the filter cards are getting too much emphasis and are overshadowing the bus cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CbX3cXXs7xi42jVq9OgBUA.png" /><figcaption>Search results and filters</figcaption></figure><p><strong>2. Iterations for Navigation Bar :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RfSJo5UlNprzYgPdsAzcmw.png" /></figure><h4>3. Bus Details Cards</h4><p>For bus detail cards, I tried to follow the same structure that I have designed for those on the website but it didn’t work out considering the screen size and scanning pattern.</p><p>The price was not getting enough emphasis, so I tried different iterations with reduced font sizes, different colours and dividers. At last, I came up with a new layout that follows the similar reading pattern but makes the price stand out in a better way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blIWTu6iAtTzmxxebzS2TQ.png" /></figure><h3>Booking Flow</h3><p>In the below image, you can see the redesigned screens of the booking flow. I followed the same flow on app as I did on the website while tweaking some things considering the space limits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2y7p-ZwwvEzlL5NQIjmYjQ.png" /></figure><p>The navigation bar clearly indicates the next step as the users proceed with the booking flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TCxwWFqXoEOo9oZuxkFneQ.png" /></figure><h4>The Seats Selection Page</h4><p>I wanted to show price breakdown based on the seats selected. And, considering the different screen sizes of phones, I didn’t show all the information on the same page because I didn’t want to compromise on the size and placement of seats layout. So, I provided <strong>modal sheets for showing the seat indicators and price breakdown.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rmpG21FOvMqAk_lfpYF9Pg.png" /></figure><h4>Payment Screen</h4><p>I have redesigned the way payment breakdown and trip details look. This structure makes it easier for the users to quickly review all the details before checkout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_LJdkUK5BQH2D0YPijMBg.png" /></figure><p>And last but not the least..</p><h3>Introducing Dark Mode for redBus</h3><p>Users falling into younger age bracket are inclining more towards Dark UI’s because of its elegant and contemporary visual style that embraces luxury.</p><p>Some benefits of introducing dark mode for redBus are :</p><ul><li>It’s easier on the eyes of users when they are using the app in dimly lit rooms.</li><li>It might actually be an add-on for redBus in increasing the user engagement.</li></ul><p>Another common advantage of Dark Mode is the reduced energy consumption on devices with OLED and AMOLED displays.</p><p>So, here you go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mX_sVz8Fqbsf1zNG8mebSg.png" /></figure><p>That’s it, folks! Hope you enjoyed this detailed case study.</p><h3>Reflection and Key Takeaways</h3><p>This project was a golden opportunity for me to dive deeper into Information Architecture and work on my Visual Design skills simultaneously.</p><h4>Learning :</h4><ul><li>In-depth analysis of the design decisions is really important to make sure that you’re fulfilling user requirements through empathy.</li><li>Each data point holds a different rank in hierarchy and needs to be identified and conveyed accordingly.</li><li>I understood the common UI and UX paradigms that exist.</li><li>I learnt how to design for both, an app and a website, for the same product.</li><li>Small changes in design can make a huge impact on the whole user experience.</li><li>I understood how to design interfaces applying the dark mode human interface guidelines by Apple.</li></ul><h4>Challenges :</h4><ul><li>I worked on a lot of iterations to arrive at the right solution. During this process, I realised that <strong>iteration is the key to any optimum design solution. There’s no other way around.</strong></li><li>While working on design solutions for a problem, I came across some micro challenges, which made the whole project even more interesting. I learned how to resolve those challenges without compromising on the primary design solution.</li><li>Does “working on a windows laptop with frequent power cuts” count? :P<br><br>Hit me up on <a href="http://www.linkedin.com/in/vanshika-nagpal-068185167">LinkedIn</a> and <a href="https://twitter.com/Vanshika1125?t=E4qrzqjQXnmlN8tv9fgo5g&amp;s=09">Twitter</a> if you want to discuss further. :)</li></ul><figure><a href="https://muz.li/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*499xtQAyb2ongWJCJHrhrw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fce2c5f1d2db" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/ui-ux-case-study-enabling-users-to-book-tickets-seamlessly-with-least-friction-fce2c5f1d2db">UI/UX Case Study — Enabling users to book tickets seamlessly with least friction</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>