<?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 Anaelle Damien on Medium]]></title>
        <description><![CDATA[Stories by Anaelle Damien on Medium]]></description>
        <link>https://medium.com/@anaelle.damien?source=rss-87b74a9793fe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7PDJi5XI_dEx73dt</url>
            <title>Stories by Anaelle Damien on Medium</title>
            <link>https://medium.com/@anaelle.damien?source=rss-87b74a9793fe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:53:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anaelle.damien/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[Well-being challenge : Mona]]></title>
            <link>https://medium.com/@anaelle.damien/well-being-challenge-mona-5e2b70aef4f?source=rss-87b74a9793fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e2b70aef4f</guid>
            <category><![CDATA[periods]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[periods-problem]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[menstrual-cycle]]></category>
            <dc:creator><![CDATA[Anaelle Damien]]></dc:creator>
            <pubDate>Mon, 15 May 2023 14:40:20 GMT</pubDate>
            <atom:updated>2023-05-15T14:40:20.981Z</atom:updated>
            <content:encoded><![CDATA[<h3>Well-being challenge : Mona</h3><p><strong>Hello and welcome !</strong></p><p>I’ll be presenting you our 4th project at Ironhack that I realised in 2 weeks with my lovely teammate <strong>Luisa</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*earX7xY_Hr0TCPTFUPHvLw.png" /></figure><h3>Brief</h3><p>The challenge we faced on that project was Creating a <strong>disruptive health app</strong> for the “Daily Health Conference” to implement in their new set of digital mobile apps. The app needs to be<strong> motivating</strong> for their user to adopt new heath-improving routines. In order to do so, they’ll need:</p><ul><li>To be able to manage their progress</li><li>Have a control over their personal data.</li></ul><p>In order to do so, we’ll need:</p><ul><li>A focus on one aspect of wellness</li><li>User profile and goals</li><li>A main User flow</li><li>A UXR strategy</li><li>Account management</li><li>Consent to use Data from user</li></ul><p>The specific wellness focus we chose is the menstrual cycle.</p><h3>A market overview</h3><p>For us to start well on our project we needed to look further into already existing apps and what might be less exploited on the market.</p><p>To do so, we chose mutltiple apps rearanging them in a table and picking at things that were present or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F87DPZ-joAeTJXfiqoE_aQ.png" /></figure><p>What we can see is that there are very few apps that tackle problems such as :</p><ul><li>Mood, symptoms and activity prediction</li><li>Personal goal</li><li>Achievements</li><li>Pain and flow strenght prediction</li></ul><p>This already gave us a little idea of what was the space we could take in this industry.</p><h3>Quantitative/Qualitative researches</h3><p>Next step for us was to get some insights on what are the problems that real life people are facing.</p><p>The first phase consisted in building a form with questions around people’s cycle in order to get as much data as possible on our subject. We ended up with <strong>82 responses</strong> on our form by distributing it on social medias and any groups we have on discord and other apps. Since this subject is touching such a broad spectre of people, we didn’t have to filter the groups we sent the form to.</p><p>What we got from it:</p><ul><li>Most people experience<strong> PMS</strong></li><li>In total only <strong>48%</strong> of people<strong> can alleviate</strong> at least often <strong>the pain</strong> from their cycle</li><li>Only <strong>25%</strong> of people are able to <strong>take advantage of their cycle</strong></li><li>Roughly <strong>51%</strong> of people would be<strong> interested to form new habits</strong> around their <strong>cycle</strong>.</li></ul><p>After gathering all of those informations, we wondered :</p><blockquote><strong><em>“Why aren’t people actually forming new habits around their cycle?”</em></strong></blockquote><p>To answer this question, we interviewed 5 people. Here are some quotes that brought us some elements of answer</p><blockquote><strong>“[when on my period] I can’t really go out much, it’s inconvenient at work”</strong>-<em>User4</em></blockquote><blockquote><strong>“I don’t have much knowledge on my cycle” </strong><em>— User3</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-KfkOcxSXqVTlcRQAC0Sg.png" /></figure><p>Receiving those feedbacks, we wondered something else :</p><blockquote><strong><em>“What would be their motivation to take up new habits?”</em></strong></blockquote><p>Here is what we gathered:</p><blockquote><strong>“I stick with habits when it works”</strong><em>- User4</em></blockquote><blockquote><strong>“It didn’t work so i kind of gave up”</strong><em>- User1</em></blockquote><blockquote><strong>“I would need to see the need for it to take a new habit”</strong><em>- User3</em></blockquote><p>The conclusion we drew from all of this is that people might not create habits based on their cycle because either they think it’s normal to suffer during their period or they might not be aware of what their cycles holds.</p><h3>Persona</h3><p>We now had a sense of who would be our <strong>main user</strong>, how they would behave and what would be their goals and pain points.</p><p>This is how we created <strong>Restless Regular Amy</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVmIH_o8r3e6KwTNZ71ZcQ.png" /></figure><p>Let’s take a little peak at her <strong>Goals</strong>:</p><ul><li>Not being inconvenienced by her period</li><li>Alleviate the pain of her cycle</li><li>Learn about her cycle</li></ul><p>And now her <strong>frustrations</strong>:</p><ul><li>Has to adjust her life around her period</li><li>Too busy to research infos about her cycle</li><li>Doesn’t know if a solution is going to work.</li></ul><h3>User journey map</h3><p>Based on her story,<strong> behavior</strong> and <strong>personnality</strong> we were now able to decide on a <strong>journey</strong> that would represent well what areas we could help her on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UYCUwBiu2NZNOcOcUcdjYQ.png" /></figure><p>The story of her <strong>journey is</strong>:</p><blockquote>“Amy plans on going to a concert with friends but she then realises that she will get her period at the exact time of the concert. She tries to find infos in order to try and minimise the symptoms by acting beforehand but she can’t find any valuable ones and just realises she will have to use pain killers instead.”</blockquote><p>Based on all of that, we decided on mutliple <strong>How might we statements</strong>:</p><ul><li>HMW preserve her initial excitement?</li><li>HMW help her get to a point where having her periods is not a big deal?</li><li>HMW help her access reputable informations about her cycle?</li><li>HMW help her find solutions?</li><li>HMW help her not get overwhelmed by all the infos out there?</li><li>HMW help her relieve her pain?</li></ul><h3>Probem statement</h3><p>Looking at Amy’s behavior we then found the following statement to be the one that will lead our project:</p><blockquote>People with menstrual cycles need to find a way to attune the physical, dietary and recreative habits they want to their cycles because they are regularly inconvenienced by the symptoms and the overload of questionable and differing informations(internet, close ones etc…) on this subject leads them to drop their researches and stay in pain.</blockquote><h3>MoSCoW and MVP statement</h3><p>As usual, after finding what the central problem is, we needed to decide on what our <strong>minimum viable product</strong> would be. In order to do so, we used the famous <strong>MoSCoW method</strong> which determined what must, should and could be in our app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQp80jp6Jwclxgr2idoxbQ.png" /></figure><p>Deciding on those features, we were able to determine our <strong>MVP statement</strong>:</p><blockquote>At the bare minimum, the goal of our app is to help the user track their cycle while receiving information specific to both the point in their cycle and the goals they choose.<br>It will require a graph to show the user’s progression, a profile setting with personal questions such as what concerns do they have for their cycle and areas they want to improve, ways to choose which data they want to share and a gamification of the app for motivation purposes.<br>By creating those features we will ensure that the user can create habits they will stick to and find solutions that are relevant to them for their cycles while receiving positive feedbacks and ideas during the process.</blockquote><h3>Lo-fidelity</h3><p>You can have a <strong>glimpse</strong> here of what the first steps of wireframing/ prototyping look like before iterating and changing up some things in the Mid and High-fi prototypes. As you can see bellow, we would for the first use integrate a <strong>questionnaire</strong> in order for us to get better <strong>recommandations for our users</strong>. However, this questionnaire would still be present in the actual app but won’t be shown in order for the final prototype to be coherent with Amy’s journey who would already have her infos logged in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s7vBMqsKTW88NWu7gEmtbg.png" /><figcaption>In-app questionnaire</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XUrzCKxWRPZVoMJSVBz22w.png" /><figcaption>Lo-fi pages</figcaption></figure><h3>Amy’s Userflow</h3><p>Thanks to the<strong> Lo-fi prototyping </strong>we had a general idea of the feel of our app, nonetheless, it is very important to keep in mind our actual typical user: Amy. To do so we needed to <strong>put ourselves in her shoes</strong> and imagine which steps she would go through. This is where the userflow will be useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9klZm0QH74GYx1RT4XXVrQ.png" /></figure><h3>Mid-fidelity</h3><p>We made a few improvments from the lo-fi to the mid-fi, stylising a little more our design, adding features, changing some other etc…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kcQxVSsAQ9qo9tI7CEHCRQ.png" /></figure><p>But those were not our final changes yet…</p><h3>Visual competitive analysis</h3><p>Entering in the styling part of our prototype, we first wanted to look at how our<strong> competitors </strong>did the UI design of their apps. Looking at the good and the bad gave us a better understanding on how to finish up our own app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNUJevU8lCwI-rDBrUAiWg.png" /><figcaption>Visual competitive analysis including Flo, Clue and Clover</figcaption></figure><h3>Moodboard and style tile</h3><p>Given all those informations we started to find which words we wanted to <strong>represent</strong> our app. After choosing the words we liked, we assembled images that gave that feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7C9sdJD9GL8LxiTaLV5Pw.png" /><figcaption>Moodboard/Attributes</figcaption></figure><p>To make sure that what we wanted to showcase came across well, we <strong>tested our moodboard</strong> with other teams working on other projects. Overall it was well received and this was our greenlight to start crafting our <strong>style tile</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mPjXKL3p9S3zl3SMi4bJdw.png" /><figcaption>Style tile</figcaption></figure><p>We chose a spectre of colors that were very close to eachother for a cohesive feel, making sure in the final design that they didn’t bother anyone by <strong>accessibility testing</strong> the combos of each pages. We also chose the <strong>Century Goth</strong> font because it is a font that is easily readable by <strong>dyslexic people</strong>.</p><h3>Hi-fidelity</h3><p>Finaly, here is our final prototype.</p><p>Mona is an application that allows you to start out new habits based on your menstrual cycle. It shows you which mood you’ll be in in the following days and helps you by suggesting new habits that worked for other users in the same situation as you are. Thanks to cute animations and graphs you’ll be able to track your progresses.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2F8a8dfac18fa04509a1ff505333d1a10c&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2F8a8dfac18fa04509a1ff505333d1a10c&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2F8a8dfac18fa04509a1ff505333d1a10c-00001.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="1920" height="1440" frameborder="0" scrolling="no"><a href="https://medium.com/media/35675c1da3db4f339319f0a4fe78ae59/href">https://medium.com/media/35675c1da3db4f339319f0a4fe78ae59/href</a></iframe><p>Test it <a href="https://www.figma.com/proto/EO0AXMcgW3gRMDsGgfYrBL/Ana%C3%ABlle-%26-Luisa?page-id=116%3A21&amp;type=design&amp;node-id=1927-41235&amp;viewport=1390%2C-626%2C0.19&amp;scaling=scale-down&amp;starting-point-node-id=1638%3A37422&amp;show-proto-sidebar=1"><strong>Here</strong></a> !</p><p><strong>Thank you so much</strong> for reading through this case study. It was by far the most challenging one but also the one <strong>I’m the most proud of</strong> so far. Working with<strong> Luisa </strong>was amazing and she challenged me on taking time to be more thoughtfull while designing and be less in a rush and I thank her very much for that.</p><p><strong>I’ll see you for the next and final case study of my bootcamp at Ironhack on the next article !</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e2b70aef4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge: Redesigning the Twitch app]]></title>
            <link>https://medium.com/@anaelle.damien/challenge-redesigning-the-twitch-app-563538f1a21c?source=rss-87b74a9793fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/563538f1a21c</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[twitch]]></category>
            <dc:creator><![CDATA[Anaelle Damien]]></dc:creator>
            <pubDate>Sun, 30 Apr 2023 18:39:46 GMT</pubDate>
            <atom:updated>2023-04-30T18:39:46.957Z</atom:updated>
            <content:encoded><![CDATA[<p>Our challenge for this case was to <strong>redesign an app</strong>. The app we chose to redesign was <strong>Twitch</strong>. In this instance we only used UI, of course for an actual full rebranding of an app, we would need to use UX, but the idea of this challenge was to practice our <strong>UI skills</strong>.</p><p>Shoutout to <strong>Di’andre</strong> for being my amazing teammate on this 3 days project.</p><h3><strong>How it started</strong></h3><p>Twitch is an app that I know and use fairly often. I already had some thoughs on what worked in my opinion and what didn’t on this app. Being that we didn’t conduct any UXR interviews, we would need to base our design on those assumptions. The idea was for us to redesign 4 screens that were following each other in the user journey on the app.</p><h3>Cloning screens to understand them</h3><p>In order to better understand functions from the actual application, we started by cloning the 4 screens we intended to work on. You might ask yourself at this point:</p><blockquote>“What are those four screens ? and what is the chosen user journey?”</blockquote><p>To which i will answer that the user journey we worked on was that the <strong>user would want to discover a new twitcher through chosing a category they like in the search section and scrolling to discover new creators, ultimately clicking on one stream to watch it.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-3eD4YyM9uVwde0kwPgaQ.png" /><figcaption>4 screens we worked on</figcaption></figure><h3>So what’s up with the Twitch app ?</h3><p>The first thing we’ve gathered from looking closely at it is that everything feels very clustered. There is writing everywhere and it’s challenging to actually be willing to discover a new creator through all the cluster, the words, the tags and the general infos restraining us to actually pay attention to the images. Our word for this challenge: <strong>simplify</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IKPCYyUfVW_2ODrF7M7iA.png" /><figcaption>Heuristics analysis part1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJRLYetahv8vf3wsPmgIVg.png" /><figcaption>Heuristics analysis part 2</figcaption></figure><h3>Competitive analysis</h3><p>As seen down bellow, we’ve done 3 different competitive analysis that was useful for us to see what we could do differently in this design. When looking at the two streaming platforms Rumble and Kick you can immediately see that it is almost identical to the twitch platform. We also chose to include YouTube, because YouTube back in the days was well known for its gaming content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTqjv60OVMFqNxUbGSDapQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ywC_CBomFCjp4paWsTYwQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aYs5-XUE9D6LCskugAgF8A.png" /></figure><h3><strong>Brand attributes and moodboard</strong></h3><p>We found the actual brand attributes of twitch and kept it as is, the difference is the approach we had to it in our moodboard. We wanted our moodboard to reflect the neon/gaming aesthetic so that we could incorporate that later on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrf1mBBd9tx6fgjtUSZEfA.png" /><figcaption>Moodboard</figcaption></figure><h3>Style tile/ AI</h3><p>In order to make it easier for us in the making of the app, we settled on a palette which is pretty complementary and used the helvetica font because it is known to be very accessible which is important to create a community. We chose also some components and component sets that we would use in the design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CrbiXia3J26O9rRLxe8Tvw.png" /></figure><h3>Our prototype</h3><p>Finally, after all those things put in place, we could start creating our Hi-fi prototype, completed with smart animations. The idea was to take Tik Tok as an exemple, so that the “For you” page would be less clutered but also that it would be more addictive to use; it could in the end be a better way to showcase new creators. We then created the other pages keeping them pretty similar to the original app but changing some details along the way, such as the notification bell and the information button underneath the livestream.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNuffUuWTcGQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNuffUuWTcGQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNuffUuWTcGQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2de7d7974742b5211fbd0e6ccb985911/href">https://medium.com/media/2de7d7974742b5211fbd0e6ccb985911/href</a></iframe><p>As always, i am putting the link <a href="https://www.figma.com/proto/Sdv3qN8NeGIxY9KkLqJqWN/Ana%C3%ABlle-%26-Di-Andre?page-id=116%3A21&amp;type=design&amp;node-id=783-92&amp;viewport=3004%2C665%2C0.38&amp;scaling=scale-down&amp;starting-point-node-id=736%3A126"><em>here</em></a> if you want to try it out for yourself.</p><h3>Thank you for reading and I hope to see you soon in the next project !</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=563538f1a21c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Le FoxClub]]></title>
            <link>https://medium.com/@anaelle.damien/case-study-le-foxclub-4e340c851fab?source=rss-87b74a9793fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e340c851fab</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[sports]]></category>
            <category><![CDATA[wireframe]]></category>
            <dc:creator><![CDATA[Anaelle Damien]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 19:36:14 GMT</pubDate>
            <atom:updated>2023-04-24T19:36:14.493Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Hello and welcome</strong> back! Today, i will present to you an e-commerce website we made together with my French teammates <strong>Louise</strong> and <strong>Pauline</strong> based on an existing local commerce. <strong>Let’s get into it !</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-hUGN4BGliLC9TJZcWTAQ.png" /><figcaption>Le FoxClub Homepage</figcaption></figure><h3>The Context</h3><p>This project was a first for us. Indeed, it was a complete project that we had to achieve, starting from the <strong>UX researches to an Hi-fidelity prototype</strong> in only <strong>a week</strong>. The challenge of this project is that we had to base ourselves on an <strong>existing commerce</strong> so we had to represent and/or create a design based off of what already existed. Luckily we quickly found a business thanks to Pauline. The business we worked on was initially called <strong>“Le Five”</strong>. It is a <strong>multi-sport complex</strong> franchise based in <strong>La Rochelle, France</strong>. There was something interessting about this sport complexe: It grouped together <strong>multiple franchises</strong> and the owner thought of changing the website to a completely <strong>new site that would group all the activities</strong> of the franchises together. This meant for us that we were going to have to create a whole new identity, being careful of what the owner would appreciate to see on this site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*deuRZy7jsaDiL7J-Fh945A.jpeg" /><figcaption>Original site: Le Five</figcaption></figure><h3>UXR/Stakeholder interviews</h3><p>In order to be sure of the direction we were meant to take on this project we of course conducted a<strong> stakeholder Interview</strong>.</p><p><strong>Here’s what we gathered from this interview:</strong></p><blockquote>The <strong>values</strong> of the club are :<strong> Conviviality, Easy-to-play, accessibility and well-being.</strong></blockquote><blockquote>The main <strong>needs</strong> of the owner are: <strong>a possibility to pay online, Giving a good image of the complexe and for the users to receive good informations on the activities.</strong></blockquote><blockquote>His <strong>expectations</strong> for the site are: <strong>Clear and modern, Sober and convivial, Page for each sport, Description, videos and pictures.</strong></blockquote><p>Now we’ll review the main points that were talked about in the UXR Interviews.</p><p>The <strong>frustration</strong> points :</p><ul><li><strong>Some plateforms are too complexe</strong></li><li><strong>They are getting lost in the infos</strong></li><li><strong>they can encounter reservations problems</strong></li><li><strong>the lack of schedule.</strong></li></ul><p>Based off of those frustration points we discussed what they would <strong>need</strong> in order to feel more confortable on those sites and we were able to find some needs they have:</p><ul><li><strong>See the availability of classes</strong></li><li><strong>More clear informations</strong></li><li><strong>Transparency.</strong></li></ul><p>And from there we were able to ask for their <strong>expectations</strong> for the website, here’s what came back most :</p><ul><li><strong>See how many places are left</strong></li><li><strong>Being able to choose the payment method</strong></li><li><strong>A good showcase of informations.</strong></li></ul><p>We were then able to better understand what pain points we would have to relieve the users from while creating our website.</p><h3><strong>Meet Fitness Fiona</strong></h3><p>Following those interviews, we got to create our <strong>primary persona</strong> which is <strong>Fitness Fiona</strong>. She’s 25 years old living in France and her main frustrations are that <strong>she finds the reservation system unpractical, she’s not able to pay for her share of the reservation and that she’s getting lost on the complexe’s website.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhF57h6t5wkPfDLDfPgIYQ.png" /><figcaption>Fitness Fiona Personae</figcaption></figure><p>After the creation of Fitness Fiona, we could determine How Might We Statements(HMW) based on what her typical journey is.</p><p>Here’s her <strong>typical day</strong> :</p><blockquote>“Fiona plans to reserve an evening session in a new sport complex at noon. However, she struggles to find the infos she needs to register. She shows up at the sports complex without a reservation but manages to secure the last spot in the session she wanted and quickly joines the class.”</blockquote><p>The <strong>HMW statements</strong> we issued from her journey were :</p><ul><li><strong>HMW make it easier for her to book a workout</strong></li><li><strong>HMW help her navigate through the website ?</strong></li><li><strong>HMW help her find the infos she needs ?</strong></li><li><strong>HMW help her find out if there’s places left in sessions ?</strong></li><li><strong>HMW help her enjoy the sport moment without worrying about booking the next session ?</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSwWH8g4cwOmkO1fnjeuOQ.png" /><figcaption>User Journey Map</figcaption></figure><h3><strong>Problem statement</strong></h3><p>Thanks to all the data we’ve gotten above, we were able to issue our problem statement which highlights what’s the <strong>main problem</strong> we need to <strong>tackle</strong> in our new website :</p><blockquote>“Young active women need to <strong>find a way to book a sport session</strong> because <strong>locating information about the availability</strong> of free slots for classes <strong>poses a challenge</strong> for them and <strong>discourages them from coming back to a sport complex.</strong>”</blockquote><h3>MoSCoW Method and MVP statement</h3><p>Based on our problem statement and what we learned so far, each of us tried to imagine something that would have to go on our site, using the <strong>Crazy 8’s technique</strong> and then voting on our ideas. We then chose which ones would answer our problem statement best using the <strong>MoSCoW Method</strong> which consist in <strong>grading</strong></p><ul><li><strong>the must haves : a showcase of which places are left for any activity, category cards for each activity and a clear planning.</strong></li><li><strong>the should haves : a description of the activity and a video to better help the user to get all the infos he needs.</strong></li><li><strong>the could have : showing the difficulty of a course, joined reservations and a profil sections</strong></li><li><strong>and the won’t haves : a fidelity point system.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IivLro_xemgfS7HE-PaYpw.png" /><figcaption>MoSCoW Method</figcaption></figure><p>This method helped us to determine our MVP statement which is :</p><blockquote>“Young active women need to <strong>find a way to book a sport session</strong> because <strong>locating information about the availibility</strong> of free slots for classes <strong>poses a challenge</strong> for them and <strong>discourages them from coming back to a sport complex.</strong>”</blockquote><h3>Sitemap and userflow</h3><p>The <strong>sitemap</strong> we drew was supposed to help us have a map to create our site, to know where any page is leading which will allow us to create our <strong>userflow.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDO3EVggaFyLqsm6FThxnQ.png" /><figcaption>Sitemap</figcaption></figure><p>For the <strong>Userflow</strong>, we chose a simple pass which went from the <strong>homepage</strong> to being able to<strong> show your code bar at the entrance</strong> of the sport complexe. The goal here was to show any step and what page and pop up will appear depending on the action of the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFWZpjDtJR7lYWYwcitaHw.png" /><figcaption>UserFlow</figcaption></figure><h3>Lo-fi and Mid-fi Wireframing</h3><p>Now that we had a map and that we knew which user’s action would lead to what, we only had to start making our <strong>Lo-fi</strong>, following the supposed <strong>behavior</strong> of the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-nagb8GFQNPGz3Q_8PYlw.png" /><figcaption>Lo-fi</figcaption></figure><p>Once the Lo-fi made, we needed to <strong>test it</strong>. We asked multiple people to help us out by testing. What came out of those tests was that the <strong>planning system</strong> was<strong> not easy enough</strong>, that it was still <strong>too long</strong> to get from start to finish.</p><p>Keeping those reviews in mind, we then started to work on our mid-fi which would guide our final Hi-fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XuGgBXdGxb1xWmAWK_S5JQ.png" /><figcaption>Mid-fi</figcaption></figure><h3>Moodboard, brand attributes and style tile</h3><p>In order to be sure to have a <strong>cohesive</strong> design, we needed to decide on <strong>brand attributes</strong>. We settled on those four attributes:</p><ul><li><strong>inclusive</strong></li><li><strong>Community</strong></li><li><strong>Innovative</strong></li><li><strong>Active.</strong></li></ul><p>We needed our brand attributes to be both <strong>realistic</strong> but also <strong>different</strong> enough that it wouldn’t look like just any sport complexe.</p><p>To represent our brand attributes we created a <strong>moodboard</strong> which is a way to <strong>represent visually</strong> and get a general idea of what the feeling of the company was going to be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52Qh6cLqtKQFcsSBTeT0BQ.png" /></figure><p>Focusing on the whole idea of the club we chose a color palette.</p><ul><li><strong>Yellow</strong> for the <strong>warmth </strong>of the <strong>community</strong></li><li><strong>Dark blue</strong> for the <strong>stability</strong></li><li><strong>sky blue</strong> for the <strong>relaxing</strong> quality of the complexe.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MfSlQcS-lnITJxZpxUBe4g.png" /></figure><p>To complete our styling, we chose a specific Typographie : Futura.</p><p>Futura is a <strong>classic</strong> that never gets old and still keeps a <strong>modern</strong> feel. it is also <strong>easily readable</strong> and will be pleasing to the eye of the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jhVH9wrRhQKBThxH4SMXg.png" /></figure><h3>Final Hi-fi prototype</h3><p>Here’s our final product, after all those steps we were able to put together a Hi-fi prototype taking care of representing our brand attributes as much as possible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEllUTrMpd08%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEllUTrMpd08&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEllUTrMpd08%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6484ae2dc72d3d03598d555ac498063a/href">https://medium.com/media/6484ae2dc72d3d03598d555ac498063a/href</a></iframe><p>You can test the prototype yourself right <a href="https://www.figma.com/proto/CQEIZSqq7kfH8PYzlO9U1w/T1-Le-Five-%7C-Design-File?page-id=116%3A21&amp;node-id=1340-2213&amp;viewport=409%2C44%2C0.1&amp;scaling=scale-down&amp;starting-point-node-id=1340%3A2705"><strong><em>here</em></strong></a>.</p><h3>How we would go further</h3><p>If we had to go further in the project, we would add a <strong>profile page</strong> that would allow the user to make <strong>reservations with friends</strong> and <strong>share the payment</strong>, an <strong>Event page</strong> and a <strong>room simulation</strong> to make it easier to get around the complexe.</p><p><strong>Thank you</strong> very much for reading ! Hope to see you on the <strong>next article</strong> !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e340c851fab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study : Food sustainability]]></title>
            <link>https://medium.com/design-bootcamp/case-study-food-sustainability-6371509f91aa?source=rss-87b74a9793fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/6371509f91aa</guid>
            <category><![CDATA[organic-food]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[sustainability]]></category>
            <dc:creator><![CDATA[Anaelle Damien]]></dc:creator>
            <pubDate>Sun, 09 Apr 2023 17:24:49 GMT</pubDate>
            <atom:updated>2023-04-11T07:32:04.231Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study : Food sustainability</h3><p>Here’s the presentation of our team’s first project at <strong>Ironhack’s</strong> Bootcamp. It was a real pleasure to work with my teammates <strong>Maria</strong> and <strong>Di’André</strong>. <strong>Hope you’ll enjoy !</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pWoAr5oWp6Lg9lOUTWWc5g.jpeg" /></figure><h3>Brief overview</h3><p>In the last decades, there has been a <strong>rise in consciousness</strong> on the importance of <strong>good nutrition</strong> and the <strong>responsibility</strong> that individuals have to provide themselves with good food. Organic food is not <strong>accessible</strong> to everyone, being restricted to those who can actually afford it.</p><p><strong>Supermarket chains</strong> and other big companies benefit from the organic food market and conscious customers, but don’t actually solve the situation — they just <strong>make the gap and the impact bigger</strong> with unsustainable models.</p><h3>Challenge</h3><p>Our main challenge was finding a solution on <strong>how to make organic food more accessible while fueling fair relationships between producers and customers</strong>.</p><p>We had to :</p><ul><li><strong>Create a mobile app</strong></li><li><strong>Offer a service to the user</strong></li></ul><h3>Day One</h3><p>Meeting our teams for the first time, we discussed our brief. We went into this project with some <strong>preconceived Ideas</strong> about the sustainable food industry. We thought at first that it was extremely important to tackle the <strong>food waste problem</strong> at the same time as finding a solution for the challenge at hand. We also thought about the way to offer <strong>ecological deliveries</strong> and that we had to share thorough <strong>informations about the producers</strong>. In order to better understand our challenge we moved to the first step.</p><h3>Secondary research</h3><p>During this phase of the project, we all focused on first finding what are other <strong>apps</strong> and <strong>services</strong> that are trying to solve similar problems.</p><p>Some app we found :</p><ul><li><strong>Phenix : App that allows users to buy food that is about to go bad from supermarkets for a fewer fee.</strong></li><li><strong>Too good to go: Mobile app that allows users to buy unsold products from restaurants, bakeries etc…</strong></li><li><strong>Urby: Transportation service that works with low emission vehicles.</strong></li></ul><p>We also found some articles about sustainability strategies and the sustainable food industry to learn more about our subject.</p><p>This marked the end of our first steps on the project.</p><h3>Day Two</h3><h3>UXR Interviews</h3><p>On the second day of our project, we found 5 people around us that would be willing to answer some of our questions on the subject.</p><ul><li><strong>Georgia (Designer, 28 years old, Woman)</strong></li><li><strong>Mohammed (Intermedia student, 28 years old, man)</strong></li><li><strong>Susa (Translator, 39 years old, Woman)</strong></li><li><strong>Hippolyte (Developer, 27 years old, man)</strong></li><li><strong>Ponja (Kindergarden educator, 31, woman)</strong></li></ul><p>It was challenging to find in such short notice mutltiple people that had the time attend those interviews. Nonetheless, it was a great experience. We proceeded by each interviewing a person we didn’t know, so that the interviews would not be biased by the link we had to the interviewe. For exemple, knowing Hippolyte, I interviewed Ponja and Susa and took notes for Mohammed’s interview.</p><p>We had some interesting insights from those interviews, some confirmed our beliefs, and some made us think twice about our problem. In order to classify which pain points we had to use a new technique we didn’t know about yet.</p><blockquote><strong>“Living in the city it’s more expensive. My mom who’s out of town […] it’s easier for her to have access and it’s less expensive”.</strong></blockquote><h3>Affinity Diagram</h3><p>The affinity Diagram was indeed the technique we used. We clustered all the infos we had and tried to organise them in big categories to see which global themes stranded out the most. It could have been a complicated process, but the discussions with the team flowed really well and we all thought about what would be those categories before dot voting on them.</p><p>In the end of the vote, the 3 main categories we kept were <strong>how expensive</strong> is organic food, the <strong>lack of motivation to do researches</strong> and the <strong>low availability of producers</strong> around us.</p><p>Having gathered all those informations and seeing where the interviews lead us in term of what problems we were facing, we could start to see who would be our main user.</p><h3>Day Three</h3><h3>Persona</h3><p>This is the step where our very important “Sustainable Suzie” was born. We each drafted a different persona based on the UXR interviews, with goals, a biography and needs. We then had a chat about what we would like to incorporate from each of our Personas or not. It was a really easy discussion and we then created Sustainable Suzie (name courtesy of Maria).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41eApSZbuYVBXrYazOfAaQ.jpeg" /></figure><p>As you can see above, not only is Suzie <strong>very busy</strong>, the<strong> budget</strong> she has is limited because of her incomes, which is perfectly underlined by the quote we’ve gathered during our interviews and used in our persona:</p><blockquote><strong>“In the beginning of the month I mostli buy organic, but in the end of the month money is short”.</strong></blockquote><h3>User Journey Map</h3><p>Having our main persona decided on and here characteristics highlighted, we could more easily empathize on how she could feel about her experience with organic food. This is how we imagined (still based on our UXR researches) what an everyday shopping experience could be like for Suzie.</p><p>Based on this scenario:</p><blockquote><strong>“Suzie is preparing her meal plan for the week. She’s gonna go shopping in the cheapest supermarket near her. She wants to chose food that is healthy but also inexpensive.”</strong></blockquote><p>We came up with this timeline and those How Might We statements :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYpjX1LdAU2H_wCNiZV8qg.png" /></figure><h3>Day four</h3><h3>Problem statement</h3><p>Came the time to define what was THE problem we needed to solve first.</p><blockquote><strong>Mindful, busy metropolitans with low incomes need to find a way to access affordable, fresh and sustainable produce because organic food in supermarkets exceeds their budgets.</strong></blockquote><p>This problem statement was based on our researches. Indeed, we saw that most people we interviewed couldn’t afford organic food all the time, and that the affordable way (going directly to the producers) was complicated when living in a big city.</p><h3>Ideation</h3><p>Following the core definition of our project with our problem statement, we could start the Ideation process.</p><h4>Crazy 8&#39;s</h4><p>We started by doing our crazy 8’s that consisted of each of us drawing as many ideas on how to solve our problem as possible in 8 minutes (we had to take a little longer).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWX-EXf60jTEXMJhJZf_Sg.jpeg" /></figure><p>After that, we dot voted on which ideas we thought were the most relevant at the moment. It the helped us to define the bare minimums of what we’ll need in our application so that not only will it be less expensive and accessible for our users but so that producers would be fairly compensated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UP1W66Yu45ozZDVhQs7Q-Q.jpeg" /></figure><h4><strong>MVP statement</strong></h4><blockquote><strong>“The goal of our grocery shopping application is, at the bare minimum, for consumers to pick the most suitable producer around them, place orders on local, seasonal and affordable produce in a storefront.<br>It will require a geolocation search function, a payment system and an environmentally friendly delivery system.</strong></blockquote><blockquote><strong>By creating those features we will help consumers to manage their monthly budgets, get sustainable and locally produced foods delivered to their doorstep, while producers are fairly compensated.”</strong></blockquote><p>To further show what our service was, and how the delivery would happen we then concept sketch (I took the pen for this one).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ng93UbhL9hM0imBGHt7aVw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAQ-d-6jOSkzFqTSF7VXPg.jpeg" /></figure><h3>Day five and six</h3><h3>Lo-fidelity wireframing</h3><p>After deciding on what we absolutely needed to incorporate in our application with the MVP statement, we finally started the Lo-fidelity wireframing. Making sure that everything was well grouped together and looked clean, we could then prototype our wireframe and get to a crucial step: Concept testing. Our concept testing went well, most of the person interviewed thought our prototype was clear and simple. There still was one tester that felt lost because we didn’t yet incorporate a navigation bar, which we did right after those reviews, agreeing that it would be important to implement that feature.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FP0WB6_bBx4s%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DP0WB6_bBx4s&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b7a8db22b9e73d199dc8142f85b85e03/href">https://medium.com/media/b7a8db22b9e73d199dc8142f85b85e03/href</a></iframe><blockquote>You can click<strong> </strong><a href="https://www.figma.com/proto/qy3LKqEIE8d0EpUUFsoKOL/T3---Food-sustainability%7C-Design-File?page-id=16%3A321&amp;node-id=843-1959&amp;viewport=527%2C497%2C0.35&amp;scaling=contain&amp;starting-point-node-id=843%3A1959"><strong>here</strong></a> to get to the prototype and test it yourself .</blockquote><h3>What I’ve learned and what could go further for our project</h3><p>This project taught me so much about all the steps necessary to create an effective user experience, the importance to find the actual pain points and how to go through this process with a (wonderful) team.</p><p>What could go further for our application is of course developing it to the high-fidelity step. We could also imagine new fonctionnalities such as a peer-to-peer chat or shared recipies and where to find the ingredients. These fonctionnalities could help us build a community around the app which would be nice to make the number of user grow.</p><p><strong>Thank you for reading my first case study !</strong></p><p>Don’t hesitate to leave a comment and i’ll see you soon !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6371509f91aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-food-sustainability-6371509f91aa">Case study : Food sustainability</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[Challenge 1 : Design thinking]]></title>
            <link>https://medium.com/@anaelle.damien/challenge-1-design-thinking-c44b69ffb07?source=rss-87b74a9793fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/c44b69ffb07</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Anaelle Damien]]></dc:creator>
            <pubDate>Sun, 19 Mar 2023 19:03:48 GMT</pubDate>
            <atom:updated>2023-03-19T19:03:48.933Z</atom:updated>
            <content:encoded><![CDATA[<h3>Challenge 1 : Design thinking</h3><p><strong>Hi there and welcome back !</strong></p><p>For this challenge, we’ll work based off of City mapper. The challenge is to find a way to allow the user to not have to buy different transportation and to refrain them from having to go thtough different queues.</p><p><strong>What’s City mapper ?</strong></p><p>City mapper is an app used by more than 50 million people. It’s main goal is to facilitate your everyday trajects when you are taking public transportation. It’s available in every major city in the world and will take notice of any perturbations in your way to ensure you the best possible traject.</p><p><strong>Let’s emphahize a bit !</strong></p><p>Who’s the audience ?</p><p>The audience is very wide. Indeed, they are everyday users of public transportation ranging from 15 years old to 70 years old, including students, workers and tourists alike.</p><p>Who’s my client’s competitors ?</p><p>They will mainly be apps such as google maps or WeGo APK.</p><p><strong>What are the main pain points for the audience ?</strong></p><p>The main pain points that i was able to find through my interviews were:</p><ul><li>The app not displaying the right time of passage for buses ( it is indeed a problem in Paris right now because of a lack of Bus drivers)</li><li>Having to pay twice when changing transportation.</li><li>Confusion for some transportation’s payment such as RER.</li></ul><p>Here are a few thoughts on some of those problems:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0alkWsPvZQUsKQ6f-L8x3g.jpeg" /><figcaption>Brainstrorming to find solutions on pain points</figcaption></figure><p><strong>Prototype</strong></p><p>I chose to try and tackle the “having to pay twice problem”.</p><p>Here’s my prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*piPZwTdYJw3H_7UcKz9VaA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ly0A6RHlCy1Wtmr-NYltbA.jpeg" /></figure><p>The idea with this prototype was to end up being able to use your phone like a ticket, or more like a pass that you can just swipe. The ticket will be usable for 2 hours. Of course, it might only be usable on last-gen phones for now, but working with this solution might open the doors to newer ways to naviguate trough cities.</p><p><strong>What I learned ?</strong></p><p>Throughout this process, i learned to interview users in order to find a problem to solve. I also learned how to ideate to find a solution to pain points.</p><p><strong>I hope you enjoyed the reading. As always, feel free to comment and i’ll see you on the next post !</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c44b69ffb07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Wireframe Challenge]]></title>
            <link>https://medium.com/@anaelle.damien/my-wireframe-challenge-21fefe86bb6b?source=rss-87b74a9793fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/21fefe86bb6b</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Anaelle Damien]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 13:58:49 GMT</pubDate>
            <atom:updated>2023-03-14T13:58:49.216Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Hello and welcome</strong>. I will be starting a bootcamp at Ironhack on March, here’s the realisation of my first Challenge for the formation’s prework !</p><p>The app i chose to base my wireframe on is Dice. Dice is an application which allows you to book tickets and browse events in your area. I chose this app, first and foremost because it’s an app that i appreciate as a user. It is simple, effective, an pretty. I also appreciate the fact that it uses QR codes and that once bought, you can use your ticket just by presenting your phone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7siRVtdsUDW1WQ6ijrzdQ.jpeg" /><figcaption>Dice plateform images</figcaption></figure><p>First, let me introduce you to my lo-fi, pencil-drawn wireframe:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QxIZDvFcp0jB8ZfAm6-Z7Q.jpeg" /><figcaption>Lo-fi wireframe of Dice’s mobile app</figcaption></figure><p>As you can see, the user flow i chose to go with, is the ticket-buying experience.</p><p>In order to convey the right experience through my prototype, i needed to be well aware of what my own experience as a user was like.</p><p>I noticed that it was a very simple, yet efficient, one button = one action and that it was how you get from one page to another. The buttons are the connector and probably the most important part of this design, so in my work on figma, i needed to make sure that i had a special frame reserved to it. What i did in the first place was to break down the different parts of the app ( top-nav, bottom-nav, main etc…) and allow each one a special frame, which will make it way easier to place my elements in, and will be more neet.</p><p>I also had to identify how to word the different phrases, what will be worded as an username, a follow, what wording will i keep and what will only need some lorem ispum.</p><p>Finally, in the prototyping phase, i had to connect each page one to another, and decide what scroll type i will use.</p><p>Now that you saw the Lo-fi version of my wireframe, here is the final prototype that I made through Figma :</p><p>&lt;iframe style=”border: 1px solid rgba(0, 0, 0, 0.1);” width=”800&quot; height=”450&quot; src=”<a href="https://www.figma.com/embed?embed_host=share&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2Fnj6BPYpqPLJdd3gVPlWXPK%2FUntitled%3Fpage-id%3D0%253A1%26node-id%3D1%253A2%26viewport%3D146%252C166%252C0.68%26scaling%3Dcontain%26starting-point-node-id%3D1%253A2">https://www.figma.com/embed?embed_host=share&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2Fnj6BPYpqPLJdd3gVPlWXPK%2FUntitled%3Fpage-id%3D0%253A1%26node-id%3D1%253A2%26viewport%3D146%252C166%252C0.68%26scaling%3Dcontain%26starting-point-node-id%3D1%253A2</a>&quot; allowfullscreen&gt;&lt;/iframe&gt;</p><p>What i enjoyed about this experience is the deeper understanding of how the UX behind a good application might work. What i think was harder for me was to know exactly how much elements is too much for a wireframe, but i think i managed to keep it simple in the end.</p><p><strong>I hope you enjoyed the read, and don’t hesitate to comment your thoughts !</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21fefe86bb6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>