<?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 Maud de Boer on Medium]]></title>
        <description><![CDATA[Stories by Maud de Boer on Medium]]></description>
        <link>https://medium.com/@mauddeboer?source=rss-5a3e2f9d8cc5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*IILkdDVGXUMsW6Pd</url>
            <title>Stories by Maud de Boer on Medium</title>
            <link>https://medium.com/@mauddeboer?source=rss-5a3e2f9d8cc5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:27:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mauddeboer/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[Case study: Integrating voice assistance to the Zoom app]]></title>
            <link>https://medium.com/design-bootcamp/case-study-integrating-voice-assistance-to-the-zoom-app-1d3dd235651d?source=rss-5a3e2f9d8cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d3dd235651d</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Maud de Boer]]></dc:creator>
            <pubDate>Sat, 21 Nov 2020 15:22:42 GMT</pubDate>
            <atom:updated>2020-11-21T15:22:42.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Zoom (logo) + Voice assistance?" src="https://cdn-images-1.medium.com/max/1024/1*iV57gZ1rXxc5tEno7QnBWg.png" /></figure><p>For the fourth and first solo project at the Ironhack bootcamp, we were challenged to clone and incorporate a new feature to an existing app. After some group projects, it felt like an exciting challenge to tackle, mainly because we would learn about UI design.</p><h3><strong>Brief</strong></h3><p>In this two-week design sprint, Ironhack assigned us a random app, combined with a random feature. For this project, I received the following combination:</p><blockquote>“Add a voice-activated feature to Zoom.”</blockquote><h3><strong>Getting to know the user</strong></h3><p>For this UI-heavy project, we were asked to conduct guerrilla research to understand our user and their possible pain points. But first, I wanted better to understand the app and voice activation through secondary research.</p><h4><strong>What is Zoom?</strong></h4><blockquote><a href="https://zoom.us/about">Zoom</a> is a cloud-based video conferencing service you can use to meet with others virtually — either by video or audio-only or both</blockquote><p>Because of the COVID-19 outbreak, Zoom has seen tremendous growth in the past year. Companies, schools, and individuals are widely using it to meet up with others for meetings, classrooms, or to have a chat with one another. During the Bootcamp, we’re also using Zoom as our primary classroom tool.</p><h4><strong>What is voice-activation?</strong></h4><p>Voice activation and voice assistance have gained popularity in the past years, with solutions such as Siri for iPhone, Google Assistant, and Amazon’s Alexa. It’s defined as:</p><blockquote><a href="https://cie-group.com/how-to-av/videos-and-blogs/voice-control">Voice activation or voice control</a> allows the user to activate or control a wide range of home automation and AV devices simply using their voice, as opposed to pressing buttons to use a touchscreen interface device.</blockquote><h4><strong>Guerrilla research</strong></h4><p>With this information in mind, I moved on to the next phase to get to know my user and their pain points. I realized I had a question on top of my mind, which I needed an answer to, which was:</p><blockquote>“Who uses Zoom for mobile? And why?”</blockquote><p>I set up a super short interview and went ahead and interviewed three random Zoom users. The first questions were based on their experience when using Zoom. Interesting insights about past behaviors of using Zoom were:</p><ul><li>Zoom is mostly used from the comfort of home and on a desktop computer or laptop</li><li>Zoom is used both professionally and personally</li><li>Zoom for mobile is only used when the internet connection was bad, or their laptop battery died, and they had to quickly switch from device</li></ul><p>After that, I asked them about their past experiences using a voice activation system or voice assistant. The main findings from this part were:</p><ul><li>Voice activation should be considered as a voice assistant</li><li>User use voice assistance in a private environment</li><li>Interviewees used voice assistance for basic tasks regularly, such as setting a timer or create reminders</li></ul><h3><strong>Brainstorm on possible concepts</strong></h3><p>With this information in mind, I realized I had to think in the most logical way possible. I needed to find out if there is a possibility to use Google Assistant to activate Zoom in any way possible. After a quick test using Google Assistant, I found out I couldn’t.</p><figure><img alt="3 examples which shows that Zoom doesn’t work with Google Assistant yet" src="https://cdn-images-1.medium.com/max/979/1*tueJLHHdEasr4lYBKg7TSg.png" /><figcaption>I tested Google Assistant on an Android phone to see if you can schedule a Zoom meeting and invite someone to a Zoom meeting. It showed me that Google Assistant doesn’t work yet in collaboration with Zoom.</figcaption></figure><p>I felt there was a gap and went straight ahead to do some brainstorming. After using the crazy-8’s method, I defined the strongest concepts and put them out for the test. Besides, I added questions to ask about past behaviors to validate previous research. Eventually, I validated the concepts with ten users.</p><figure><img alt="Research findings from concept testing" src="https://cdn-images-1.medium.com/max/1024/1*h0O66U3OK7xnQDfI-YTeiA.png" /><figcaption>Survey Results for Concept testing</figcaption></figure><p>For this project, I chose to incorporate voice assistance to Zoom Android to:</p><ul><li>Set meetings with contacts,</li><li>Set reminders for Zoom meetings,</li><li>And send out invites to contacts.</li></ul><h3><strong>The user and its problem</strong></h3><p>With the results in mind, I defined the problem statement, hypothesis statement, and jobs to be done.</p><figure><img alt="Problem- and hypothesis statement, and jobs to be done" src="https://cdn-images-1.medium.com/max/1024/1*jyg1AnGLKpDu4gVueAlG5A.png" /></figure><p>And created a user persona to relate to my user.</p><figure><img alt="Thomas Huijzer is the user persona of this project, he’s a tech savvy user, and uses Google Assistant" src="https://cdn-images-1.medium.com/max/1024/1*ejfkQ6vNq3O6D6uEbHg1FA.png" /><figcaption>Meet Thomas, the User Persona</figcaption></figure><h3><strong>Defining the MVP</strong></h3><p>I must admit that I didn’t follow a linear path to defining the MVP for this feature. I used the MOSCOW method to prioritize the points included in this feature.</p><figure><img alt="Feature Prioritization using the MOSCOW method" src="https://cdn-images-1.medium.com/max/1024/1*gGPtBgiZoFeABs1jXfBJHg.png" /><figcaption>Feature Prioritization using the MOSCOW method</figcaption></figure><h3><strong>Lo-fi prototype</strong></h3><p>I was asking myself how this feature could be part of the Zoom app. Here I asked for some help from my cousin, who uses Google Assistant for all sorts of things. I made screenshots of the screens that I had to work with and asked him if this was the right way to approach the concept. After that, I drew some lo-fi screens and did some usability testing with three users of Zoom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRI6j8m24-E8ctEcPwMHJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*wXozU544vgwfE6ZEFChI2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*biLHNdkUy8CTTMd0WcRA1w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kuEwtjvrSoGBHPLgAQv1w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZ0ufdyiFuKgdq1gPYYieA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvnCbP1omT7zkTS-EPnXNA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7iqhc2gCaHxc1iW0SXObvw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nfVDepJ08RRUZ_76WG4nMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2O-sfIHkCZ3J2XGPrr5Pjw.png" /></figure><p>Main findings from usability testing were:</p><ul><li>The screens are self-explanatory, and the flow makes a lot of sense.</li><li>The Google Assistant is mostly used outside of the Zoom app. It makes the most sense to put the feature on the settings page.</li><li>There is a way to change the same settings, but from the Google Assistant’s settings page, but I left it at Zoom for this project’s scope.</li></ul><h3><strong>Hi-fi prototype</strong></h3><p>After creating the lo-fi screens, I realized I didn’t have to do much designing myself. It felt like an excellent opportunity to practice even more with Figma.</p><p>I wanted to become familiar with the UI design of both Zoom and Google assistant, so I studied both of them and tried to recreate a perfect clone. Some of the lessons we had also covered smart animate, and although I didn’t have the time to dive deep into it, I still got last-minute help from my teacher to mimic the dialog between the user and Google Assistant.</p><h4><strong>Usability test results</strong></h4><p>I did a quick round of usability testing with zoom users to get feedback. But soon after, I found out that some parts of the design remained a bit unclear, such as the text bubble that appears on the Zoom app’s home screen. I needed to change some bits. I inserted the feedback, which was:</p><ul><li>The text bubble on the home page was quite confusing. By adding animation, I solved this problem and increased usability.</li><li>At a certain point, if you wanted to move from one screen to the next, you could only click on the link icon. I changed this into making the whole component clickable.</li><li>I added a delay animation to mimic a real dialog between the user and Google Assistant.</li></ul><p>Finally, I asked my testers for their opinion.</p><blockquote>One of the comments I got was that it looks realistic, which felt like a great compliment!</blockquote><p><em>You’ve finally come this far to see the result. </em><strong><em>I hope you enjoy it!</em></strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FH6Wy2Vt4gBwmRcTVHPFR9A%2FMaud-ZOOM-VOICE-ACTIVATION-FEATURE%3Fnode-id%3D307%253A180%26viewport%3D146%252C326%252C0.13284753262996674%26scaling%3Dscale-down&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FH6Wy2Vt4gBwmRcTVHPFR9A%2FMaud-ZOOM-VOICE-ACTIVATION-FEATURE%3Fnode-id%3D307%253A180%26viewport%3D146%252C326%252C0.13284753262996674%26scaling%3Dscale-down&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F34c6bcf2-75a7-481d-8e91-d2057d0e632d%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/3abd911eb8279f1d04663ea85ccb2631/href">https://medium.com/media/3abd911eb8279f1d04663ea85ccb2631/href</a></iframe><h3><strong>KEY LEARNING POINTS</strong></h3><p>In this project, I learned a lot by practicing and just doing. Some of the key learning points I had for this project were:</p><ul><li><strong>Trust the process:</strong> sometimes you have to go with the flow to land precisely at the place you need to be.</li><li><strong>Make more time for testing:</strong> I have the feeling I have been saying this all the time, but making more time to test and gather user insights, will make you a better designer in the long run.</li><li><strong>Don’t pixel push too much:</strong> sometimes I feel the urge to make it incredibly perfect, but I find myself wasting a lot of time on things that are not that important. When you think about the big picture, everything will fall into place and look perfect anyway.</li></ul><p>If you want to get more insight into my process for this project, please feel free to access my <a href="https://www.figma.com/file/H6Wy2Vt4gBwmRcTVHPFR9A/Maud-ZOOM-VOICE-ACTIVATION-FEATURE?node-id=2%3A10">Figma file</a>.</p><h3><strong>After this project…</strong></h3><p>After this project, someone sends me some interesting articles stating that <a href="https://www.cnet.com/news/zoom-is-taking-over-your-alexa-google-assistant-and-portal-displays-next/">Zoom integrates with Alexa and Google Assistant to be available on every smart display</a>.</p><p>And some weeks after that, I found out that, similar to this project, <a href="https://9to5google.com/2020/09/15/google-home-2-28/">Google Home and Google Assistant will enable users to send Google Meet invitations to other individuals</a>.</p><p><em>Thanks for reading! If you’re interested in more stories, that don’t forget to follow me and stay tuned.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d3dd235651d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-integrating-voice-assistance-to-the-zoom-app-1d3dd235651d">Case study: Integrating voice assistance to the Zoom app</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 3 — Redesigning the Tripadvisor app]]></title>
            <link>https://medium.com/@mauddeboer/ironhack-challenge-3-redesigning-the-tripadvisor-app-817320cb3c?source=rss-5a3e2f9d8cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/817320cb3c</guid>
            <dc:creator><![CDATA[Maud de Boer]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 00:11:27 GMT</pubDate>
            <atom:updated>2020-06-30T00:11:27.927Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Challenge 3 — Redesigning the Tripadvisor app</h3><p>For the third challenge of the Ironhack pre-work module, we were asked to redesign a popular trip planning website based on respondents’ main problems when using the application. We had to come up with a scenario, test some applications according to Nielsens’ Heuristic Principles, interview users that fit into the scenario locate pain points of the user, and finally, sketch a prototype for new or improved features.</p><h3>The scenario</h3><p>At first, I had to sketch a scenario based on some simple questions:</p><ul><li>Who is the user?</li><li>What is the destination?</li><li>Why are they using this app?</li></ul><p>In this case, I chose the following:</p><h4>User type: Backpacker (solo traveler) — 18–38 years old.</h4><p>I chose this persona, as it is closest to my heart. I did some solo traveling myself and enjoyed it a lot. In this case, I could also conclude that when you are traveling solo, you have a lot of freedom to do as you choose, while at the same time, you have to work with a budget.</p><p>I could imagine that this persona already booked the flight to a particular destination, and has some list with places that he/she wants to visit. But when you have six months to travel, you do not have a planning set. I assumed that the persona wanted to book excursions when being in a particular country.</p><h4>Location: Machu Picchu, Peru</h4><p>I chose this particular location as I have been traveling in Peru for a couple of months myself. While being in Peru, I also visited Machu Picchu and did this solo. I loved the experience I had in Peru and Machu Picchu, and I found it interesting to see how others would book a trip being in, for example, Amsterdam.</p><h4>Why would this user use a travel app?</h4><p>In this case, the ‘backpacker’ is a very flexible person that lives from day to day without really planning everything on forehand. The user will probably only book a single flight ticket to the country they want to visit, but might not book their return flight simultaneously.</p><p>In this case, I found it essential that the app should contain at least an option to book a hotel, and an opportunity to book an excursion.</p><h3>Usability research</h3><p>The second was usability research using <a href="https://medium.com/jefferson-w3c-collaboration/heuristic-evaluation-understanding-the-biggest-usability-challenges-e3c36f2f584a">Nielsen’s heuristic principles</a>. From the briefing, four travel apps were suggested: Kayak, Skyscanner, Tripadvisor, and Hopper — our task was to apply the principles in our research and choose an app that best fit the target.</p><p>Considering the usability heuristic evaluation, and the chosen scenario, I decided to go with Tripadvisor. Because there is a need to book a hotel/hostel and excursions, Tripadvisor was the best to work with, as other options lack the option to book excursions. Besides, what I liked about the app was the option to ‘create a trip’ and fill in dates. Through this, you have your traveling calendar, and you can add flights, hotels, and excursions to your planning. I can imagine that this would be a fantastic feature to have when you are traveling by yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*NFgxR0A7Ek7Y3VwFE7j4xQ.png" /></figure><h3>User interviews</h3><p>I finally arrived at the stage where I could put my assumptions aside and do user research through a task and an interview. For me, this was the hardest stage, as I am not developing a feature for myself but for someone else — which is very important to remember.</p><p>The task I developed was the following:</p><ul><li>Book a hotel/hostel in Cusco;</li><li>Book an excursion from Cusco to Machu Picchu that best fits your preferences.</li></ul><h3>Main findings</h3><p>First, I asked my interviewees to do the 5 seconds test. Surprisingly, everyone knew what the purpose of the app was. Some users even knew that it was about TripAdvisor.</p><p>Second, I asked the users to perform the task I have set for them. During the task, I watched what they were doing in the app, and I asked them to talk out loud why they were taking specific steps and what they thought of every step along the way. From this, I could locate the main pain points, which were:</p><ul><li>The overall usability of the app was fine, and actually, very clear. But there was a lot of information available through the use of many little elements. Some found it disturbing to receive that much information.</li><li>When looking for a hotel or hostel, the experience was apparent. However, when you want to book an actual room, you will go to the <a href="http://booking.com/">booking.com</a> website. When you take the time to find accommodation, finally, you have to look for it on <a href="http://booking.com/">booking.com</a> again. Why can’t you book it directly from Tripadvisor, or even, get directly directed to a reservation page on <a href="http://booking.com/">booking.com</a>?</li><li>When looking for an experience or excursion, there also was a lot of information. You have no idea where to start looking, as the list is not filtered and contains an overload of experiences that might not fit the users’ preferences.</li></ul><h3>Applying improvements</h3><p>Overall I found the main pain point to be the overload of information. So I took this to the next step through lo-fi prototypes. I still have to get used to drawing so much on paper, but here you go.</p><p>In the end, I decided to simplify the experience for users to remove unnecessary information, make a simple layout, and add an indicator that shows your location in the process. In this case, I chose to design it around the second task, which was to book experiences in the application.</p><p>After drawing low-fi frames, I wanted to move it to mid-fi frames. But unfortunately, due to time constraints, I wasn’t able to make it in time for the deadline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WLH2p6ZL5J7m_4R19rucgA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tektXgIojEXVbP3JxacODw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2smSwT51Km3vAc4luiCxAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBVr-mN25fJyLhkq5o9mEA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sLF31I6NrHdKoRxityg5CQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWJvLZWzYKck8ta2TFLajA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6i3Qli-2nhidINhF0Bh8bQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B9xz7V4WdOujxzrojvL11g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dM4eIm6cZxSpPQVDcJPIw.jpeg" /></figure><h3><strong>Conclusion</strong></h3><p>For starters, I overlooked the amount of time that I had to spend on this exercise, so I had to do it in quite a rush to finish everything on time for the deadline. Postponing tasks is something that I have been doing forever, and it has to stop. It is something I have to work on in the future — hopefully within my Ironhack journey.</p><p>I enjoyed working on the challenge it, but it was by far the most challenging exercise of the whole pre-work. Many new terminologies and methodologies were learned, which was quite overwhelming, but very interesting at the same time.</p><p>In the end, I wished I put a little bit more research into making the application better. In this case, I already went quite deep into making the task so narrow that there was no room to look at other options. Besides, when I did the interviews, I was quite rushed, which might be why I felt the answers were still on the surface. The mantra of this exercise was: “I’m not the user of the product I’m creating and evaluating.” I always find this quite tricky, but I must learn to put myself into the shoes of someone else.</p><p><em>Thanks for reading! If you’d like, you can follow my profile for further updates on my Ironhack journey.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=817320cb3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 2 — Making Wireframes for the Discogs app]]></title>
            <link>https://medium.com/@mauddeboer/ironhack-challenge-2-making-wireframes-for-the-discogs-app-e0f21f6208a8?source=rss-5a3e2f9d8cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0f21f6208a8</guid>
            <dc:creator><![CDATA[Maud de Boer]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 13:31:40 GMT</pubDate>
            <atom:updated>2020-06-30T11:46:32.444Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Challenge 2 — Making Wireframes for the Discogs app</h3><p>For the second challenge in the Ironhack Prework, I was asked to ‘reverse engineer’ an application of my choice and make wireframes of a flow. For this challenge, I chose to work on the Discogs app. Discogs — short for discographies — is known as a website and database where users can find information on released music, both physical and digital. Besides, Discogs is a widely known marketplace to buy and sell music — preferably for music on vinyl.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/373/1*i5QxDbPixPL4FnU_Yf_54w.png" /></figure><h3><strong>User Flow: Buying music from the Discogs Marketplace</strong></h3><p>I am a vinyl collector and music enthusiast to the bone. I use Discogs to discover hidden gems, get updates through communities, and buy vinyl to grow my collection. For the flow, I had one clear goal in mind: to buy music — preferably from my ‘Wantlist.’</p><p>From this point of view, I first wanted to make Lo-Fi prototypes using pen and paper. Ironhack likes the term ‘learning by doing.’ In my case, I want to get more comfortable with this term. I started with rapid prototyping and set a timer of 5 minutes for seven frames.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDsTnDgSeR80fKlJgujfFw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6IBq1qvW9qxJ4K-BwSd-oA.jpeg" /></figure><h3><strong>Which elements were used in the Discogs app?</strong></h3><p>When looking at the overall UI of the application, I could identify some key elements used, which were:</p><ul><li>Icons</li><li>Buttons</li><li>Ratings (stars)</li><li>Indicators</li><li>Search input</li><li>Media player</li></ul><h3><strong>The Wireframes</strong></h3><p>For the challenge, we were instructed to create a minimum of five black and white wireframes. Below you can see side-by-side comparisons of the original screenshots of the user flow next to the wireframes. And to top it off, I made a prototype in InVision to make it interactive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*8Kx_yDnptK7f7CaqQtUt7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*oP-TXD-phOLgoG0I9S4Edw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*S_YViLbE61BNdtIinFOJMQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*l__nQ2rRtq0hx-j28O7gvA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*R6Kfeyo_IbB0BJ-WRo351A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*olegS37EiAj-_ebdpFLwrg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*HMExB_awhqQwxIwpghSTAw.jpeg" /></figure><p><a href="https://invis.io/QSXVG33NCTH#/423296143_Screen_1">Click here to view the project `Prototype Discogs App`</a></p><h3><strong>Conclusion</strong></h3><p>Reverse engineering the Discogs app, and making wireframes, was an exciting experience. One that I actually found very pleasing to execute. I was surprised by how simple the process was when using the right tools, like the Ironhack wireframe kit on Sketch. In the end, tools like this made the challenge easier. My main finding from this exercise was discovering how easy a User Interface is when you take away all the colors and images.</p><p><em>Thanks for reading my article, and don’t forget to follow me if you want to receive any updates on my Ironhack journey. For the music lovers out there — </em><a href="https://www.youtube.com/watch?v=BGp2Kby4xZo"><em>here</em></a><em> is a link to the best song from this album.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0f21f6208a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 1 — Design Thinking and CityMapper]]></title>
            <link>https://medium.com/@mauddeboer/ironhack-challenge-1-design-thinking-and-citymapper-591e04fe3153?source=rss-5a3e2f9d8cc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/591e04fe3153</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[paper-prototyping]]></category>
            <category><![CDATA[citymapper]]></category>
            <dc:creator><![CDATA[Maud de Boer]]></dc:creator>
            <pubDate>Tue, 16 Jun 2020 13:15:55 GMT</pubDate>
            <atom:updated>2020-06-16T13:19:20.468Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Challenge 1 — Design Thinking and CityMapper</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zMGGzHqcrc4brmCpnyDzog.jpeg" /></figure><p>My first ever challenge for Ironhack: A case study for mobile public and private transportation app Citymapper!</p><h4><strong>Short introduction</strong></h4><p>For those who aren’t familiar with the application — CityMapper is a transportation app that gets people from A to B, emphasizing public transportation. The main goal of the application is to solve urban mobility by offering the quickest and cheapest public and private transport to its users.</p><p>For the exercise I had to:</p><ul><li>Define the users,</li><li>Interview 5 possible users,</li><li>Define the problem,</li><li>Ideate solutions;</li><li>And finally, create a paper prototype</li></ul><h4><strong>So what is the problem?</strong></h4><p>Although the current product of CityMapper solves some of the main problems of urban mobility, there is one pain point for many users: the different amount of public transport tickets the users have to purchase.</p><p>Public transport tickets come in paper or plastic cards. Buying different public transport tickets is often necessary to go from point A to B., and the process of purchasing these tickets can be very annoying (queues, vending machines that don’t work, etc.).</p><p>Finally, things like pricing or purchasing the correct ticket can become a real pain when you are abroad.</p><p>The task is to create a feature for this app that solves the pain of having to purchase different public transport tickets by different channels.</p><h4><strong>Emphasize</strong></h4><p>In the first stage, I had to think about for whom I am solving the problem. I chose to hold on to one central aspect, which was to solve users’ issues by not having to purchase tickets through more than one channel. The audience I chose to focus on was students who were also traveling regularly.</p><p>From this point of view, I build my first every user interview guide. In this guide, the questions were based on:</p><ul><li>The previous experiences users had when purchasing tickets for public transportation,</li><li>In which city/country they used a public transportation app,</li><li>If they prepared their itinerary beforehand,</li><li>If the price is essential, and how they calculate their costs,</li><li>And last, which applications they’re currently using and what they (dis)like about this app.</li></ul><p>In the end, I interviewed six different users, from 18 to 30 years old. All users are students and travel a lot within the Netherlands, but to other countries as well.</p><h4><strong>Define</strong></h4><p>It was fascinating to see that those different users have different points of view when it comes to traveling with public transportation, and their expectations regarding purchasing tickets for public transport. But overall, I could find some patterns concerning all users that were interviewed.</p><p>All of the users check their itinerary beforehand and plan how they want to go from A to B. Price was not essential for most users, but prices for long-distance was! In the end, all users want to be there as fast as possible, for the best price.</p><p>All users will only use the vending machines at the stations to purchase public transportation tickets, most of them do not look online for information, but trust the information when they do. They also think vending machines and counters are quite slow, which could be quite irritating when you’re missing a bus/train because of it.</p><p>But everyone concluded that they expected the application to be easy, simple, and fast to use. Next to that is that all users want tickets to be contactless — which could mean something as simple as an online ticket or some kind of card besides a mobile device.</p><blockquote>Disclaimer: people in the Netherlands mostly use a public transportation card, specially designed for Dutch public transportation usage.</blockquote><p>From the user interviews, I could conclude that when it comes to purchasing public transportation tickets, users miss something clear, easy, and fast. And at the same time, they want to know the amount they have to pay for, especially if they are a student and traveling on a small budget.</p><h4><strong>Mindmapping</strong></h4><p>From this problem statement, I started to brainstorm and put ideas on paper. I started mind-mapping, and created four pain-points to build upon, and started to add quotes from the interviews to these points. I indicated the points with a <strong>:)</strong> (positive)<strong> :(</strong> (negative) and<strong> :|</strong> (neutral smiley).</p><ul><li><strong>Cost </strong>— Users want the cheapest ticket linked to the most convenient route.</li><li><strong>Information</strong> — Users want to receive up-to-date information that they can trust.</li><li><strong>Time</strong> — They don’t like waiting in the line for a counter, nor waiting for the vending machines. At the same time, they don’t want to spend too much time finding information online.</li><li><strong>Practicability</strong> — Users prefer something digital because they lose paper tickets easily. Besides, they don’t like physical tickets because of the single-use paper waste.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EP86PNItszccASBwewI_kA.jpeg" /></figure><p>At this stage of the process, I came to the conclusion that this is not so much about actually purchasing a ticket for public transportation, it is about knowing where to purchase and that the user gets the right information on an app/webpage to see the cheapest options. Thus, I came up with the following problem statements:</p><blockquote>“As a user, I want to find the cheapest option that matches my itinerary.”</blockquote><blockquote>“As a user, I want to know which tickets to purchase and where I can do this best.”</blockquote><h4><strong>Ideate</strong></h4><p>Before coming up with ideas to change some things of the app, and ideate on new ideas to add a feature, I wanted to test the usability of CityMapper with my interviewees. After the interview, I asked them if they could test the app and tell me what they like and dislike about the application.</p><p>What came out as likes for the app was the color usage, the different zoom-in zoom-out function whenever you change into a different method of transportation, and real-time updates for when e.g., the bus is coming, but as well whenever there is a delay because of traffic.</p><p>The users found the application overall a little bit overwhelming, as it shows a lot of information. They disliked the fact that they could not see any prices, and where you can best purchase a ticket or buy a ticket online. They did not understand why the app shows how much calories you would burn when you walk. They also found the symbols for the bus/tram/metro/train a little confusing, as it would only show numbers.</p><p>After this, I found out that the application overall needs some changes according to UI. And the application needs a feature for users/tourists to gain information and purchase a ticket for their trip. I decided to start prototyping and split it up in two separate sections.</p><h4><strong>Prototype</strong></h4><p>The first step to make general changes to UX and UI. I started off looking at the home page of the application and the page after that. The images shown below are a little bit unclear, but I wanted to point out some changes I would make to the application, such as:</p><ul><li>Add pricing and option to get information on which tickets to buy and where.</li><li>Remove numbers of busses/trams/metro’s and change them into a general symbol for the bus/train/tram/metro etc. Add numbers of busses/trams/metro’s on the next page.</li><li>Show only one best option and show other recommendations below in a small manner.</li><li>Remove calories of walking and biking routes.</li><li>Change all functions of nearby stations on the home page, and make it one general function.</li><li>Add a ticket information feature on the home page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oc4GIw3a6XT24B3U8bKFdg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TFERm3wpoNXNn_yoW-F59A.jpeg" /></figure><p>The second step was to add a feature for users to purchase tickets online, but also an information page on where to purchase tickets.</p><p>Idea 1: Add feature to home page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bw_ObC4yzpXE37ksprym3w.jpeg" /></figure><p>Idea 2: Add feature when finding an itinerary</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FEG2J5RRMet3_XRYjDu0Uw.jpeg" /></figure><p>From this point, I first started prototyping and drawing different options for the product purchase page. For this, I drew different types of smaller frames, and highlighted what I liked about it, and worked my way around this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*whqc5vMTel9pZO-GUenmLQ.jpeg" /></figure><p>Next was drawing the actual paper prototype. I first drew the feature from the homepage, and after that, the feature from choosing the itinerary. I came to the conclusion that instead of drawing two whole separate prototypes, I could make one that worked for both ideas one and two. Below you can see the final prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aZy3dih98ryskwf4ohD5EQ.jpeg" /><figcaption>Idea 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53lwu5lGs84Nv8T5zOz6NQ.jpeg" /><figcaption>Idea 2</figcaption></figure><h4><strong>In conclusion</strong></h4><p>I really enjoyed working on this challenge, but I must say it got me a little bit out of my comfort zone. What I have learned in the end is not to overthink it too much, and look at the process as one learning curve. Go with the flow is sometimes a bit hard for me, especially when it comes to education. In the end, I made something I might not be 100% proud of, but I’m off to a good start.</p><p>Thanks for reading, and follow me for more updates in the future! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=591e04fe3153" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>