<?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 Marine Prat on Medium]]></title>
        <description><![CDATA[Stories by Marine Prat on Medium]]></description>
        <link>https://medium.com/@mprat.mc?source=rss-b9d86a256c72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CSHDiQD6TidcEjY6m8ObOg.jpeg</url>
            <title>Stories by Marine Prat on Medium</title>
            <link>https://medium.com/@mprat.mc?source=rss-b9d86a256c72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:22:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mprat.mc/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: LibNgo]]></title>
            <link>https://medium.com/design-bootcamp/case-study-libngo-41488fc2200b?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/41488fc2200b</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Tue, 26 Apr 2022 11:46:34 GMT</pubDate>
            <atom:updated>2022-06-03T13:28:38.266Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCvVuL1npqQ-LkVZSLjGyQ.png" /></figure><p><em>In this case study, I will share my process in designing the app for </em><a href="https://www.libngo.fr/"><em>LibNGo</em></a><em>.</em></p><h3>About</h3><p>This my 5th and final project at Ironhack’s UX/UI bootcamp. This project is based on a design thinking process and includes UX and UI design.</p><p>I worked with LibNGo, a french startup based in Bordeaux that has created a platform for physiotherapists to help them find substitutes. They already have an in-house UX team working on the redesign on the website, so I focused on creating a flow for a new app for them as they want to reach more people.</p><p>Team: Individual project</p><p>Role: UX/UI</p><p>Duration: 11 days</p><p>Tools: Figma, Trello, Pen &amp; paper</p><p><em>Hackshow Finalist — Selected among the top 3 projects at Ironhack Paris (Feb 2022 cohort)</em></p><h3>Process</h3><h4>☞ Challenge</h4><p>My brief was to create an app from scratch, and focus on the substitute user flow, and on the main feature: the research of a job offer.</p><p>LibNGo has a <a href="https://www.libngo.fr/">website</a>, which is responsive but the user experience is not ideal on the mobile version, so my task was to redesign it to have it look different, but not to change the colours or confuse the user if they are swapping from one device to another.</p><h4>☞ Desk research</h4><p>I started by looking around on Facebook as LibNGo had told me most physiotherapists used this platform to post job offers and apply to them. It is fair to say that even though Facebook enables people to do a lot of things, it is far from ideal to post jobs: there are dozens of physiotherapists groups, split by city or region, where people constantly post offers. It is confusing, hard to explore, and annoying to mix personal and professional life.</p><p>There are other competitors as well, some on apps (Rempleo, Appines), and some on websites (docndoc, physiorama, remplafrance, etc). They all have a similar purpose: posting ads for doctor substitutes, but not all of them have the same features, and after comparison it appeared that <strong>LibNGo had all the features that the others combined offered</strong>.</p><p>This is important for them and had to be kept on the mobile app.</p><h4>☞ User Research</h4><p>I then did a survey online and had about 65 respondents, and I also interviewed 5 physiotherapists to better understand their needs.</p><p>As expected, they overwhelmingly use Facebook as a job posting platform (<strong>88% of them do</strong>), and all of them are unhappy with that. They are all hoping for a better solution to exist, but the biggest hurdle is the number of ads: they are all on Facebook currently, so it is extremely hard to move away from this platform — even if no one wants to use it..</p><p><strong>100% of resident doctors have looked for substitutes</strong>, so their need is clear; and substitutes are often young graduates eager to work and launch their career, but they don’t have much time to dig through Facebook: they want to search by location, and select their availability. It sounds simple and obvious, but Facebook does not do that and still manages to be the leader.</p><h4>☞ Definition</h4><p>This research is synthesised in Johanna, my user persona: she is a recent physiotherapy graduate looking for job offers, and she needs to find them easily, she wants to filter through all the available ads, because it is currently very frustrating to do so: either dig through Facebook or be lucky enough to have an acquaintance who is hiring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5DvGPOeSCXOkfHk7CIhSAA.png" /><figcaption>Johanna, the user persona</figcaption></figure><h4>☞ Problem</h4><p>Substitutes in liberal health professions need an appropriate and consolidated place to find suitable replacement ads and filter through them because it takes them too much time and effort to sort through all the offers on Facebook, and they may miss some as they are posted in lots of different places.</p><h4>☞ Solution</h4><p>The current website has a big emphasis on the map, it uses a large portion of the screen, and I wanted to keep that in the app not only for continuity, but also because the users confirmed that this is what they wanted and needed. People also want to select their availability easily, and have all the same features as the current website has.</p><h4>☞ Wireframes &amp; Testing</h4><p>After the first drafts of low fi and mid fi, I tested my prototype with substitute physiotherapists, and made lots of changes and improvements. I’ll show you the 3 main ones below.</p><p>1. A step was missing between “apply” and actually applying. An extra screen was needed to add a personalised message: all users wanted to write a message with their application; and to reflect on the fact that you actually want to apply: this prevents errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MTUdvy8yV0DWjetMV-qJaQ.png" /><figcaption>1st change</figcaption></figure><p>2. The personal information screen was probably the hardest for me to design. As it is a lot of text, I found it challenging to make it clear and appealing. The main comment that came through was that it was not clear which information was private and which was public, so I made a clear separation between the two parts. I also removed the “save” button and added an extra step to edit your info, also for error prevention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OP69CjSBVGZ_9eDmjIcl4A.png" /><figcaption>2nd change</figcaption></figure><p>3.Last but not least, I added a button to go back to the map on the search results as it was not clear to users that you could drag the screen down to return to the map. I also added a bold and purple stroke around the selected filters to draw attention to the fact that those filters were applied and having an impact on the search results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K51Q6lQkVbECRs-WhDbP-w.png" /><figcaption>3rd change</figcaption></figure><h4>☞ UI design</h4><p>LibNgo asked me to use their primary colour, “Royal blue”. They also wanted the design to convey their brand attributes (kindness, social justice, facilitation), so I kept all UI elements round, to emphasise this.</p><p>I chose to keep all screens mostly white, to allow for an easy switch to dark mode, but also to avoid overwhelming the user: they already have lots of content to sort through and absorb. I used the LibNGo Royal blue in UI elements to make clear clickable areas and important actions.</p><p>After a desirability test with physiotherapists, the main adjectives that came through were: intuitive, easy to use, clear, and not overwhelming.</p><h4>☞ High fidelity prototype</h4><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%2F9PsDoh17a3sfv9eFxpaxDN%2FPortfolio%3Fnode-id%3D81%253A1885%26viewport%3D241%252C48%252C0.42%26scaling%3Dscale-down%26starting-point-node-id%3D87%253A5656&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2F9PsDoh17a3sfv9eFxpaxDN%2FPortfolio%3Fnode-id%3D81%253A1885%26viewport%3D241%252C48%252C0.42%26scaling%3Dscale-down%26starting-point-node-id%3D87%253A5656&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fbd41beae-8d74-41f7-8b1a-11b783d35145%3Fheight%3D244%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/17d0a67bac88b64884f19ab06a04a039/href">https://medium.com/media/17d0a67bac88b64884f19ab06a04a039/href</a></iframe><p><a href="https://www.figma.com/proto/9PsDoh17a3sfv9eFxpaxDN/Portfolio?node-id=81%3A1885&amp;viewport=241%2C48%2C0.06&amp;scaling=scale-down&amp;starting-point-node-id=87%3A5656">Or click here to open in another window</a></p><h3>Outcomes &amp; Lessons</h3><p>This was a great project to work on, and I am extremely thankful to LibNGo for giving me this challenge, and being so supportive along the way.</p><p>Working alone was a good experience too as it reassured me in my abilities and proved to me that I could handle the process.</p><p>I am looking forward to LibNGo launching their app!</p><p>Thank you for reading me !</p><p>Check out my other case studies<a href="https://medium.com/@mprat.mc"> here</a> 🙋‍♀️ and my <a href="https://www.marineprat.me/">portfolio</a></p><p>Let’s connect on<a href="http://www.linkedin.com/in/marine-prat-89989453"> LinkedIn</a> 🤝</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41488fc2200b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-libngo-41488fc2200b">Case study: LibNgo</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[Case study: Wellness app]]></title>
            <link>https://medium.com/design-bootcamp/case-study-wellness-app-6a52714ec5c1?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a52714ec5c1</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Thu, 31 Mar 2022 17:43:19 GMT</pubDate>
            <atom:updated>2022-04-26T11:47:41.876Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZCL3Gp12FjhZaNlNFvFScg.png" /></figure><p><em>In this case study, I’ll share our process in designing a wellness app MVP.</em></p><h3>About</h3><p>This is the 4th project at Ironhack’s UX/UI bootcamp. This project is based on a design thinking process and includes UX and UI design.</p><p>Our area of research is wellness, and we decided to focus on stress management. We have researched people’s relationships with stress, and we have seen the possibility to create something new in this area — a tool to help people prepare for difficult discussions at work.</p><p>The project is based on an implementation intention strategy; it is a simple way to follow through with our intentions and do what is necessary to attain our desired results.</p><p>Team: <a href="https://medium.com/@julia.toquet">Julia</a> and I<br>Role: UX/UI <br>Duration: 8 days</p><h3>Process</h3><h4>☞ Challenge</h4><p>Develop a digital product for the wellness industry, that makes a user’s relationship with mental, physical, or emotional well-being better. The tool should track the user’s progress and pushes them to commit to a healthier lifestyle.</p><h4>☞ User Research</h4><p>For the survey, we prepared questions about stress reasons and coping mechanisms. We used Lean Survey canvas for it. The primary goal of the survey was to find the pain points and to see the patterns in people’s stress factors. We got 113 responses, and here is one of the most important findings — The 2 main reasons that create stress are : <strong>Work</strong> (68,1%) and <strong>Interpersonal relationships</strong> (37,2%).</p><p>The key findings from the interviews and the survey:</p><ul><li>78,8% of our respondents consider being stressed at least from time to time</li><li>93,7 % said that stress had an impact on their daily life</li><li>People do not consider that they have the tools to manage their stress</li></ul><h4>☞ Desk research</h4><p>We read reports about stress factors and how people were dealing with them, and conducted a competitor analysis to have a better idea of what the market looked like.</p><p>This showed gaps in the market, as well as crowded areas: we could find lots of meditation apps, breathing exercises apps, journaling apps, but they were not often tailored to users, and none addressed how to approach stressful discussions — which was a need our users had.</p><h4>☞ Definition</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QsvBiHl_Eu3T-ZiyV1_doA.png" /><figcaption>User persona</figcaption></figure><p>Her typical journey is coming to work and having her boss giving her a project to do in a too short amount of time, and it creates stress for her. She does not know how to speak with her boss about it and needs help. She feels helpless as she does not have the tools to manage her stress or change the situation.</p><h4>☞ Problem</h4><p>Young professionals need to find a way to quickly reduce their stress at their workplace because it affects them physically and they want to feel better fast so that it does not affect their personal life.</p><h4>☞ Solution</h4><p>Create an app to help people to have discussions at work about sensitive topics:</p><ul><li>Give personalized tips to help prepare and to take a step back</li><li>Give breathing exercises</li></ul><p>For our MVP we chose to focus on a user journey to give personalized tips to Emma.</p><p>We tested our concept with a psychologist, and some users.</p><h4>☞ Userflow</h4><p>The user flow we designed is:</p><p>Open app &gt; Choose your current feeling &gt; Go to personalized communication tips &gt; Choose who you need to talk to &gt; Choose topic of discussion &gt; discover advice &gt; do breathing exercise &gt; close app</p><h4>☞ Moodboard</h4><p>We wanted to balance the stress at work with an uplifting, calm and kind app feeling that would give confidence to users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1mkgUj8IcfOD4FhKQOm6Q.png" /><figcaption>Our moodboard</figcaption></figure><h4>☞ Style guide</h4><p>The main UI colors are: green, pink and yellow. We tried to create a cheerful atmosphere, while staying minimalistic and suitable for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xk1JLDNeqQhQnttDOsq2kQ.png" /><figcaption>Part of our style guide</figcaption></figure><h4>☞ High fidelity screens</h4><p><a href="https://youtu.be/8ImleI7o_kI">Here is a short video</a> of the prototype, and you can play with the prototype below:</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%2FYzMqMWUdbZNifyQS9I5BsI%2FApp-design%3Fnode-id%3D70%253A3630%26viewport%3D242%252C48%252C0.1%26scaling%3Dscale-down%26starting-point-node-id%3D70%253A3634&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FYzMqMWUdbZNifyQS9I5BsI%2FApp-design%3Fnode-id%3D70%253A3630%26viewport%3D242%252C48%252C0.1%26scaling%3Dscale-down%26starting-point-node-id%3D70%253A3634&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fa5564619-5b3c-4ef7-ab87-1e81b1d0fed1%3Fheight%3D400%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/2f49838d0924e31f2b67537f9ed026f8/href">https://medium.com/media/2f49838d0924e31f2b67537f9ed026f8/href</a></iframe><h4>☞ Testing</h4><p>We tested our concept and prototype throughout the project and got valuable feedback at each stage that allowed for incremental enhancements. Each test helped us improve our concept and design, and ensure that it was answering user needs and goals.</p><p>We also conducted a desirability test with our high fidelity prototype, and the main attributes people chose were Accessible, Friendly, and Easy to use, which described accurately what we were trying to achieve.</p><h3>Outcomes &amp; Lessons</h3><p>This was a great challenge to tackle, which allowed us to go through all the design steps of UX and UI.</p><p>As with previous projects, I learnt a lot through all the steps. Testing our prototypes was hugely impactful, and helped us to make it better with every iteration. I would love to have more time to test and continue the improvement, but as we were limited in time and were tasked to only do an MVP, we had to stop at some point!</p><p>Thank you for reading me !</p><p>Check out my other case studies <a href="https://medium.com/@mprat.mc">here</a> 🙋‍♀️ and my <a href="https://www.marineprat.me/">portfolio</a></p><p>Let’s connect on <a href="http://www.linkedin.com/in/marine-prat-89989453">LinkedIn</a> 🤝</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a52714ec5c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-wellness-app-6a52714ec5c1">Case study: Wellness 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[Case study: App redesign]]></title>
            <link>https://medium.com/design-bootcamp/case-study-app-redesign-4f53e9c149ca?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f53e9c149ca</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Wed, 23 Mar 2022 15:24:23 GMT</pubDate>
            <atom:updated>2022-04-26T11:47:54.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tU8uhW3VYJATNvS8kDgU2g.png" /></figure><p><em>In this case study, I will share my process in redesigning Doctolib’s app.</em></p><h3>Overview</h3><p>This is Ironhack’s 3rd project: redesigning a few screens of a well known app.<br>This project is done alone, and in 3 days.</p><p>I chose to redesign Doctolib because I think that the app is pretty good, but that there is some room for improvement.</p><h3>Users &amp; Audience</h3><p>It was a pretty fast project, and only focusing on <a href="https://www.interaction-design.org/literature/topics/ui-design">UI (user interface)</a>, so we did not focus much on UX (user experience), and did not do user research as we did not change any content.</p><p>The users are meant to be the same ones as the original Doctolib app, so it is important to respect the spirit of the app: booking doctors appointment easily, and having lots of information about doctors.</p><h3>Process</h3><p>☞ <strong>Research and analysis</strong></p><p>The first step was to clone 3 screens that I had chosen on the app, to have an idea of what we are dealing with, and see if there are some major issues to fix.</p><p>I chose to recreate: the home page, the search, and the previous bookings page.</p><p>Thanks to this, I was able to identify that Doctolib uses only one font, but in a lot of different sizes, colors, and weights. I also realized that all of their boxes were squares and only some of them had slightly rounded angles.<br><strong>All of that taught me that even though the app’s UI is pretty consistent, there were instances when it was not so consistent.</strong></p><p>The next step for me was to conduct a <a href="https://www.interaction-design.org/literature/topics/heuristic-evaluation#:~:text=Heuristic%20evaluation%20is%20a%20process,usability%20from%20early%20in%20development.">heuristic evaluation</a> of the chosen screens. Here again, the major issues that came up were <strong>consistency</strong>, and <strong>minimalist design</strong>: it was sometimes so minimalist that it made the app loose clarity.</p><p>Finally I did a visual competitors analysis: I looked at the design of similar apps: Qare, Maiia, and Keldoc.<br>This was to gauge what was on the market, what colors and UI they were using, and what they focused on. This helped me to have ideas to differentiate Doctolib, whilst being coherent with the market.</p><p>☞ <strong>Moodboard</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QP8B63NQwM3ZfnKTxnBIfg.png" /><figcaption>My moodboard for Docolib’s redesign</figcaption></figure><p>Based on attributes that I thought fitted Doctolib best, I created a moodboard around: <strong>trust</strong>, <strong>health</strong> and <strong>transparency.</strong></p><p>This helped me choose the colors of my redesign, the font and the style of UI I would use. I chose to use greens a a primary color, and orange as a functional color. I chose Avenir as the font, because it is clear and legible (and the font name also happens to suit quite well the app!)</p><p>My main focus was to make the app very clear, so I wanted lots of consistency, and not too many different elements, that’s why I reduced they different typographies to 3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*prNiZyGHFi-O73ff9pb5Ew.png" /><figcaption>Colors and typography chosen</figcaption></figure><p>☞ <strong>Redesign</strong></p><p>Once the colors and typography were chosen, I ideated on different layouts possible. I did not want to change the layout drastically as I think the existing one was quite clear; the only big change I did was on the homepage: I reduced the amount of information so that everything is on one screen, and no scrolling is necessary. This meant that “favorite doctors” would have their own screen. I also changed the search a bit by adding recommendations, and I changed the search appeared, to provide an easy way out for people who want to leave it and return to the home screen easily.</p><p><a href="https://www.youtube.com/watch?v=uRxbJbqsfY4">Here is a short video</a> to show the prototype, and you can play with the prototype below:</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%2FrM0dztcd1jWhMpeepyAD8Q%2FDoctolib-redesign-backup%3Fnode-id%3D27%253A636%26viewport%3D242%252C48%252C0.26%26scaling%3Dscale-down%26starting-point-node-id%3D36%253A292&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FrM0dztcd1jWhMpeepyAD8Q%2FDoctolib-redesign-backup%3Fnode-id%3D27%253A636%26viewport%3D242%252C48%252C0.26%26scaling%3Dscale-down%26starting-point-node-id%3D36%253A292&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fa519b2f5-ba7b-40c9-857c-0e56e4afb639%3Fheight%3D400%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/9c55305d99609d063185bd80b2679ba8/href">https://medium.com/media/9c55305d99609d063185bd80b2679ba8/href</a></iframe><p>☞ <strong>Style guide</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mG6-nSP2g8AIrMIeG4R_ag.png" /><figcaption>My style guide for Doctolib’s redesign</figcaption></figure><h3>Outcomes &amp; Lessons</h3><p>Thanks to the design critique I was able to refine my design, it is very interesting to hear what other designer think, and what details make a difference.</p><p>This design challenge was a very interesting exercise on two main points:<br>- It was the fist project alone, and I realized that even if it makes me a lot more efficient, fast and organized, it made me less creative as you do not have other people to bounce ideas with. I knew it would be the case, but I never felt more alone than when I had to sit in front of my blank paper and decide how to lay out the first screen.<br>- It was the first entirely UI project, and I loved it. I thoroughly enjoy spending time on Figma, and playing with all the settings and tools that this software offers. Youtube and Figma community are your best friends, and it amazes me the amount of tips and tricks you can learn.</p><p>Thank you for reading me !</p><p>Check out my other case studies <a href="https://medium.com/@mprat.mc">here</a> 🙋‍♀️ and my <a href="https://www.marineprat.me/">portfolio</a></p><p>Let’s connect on <a href="http://www.linkedin.com/in/marine-prat-89989453">LinkedIn</a> 🤝</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f53e9c149ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-app-redesign-4f53e9c149ca">Case study: App redesign</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[Case study: Website re-design]]></title>
            <link>https://medium.com/design-bootcamp/case-study-website-re-design-d3cd6a0f0f18?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3cd6a0f0f18</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Wed, 16 Mar 2022 10:07:31 GMT</pubDate>
            <atom:updated>2022-04-26T11:48:06.425Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EXP30Z13dqNxGwDyefqK8Q.png" /></figure><p><em>In this case study, I will share our process in redesigning </em><a href="https://www.leschineusesdevintage.com/"><em>“Les Chi(n)euses” website</em></a><em>.</em></p><p>This is our 2nd project in Ironhack’s UX/UI bootcamp.</p><p>I tackled it with a wonderful team: Ingrid and <a href="https://medium.com/@martadagna">Marta</a>, and our timeline was 7 days.</p><h3>Overview</h3><p>The challenge was to find a brick and mortar shop with or without a website, and offer to design one for them.</p><p>The shop we selected was “<a href="https://www.leschineusesdevintage.com/">Les Chi(n)euses</a>”, a vintage furniture shop. They already had a website, but one that could be improved.</p><p>Dominique, one of the shop owners, was nice enough to give us an hour of her time to interview her, so that we could have insights in her industry and shop.</p><p><strong>The aim of this project was to create a high fidelity prototype of a buying flow.</strong></p><h3>Users &amp; Audience</h3><p>We got to understand who were the shop customers thanks to our interview with Dominique, but also with some research on general trends and user interviews.</p><p>Customers tend to be between 28 and 40 years old, eco-aware, and in search for unique items with a story. They also preferred vintage furniture to new furniture as they associated it with a higher quality, and better materials.</p><p>We created a <a href="https://en.wikipedia.org/wiki/Persona_(user_experience)">user persona</a> in order to have a clear audience, and pinpoint their goals, needs, motivations and frustrations.</p><p>Meet Andrea, our user persona:<br>Their goal is to look for and buy unique vintage furniture online at a relatively affordable price.<br>Their needs are: to easily find all the information he needs, and to know the story behind the items.<br>Their motivations are: to treasure hunt to find the best vintage pieces, and to have an eco-friendly impact when buying furniture.<br>Their frustrations are: that many items online turn out to not be available at the shop, and that it is hard to trust vintage shops online</p><h3>Process</h3><p>☞ To begin with, we <strong>listed all of our doubts, assumptions and certainties</strong> about the subject, so that we would know where we stand. Then, we did some research online and had a few interviews, including the one with the shop stakeholder, to answer our doubts, and confirm our assumptions and certainties.</p><p>☞ Then, we did a <strong>business analysis and competitor analysis</strong> to see what other shops were doing, what features they had on their websites, how their websites looked, what was their value proposition, etc.<br>We found that Les Chi(n)euses has a good positioning, and is selling in a niche: furniture from 1940 to 1970 at a very affordable price.<br>We also found that most websites had a review section and a wishlist, while Les Chi(n)euses hadn’t. However, Les Chi(n)euses have a clear value proposition and show featured items on their website, which is very positive as most competitors do too.</p><p>☞ We also recreated the <a href="https://en.wikipedia.org/wiki/Sitemaps"><strong>sitemap</strong></a> as a schematic, and found that it was quite complex, with many pages accessible from the homepage only.</p><p>☞ Finally, we conducted a <a href="https://www.interaction-design.org/literature/topics/heuristic-evaluation#:~:text=Heuristic%20evaluation%20is%20a%20process,usability%20from%20early%20in%20development."><strong>heuristic evaluation</strong></a>, or <em>usability inspection,</em> in order to see what usability issues the current website had. <br>We found that the website had issues with 8 out of 10 of the heuristic principles, which means that it is not straightforward and easy for people to use.</p><blockquote>☞ <strong>Main Problem</strong></blockquote><blockquote>All the research and analysis done above helped us to add traits to our user persona, and to define what was the problem of the current website.</blockquote><blockquote>The main issue of the current website is that it did not convert enough sales: most online sales were actually made on an online marketplace. This showed that vintage furniture <strong>can</strong> be bought online, so we had to understand why the current website was not working as it should in terms of sales.</blockquote><p>☞ Once we had a clear idea of the problem to tackle, we started to <strong>ideate</strong> and create <strong>low-fi prototypes</strong> as it is easier to discuss ideas and iterate on paper.</p><p>☞ We the identified the main building blocks of our design and created them in <a href="https://mockitt.wondershare.com/prototyping/mid-fidelity-prototype.html">mid-fidelity</a> on Figma. We then put together our pages and prototype, and continued to iterate throughout.</p><p>☞ Once the first version of our mi-fi prototype was ready, we started to conduct user tests. With each test done, we received feedback and insights and iterated our prototype, until we were satisfied that users found it easy to use, understood everything, and no more issues came up. <br>This took us 7 rounds of testing and iteration: we could have continued but we were on a timeline, and “not having issues” was our aim: we did not have time to make everything perfect <em>(and perfect does not exist)</em>.</p><p>☞ All of this leads us to creating the hi-fi version!<br>To do this, we first have to create a mood board, pick colors, and typefaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W2BfbbqxYH9n5kFyFAldSQ.png" /><figcaption>Our mood board</figcaption></figure><p>We chose to use two fonts: one for titles, and the other one for the rest; and picked a blue/green for our primary color, a rusty orange as a functional color (mainly to indicate errors), and a dark brown and creamy white as our neutral colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QdjCTEv2Qvp8TtstfaxF_g.png" /><figcaption>The colors we chose</figcaption></figure><p>And now the hi-fi version 🥁🥁🥁</p><p>We added all fonts and colors, made shapes fit, corrected alignment, and made sure the look and feel was reflecting our mood board and intention.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyRodwSWiO7k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyRodwSWiO7k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyRodwSWiO7k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f9c19d70ba1dcf62ee85784fd89c3f1f/href">https://medium.com/media/f9c19d70ba1dcf62ee85784fd89c3f1f/href</a></iframe><p>See below the before and after versions of Les Chi(n)euses website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*3zWl6gHmpA-Z0qFUKggcQA.gif" /><figcaption>Current website vs our Hi-fi prototype</figcaption></figure><h3>Outcomes &amp; Lessons</h3><p>I have learnt a lot from my teammates in terms of open communication and transparency. We were very honest with each other from the start, and kept this going until after the project, which I think made the experience very enjoyable for everyone as we always knew where everyone stood.</p><p>I always thought that I was a quite straightforward an open person, but working with Ingrid and Marta showed me a whole new world, and I can’t stress this enough but I really loved it and feel like I grew a lot from this.</p><p>This was our first team project using Figma, and this has taught me that organization is key: keep your files clean, and rename everything from the get-go. This can be a life savior down the line.</p><p>Thank you for reading me !</p><p>Check out my other case studies <a href="https://medium.com/@mprat.mc">here</a> 🙋‍♀️ and my <a href="https://www.marineprat.me/">portfolio</a></p><p>Let’s connect on <a href="http://www.linkedin.com/in/marine-prat-89989453">LinkedIn</a> 🤝</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3cd6a0f0f18" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-website-re-design-d3cd6a0f0f18">Case study: Website re-design</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[Case study: Culture & Heritage]]></title>
            <link>https://medium.com/design-bootcamp/case-study-culture-heritage-9e7df067da19?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e7df067da19</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Thu, 03 Mar 2022 08:25:00 GMT</pubDate>
            <atom:updated>2022-04-26T11:48:18.140Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gI-FDztJLmCtjcmCuOOo0Q.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@charlotte-may?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Charlotte May</a> from <a href="https://www.pexels.com/photo/a-part-of-the-interior-of-metropolitan-museum-5825359/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p><em>1st project in Ironhack’s UX/UI bootcamp</em></p><h4>Objectives:</h4><p>Our goals for this UX/UI case study were:<br>1. Find out how to make museums and other public institutions more accessible to people<br>2. Understand museum users and find out their main pain points<br>3. Design a low-fi prototype of our solution<br>4. Iterate until we can validate the design</p><h4>Why did we focus on this?</h4><p>The brief came from Ironhack’s UX/UI bootcamp:</p><blockquote>How might we help museums and other public institutions fulfilling their mission of preserving cultural heritage while making it more accessible to a wider audience?</blockquote><p>After interviewing 5 people, it became clear that the <em>museums and other public institutions</em> experience could benefit from an update.</p><p>Our thought process was: <strong>if we can bring more people into museums and other public institutions, then the cultural heritage will be preserved</strong> because people will know about it, and the knowledge will be passed on.</p><h4>Users &amp; Audience</h4><p>Our initial assumption is that the proposed solution should ultimately be for people who visit museums, or other institutions, or for people who want to visit those places.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*tlMV4RRC5gXZYOepwFfHIQ.png" /><figcaption>Design by <a href="https://vijayverma.co/">Realvjy</a></figcaption></figure><h4>Scope &amp; Constraints</h4><p>The timeline was seven days, and we were working in a team of three. The final deliverable was a low-fi prototype.</p><p>Because of the short timeline, our primary research only consisted of 5 interviews, and we kept our prototype low-fi to allow for fast iterations.</p><h4>Process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oq95wWd-n-HZ4L26NXW04w.png" /><figcaption>Lots to be done in a week!</figcaption></figure><p>We followed a user centered process, and concentrated on secondary and primary research to find out pain points and design opportunities in order to find a solution for the problem at hand.</p><p><strong><em>☞ Discover</em></strong></p><p>We interviewed five people, and gathered all our data in a miro board:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SMCn4IqiWdxyL8nkCk2sBA.png" /><figcaption>Our affinity diagram on <a href="https://miro.com/">Miro</a>. In green: design opportunities; in purple and red: pain points highlighted in secondary and primary research; in blue and orange: other insights from secondary and primary research</figcaption></figure><p>Putting all our data on sticky notes and assembling them in affinity groups really helped us make sense of the data and see trends emerge.</p><p>To create groups, we started by putting together insights that felt like they were about the same subject. This is of course very subjective, but we did that as a group, which helped to balance the subjectivity. Once small groups were made, we named them, and placed them into bigger groups.</p><p>For instance, the group with insights “before the visit” has 6 sub-groups which describe different aspects of preparing a visit of a museum or cultural institution.</p><p>The 4 main groups are: “meaning of culture”, “before the visit”, “during the visit”, “after the visit”.</p><p>This helped us see Junior come to life, as his traits became quite clear once the sticky note groups were made:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EG6DoIzFOGLktmjsKOj0Iw.png" /><figcaption>Our simplified primary persona: Junior</figcaption></figure><p>Junior’s main traits:<br><strong>❖ Goal:</strong> having interesting activities during his free time<br><strong>❖ Motivation:</strong> going to museums teaches him about culture and history<br><strong>❖ Need:</strong> find information quickly and easily about the museum details<br><strong>❖ Frustration:</strong> it is sometimes hard to find the information about places</p><p>With this guy in our heads, we can now map out his journey from finding out about an exhibition until going to the museum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCwCYiLQdVhwwjYZTPQJ-Q.png" /><figcaption>Junior’s current experience in going to the museum, made on <a href="https://miro.com/">miro</a></figcaption></figure><p><strong><em>☞ Define</em></strong></p><p>And now, time for the <strong>problem statement.<br></strong>This is the <em>Define</em> stage, and the next step is to find solutions!</p><p>After looking at all of the data gathered and the analysis we created, we focused on the <strong>first pain point our user encounters: the lack of information which leads to him missing the event he wanted to go to.</strong></p><p>This first issue in Junior’s journey inspired the problem statement we defined:</p><blockquote>Students in higher education who want to go museums need a way to find all the information about museums easily because having multiple places to access the information prevents them from having timely information and they miss events.</blockquote><p>In short, we need to give <strong>personalized </strong>and <strong>timely</strong> information.</p><p><strong><em>☞ Develop</em></strong></p><p>Once we had defined the problem statement, we started to ideate. We did a mind map, and then a round of “worst &amp; best ideas” followed by a round robin.</p><p>With this we came up with a few ideas, which we voted on to prioritize and create a user flow.</p><p>The happy path we designed is from opening the app until a ticket is booked.</p><p><strong><em>☞ Deliver</em></strong></p><p>Once the user flow created and clear in our minds, we sketched the low-fi prototype in order to have our users test it.</p><p>We asked a few people who fitted our primary persona to look at the paper screens and mimic their use of the “app”. We asked them to book a ticket, and they clicked on the buttons they thought would lead them there. Our process was more of an observational one, and once the observations were made, we asked questions about why and how they made their choices.</p><p>After a few tests we improved on the layout and the labels to make the screens more understandable.</p><p>The aim of the user flow is to book a ticket on the app. Our focus was to provide the users with personalized information, and with the option to receive notifications so that the information is received in a timely manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3JQvXgOQv2Yp6XKdXW0HpQ.png" /><figcaption>Click on the image to see in more detail</figcaption></figure><h4>Takeaways</h4><p>As this is the first bootcamp project, it ended once the low-fi prototypes were finished and tested.</p><p>I learnt a lot during this first Ironhack project, mainly to <strong>trust the process</strong>, and how to apply best practices.</p><p>On my next projects, I would like to learn to distance myself more from trying to find a solution; it is probably only natural to think of solutions as soon as you read the brief, but I definitely learnt that you need to go through the process first.</p><p>Thank you for reading me !</p><p>Check out my other case studies <a href="https://medium.com/@mprat.mc">here</a> 🙋‍♀️ and my <a href="https://www.marineprat.me/">portfolio</a></p><p>Let’s connect on <a href="http://www.linkedin.com/in/marine-prat-89989453">LinkedIn</a> 🤝</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e7df067da19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-culture-heritage-9e7df067da19">Case study: Culture &amp; Heritage</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 2: Wireframing]]></title>
            <link>https://medium.com/@mprat.mc/ironhack-challenge-2-wireframing-ea63c1cca8e7?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea63c1cca8e7</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Tue, 01 Feb 2022 15:57:03 GMT</pubDate>
            <atom:updated>2022-04-05T15:12:15.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UL35X2CyHVbg0c8JbAC7zA.png" /><figcaption>Source: <a href="https://www.duotonesports.com/">Duotone</a></figcaption></figure><h3>Ironhack Challenge 2 — Wireframing</h3><p>For this 2nd pre-work Ironhack challenge, I’ll try my hand at wireframing. <br>I’ve chosen the app Duotone, they have found a way to convey very clearly the information they want to get across, and the UI is completely intuitive which makes it very easy to use.</p><p><a href="https://www.duotonesports.com/">Duotone</a> sells kitesurfing equipment, and they have created an <a href="https://www.duotonesports.com/kiteboarding/academy-app/">app</a> to teach tricks with clear step by step videos and text explanations.<br>There are more than 200 trick lessons, and fitness training, with all the videos shot in 4K and developed with kitesurfing professionals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MvmxNzHdnNiz-8DdVG9GA.png" /><figcaption><a href="https://www.duotonesports.com/kiteboarding/academy-app/">Duotone app</a> screenshots</figcaption></figure><p>The tricks are divided into a few categories, as you can see in the 2nd screen. Once you select a category, you can explore all the tricks within that category. In each lesson, you can see a step by step video, and text which goes over those steps.</p><blockquote>Home -&gt; Lesson categories -&gt; Lessons within selected category -&gt; Lesson selected which contains a 4K video, written step by step explanations, votes and discussions.</blockquote><p>The flow I’ve chosen to explore is from the home page until the “pop” lesson: you need to click on “Lessons” in the bottom menu, then on the “Hooked” category of lessons, and finally click on the “pop” lesson which then goes over 2 pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnlU7E5AuslYW-NTi0RnUg.png" /><figcaption>Wireframes I have designed with Figma</figcaption></figure><p>You can see the prototype in Figma <a href="https://www.figma.com/proto/HDAYHwRzJF168uW7yw48Md/Ironhack---Challenge-2%3A-Wireframing?page-id=101%3A257&amp;node-id=101%3A258&amp;viewport=241%2C48%2C0.36&amp;scaling=scale-down&amp;starting-point-node-id=101%3A258"><strong>here</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6RbwU9bBntEvwAv7gc7RA.jpeg" /><figcaption>Source: <a href="https://www.duotonesports.com/">Duotone</a></figcaption></figure><p>I’ve enjoyed creating these wireframes on Figma, as I have learnt a lot on the process, and I got to watch new tricks, which is always a plus!</p><p>Creating the prototype was very interesting too, as it shows the flaws on your wireframes, and you see all the little things you need to choose and fix.</p><p><em>Thank you for reading me!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea63c1cca8e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 1 — Citymapper]]></title>
            <link>https://medium.com/design-bootcamp/ironhack-challenge-1-citymapper-90cca91649db?source=rss-b9d86a256c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/90cca91649db</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Marine Prat]]></dc:creator>
            <pubDate>Mon, 24 Jan 2022 12:21:18 GMT</pubDate>
            <atom:updated>2022-04-05T15:12:41.778Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Challenge 1 — Citymapper</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*p0dHM6R46X6GY0EfhptW1g.png" /><figcaption>Image source: Citymapper</figcaption></figure><p>In this first UX/UI Ironhack bootcamp pre-work challenge, I will look at Citymapper, and try to improve it by adding a feature.<br>To do this, I have interviewed 5 people who use the app to travel to find out their main pain points.</p><p>Citymapper is a public transit app that enables users to find the best route in one of the +100 cities available on the app, both online and offline. The app will offer a few different options for the transport type, and for the route to take; it lets you know the time required, and if it is a paid route it will tell you the cost. But it won’t let you book the tickets directly on the app.</p><h4>1. Empathize, 2.Define, 3.Ideate, 4.Prototype</h4><ol><li>Interviews showed that there are a couple points that could be improved:<br>- The price of the route is indicated, but there is no way to purchase tickets.<br>- Public transport in most cities requires you to purchase a card, or paper tickets, which are easily lost.<br>- Language and technology barrier make purchasing tickets or cards at machines a hassle. <br>- Queues at vending machines are often discouraging.</li></ol><p>2. I’ll focus on solving what seems to be the biggest issue: <strong>buying tickets directly on the app, thus saving the hassle of using foreign ticket machines.</strong></p><p>3. After some brainstorming, and a few (bad) ideas, what I think could be a solution is offering the option to pay for public transport directly with your smartphone using NFC: you’d have to purchase the tickets corresponding to your route on the app, and then <em>voilà!</em> You only need to tap your phone when taking the bus, tube or bike. <br><em>This is assuming most buses, tubes and public bikes accept contactless card payments, thus NFC phone payment. <br></em><strong>With this, you’d only need to purchase exactly what you need, and won’t need tickets or cards: you’d only need your smartphone to have a wallet enabling you to pay with your phone. </strong><br>Citymapper will download a “credit card” in your wallet, and once you purchased credit on citymapper to pay for the transport, it will go on this card, which makes it easy to pay. You’ll also receive a QR code in case the NFC payment is not available.</p><p>4. Here’s the prototyped solution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*KVyV9C49CTW8vptPzZPLWw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*FCELR6MfW-PtgllYZatGTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*uSO7VkRrnLquKqj5D3Xp1g.jpeg" /><figcaption>My paper drawn prototypes</figcaption></figure><p>This first Ironhack challenge was very interesting, and gave me my first insight in what UX really is. I’m looking forward to learning more!</p><p><em>Thank you for reading me!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90cca91649db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ironhack-challenge-1-citymapper-90cca91649db">Ironhack Challenge 1 — Citymapper</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>
    </channel>
</rss>