<?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 Vaibhav Khandelwal on Medium]]></title>
        <description><![CDATA[Stories by Vaibhav Khandelwal on Medium]]></description>
        <link>https://medium.com/@vaibhaviitr?source=rss-7b775d0ab0bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*K3hfxKIqQYQ-oTMEfTCtVw.jpeg</url>
            <title>Stories by Vaibhav Khandelwal on Medium</title>
            <link>https://medium.com/@vaibhaviitr?source=rss-7b775d0ab0bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:37:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vaibhaviitr/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[Ridesharing app for commuters | Design Case Study | Task Flipkart]]></title>
            <link>https://vaibhaviitr.medium.com/ridesharing-app-for-commuters-design-case-study-task-flipkart-f08e37e5207a?source=rss-7b775d0ab0bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f08e37e5207a</guid>
            <dc:creator><![CDATA[Vaibhav Khandelwal]]></dc:creator>
            <pubDate>Sun, 28 Nov 2021 18:16:38 GMT</pubDate>
            <atom:updated>2021-11-28T18:29:37.618Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sq0kLYT57BEzed2U3uYlKQ.png" /><figcaption>Cover Banner showcasing 3 of the important screens from both ends.</figcaption></figure><h3><strong>Problem Statement</strong></h3><p>Design an app for carpooling/bike pooling to help commuters (Ride-seeker &amp; Driver) to discover, connect, route match, coordinate, and cost-share in a seamless manner.</p><p>If a user (ride seeker) needs to get somewhere e.g. commuting to work, why not get a ride from someone who is traveling in the same direction, share costs, get a comfortable ride, and be faster compared to buses or metro. On the other side — the app should enable the user (driver) to get co-riders who are traveling on a common route to share his/her personal vehicle with.</p><h3><strong>Problem Analysis</strong></h3><p>To design an app for carpooling or bike pooling for two types of users:</p><ul><li><strong><em>Drivers (or Ride-offerers):</em></strong> The one who owns the car or bike of their own and is willing to share his ride with co-riders.</li><li><strong><em>Riders (or Ride-seekers):</em></strong> The ones who don’t travel with their own vehicle and need a ride from drivers.</li></ul><p>The users are referred to as commuters that are daily riders or passengers.</p><p>The users should be able to do the following through the app:</p><ul><li>Discover their rides</li><li>Connect between drivers and ride seekers</li><li>Route match</li><li>Coordinate between themself</li><li>Cost-sharing accordingly</li></ul><p>The app should allow both kinds of users to do any of the following: Ridesharing or Ride seeking from 1 app.</p><h3><strong>Primary Research</strong></h3><blockquote>The purpose of this research was to understand + validate user needs and pain points. This would help make necessary assumptions and prioritize user needs.</blockquote><h4><strong>What do I need to extract from the research?</strong></h4><ul><li>Pain points from both the driver’s end and rider’s end.</li><li>How ride-sharing scenarios in this case should differ from the current uber pool or ola share scenarios?</li><li>What factors would one consider while connecting with a particular driver, which might affect their riding experience?</li><li>Frustrations faced by users while travelling via cab (uber and ola) and public transports (Busses and autos).</li></ul><blockquote>I talked to Four users regarding this and followed the below rough questionnaire.</blockquote><h4>Rough Questionnaire</h4><ol><li>What places do you travel to frequently?</li><li>How do you prefer to travel to those places? (Way of commuting eg. own car, public transport, cabs, friends pickup, etc.)</li><li>What are the pain points that you face while using public transport?</li><li>How do you choose whether to go via cab or bus or which app to use for cab booking?</li><li>Do you always use the same route to go to those places?</li><li>Have you ever used any ride-sharing services like uber pool, ola share, or sRide?</li><li>How is your overall experience with pooling? Things that you liked and things that you didn’t?</li><li>What factors do you think of while booking a pooling service? (like cost, driver, co-passengers, car or bike type, etc.)</li></ol><h3>User Insights and Pain Points</h3><blockquote>These are the collective insights that I obtained by interviewing 4 users.</blockquote><h4>Insights</h4><ul><li>People generally visit — Workplace, Gym, Restaurants and cafes, Weekend Travelling, Health checkups</li><li>Most people travel via cab or public transport to workplaces but they use their own vehicle for other purposes.</li><li>Unreliable bus timings, long queues and waiting times at peak hours, and tiresome multi-model travel with no guarantee of getting a seat.</li><li>Choosing whether to use public transport or go via cab depends on the availability of cabs or public transport, time constraints, cost of cabs, etc.</li><li>The route to work or somewhere known is generally fixed and kept in mind on the basis of which is shortest, less time taking and comfortable.</li><li>Most people have used ride-sharing services like Uber Pool or Ola share so they have a decent idea of how they work.</li><li>Likes of ride-sharing (or pooling)<br> — Cost breakdown is cheap and is affordable as compared to cabs.<br> — Other co-passengers are picked up from nearby areas, so there is less chances or need of re-routing.<br> — Its a good meet and greet type of networking service if you find professional co-passengers working at some good posts.</li><li>Dislikes of ride-sharing (or pooling)<br> — There are always trust issues that arise while booking a pool service as no information about your co-passengers is shared. It&#39;s ever harder for women riders.<br> — Sometimes, when already there are passengers travelling and your drop is last then journey time increases as the drops are sometimes so off-routes.</li></ul><h4><strong>User Pain Points</strong></h4><blockquote>Based on the insights I clubbed from user interviews, I devised certain pain points from both drivers and riders perspectives.</blockquote><p><strong>Drivers Perspective</strong></p><ul><li><strong>Rising fuel costs<br></strong>Cuts into their monthly budgets</li><li><strong>Trust<br></strong>Hard to find verified, reliable people for carpooling/ride-sharing</li><li><strong>Route<br></strong>Hard to find cost-effective transport options on their route</li><li>Traffic congestion and parking woes in urban areas</li><li><strong>Carbon footprint<br></strong>Greater climate-change awareness leads to increasing guilt about driving solo</li></ul><p><strong>Riders Perspective</strong></p><ul><li><strong>Cost<br></strong>Private cabs are comfortable but are costly.</li><li><strong>Safety woes<br></strong>Public transport can be unsafe at odd hours, and it’s worse for women.</li><li>Couldn&#39;t <strong>trust</strong> on co-passengers in the pool and share services.</li><li><strong>High travel time<br></strong>Flaws in ride algorithms lead to pick-ups and drops that aren’t on the route.</li><li><strong>Public transport issues<br></strong>Unreliable bus timings, long queues and waiting times at peak hours, and tiresome multi-modal travel with no guarantee of getting a seat.</li></ul><h3>User Research</h3><h4>Potential Target Groups</h4><p><strong>For drivers</strong></p><ul><li>Age group — 18 to 40 years</li><li>Tier 1,2 cities</li><li>Car/Bike Owners</li></ul><p><strong>For riders</strong></p><ul><li>Age group — 16 to 50 years</li><li>Tier 1,2 cities</li><li>Either car/bike owners or no vehicle</li></ul><h4>Use Cases (User Scenarios)</h4><p>By considering both drivers and riders as customers (users), there are many use cases for which they might use the ride-sharing app. So, I put almost all the cases into 3 buckets:</p><ol><li><strong>Commuter use case (Regular users)</strong><br> — High frequency on working days<br> — Includes people going to workplaces like offices, stations, malls, etc.<br> — Generally, trustworthy riders and drivers are found.<br> — Service will be used most in the morning and evening time.</li><li><strong>Recreational use case (Not regular)</strong><br> — Medium frequency<br> — Includes people going to Restaurants, Malls, Parks, movies, etc.<br> — These cases will occur a maximum of 5–10 times a month.</li><li><strong>Intercity Travel use case<br> — </strong>Very low frequency<br> — Includes people going on vacations, meeting relatives, attending conferences, etc.<br> — 3 to 4 times a year.</li></ol><blockquote><strong>As the commuters fall under the Work Use case bucket, I am majorly focussing on solving for them. This might eventually work for other use cases too.</strong></blockquote><h3>User Personas</h3><blockquote>Keeping the use cases and users involved with the solutions in mind, I created 3 user personas for covering multiple pain points and solving for wider audience.</blockquote><h4><strong>Driver</strong></h4><p><strong>Aman Sethi</strong> (Age 30 years)</p><ul><li>Married for 2 years now</li><li>Product manager</li><li>Lives in Aashraya Enclave, Kormangala, Bangalore (22 km from his workplace)</li><li>Honda Amaze owner (Goes to office solo, daily, using his car)</li><li>Spends roughly 10% of his income on fuel costs.</li><li>Pain Points<br> — So expensive to drive cars these days and that too for a single person.<br> — Driving solo for 22 km is again so boring to follow regularly, Can&#39;t use your phone too.<br> — How can I give a lift to someone like that? How can I trust that person?</li></ul><h4><strong>Rider 1</strong></h4><p><strong>Rashi Singh</strong> (Age 25 years)</p><ul><li>Unmarried</li><li>Works at Restaurant in Bangalore</li><li>Lives in a rented complex at Akash Vihar, Bangalore</li><li>Usually takes public transport like city busses or auto-rikshaws.</li><li>Waits at the bus stand for almost half an hour sometimes. Also, the bus stand is quite far from the apartment.</li><li>Faced unusual and strange incidents with strangers sometimes.</li><li>Cabs are unaffordable on a regular basis.</li><li>Pain Points<br> — If you choose comfortable rides (cabs) then it&#39;s costly, if you choose budget-friendly rides (public busses)then they are not comfortable. Isn&#39;t there any option which is comfortable and less costly?<br> — But even if it exists (solution), what about your security. Being a girl its so hard to travel with strangers these days.</li></ul><h4><strong>Rider 2</strong></h4><p><strong>E.M. Rao</strong> (38 years)</p><ul><li>Senior Engineer at an MNC, Bangalore</li><li>Lives in Whitefield Bangalore (18 km from Bosch)</li><li>Owns Creta (SUV) but generally prefers public transport</li><li>Takes 1.5 hours to travel on a usual 45 min route</li><li>Health issues as the body is growing old.</li><li>Pain Points<br> — A lot of time is wasted by traveling by public transport.<br> — Uncomfortability<br> — Cost at some point<br> — Environment issues with lots of vehicles.</li></ul><blockquote>These user personas are used in designing the app screens and features.</blockquote><h3>Ideation</h3><blockquote>After clearing out some blockers and understanding the important pain points, the assumptions and key features of the app are now striking in my mind. Followed many processes like creating user journeys and user stories for different personas which I dint feel mentioning because those points will covered here.</blockquote><h4>Assumptions</h4><blockquote>Many of the assumptions are mentioned wherever necessary in the documentation. These are 2 important ones I thought to mention.</blockquote><ul><li>To avoid the extra step of bidding cost and agreeing on a number. I assumed that the cost breakup of a ride is estimated by the app itself using an algorithm similar to Uber Pool one.</li><li>Assuming the KYC of users is done in the onboarding step which will build at least a little amount of trust.</li></ul><h4>Prioritized pain points to solve for</h4><ul><li>To share <strong>cost</strong> breaking among the users in such a way that it&#39;s cheaper for riders to take services and it&#39;s more effective for drivers to give rides to them.</li><li>To reduce the fear of <strong>trusting unknowns</strong>.</li><li>To reduce the <strong>traveling time</strong> overall (from finding transport to the rerouting of cab drivers).</li><li>To reduce the <strong>efforts of interaction</strong>, whether it&#39;s with an app&#39;s interface or with cab drivers not getting correct locations.</li><li>To reduce the <strong>environmental issues</strong> (it will be a very small change but it can be the start of something big).</li></ul><h4>Key Features</h4><ul><li>The user can choose between whether to offer ride or request ride on the home screen. Also on the next screen while inputting start and destination location.</li><li>The app is map view based, i.e most of the interactions are while viewing route or navigating.</li><li>A side menu is given to quickly go to various screens like messages, Previous rides, Payments, settings etc.</li><li>The rider can choose how many seats he/she requires and the results are displayed accordingly.</li><li>Similarly, a driver can choose the seating capacity and waiting time he/she can devote for riders.</li><li>Listing the ride information for riders allows them to see who the driver is, rating, vehicle details, waiting time, drop time, seat capacity etc. The rider can also click the driver photo to view his/her full profile.</li><li>The rider is also provided with the details of their co-riders to gain a pinch of trust and assure safety.</li><li>For safety, emergency buttons and ride-sharing options will be given.</li><li>Similarly, the driver can accept or reject any request according to his/her will.</li><li>The driver will be given the option to call or message (via app) if the rider takes time.</li></ul><h3>Information Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mUTyCm_O8UVLVYDqrou4AQ.png" /><figcaption>Information architecture covering both rider and driver flow.</figcaption></figure><h3>User Workflow (interaction with app)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z6HhYMyVDnCW6pjkeyhDgQ.png" /><figcaption>User Workflow of Rider end (Green) and Driver end (Blue)</figcaption></figure><h3>Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jb2ZskJcdKlKGVg9XF6FBA.jpeg" /><figcaption>Wireframes — Rider Screens</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5zXqehIv3QXGHmYVhwP9CQ.jpeg" /><figcaption>Wireframes — Driver Screen</figcaption></figure><h3>Designed Screens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZ0x6APG0ilUSXHyAunCSA.png" /><figcaption>Designs — Rider Screens</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-kYuKuKVfAB9Er0DehkNQ.png" /><figcaption>Designs — Driver Screens</figcaption></figure><h3>Future Scope</h3><h4>Ride Scheduling</h4><p>It is not always possible that the driver finds a rider once he/she has started his/her journey. so, in order to fetch more riders, the driver can schedule the ride for later.</p><h4>Women-centric user experience</h4><p>With increasing concerns of women security in the current commuting ways. We have decided to incorporate a feature for women which connects them only with women drivers in the subsequent versions.</p><h4>Subscribe to another user</h4><p>Why book the same driver for the same time and same destination daily, when you can subscribe to him/her for the upcoming week/month and save more?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f08e37e5207a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart Car Parking App | UX Case Study | Meesho Assignment]]></title>
            <link>https://vaibhaviitr.medium.com/overview-c194935f78af?source=rss-7b775d0ab0bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c194935f78af</guid>
            <dc:creator><![CDATA[Vaibhav Khandelwal]]></dc:creator>
            <pubDate>Sat, 30 Oct 2021 03:32:39 GMT</pubDate>
            <atom:updated>2021-11-14T18:11:23.981Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_hs9AH50-Aywx3PcAuTqQ.png" /></figure><h3>Overview</h3><p>This documentation is the walkthrough of all my design processes, design decisions, user flows, wireframes, and prototype for a 42-hour design task given by Meesho as a part of the product Designer — I hiring process.</p><h3><strong>Problem Statement</strong></h3><p>We are launching fully automated car parking centers in certain cities for tourists and locals. The centers are multistorey, and each floor has multiple parking spaces. People are required to book parking space as per their requirements and pay the charge on an hourly basis.</p><p>We would require an app to help people explore, decide, and book parking space and use them for the booked time. Since it’s a fully automated system, consider that the whole experience is technology-driven without any human intervention.</p><p>Design wireframes &amp; flows covering the following phases in a user journey:</p><ul><li>Discovery</li><li>Decision</li><li>Booking</li></ul><h3>Understanding the problem</h3><p>We need to build a mobile app to help people explore, decide, and book parking space and use them for the booked time.</p><h4><strong>Scenario</strong></h4><ul><li>We are launching car parking centers in certain cities, for tourists and locals</li><li>Centers are multistorey, and each floor has multiple parking spaces.</li><li>Fully automated systems, i.e no human intervention</li><li>People should be able to book parking space as per requirements</li><li>Charge for parking would be paid on an hourly basis</li></ul><h3>Users and customers</h3><p>In order to better understand and narrow down on a TG for this problem, we can classify users on the basis of:</p><ul><li><strong>Primary basis</strong></li></ul><ol><li>Car owners who drive their own car (or rented — lesser use case)</li><li>Car drivers who work as drivers for respective car owners</li><li>Cab drivers who may or may not be owners of the cars as well</li></ol><ul><li><strong>Frequency</strong></li></ul><ol><li>Lowest Frequency — Tourists, Travellers</li><li>Medium Frequency — Irregular locals</li><li>High Frequency — regular locals, job professionals, workers</li></ol><h4><strong>Potential TG</strong></h4><ul><li>Tier 1 cities</li><li>Age group: 18–45 years</li><li>Both professional (work) and recreational (malls, theatres etc) use case</li><li>Majorly local users &lt;add why not travelers)</li></ul><h3>Primary research approach</h3><p><em>The purpose of this research was to understand + validate user needs and pain points. This would help make necessary assumptions and prioritize user needs.</em></p><p>I spoke to 4 active car users in tier 1 cities for this.</p><h4><strong>What was I looking for?</strong></h4><ul><li>Frequency of external car parking usage</li><li>Understanding factors which a user considers when looking for a parking spot</li><li>Their experience at organized parking centres in current world</li></ul><h4><strong>Rough questionnaire which I followed</strong></h4><ul><li>How frequently do you use your car? For what purposes?</li><li>Do you think about parking before leaving itself? How many times do you use an external parking space? <em>(eg: empty space on a nearby road, paid parking grounds etc)</em></li><li>Can you describe an organized parking experience you recently went though? <em>(eg: at the airport or at a mall)</em></li><li>What factors do you consider when trying to decide on a spot to park your car?</li></ul><h3>Insights from research</h3><h4><strong>Basic parking experience</strong></h4><ol><li>The person drives to the destination place.</li><li>If the place has its own parking, then goes there. If not, then search for a nearby parking area to park their car.</li><li>Before entering the area, needs to collect a parking ticket issued by the watchman or someone for their car.</li><li>Then finds a decent parking spot inside the parking area to park their car safely.</li><li>Then after when they need to take out their car, they need to search for the spot where they parked their car.</li><li>If the nearby cars arent parked in an ordered manner than faces issue taking it out.</li><li>At last, goes by the exit door, hand back ticket and exit.</li></ol><h4><strong>Insights and pain points</strong></h4><ul><li>Not all places have dedicated parking spaces <em>(eg: when visiting local eateries)</em>.</li><li>In such scenarios <em>(above point)</em>, it can be time taking to identify a secure parking spot</li><li>In organized parking spaces <em>(eg: malls, theatres)</em> it can be difficult to figure out an empty parking spot on busy days <em>(weekends, holidays etc)</em></li><li>In organized parking spaces, once the user has parked the car, it can be difficult to navigate back to and remember the parking area while exiting.</li><li>On busy days, there is a lot of chaos sometimes when multiple drivers end up in same lane looking for an empty parking spot</li><li>There’s an anxiety of losing the parking ticket <em>(to be presented at exit)</em> issued at the time of parking.</li><li>Factors affecting decision making for choosing a parking spot</li><li>Should be secure</li><li>Not too far away from destination</li></ul><h3>User Persona</h3><ul><li>Bharat Nittala (age — 24 years)</li><li>Lives in Bangalore</li><li>Works at Slice as Product Manager</li><li>Owns his own car and drives himself</li><li>Travels to the office daily by car. Since the office doesn’t have a dedicated parking space, he parks it on a nearby road.</li><li>Often goes to malls, theatres, restaurants etc for recreation during the weekends</li></ul><h3>Ideation</h3><p>Before ideating on potential solutions, I wanted to list down a few assumptions and narrow down on the pain points to prioritize.</p><h4><strong>Assumptions</strong></h4><blockquote><em>Some of the assumptions are taken considering the time constraint for assignment, while others are to narrow down on the problem</em></blockquote><ul><li>There are sufficient centers to show in a particular area</li><li>All centers are uniform in security and naming of slots</li><li>Navigation within parking center would be solved for by design of centers, i.e there won’t be a direction map for reaching a slot within a particular center in app</li><li>Not solving for instant booking, based on my understanding of the problem statement</li></ul><h4><strong>Key pain points and challenges to solve for</strong></h4><ul><li>Discovery of secure parking centers nearby destination</li><li>Seamless entry and exit experience at the center</li><li>Transparency in parking centres and spaces.</li></ul><h3>User Flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pe2mXL5Vg8M1digLIDQPTw.png" /><figcaption>App User Flow (both first time users and existing ones)</figcaption></figure><p>This is the brief user journey on the app prioritizing the needs and simplifying the app experience for all.</p><p>The user flow is divided into 5 phases:</p><ul><li>Discovery of parking centres</li><li>Decision of parking centre</li><li>Booking of parking slot in the centre</li><li>Parking the car (includes QR scanning, parking, and returning back)</li><li>Payment and Exit</li></ul><blockquote>Top 3 phases are necessarily to be solved via the app.</blockquote><h3>Information Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LlABtuV9nVpaTqoZh463fw.jpeg" /><figcaption>Information architecture of the 3 phases</figcaption></figure><h3>Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dbh82LK6gL1gF0DyeI25iA.png" /><figcaption>Wireframes (sketches) based on the app flow and IA</figcaption></figure><h3>App Screens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SupD3NaYweBeSZvvLBRong.png" /><figcaption>Discovery phase based app screens</figcaption></figure><p>The app name is ParkIt (as the 1st screen is depicting).</p><p>The second screen is the home screen. The user lands here after onboarding or when they opens up the app after. When we think of discovery of a place or where to find some place, we use google maps. Taking this fact as a user friendly point, designed the screen with a map and a search bar, provided with some nearby parking suggestion cards at the bottom.</p><blockquote>Note : The early iteration of home screen was bulky as I put some irrelevant information in the cards. The “Book Slot” CTA was big enough and was very attention seeker. Took better decisions and came up with cool iteration.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVN37KtY-APtDnd6NaE8BA.png" /><figcaption>Decision making and Booking phase based app screens</figcaption></figure><p>The 2nd screen is the main screen of the app as it allows user to book a parking space for a particular duration.</p><p>In the 1st iteration, instead of asking for just arriving time from the user, I was specifically asking for entry and exit time. Then realised that this would create an anxiety state in user if couldn&#39;t follow their duration time.</p><blockquote>A design thought : After the successfull booking, when the user scans the QR to enter but due to low brightness of the phone (many people these days do this) couldnt scan then an error prompt asking to increase brightness could be shown.</blockquote><h3>Future Scopes</h3><blockquote>Due to the time constraints for the assignment, there were a couple of things which I wanted to cover but could not.</blockquote><h4><strong>- Subscription based service</strong></h4><p>For more frequent and regular use cases for parking like going to the office, we could have a subscription based model where the user pays an amount upfront and can reserve a spot for relevant dates and time.</p><p><em>Eg: 10:00 AM to 06:00 PM on all weekdays</em></p><p>Implementation could be this way, there would be some subscription plans for a certain parking centre. If the user is regular there, then they may take the subscription which will be helpful as they should not book a slot everyday but an automated slot is given to them before handed.</p><blockquote>Thank You</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c194935f78af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revamping Protonn | Internship Experience — UX Work-Study]]></title>
            <link>https://vaibhaviitr.medium.com/revamping-protonn-internship-experience-ux-work-study-8b925514291d?source=rss-7b775d0ab0bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b925514291d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[internship-experience]]></category>
            <dc:creator><![CDATA[Vaibhav Khandelwal]]></dc:creator>
            <pubDate>Sun, 24 Oct 2021 09:57:11 GMT</pubDate>
            <atom:updated>2021-10-24T09:57:11.183Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Revamping Protonn | Internship Experience — UX Work-Study</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5pqDS8gID5NG8PV0WDxHPQ.png" /></figure><h3><strong>Context</strong></h3><p>This article is a UX work-study (also case study xD) of the work I did during my internship at Protonn in 2021. It was a 2 months work from home internship in product design. I worked majorly on revamping the product based on feedback from early users and various other hypotheses (would be discussing briefly).</p><h3><strong>About Protonn</strong></h3><p>Protonn is a business in a box solution for individual professionals (currently for the US), a SaaS startup based out of Bangalore and San Jose. Founded by 2 ex-Flipkart heads (Anil Goteti and Mausam Bhatt), protonn, allows independent professionals like lawyers, graphic designers, and nutritionists to launch their businesses online, create videos, conduct live sessions, generate payment links, and track their business’ financial performance.</p><p>Proton raised $ 9M Series A funding in July when I was about to conclude my internship. Also, they launched their first version of the app on iOS during that period.</p><p>To understand Protonn as a product, we need to define some terms and workflow of the app. The app is quite simple, starting with the registration of professionals, followed by setting up their profile and sharing their videos with clients, to making clients and giving services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*movJ2X3z3g4C6lXKwo6ZJw.png" /><figcaption>Understanding users, platforms and some other terms used within the app and are core features.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rc3SCyBl4oM0AOgIrC-vYg.png" /><figcaption>Overall Protonn workflow including both professionals and clients POV</figcaption></figure><h3><strong>Projects, I was involved in</strong></h3><p>The product work was divided into 3–4 segments, professional iOS app, professional side web app, client-side web app, and the proton marketing website. My major work was for client-side web app and professional iOS app.</p><ul><li>Passwordless Login</li><li>Revamping onboarding screens and profile setup experience</li><li>Side menu and settings section</li></ul><h3><strong>1 — Introducing passwordless sign-up experience (Client Webapp)</strong></h3><p>To interact or take services by a professional, the clients need to sign-up to protonn web app. The professional can share a certain marketing or introduction video privately with an individual client.</p><h4><strong>Problems</strong></h4><ul><li>The major problem was, when professional shares a video with a particular client, it&#39;s meant to be private to that particular client. To prevent further sharing of the video and maintain the privacy of the video, what can be done?</li><li>Not everybody uses a g-suite email id. So, if someone wants to sign up with other email ids then there is a long process of setting up a password which the user sometimes forgets and it’s an extra effort user puts to use services. What can be done to ease the login process and improve the UX?</li></ul><h4>Solution</h4><p>Taking insights and inspirations from some platforms like slack, introduced a magic link verification flow that allows clients to log in by clicking the video link from professionals and then verifying their email via a magic link. Similarly, this would solve the problem of passwordless login if a client is directly logging into their account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KuSK4rMTTWBA0C3oK84nMg.png" /><figcaption>Video sharing and sign in with email flow for clients</figcaption></figure><p>Created a prototype of the flow consisting of all the designed screens.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FD06PLdLWgyE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DD06PLdLWgyE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FD06PLdLWgyE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a2ef056f8c20b7a6db9c44ec2044add2/href">https://medium.com/media/a2ef056f8c20b7a6db9c44ec2044add2/href</a></iframe><h3><strong>2 — Revamping onboarding experience for professionals (Professional app)</strong></h3><p>After signing up, the professional needs to go through a 5-step onboarding process.</p><ol><li>Adding personal details (working sector etc.) and bio.</li><li>Making an introduction video (the first video which a client sees and works as a first impression).</li><li>Setting up services.</li><li>Setting up availability or working hours.</li><li>Setting up a payment method.</li></ol><h4><strong>Problem</strong></h4><p>Following some user interviews and testings, users find the onboarding process harder to understand due to which it is taking more time than expected. To be specific, the services section is barely explained and then the user isn&#39;t allowed to skip. Structuring the onboarding process and making it more aesthetical is what was needed.</p><h4><strong>Solution</strong></h4><p>Taking insights from some user interviews, made a few decisions after understanding the user journey of onboarding:</p><ul><li>Highlighting and simplifying copy for different services and introducing tooltips and skip features.</li><li>Allowing users to set availability for specific working business days with a time picker and introducing a time zone picking feature.</li><li>Introducing a ‘complete your profile’ prompt on the profile page to remind if the user had left any 1 of the 5 steps.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gy2Ea8e5A3TCGE4giH-IQ.png" /><figcaption>Onboarding flow from step-3</figcaption></figure><h3><strong>3 — Experimenting with the side menu and settings section (Professional app)</strong></h3><p>The side menu consists of all the profile and app functionality with customization options and settings.</p><h4><strong>Problem</strong></h4><p>As it was the launch of the app, the side menu wasn&#39;t structured. As a lot of stuff/features are being introduced in the app, the settings screen is becoming complicated and less predictable. Many of the customizations weren&#39;t included and were indirectly laid somewhere else around the app. What can be done to improve UX?</p><h4><strong>Solution</strong></h4><p>Re-ordered the components in the side menu and sectionized the settings according to priority hierarchy. Included the customization features with improved structuring of app and side menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HVyyqMt0fQtScDn6b5UPEg.png" /><figcaption>Newly designed side menu and settings page</figcaption></figure><h3>Bonus Designs</h3><p>Apart from improving the product by applying my UX knowledge, also laid my hands on designing email templates and client invoice with and without payment options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URNctPBBSQvme4hcG8CWLw.png" /><figcaption>E-mail template for magic link</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WS8pUPkmh5ldup6ffjhBpg.png" /><figcaption>Tax Invoice — Due(L) and Tax Invoice — Paid(R)</figcaption></figure><h3><strong>Key Learnings</strong></h3><ul><li>Many design practices like taking insights from a user interview, following design principles, using advanced tools, iterating, presenting, etc.</li><li>Coordinating work between, product manager &amp; design manager and taking feedbacks and converting them into appreciations.</li><li>How early-stage product-based startups make the best experiences for their users and how they acquire their early customers.</li><li>Internal product testing, product holding, feature update launch, and many professional product terminologies.</li><li>Most of all, team bonding and corporate world experience.</li></ul><blockquote><strong>Thank you</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b925514291d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dating App for Pets | Experience Design]]></title>
            <link>https://vaibhaviitr.medium.com/dating-app-for-pets-experience-design-ff909e29181?source=rss-7b775d0ab0bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff909e29181</guid>
            <dc:creator><![CDATA[Vaibhav Khandelwal]]></dc:creator>
            <pubDate>Sun, 21 Mar 2021 18:20:56 GMT</pubDate>
            <atom:updated>2021-03-21T18:20:56.357Z</atom:updated>
            <content:encoded><![CDATA[<h4>An assignment by Protonn</h4><h3>Overview</h3><p>This is documentation of an exercise given by Protonn for product design intern recruitments.</p><h3>Exercise</h3><p>Design an experience for a dating app/website for pets.</p><h3>Basic Research</h3><h4>Why doing this research?</h4><ul><li>To learn about the facts and stats of pet owners to improve their experience in the app.</li><li>To understand the target audience.</li><li>To find out pain points and needs.</li></ul><h4>Two types of Users in this case</h4><ul><li>Active Users — <strong>Pet Owners </strong>(basically my target audience)</li><li>Pseudo Users — <strong>Pets</strong> (Technically dating is for them through the owners.)</li></ul><h4>Understanding the Target Audience</h4><p>There are approximately 24 million pets owned in India till the year 2020. But not all community or class people own a pet. Me, being a member of a middle-class family is not allowed to keep pets at home. <br><strong>Most of the pet owners are of Upper class and upper-middle-class families.<br></strong>They basically are of the age group of<strong> 18–35 years.</strong></p><h4>Assumptions on the basis of research</h4><ul><li>Statista says that <strong>92%</strong> of pets owned in India are dogs. I assumed that the app features two pets — <strong>Dogs</strong> (majorly) and <strong>Cats</strong> (minorly).</li><li>Assuming a single pet dating profile could be made by a user/person.</li></ul><h3>App Flow</h3><p>The app flow is similar to a normal dating app except there is an addition of a step as there is a pseudo user who needs to be given identity on the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lPg3DBcFC6LI_hy6g_18IQ.png" /><figcaption>Basic app flow (an extra step from a normal dating app)</figcaption></figure><h3>Screens</h3><h4>Discover Screen page-</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lC6Y4ipxcp_rlpoDtstv5Q.png" /></figure><h4>Feed-</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OC3RnPh1kUgBBlnVlADgBA.png" /></figure><h4>Message Screens-</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0JMHxLcDYzvpclzU6O0pA.png" /></figure><h4>Account/Info Screen-</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFHT-qorvUucY147VDeU1A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff909e29181" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>