<?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 The UI/UXperience on Medium]]></title>
        <description><![CDATA[Stories by The UI/UXperience on Medium]]></description>
        <link>https://medium.com/@TheUI.UXperience?source=rss-2923f5ce2c38------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nwVf1Ab5rzTzfD2xS17UWw.jpeg</url>
            <title>Stories by The UI/UXperience on Medium</title>
            <link>https://medium.com/@TheUI.UXperience?source=rss-2923f5ce2c38------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:10:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@TheUI.UXperience/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[Ironhack Project 3: App Redesign]]></title>
            <link>https://medium.com/@TheUI.UXperience/ironhack-project-3-app-redesign-e795375ecf38?source=rss-2923f5ce2c38------2</link>
            <guid isPermaLink="false">https://medium.com/p/e795375ecf38</guid>
            <dc:creator><![CDATA[The UI/UXperience]]></dc:creator>
            <pubDate>Mon, 04 Sep 2023 22:31:35 GMT</pubDate>
            <atom:updated>2023-09-04T22:32:31.703Z</atom:updated>
            <content:encoded><![CDATA[<h4>Redesigning Instagram based on Jakob Nielson’s Heuristic Analysis</h4><p>A project to work on alone, an unexpected design challenge, a new design process, and a deadline of 3 days. It was clear this project was meant to shake us out of the usual project process that we started to get comfortable with. It was also a chance for us to practice our individual brainstorming and Figma skills in this brief, but interesting assignment.</p><p>Our <strong>objective</strong> was to <strong>pick an app that everyone would recognize, analyze the app to see what doesn’t follow Jakob Nielson’s Usability Heuristics, and make design improvements accordingly.</strong></p><p>This was not an easy task, but it was one to try to tackle anyway. I picked Instagram. Its simple interface would be realistic for me to redesign in the few days with my current Figma skills. Additionally, it felt like an app I knew enough to quickly, yet effectively analyze as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*McjNJtcneb74oDN96--0Tw.jpeg" /><figcaption>Instagram —<a href="https://blog.hootsuite.com/instagram-statistics/"> The 4th Most Used Social Social Platform</a> — Picture taken by <a href="https://www.pexels.com/@cottonbro/">Cotton Bro Studio</a></figcaption></figure><p>Before the analysis, I first went through the entire app as a whole. This allowed me to look at the app consciously, so I could later spot areas where the app’s details might differ from Nielson’s Heuristics. Like most people, this is an app I use in a subconscious manner, so I had to somewhat get out of that mindset to approach this project more effectively.</p><p>It was only after that, where I properly begun the analysis process where I <strong>looked at a screen, searched for Heuristics not being followed, recorded them, and moved on to the next screen.</strong> This process continued until I found a realistic amount to work with. While I went through the app, I chose to focus my analysis on the areas that are <strong>accessible to users on a day-to-day basis</strong>. This meant I chose not to focus on the Settings, as this would not be Instagram’s MVP user flow.</p><p>The <strong>first thing I noticed </strong>was the <strong>language of the icons were not consistent. </strong>Specifically, <strong>the heart icon in the home feed itself has two meanings</strong>, depending on its location. The <strong>heart icon at the top of the feed meant notifications </strong>can be viewed upon clicking it. At the same time, the<strong> heart icon underneath each post, meant the user can express their like towards the post. </strong>From this, I concluded that the <strong>heuristic not being followed</strong> is the<strong> Consistency &amp; Standards </strong>one, in this case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y6tfrHxixuhszTGuciaXaA.jpeg" /><figcaption>Heart Icon language differences — I categorized this in Severity 4</figcaption></figure><p>Liking posts play a huge role in the Instagram experience. From customizing your algorithm to showing support for those who create the content you like, liking posts has a lot of use cases and is a core feature.</p><p>However, for a user, <strong>viewing liked posts</strong> they have previously liked is <strong>not convenient.</strong> Thus, I identified that the heuristic that could be applied through a re-design is <strong>Recognition Rather Than Recall</strong>. Currently, it <strong>takes 3 clicks to view previously liked posts. </strong>Not only is the <strong>liked posts feature not conveniently accessible,</strong> which would result in the feature being less used, it is also situated in a <strong>place that requires users to remember its location.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9NFD0V1mcbaKUNs4vy-Fg.jpeg" /><figcaption>Viewing Previously Liked Posts in the Activity Section — Severity 4</figcaption></figure><p>When one uses an app consistently, they get better at using it and want to find ways to use the app to optimize the tasks they wish to do. This is where the <strong>Flexibility &amp; Efficiency of Use</strong> heuristic comes in. The Direct Messages section was a section in the app I saw an opportunity to improve the user experience, by providing options to increase efficiency.</p><p>Instagram users can use the Direct Messages to send their friends messages, and are provided the option to share Instagram posts, reels, and profiles as well. While this is great on its own, it would be even better if <strong>users had a way to search for specific things sent in the past. </strong>In the <strong>current version, there is no available method to search for old messages, </strong>which would <strong>force users to scroll up for long stretches of time</strong> until they <strong>find what they were looking for.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCWvDSR4h3FrK150fmw3Tw.jpeg" /><figcaption>Direct Messages — Lack of a method to find old messages — Severity 3</figcaption></figure><p>I noticed the Collections section that would also do better with an additional <strong>Flexibility &amp; Efficiency of Use</strong> feature. The Collections at present allows one to create new collections, and are by default organized from newest made to oldest made. But the <strong>Collections screen offers no way to organize the collections yourself. </strong>For users who like to save a lot of posts over time, providing a feature to help with this could be a great help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4p8-yrfJ_MQut_HAjlYaJg.jpeg" /><figcaption>Collections — Lack of a feature that allows users to further organize their saved posts — Severity 2</figcaption></figure><p>Lastly, I noticed that the Comments overlay that appears when one wishes to place a comment on a post could also do with a minor improvement. At the moment, there is a <strong>row of limited emojis</strong> a user is able to utilize. Unfortunately, not only does this <strong>row take up unnecessary space,</strong> the <strong>emojis contained within it are limited,</strong> resulting in <strong>users just making use of the emoji’s through their own keyboards instead. </strong>Therefore, the heuristic that this decision doesn’t follow is the<strong> Aesthetic &amp; Minimal Design </strong>one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MAs1AMlmQJkqkLdOQUBZ2g.jpeg" /><figcaption>Commenting on a post — A row of limited emojis — Severity 1</figcaption></figure><p>Looking at all of these observations, I knew I couldn’t simply dive in and start the redesign process. Before that, I had to understand <strong>what order I had to work on these changes.</strong> For this the <strong>feature prioritization graph </strong>came in handy. The graph made me understand which changes were <strong>High Severity, Low Severity, High Effort as well as Low Effort. </strong>This step in the process made the rest of my project a lot easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nk6iBGlnw82_OI3wJo-z7w.jpeg" /><figcaption>Heuristic Analysis — The graph that put my project to perspective</figcaption></figure><p>Now, that I knew the order of my tasks better, I <strong>continued with ideation </strong>with the graph in mind. The <strong>pictures below showcase the solutions I came up with </strong>for the re-design to help Instagram follow Jakob Nielson’s Heuristics more closely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*syxFD_ME_j2i_ZRbac_LIw.jpeg" /><figcaption>Low-fi Ideated solutions in order of severity and effort Pt. 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cS4A7_zUvEN1tuTjdxU8jg.jpeg" /><figcaption>Low-fi Ideated solutions in order of severity and effort Pt. 2</figcaption></figure><p>I was officially entering the high-fi stage. To understand what the high-fi redesign would contain, I had to understand Instagram’s app branding. So I <strong>created a Style Tile</strong> to identify <strong>brand colors, neutral colors, semantic colors, typography, and iconography.</strong></p><p>I was surprised to see how many neutrals the Instagram app used.<strong> </strong>Before this project, I would have thought that Instagram used only one black shade, one gray shade, and one white shade as neutrals, but there were more shades that I had expected, which would explain why despite Instagram’s simple design, it still looks visually complete. I didn’t have the typefaces that Instagram uses so I had to improvise on that and use DM Sans. Similarly, their icons set was not something I could find either, so I had to approach the re-design with icons from two separate designers and a couple of DIY-ed icons using those sets and combining them with my currently limited Figma skills.</p><p>Finally, it was time to <strong>create components.</strong> As with a lot of beginners, I’m always surprised at just how much this stage helps projects. The time spent on this stage always pays off later on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-gHsfBkjeDYZNnPxEOWJQ.png" /><figcaption>Components created which were used in the final high fi</figcaption></figure><p>Using the components, I proceeded to <strong>make the high-fi design. </strong>This stage was the most difficult, personally. I had to ensure to put in everything I learned from Figma labs into my process, and approach everything methodically as well. After creating my screens, I <strong>completed a prototype</strong> as well which included the solutions I presented earlier within the Ideation stage in this case study.</p><p>Do check out my prototype through the link below:</p><p><a href="https://www.figma.com/file/LrgXvSpECGfOpkiObayukL/Siwanthika---Project-3%3A-Redesign-an-App?type=design&amp;node-id=3%3A11&amp;mode=design&amp;t=nP9XQxVEmV66OPCE-1">https://www.figma.com/file/LrgXvSpECGfOpkiObayukL/Siwanthika---Project-3%3A-Redesign-an-App?type=design&amp;node-id=3%3A11&amp;mode=design&amp;t=nP9XQxVEmV66OPCE-1</a></p><p><strong>Key Learnings</strong></p><ul><li>Detach personal opinions of apps when conducting heuristic analysis.</li><li>Feature prioritization is a key to setting realistic scopes.</li><li>Get better at Figma.</li></ul><p><strong>Next Step</strong></p><ul><li>Out of the solutions presented, the one I was unable to complete was the option to drag collections across the screen. I must learn how to display this feature on Figma effectively.</li></ul><p>This case study was a quick project, but despite that, it was challenging and gave me an opportunity to exercise my skills. I am slightly better at UI/UX design now than I was yesterday.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e795375ecf38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Project 2: E-Commerce Website]]></title>
            <link>https://medium.com/@TheUI.UXperience/ironhack-project-2-e-commerce-website-c726bde293d3?source=rss-2923f5ce2c38------2</link>
            <guid isPermaLink="false">https://medium.com/p/c726bde293d3</guid>
            <dc:creator><![CDATA[The UI/UXperience]]></dc:creator>
            <pubDate>Wed, 30 Aug 2023 21:09:47 GMT</pubDate>
            <atom:updated>2023-08-30T21:09:47.703Z</atom:updated>
            <content:encoded><![CDATA[<h4>Bringing life to a neglected elaborated stone website</h4><p>This time, I got the chance to work with Abbie and Hector, who were both fantastic team mates. It was a tough project as we were to complete both UX and UI processes within the same time frame as our previous project, but we managed to pull through with careful organization and maintaining efficiency throughout.</p><h4>The Design Challenge</h4><p>Help a local business <strong>redesign their website</strong> while putting it through a <strong>rebrand</strong> and include <strong>a revamped shopping experience</strong> for users.</p><h4>1.1 Empathy: Stakeholder Interview Preparation</h4><p>We first started off by <strong>discussing our leads</strong> and briefly discussed how we would approach the stakeholder interview. At this point, we hadn’t received any confirmations from our leads yet, so we proceeded to <strong>create an interview guide. </strong>We individually came up with questions, and voted on the best ones that would make it to the final interview guide. Additionally, we started utilizing the<strong> Kanban system</strong> which would serve us well for the entirety of our project.</p><p>On the next day, we <strong>talked about our tasks for the day</strong> and how we would proceed with this project. This would become a <strong>daily habit that would compliment the Kanban system.</strong> Creating daily tasks, tracking them, and setting deadlines would be the role of the project manager. In order to <strong>improve each of our soft skills</strong>, it was decided that <strong>every person in the team would be a project manager for three days.</strong></p><h4>1.2 Granitos Cardeñosa - Our Stakeholder</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*Ob9Pavg9o3FACy5v5QtRaA.png" /></figure><p>In the nick of time we managed to get a confirmation from our <strong>stakeholder for an interview</strong>, so after we refined the interview guide, we proceeded to hold it and gather the stakeholder’s insights from it. Here are a few key things we learned from the interview:</p><ul><li><a href="https://granitoscardenosa.com/">Granitos Cardeñosa</a> is an elaborated stone business that has an <strong>artisanal </strong>approach. Unlike their competitors, they <strong>don’t take on large projects </strong>and <strong>don’t have much machinery. </strong>They have a <strong>long history</strong>, with <strong>cultural restorations, custom projects, and artisanal products,</strong> and want to be perceived in this way through their website as well.</li><li>They want <strong>+ 25% on sales</strong> by the end of the next financial years.</li><li><strong>Customers the existing form</strong> to contact the business and then <strong>ask for prices.</strong></li><li>They wanted the website to go through a <strong>complete overhaul.</strong> Since the stakeholder wanted us to deliver the project for them to implement in the future, <strong>we had to present accurate information, and rebrand the website with the original logo colors.</strong></li><li>While they knew this project was hypothetical, due to the fact that the website was not in the best shape, they considered this as a legitimate project for their company.</li></ul><h4>1.3 Secondary Research, Stakeholder Analysis &amp; Competitors Analysis</h4><p>We wanted to know what we were dealing with. Neither of us in the team were knowledgeable about the stone industry and the websites they offer, so research was especially crucial. We split duties of <strong>conducting secondary research, stakeholder website analysis, and competitors analysis </strong>amongst the three of us and shared our gatherings with each other by the end of it.</p><p>For the <strong>secondary research</strong>, we organized the stakeholder’s <strong>interview answers</strong> into the <strong>categories of Goals, Strengths, Weaknesses, and Requirements. </strong>This helped us <strong>understand the business in a more structured way. </strong>After that we gathered information on <strong>the business &amp; customer trends, </strong>to gain a clear <strong>understanding about the stone industry </strong>as a whole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UtcjPiVGVl7rfEs7DKpLiw.png" /><figcaption>Stakeholder Interview Analysis, Business Trends &amp; Customer Trends</figcaption></figure><p>At the same time, we conducted the <strong>stakeholder website analysis</strong> by first taking <strong>screenshots of the website</strong>, then <strong>creating the navigation map</strong>, and by laying out <strong>observations in the categories of ‘the good stuff’ and ‘the bad stuff’</strong>. We researched the Granitos Cardeñosa website in a thorough manner, as we found it to be confusing and to also get an idea of the scope of tasks that we’ll come across later in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ijBmDzsC42bOk_cAMKxUjw.png" /><figcaption>Stakeholder Website Analysis: Stills of the Website, Navigation Map, The Good Stuff &amp; The Bad Stuff of the Website</figcaption></figure><p>We also completed a competitor’s analysis where we were able to do a <strong>comparison</strong> <strong>between the Granitos Cardeñosa website with two of their known competitors.</strong> At first, we organized these thoughts in a detailed written glows &amp; grows format. Later, we organized the information in the form of a <strong>Features &amp; Pages chart </strong>to make the findings more digestible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4kZ_n5mRP-89ic6znAESJQ.png" /><figcaption>Competitors Analysis</figcaption></figure><h4>1.4 User Research</h4><p>We were clear about what we felt about the websites in this industry so far, but we knew it was time to understand what users experiences are actually like. We needed to hear from completely unbiased perspectives and for that, we had to interview them. After outlining the <strong>Areas of Interest</strong> we individually came up with questions accordingly. Thereafter, we voted on the best questions for the <strong>final interview guide.</strong></p><p>We found it challenging to find interview participants due to the fact that this was a niche website and not many people around us are at a position to make or renovate a home. Still, we managed to find <strong>four participants</strong> and asked them to have a <strong>Zoom interview</strong> with us. The <strong>interviewees ages ranged from early 30s to late 50s</strong>, with the majority being over 40.</p><p>We asked about the <strong>services they went for, what their website preferences were, how they find inspiration for projects, and how they find their stonework providers. </strong>From all the useful input we received from the participants, we were able <strong>dot-vote and pull out the most important points from interviews</strong> in order to complete the <strong>user research affinity diagram</strong>. The following info-graphic summarizes our findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7mE4oFUg80JuFuQVY2lzxA.png" /><figcaption>User Interviewees Thoughts</figcaption></figure><h4>1.5 Define: User Persona, Problem Statement &amp; Color Palette Analysis</h4><p>Thanks to the fact that the insights were clearly laid out in the affinity diagram and through additional insights from our interviews, <strong>creating the user persona </strong>was a relatively easy task. We included <strong>needs, frustration points,</strong> as well as <strong>personality</strong> and a <strong>biography </strong>to make the persona feel alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ePypUrwLonpKCIZ0QWRdrA.png" /><figcaption>User Persona Based on our Interviews</figcaption></figure><p>It was time to<strong> create our problem statement.</strong> For a task that consists of just creating one simple sentence, this stage is somehow always more difficult than it seems. Knowing that this sentence would impact the rest of our project, we made sure to approach this with care and ensured to refine it till it was to-the-point but covered the design challenge we had to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSaHCCelLpk32KKYuV_5YA.png" /><figcaption>Final Problem Statement</figcaption></figure><p>Just like how we completed a stakeholder analysis of the website, we also included an<strong> analysis of the color palette of the current website.</strong> While this step was not expected as a deliverable, it was something we did anyway so we had a <strong>complete picture of what our stakeholder’s website was. </strong>Additionally, while we were expected to refresh the branding, we were still expected to stay true to the brand colors, as per the stakeholder’s request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FGmderXGlkOXsD2zuOQ7Qw.png" /><figcaption>Detailed Color Palette of Stakeholder’s Wet</figcaption></figure><h4>2.1 Ideation: Crazy 8s</h4><p>At the beginning of this project, we were looking at an outdated website that needed help. Since the entire website was full of opportunities, it was hard to tell what exactly needed to be done realistically within two weeks. However, through the previous steps in the process, we were able to get a clear idea on what to ideate. Through <strong>Crazy 8s </strong>we were able to <strong>quickly think up a variety of ideas.</strong> After taking a vote, we placed these <strong>ideas into the categories: Contact Options, About Us, Purchase/Budget Request, and finally Materials/Quarry/Sustainability.</strong></p><p>Since we also had to ensure to develop a <strong>MVP that would achive the ‘Aha!’ moment </strong>we ensured to go through a <strong>prioritization process through the MoSCoW Method. </strong>This method set up our expectations of the work we had to do in a realistic manner and ensured we could complete our challenge within the provided time frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vmNSSX8Td80WjXziQcVKnQ.png" /><figcaption>Must Haves from the MoSCoW Method</figcaption></figure><h4>2.2 Information Architecture &amp; Site Map</h4><p>While keeping the Must Haves in mind, we proceeded to <strong>individually come up with a list of pages, along with what each page should have, discussed our work and voted on the most agreed ideas.</strong></p><p>Next, came the <strong>site map and information architecture. </strong>This was one of the most difficult stages in the project and it was definitely reflected in our work as all of our individual site maps looked quite different from each other. We were confused whether we had to include flows or just keep the pages. After a lot of deliberation, guidance, and trusty FigJam stickers we relied on for dot voting, we completed the site map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_yy2FCZmN2311g-hm3BiQA.png" /><figcaption>Finalized Site Map</figcaption></figure><h4>2.3 User Flow</h4><p>The User Flow were created with two types of people in mind. The <strong>first type of person</strong> is someone who knows exactly what they want and is <strong>seeking a customized stonework project</strong>. The <strong>second type</strong> is one who somewhat knows what they are looking for in terms of product, say a garden fountain, but was <strong>unsure of the measurements and materials they want</strong>. This type of person is someone who is willing to browse for information and make an educated decision based on the information the website provides.</p><p>We needed a user flow that could accommodate these two needs, it was a smooth process completing this stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A4B44r3zNqnMwf7TKH6gfw.png" /><figcaption>Completed User Flow</figcaption></figure><p>To summarize the diagram, these processes were as follows:</p><ol><li>Homepage -&gt; Search / Product Catalog -&gt; Filter Product Specifications -&gt; Add to Basket -&gt; Cart With Purchase Option -&gt; Personal Details + Delivery Method + Payment Details -&gt; Success Screen</li><li>Homepage -&gt; Search / Product Catalog -&gt; Filter Product Specifications &amp; Add Custom Specifications -&gt; Add to Basket -&gt; Request Budget Option -&gt; Contact Details -&gt; Success Screen</li></ol><h4>2.4 Low Fidelity &amp; Mid Fidelity</h4><p>We approached the <strong>lo-fidelity stage by assigning different pages and flows amongst ourselves and coming up with a range of screens to choose from. </strong>This was we could cover more ground quicker and still yield a wide selection of ideas we could vote on. After discussion on our best screens from each section such as purchase flow, home page, product details page, and product catalog, we proceeded to the <strong>mid-fi stage where these sketches were refined through Figma. </strong>Our aim was to<strong> complete a mid-fi prototype so we could have a usability testing session to see what others thought of our ideas so far.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z4IjsGHacxeH1npPFpBeTA.png" /><figcaption>Evolution of the Product/Item Page</figcaption></figure><h4>2.5 Usability Testing &amp; Iterations</h4><p>For our usability tests, we assigned a couple of tasks for our testers to complete.</p><ul><li><strong>Purchase an existing stonework product with the dimensions (30 x 50 x 10).</strong></li><li><strong>Figure out how to proceed if you want a product with your own measurements.</strong></li></ul><p>As these tasks were specific, we hoped it would allow our testers to get into the mindset of being a user in a more realistic manner. We managed to gather 3 key insights from this process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jh4TdKEn_s5ou-el5zQY2w.png" /><figcaption>Usability Tests Insights</figcaption></figure><p>Based on the feedback, we included these iterations:</p><ul><li><strong>Made the ‘Custom Project’ option more visible in the individual item page by including a drop down and a notes field.</strong></li><li><strong>Included a ‘Custom Project’ option in the homepage itself for those who don’t want to browse for products and only wish to get their specific project completed by the company.</strong></li></ul><h4>3.1 User Interface: Mood Board &amp; Style Tile</h4><p>The <strong>brand attributes </strong>we used as inspiration to create our mood board were <strong>Professional, Artisanal, and Local </strong>and to our luck people we tested were able to guess these attributes using the same words or very similar ones which meant we were heading in the right visual direction. Earlier in our project, we had already <strong>researched brand imagery which expedited the creation of our mood board </strong>as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*giDhJUPn2kbdaW92DuLEQw.png" /><figcaption>Mood Board from Brand Attributes</figcaption></figure><p>To finish up our visual thought process, we <strong>created a style tile</strong>, keeping in mind our <strong>stakeholder’s needs of sticking with the original logo colors</strong> but also ensuring that we accomplish the <strong>goal of rebranding </strong>as well. We ensured the <strong>typography was a readable typeface for accessibility.</strong> Considering many of the customer base are over 40, this was a crucial choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgK_b5S76nL1rGNSAMXW-w.png" /><figcaption>Style Tile for UI</figcaption></figure><h4>3.2 High Fidelity</h4><p>The High Fidelity process included many components including buttons, materials selection, individual product listings and many more. We tweaked them during the process, discussed visual decisions, created the final pages, and prototyped it all to make a final workable outcome. We also completed a responsive screen to top it all off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yXgXByqz9ndpl2LNQpEwPQ.png" /><figcaption>Responsive Hi-Fi Screens</figcaption></figure><p>Check our prototype through the link below:</p><p><a href="https://www.figma.com/file/PwH3Y7AdamI3xL45RJQAzY/P2-Dates--E-Commerce-%7C-Design-File?type=design&amp;node-id=3120%3A20155&amp;mode=design&amp;t=BnMxD3oZ2yof6DCS-1">https://www.figma.com/file/PwH3Y7AdamI3xL45RJQAzY/P2-Dates--E-Commerce-%7C-Design-File?type=design&amp;node-id=3120%3A20155&amp;mode=design&amp;t=BnMxD3oZ2yof6DCS-1</a></p><h4>Next Steps</h4><ul><li>Include finalized prices and shipping info as this would make the ordering process much more convenient.</li><li>A page dedicated to machinery, factories and quarries would increase customer trust</li><li>Sustainability information is especially important for potential customers from newer generations</li></ul><h4>Key Learnings</h4><ul><li>Local stone work websites are generally poorly designed and look not trust worthy for newer generations. For UI/UX designers this industry is full of opportunities with stakeholders who would appreciate any help they can get to improve their websites.</li><li>People prefer learning about materials &amp; specifications but are forced to go to stonework companies to find this info.</li><li>The Kanban method, dividing &amp; conquering work, as well as rotating project managers role made our process smooth.</li></ul><p>All in all, this design challenge was fast paced and a bit grueling, but through team work and determination, we managed to gracefully end our project with relief and pride. This project gave us a boost of motivation and by the end, it was a fantastic feeling to see our hard work pay off!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c726bde293d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Project 1: Culture & Heritage]]></title>
            <link>https://medium.com/@TheUI.UXperience/ironhack-project-1-culture-heritage-c03eec45af76?source=rss-2923f5ce2c38------2</link>
            <guid isPermaLink="false">https://medium.com/p/c03eec45af76</guid>
            <dc:creator><![CDATA[The UI/UXperience]]></dc:creator>
            <pubDate>Sun, 13 Aug 2023 19:55:03 GMT</pubDate>
            <atom:updated>2023-08-13T20:04:42.327Z</atom:updated>
            <content:encoded><![CDATA[<h4>Case study for our first group project with a focus on the UX Design Process</h4><p>In this project, we were placed in groups of 3–4. My group consisted of Darius, Johannes, Katie, and myself. I’m thankful that I got to work with these three during the first project as they were wonderful to work with.</p><h3>The Design Challenge</h3><p>We were tasked to create a mid-fidelity prototype that will <strong>help public institutions fulfill their mission to preserve cultural heritage by bridging the gap between public cultural institutions and people.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZNyJJcyesEqMNWos" /><figcaption>Interior of a Theater taken by <a href="https://www.pexels.com/@lu62/">Lucia Barreiros Silva</a></figcaption></figure><h3>1. Empathize</h3><p>While going through the project brief, we understood that the provided challenge was a broad issue with a variety of factors at play, and that we had to eventually narrow down our solution to solve the most important factors.</p><h3>1.1 Brainstorming &amp; Secondary Research</h3><p>To kick-off our project, we first had a <strong>brainstorm session followed by a discussion</strong> as to why there is a gap between people and cultural institutions along with their events. All of us had very different perspectives, which was a good thing, as it helped broaden our minds throughout this project.</p><p>Since we were aware that this solution was not going to be for us, but instead the user, we had to get to the bottom of the problem. We held a <strong>secondary research session</strong> where we individually researched a pain point and came across facts &amp; figures as well as opinions from forums, to see what barriers people face when it comes to visiting cultural institutions and the events they hold. We clustered our findings to form the following statement.</p><p><em>Museums struggle to attract a broad audience and create a inclusive environment due to limited marketing, physical accessibility, and a lack of information.</em></p><h3>1.2 User Interviews</h3><p>To ensure we were heading the right direction, we knew we had to do further research by conducting interviews. We were also aware that we had to remove any bias at this point. After defining our learning goals, so we were clear on what areas to explore during the interviews, we individually typed up our interview guides. After that, we <strong>voted for the best questions and created our finalized interview guide.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*j2eauu9UebEHwfb4zm47mQ.png" /><figcaption>Voting process for interview guide. Hearts indicate questions we like. Stars indicate essential questions.</figcaption></figure><p>Finally, we<strong> conducted the interviews </strong>of 5 participants. We recorded the interviews to refer back to later so we wouldn’t miss anything the interviewees mentioned. In addition, referring to recordings would remove any potential biases during transcription. During the interviews, we took note of their thoughts and feelings on <strong>areas of limitations such as social, physical, monetary, and marketing.</strong> We noticed that a lot of the input from our participants were vastly different from our assumptions during our initial brainstorming session. It was interesting to learn about the commonly shared opinions as well as opposing ones which stemmed from geographical factors.</p><h3>2. Define</h3><p>To organize our findings, we <strong>created an affinity diagram </strong>and clustered our interviewees thoughts into the following categories:</p><ul><li>Marketing Channels</li><li>Generating Interest</li><li>Accessibility</li><li>Visitor Experience</li><li>Miscellaneous</li></ul><p>From there, we <strong>held a dot-voting process</strong> to prioritize the most important as well as most achievable areas of interest for our mid-fidelity prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*9ZzxBRpriGuvBmogTdmafA.png" /><figcaption>Finalized Areas of Interest</figcaption></figure><h3>2.1 User Persona</h3><p>It was time to synthesize our affinity diagram findings and what better way to do this than define our target user by<strong> making a user persona.</strong> We first worked on the psychographics of this user persona as<strong> goals, needs, and pain points</strong> (frustration statements) are the most crucial part of the persona. After that, we worked on the rest of the user persona, such as job, personality, and motivations.</p><p>Somewhere down the line we reworked our user persona as it was initially too niche and would contradict our design challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Knt1ix9LnzAo4369Eyt3Vg.png" /><figcaption>User Persona</figcaption></figure><h3>2.2 User Journey Map</h3><p>With this we were able to <strong>create a User Journey Map</strong> that Benjamin would experience as he tries to find cultural events without a solution. The map includes the <strong>emotional journey at each stage, but also pain points as well as opportunities </strong>where we explore how our solution could help Benjamin in our solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwpPVZZdlmsDg9hCnWlXTw.png" /><figcaption>User Journey Map</figcaption></figure><h3>2.3 Problem Statement</h3><p><strong>Creating a Problem Statement </strong>was a bit more difficult that we thought. We individually worked on one and used those to create a finalized problem statement. Yet, we had to later rework this as well as it was originally too broad.</p><blockquote>People who are open-minded to culture and heritage need a way to easily gain awareness and engage with cultural institutions because of limited available information.</blockquote><h3>3. Ideate</h3><p>Right after, we jumped straight into <strong>ideating through Crazy 8s. </strong>We individually attended this task, put together our ideas, and once again, voted for our Top 3. We observed that there were <strong>some overlapping ideas as well as ones that we could merge together.</strong> At this point, it was reassuring to visually see our progress and know that the previous steps paid-off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2C_JEdW3z0A3NYp-Dk6MuA.png" /><figcaption>Crazy 8s Process</figcaption></figure><h3>3.1 Feature Prioritization</h3><p>To get a clear idea of our MVP, we had to put our feature ideas <strong>through the MoSCoW method. </strong>This technique allows a team to decide on the product’s main tasks and underline which features are <strong>must haves, should haves, could haves, and won’t haves</strong>. This was one of the toughest stages for us in this project since all the features we had agreed upon earlier were what we all saw as essential. Of course, we still proceeded and made the tough calls as a team. For a couple of features, it took quite a bit of discussion, but ultimately we managed to come to agreement on the decisions made through the MoSCoW chart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*64oi1JAciywpIhUiHHz1vg.png" /><figcaption>Feature Prioritization Process</figcaption></figure><h3>3.2 User Flows</h3><p>Probably one of the most easiest stages in this project was <strong>making the user flow. </strong>During this stage of the project, we were quite clear on what our product was and what we wanted it to accomplish. After <strong>answering questions to uncover what our user flow should ultimately contain </strong>including goals, types of decisions, and solutions, we went ahead and created our individual user flows. As usual, we <strong>took a vote on the best parts of each user flow. </strong>We then discussed the user flow and <strong>created a final user flow together. </strong>Throughout this stage, we made sure to <strong>stick to the ‘Aha! Moment’ </strong>and that made it easier to make a user flow that made sense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ML4Ol9tzIn70HfpfXqHmig.png" /><figcaption>Finalized User Flow</figcaption></figure><p>We had 2 paths for the user flow. One for those with no accounts, and one for those who do.</p><ul><li>For <strong>those with no profiles, the user flow allows them to peruse the app’s homefeed, individual event details screen, and search for cultural institutions or events that they may be looking for. </strong>Upon clicking a feature like the ‘heart’ button, they will be redirected to the create user profile page, since features like this are only available to those with profiles.</li><li>Meanwhile for<strong> those with user profiles, the user flow is much more wider, as they have access to all the app’s features. </strong>Through creation of a user profile, they are able to put in their <strong>areas of interests regarding culture &amp; heritage, location, </strong>and other information that <strong>will allow them to have a customized homefeed. </strong>This is the optimal way of using the app. Pressing the<strong> ‘heart’ button will catalogue the cultural events</strong> they like which would <strong>further curate their homefeed better through an algorithm.</strong></li></ul><h3>4. Develop</h3><p>It was time to put on our creativity thinking hats again. In this stage, we <strong>worked on low-fi designs on all the screens in the user flow</strong> individually. Putting our designs together prompted discussions, especially with the homefeed screen as well as the event details screen, as these were the toughest screens to tackle. <strong>Through discussions, we finalized what each screen should have and then produced our mid-fi designs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VS8Ke3rg2pjT6mP4wiD12g.png" /><figcaption>Lo-Fi Homefeed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l0UvidDmTag5LHzBjUR9EA.png" /><figcaption>Mid-Fi Homefeed (prior to usability testing)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mq67uO96F4pppghg-IN8WA.png" /><figcaption>Lo-Fi Event Details</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1ECi1TTsXpgVW0Rbhd-8w.png" /><figcaption>Mid-Fi Event Details (prior to usability testing)</figcaption></figure><p>Since Johannes’ mid-fi designs were the most complete and presentable, we decided to complete the prototype through his work. Our team is detailed oriented and this stage suited us the most. With productive discourses, we were able to refine the design together, keeping in mind that we most likely will have to iterate as well.</p><h3>4. Iteration following Usability Testing</h3><p><strong>Holding usability testing</strong> was eye-opening and it was intriguing to hear what people had to say on the prototype. Hearing <strong>everyone’s responses is truly what perfected our prototype </strong>and while we always knew how important this stage was, it was a fascinating experience observing <strong>how the participants interacted with the mid-fidelity screens and finding out what they understood and what needed refining. </strong>Here’s what we refined upon their feedback:</p><ul><li>Changed the icons used for the filter and settings buttons to avoid confusion</li><li>Adjusted the spacing between the event run time dates</li><li>Reduced the amount of description text displayed in the home feed for each event</li><li>Placed description text under accessibility icons to provide clarity</li><li>Included title ‘Recent Other Events’ within event details screen</li><li>Placed a ‘more’ button for the description text within the event details screen</li><li>Provided an explanation text on the screen asking for location so users knows why the location is useful (curating feed based on location)</li><li>Included another explanation text on the user profile creation page, specifically the interests selection page, so users will be made aware that selecting interests will result in a curated homefeed</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LmJjawHKxOM4CK2G3WHSxw.png" /><figcaption>Refined Mid-Fi Homefeed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QE9AcwymMxVbgG1dgRt6XQ.png" /><figcaption>Refined Mid-Fi Event Details</figcaption></figure><h3>4.1 The Prototype</h3><p><a href="https://www.figma.com/file/RVwF6OvqT1EQ4KqZJ18QEl/Design-File---Elephant-Seals?type=design&amp;node-id=1724%3A5695&amp;mode=design&amp;t=w4oQoyr4ULJ1E5Yb-1">https://www.figma.com/file/RVwF6OvqT1EQ4KqZJ18QEl/Design-File---Elephant-Seals?type=design&amp;node-id=1724%3A5695&amp;mode=design&amp;t=w4oQoyr4ULJ1E5Yb-1</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c03eec45af76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Channel Groups Feature]]></title>
            <link>https://medium.com/@TheUI.UXperience/channel-groups-feature-76c765f8a9c?source=rss-2923f5ce2c38------2</link>
            <guid isPermaLink="false">https://medium.com/p/76c765f8a9c</guid>
            <dc:creator><![CDATA[The UI/UXperience]]></dc:creator>
            <pubDate>Wed, 05 Jul 2023 10:54:45 GMT</pubDate>
            <atom:updated>2023-07-05T11:05:46.056Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ironhack’s Prework Challenge 2: Wireframing</h4><h3>The App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*Hvy2moO_IdYhkyjufQKsGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*w9B6Qtuo4AlF7JwMXRoSJw.png" /><figcaption>An Open Source Streaming Client</figcaption></figure><p>Newpipe is a solution for those who value control over their online presence and privacy, but don’t want to miss out on watching YouTube videos. It works by transmitting only the necessary data to play the media to external servers. In addition, Newpipe also provides extra features such as organization of subscriptions into Channel Groups, bypassing annoying ads, and more to enhance users’ experience. To top it off, one doesn’t require an account to make use of the app.</p><h3><strong>The Chosen User Flow</strong></h3><p>The user flow I made a wireframe for is regarding the Channel Groups. To be exact, creating a new folder utilizing this feature. Personally, this aspect is crucial for my video viewing experience, as I now follow a lot of channels. Categorizing my subscriptions into neat little folders is an organization dream, and it saves me a lot of time from having to sift through a multitude of videos in the feed just to find one regarding a specific topic. I’ve noticed this feature has reduced my distraction while watching content as well. For example, if I have the goal to learn some Spanish for the day which I’d like to follow with watching an interior design video, I simply go to my ‘Spanish’ folder, learn what I have to learn, then visit my ‘Interior Design’ folder, watch what I’d like to watch, and exit the app right after.</p><h3>The Lo-fi Wireframe</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQwKp_b5q9GpYv-ZP9_VyQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UPVFxWus-HWNs_-WhLqmbA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*xkKuUz0Z0eAqAvZrCh0j0A.jpeg" /></figure><h3>The Wireframe Prototype</h3><p><em>Task: Create a new Channel Group with subscriptions</em></p><p><a href="https://www.figma.com/proto/xke9242WFmjdZ9Jiso6gk1/Challenge-2%3A-Wireframing?type=design&amp;node-id=77-6655&amp;viewport=316%2C698%2C0.5&amp;t=NdRx2VaU26v7H48G-1&amp;scaling=contain&amp;page-id=77%3A6654%3Ffuid%3D1253804202172855838&amp;mode=design">https://www.figma.com/proto/xke9242WFmjdZ9Jiso6gk1/Challenge-2%3A-Wireframing?type=design&amp;node-id=77-6655&amp;viewport=316%2C698%2C0.5&amp;t=NdRx2VaU26v7H48G-1&amp;scaling=contain&amp;page-id=77%3A6654%3Ffuid%3D1253804202172855838&amp;mode=design</a></p><h3>Conclusion</h3><p>This time, the challenge called for creating a wireframe for a user flow of our preference. The user flow I chose was the creation of a new folder within the Channel Groups feature in NewPipe. After careful observation of what the user flow I chose included, I was able to create a lo-fi wireframe which gave further clarity and solidified my understanding of the flow. Thereafter, I completed a wireframe prototype which allowed me to learn more about Figma’s capabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c765f8a9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading the Citymapper Experience]]></title>
            <link>https://medium.com/@TheUI.UXperience/upgrading-the-citymapper-experience-ebdec986e48e?source=rss-2923f5ce2c38------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebdec986e48e</guid>
            <dc:creator><![CDATA[The UI/UXperience]]></dc:creator>
            <pubDate>Mon, 03 Jul 2023 11:10:39 GMT</pubDate>
            <atom:updated>2023-07-03T11:52:23.181Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ironhack Prework Challenge 1: Design Thinking</h4><h3><strong>The Client</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6eASJvZyvki1dP7pj2n6PA.jpeg" /><figcaption>Making Cities Usable</figcaption></figure><p>Citymapper is an online mapping and public transit app with over 10 years of expertise under its belt. It has successfully provided transport options with live timing to enhance the urban mobility experience. With its features that help users find the quickest route and even indicate main roads to avoid dimly lit areas, this app is beloved my millions and continues to be a stand-out solution for anyone residing in major cities.</p><h3><strong>The Pain Point</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*tsQkw0-oM6C6fLm2E5nc-A.png" /></figure><p>Despite the advantages Citymapper has to offer, a recurring pain point highlighted by the users, is that <em>purchasing a variety of different public transport tickets </em>is frustrating.</p><p>Knowing the heart of the problem provided me good head start. However, in order to come up with a solution, I needed to understand how exactly users are affected and what they would like in the solution.</p><h3><strong>The Interview Process</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*Nc1hJH1n8qyw2hq1-A3pKA.png" /></figure><p>Below were the questions I prepared for five people of a similar demographic with varying lifestyles:</p><ul><li>What is your primary mode of transport?</li><li>When a journey to an unfamiliar location within the city is upcoming, what is your approach to planning the commute?</li><li>How do you manage planning journeys requiring multiple public transport channels in a foreign country? <br>- Do you gather information prior/soon after visiting the country? <br>- Do you do all the necessary procedures on the go?</li><li>What are the most important aspects to you while commuting?</li><li>Which purposes do you use Citymapper for (business trips/leisure/daily commutes)?</li><li>Describe a scenario when being unable to buy tickets at a go for multi-channel trips frustrated you.</li><li>Would you prefer purchasing all tickets:<br>- At a go, in bulk.<br>- Select specific tickets as you prefer.<br>- Both be available as options.</li><li>Would you prefer purchasing all tickets:<br>- Prior a journey.<br>- On-the-spot.</li><li>Which of the features would you prioritize more?<br>- Compare prices and choose the cheapest routes.<br>- Compare duration of routes and choose the ones that are the least time-consuming, regardless of the price.</li></ul><h3><strong>The Limitations Communicated to Interviewees</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*Vcm66lDfaMOl1HXirfKpcQ.png" /></figure><p>Since the pain point was already established and is the sole problem that requires a resolution, interviewees were either aware of or made aware of the following limitations:</p><ul><li>Citymapper primarily focuses their coverage for major cities. Towns, villages, and the like are generally not covered in many countries.</li><li>Citymapper does not have a feature that displays routes between major cities.</li></ul><h3><strong>The Main Takeaways from Interviews</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*qb7FtzUv1A8v5iS18v-IjA.png" /></figure><ul><li>Regarding public transport in foreign countries, all interviewees answered that they gather information on them before visiting the countries.</li><li>4 of them responded that they would prefer booking tickets on-the-go after gathering information, while 1 answered that they would like to buy tickets for the routes before entering the country.</li><li>3 interviewees prioritize the quickest routes, while 2 prioritize the cheapest ones.</li><li>While all answered that they would like to buy tickets at-a-go in bulk, 1 mentioned that an option to buy tickets separately would also be useful.</li></ul><p>Key words/phrases that came up during the interviews:</p><p><em>speed, time-consuming, duration, gather information prior, hassle, cost, waste of time, efficiency, confusing, at-a-go in bulk, frustrating, safety, reliability, delays</em></p><h3><strong>The Ideation Stage</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*i60W33R34sqA27XgpE4Ghg.png" /></figure><p>By applying the <em>“How Might We?” </em>method, it helped me focus on what the users need. These are the questions that I kept in mind while ideating solutions:</p><ul><li>How might we allow users purchase tickets in-bulk for the routes they wish to take?</li><li>How might we ensure that purchasing tickets is a convenient process?</li><li>How might we include a way that users can opt out of purchasing, should they accidentally/prematurely begin the tickets buying process?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zaetZT3hVIv-APGS632CEA.jpeg" /><figcaption>Sketch 1 for part of the purchasing tickets process</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-YNy_7cJvaDQrWmew2UnA.jpeg" /><figcaption>Sketch 1 for part of the purchasing tickets process</figcaption></figure><h3><strong>The Final Prototype</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hk1ksvVT4qoC5Dfo17cV3Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PGgg9Rk8-KmrSnHpI4j8zQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNsX922z2tB2uxezustw-w.jpeg" /></figure><h3><strong>What I Learned</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*tGmi85IyInHEGftTPkKIPw.png" /></figure><p>The challenge presented encouraged me to try out things I haven’t done before. For starters, Citymapper wasn’t an app I was very familiar with and this challenge allowed me to explore it for myself. More importantly though, it led me to conduct interviews, which is something I haven’t had much experience with in the past either. During the process, I thought the interviewees would answer certain questions in a specific way, but I was surprised to find out that their thinking process was not what I had predicted. Also, the ideating process as well as sketching out a prototype made the gears in my brain work differently from what I’m used to. Overall, I thought this was an interesting assignment to begin my UX/UI learning journey.</p><h3><strong>Conclusion</strong></h3><p>In this design challenge I was tasked with improving the Citymapper app as a result of complaints from users from which a pain point was identified. The hassle and time-wasting process of having to buy a variety of different public transport tickets was dampening the Citymapper experience. After ensuring I understood the core problem, I set up an interview process to get a deep clarity on the issue, and gain empathy for the users affected by this issue. Through this, I was able to identify patterns amongst the interviewees responses, and ideate. The ideation stage provided further direction for the task at hand, with the help of the pain point being established. Finally, that allowed me to create a lo-fi prototype with a fitting solution. This challenge pushed me to start thinking from a designer’s point of view and gave me a slight peek into what it means to be working in UI/UX.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebdec986e48e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>