<?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 Anupama Dhareshwar on Medium]]></title>
        <description><![CDATA[Stories by Anupama Dhareshwar on Medium]]></description>
        <link>https://medium.com/@anupamadhareshwar?source=rss-576071518ad2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7lIwMJqJk4zWew1A4YL2VA@2x.jpeg</url>
            <title>Stories by Anupama Dhareshwar on Medium</title>
            <link>https://medium.com/@anupamadhareshwar?source=rss-576071518ad2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:22:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anupamadhareshwar/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[Daily UI challenge]]></title>
            <link>https://medium.com/@anupamadhareshwar/daily-ui-challenge-8c0f17a08ced?source=rss-576071518ad2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c0f17a08ced</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[dailyui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[100daysofui]]></category>
            <dc:creator><![CDATA[Anupama Dhareshwar]]></dc:creator>
            <pubDate>Sat, 24 Jun 2017 09:23:43 GMT</pubDate>
            <atom:updated>2017-10-09T16:45:24.156Z</atom:updated>
            <content:encoded><![CDATA[<p>Having a go at the 100 days of UI challenge. I’ll be updating this page regularly.</p><p>Daily UI 001: Sign Up page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BJrGnBH58FETqqXgS7Fglg.png" /></figure><p>Daily UI 002: Credit card checkout</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eMagr2_cHnUYUxSNDmiDUQ.png" /></figure><p>Daily UI 003: Landing Page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hAzeT6akCLopgxpchVUbw.png" /></figure><p>Daily UI 004: Calculator</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0sQAnEjVjq8vJGT2Uh0rbQ.png" /></figure><p>Daily UI 005: App Icon</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnXtdgAH-Fpi9HUrWMAePw.png" /></figure><p>Daily UI 006: User Profile</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmEiMCHFQbLoNYH-8nk3PQ.png" /></figure><p>Daily UI 007: Settings - I did take longer for this one but happy with the UX elements</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnt00PYjoD14diKkhODePA.png" /></figure><p>Daily UI 008: 404 Page- Had a little fun with this one</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6yNtiki30A84t2XIkIpM4A.png" /></figure><p>Daily UI 009: Music player</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HFFI_NP3oVGLK34J046hlA.png" /></figure><p>Daily UI 010: Social Share</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lzv_jFAdxec0Krnf_c4ZRA.png" /></figure><p>Daily UI 011: Flash Message</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-e80w2eOUfW1C0BE1rlxtQ.png" /></figure><p>Daily UI 012:E-Commerce Shop (Single Item)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7o3XwlzutdfOHWgw2Ez2w.png" /></figure><p>Daily UI 013:Direct Messaging</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PKpCdWza7ZfEZeC_7lakKQ.png" /></figure><p>Any changes you’d like to suggest? Comment below :)</p><p>Follow my work daily on Twitter @anudhareshwar!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c0f17a08ced" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a good event booking experience]]></title>
            <link>https://medium.com/@anupamadhareshwar/designing-a-good-event-booking-experience-66fc1c45a1c9?source=rss-576071518ad2------2</link>
            <guid isPermaLink="false">https://medium.com/p/66fc1c45a1c9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Anupama Dhareshwar]]></dc:creator>
            <pubDate>Fri, 09 Jun 2017 06:14:53 GMT</pubDate>
            <atom:updated>2017-08-24T17:34:35.802Z</atom:updated>
            <content:encoded><![CDATA[<p>On an event booking website, the most important page is that which provides all the details about an event. This page has all the necessary information that customers need to know before booking their tickets. The trickiest part about designing this page is deciding what details to emphasize and how much of them to emphasize. Should the price of the tickets be shown first? Should the time and venue be shown first? Should there be pictures of the event? The list goes on.</p><p>Most often, all the information on the page about an event is supplied by the event organizers rather than the website administrators. This leaves the designer an added task of dealing with misplaced, repetitive or missing information.</p><p>Consider the following details page of a popular event booking website. (Pictures ordered as seen while scrolling from top to bottom)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMzLN8Fq7l3nvbG_qRxY9Q.png" /><figcaption>screen 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vl-z23AAkg9WvO_Sjj9FJg.png" /><figcaption>screen 2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwmrYcl3nVfggxCNmbx0RA.png" /><figcaption>screen 3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKKTCv94JVJWB5Cj1LO6DQ.png" /><figcaption>screen 4</figcaption></figure><p>I recently worked on redesigning the event details page for this website. I started my design process by conducting a set of user tests to understand the pros and cons of the design and areas where users were getting stuck.</p><p>I explored the website by myself first to list out the different functions I wanted to test with the users and created a test plan.</p><h4>The testing process</h4><p>I conducted 5 user tests and set up the following 5 tasks for each participant:</p><p>a. Book Tickets</p><p>b. Search for a particular tag</p><p>c. Invite friends</p><p>d. Follow the organizer</p><p>e. Subscribe to the newsletter</p><p>During the test, the users were asked to think out loud while exploring the website. After the test, I interviewed each of the participants about the usability and their general impression of the website.</p><h4>Usability issues</h4><p>The most common issues raised were:</p><p>a. Participants didn’t know what the event was until they scrolled down past the image carousel shown in screen 1.</p><p>b. They also had issues with the ‘Details’ tab.</p><blockquote>“This doesn’t tell me anything about the event.”</blockquote><p>c. The details about the organizer were unclear and many participants spent time looking for the organizer’s name.</p><p>d. Participants noticed too many repetitive calls to action for the same function like Invite friends, subscribe to news letter, etc.</p><blockquote>“Why are there so many sharing options? They’re all over the place.”</blockquote><p>e. The “I am interested” floating view at the bottom blocked their view while scrolling(screen 2–4)</p><blockquote>“ This is distracting. I feel like it’s blocking stuff at the bottom of the screen”</blockquote><h4>The Analysis and Redesign</h4><p>Taking into account the concerns raised by the test participants, I made the following changes to the design</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*caUxmZQ2gcxBe2GWc3u9Eg.png" /><figcaption>screen 5</figcaption></figure><p>a. The image carousel took up 90% of the page of which the image itself took up 60%. Reducing the space allocated for the image carousel as shown in screen 5 would accommodate the Event information at the top of the page.This would give customers information about the event as soon as the page loads.</p><p>b. I assumed that the ‘Details’ tab was a description provided by the organizer and not the administrators of Events High. So, the amount of information provided and its relevance depends on the organizer. To ensure relevant entries, the form fields to be filled in must hence be designed with a clear structure and descriptive fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_COH6gGflgGqqPTgAEY2kw.png" /><figcaption>screen 6</figcaption></figure><p>c. The organizer information can be presented more noticeably as a part of the information categories so that following the organizer is easy for the customer. In screen 6 it can be seen that ‘Organized by Triyana’ and a follow button next to it is clearly specified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V625Pa0LiR1c618BkfI-iQ.png" /><figcaption>screen 7</figcaption></figure><p>d. The ‘book ticket’ floating view can be placed with the main toolbar having menu options, at the top of the screen to avoid obstruction while scrolling. This can be seen on the top of the screen in screens 6–7.</p><p>e. Repetitive calls to action like the “invite friends” button was a decision made by the designer possibly to stress the importance of the function to the website owners. However, multiple instances of this clutters the screen and distracts the customers. Repetition can be avoided by making the button prominent with a contrasting size or color to stress its importance. It can also be placed on a floating toolbar which appears throughout the page scroll. As seen in screens 6-7 where the floating view consists of a share icon to invite friends, a heart icon to favourite the event and the book tickets button along with the name of the event.</p><p>In short, the key information to highlight on an event details page includes event name, date and time, location, organizer and of course, a ‘book tickets’ option. Displaying the book tickets option even while scrolling through different sections of the website, through a non-obstructive floating view adds to the usability of the website.</p><p>Check out more of my work on <a href="https://www.behance.net/anupamadhareshwar">behance.net/anupamadhareshwar</a> and let me know what you think!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66fc1c45a1c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Packaging design in Airplanes]]></title>
            <link>https://medium.com/@anupamadhareshwar/packaging-design-in-airplanes-3bd3ee4f1f9c?source=rss-576071518ad2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bd3ee4f1f9c</guid>
            <category><![CDATA[packaging-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[airplane-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[bad-design]]></category>
            <dc:creator><![CDATA[Anupama Dhareshwar]]></dc:creator>
            <pubDate>Sat, 03 Jun 2017 17:22:29 GMT</pubDate>
            <atom:updated>2017-06-07T00:36:01.214Z</atom:updated>
            <content:encoded><![CDATA[<p>Travelling on a plane is an emotional roller coaster. The passenger is already going through a whole range of emotions, from excitement to anxiety to discomfort . The last thing you want is the in-flight services to add to the turbulence.</p><p>Recently, I had an unpleasant experience on an eight hour long flight. The discomfort started when I was assigned a misaligned window seat which left me with a breathtaking view of the plane’s inner wall.</p><p>Further, with a neighbour who took long and occasional glances at my IFE screen, I realised the need for polarizers on screens to restrict the viewing angle for self-conscious travelers like myself.</p><p>Aside from all this, I was faced with the challenging task of opening a very confusing snack box:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7XFLXUi1XsP2syPGSLZSvQ@2x.jpeg" /></figure><p>As you can see from the picture above, while the flap says “press and lift to open” , the design of the flap hardly affords opening. Since the flap opened inwards, the design required me to put my finger in the negative space between the flap and the top semicircular boundary of the box to lift it open. This is against the expected function of a flap, which generally affords a pull function to act as a lever. Needless to say, I struggled to understand exactly how to “lift” the flap alongside occasional glances from my neighbor who — very smartly if I might add — was waiting for me to figure the box out before he could have a go at it himself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zz1WaBDAr8A1xMtnO-IjQQ@2x.jpeg" /></figure><p>After some examination, I shamelessly yanked at the flap from the bottom edge of the top surface, expecting to rip the box open. To my surprise, the box ripped along a perforated edge on the right side and came off completely with its glue lining on the left side. Again, with absolutely no indication of the perforation, I had no way of knowing that the box opened that way. Strike two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A55mf6jJSX9imJZxSYrHKg@2x.jpeg" /></figure><p>What’s funny is that there was a symmetric perforated crease on the left side of the box which I only noticed while examining the picture. Neither was it visible, nor was it loose enough for the top covering to tear along it, despite my savage ripping. Strike three and yooooou’re out.</p><p>Sadly, my neighbor was just as unfortunate in figuring the box out and ended up opening his box from the left side. Now, in the dimly lit confines of an airplane, it is necessary for food packaging to open effortlessly.</p><p>And how do we make this task effortless?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HsXvKJJR9zHdAnYR9zdPA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6S2tl3CsYrU0BB5ZMcV3gw.png" /></figure><p>With visible indications of affordances, of course! A possible redesign could be to eliminate the confusion with a clear and simple design where the flap opening inwards can be omitted and the perforation along which the box is to be opened can be explicitly highlighted.</p><p>Good packaging design is especially important in a flight because people are conscious of being watched by strangers sitting with them throughout the journey. A small error could result in awkwardness for the rest of the flight. Therefore, any instance where users could feel stupid should be eliminated with good design. After all, as Don Norman puts it, there’s no such thing as stupid users, only bad design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bd3ee4f1f9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Peep Series]]></title>
            <link>https://medium.com/series/peep-series-d7d6ac255271?source=rss-576071518ad2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7d6ac255271</guid>
            <dc:creator><![CDATA[Anupama Dhareshwar]]></dc:creator>
            <pubDate>Wed, 22 Mar 2017 20:47:52 GMT</pubDate>
            <atom:updated>2017-09-12T21:22:12.380Z</atom:updated>
            <content:encoded><![CDATA[<p>Gothenburg, Sweden</p><p>Through the eyes of an outsider.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7d6ac255271" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>