<?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 Filipe Branco on Medium]]></title>
        <description><![CDATA[Stories by Filipe Branco on Medium]]></description>
        <link>https://medium.com/@filipenbranco?source=rss-8114cccfb584------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y8LRtAZZrupBf2-Xxwju7Q.jpeg</url>
            <title>Stories by Filipe Branco on Medium</title>
            <link>https://medium.com/@filipenbranco?source=rss-8114cccfb584------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:09:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@filipenbranco/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[Macronutrients, carbohydrates or proteins sound foreign to you? WiseBites is here to help.]]></title>
            <link>https://medium.com/design-bootcamp/macronutrients-carbohydrates-or-proteins-sound-foreign-to-you-wisebites-is-here-to-help-8daa226dc799?source=rss-8114cccfb584------2</link>
            <guid isPermaLink="false">https://medium.com/p/8daa226dc799</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Filipe Branco]]></dc:creator>
            <pubDate>Sun, 15 Oct 2023 00:36:58 GMT</pubDate>
            <atom:updated>2023-10-15T09:20:18.153Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Health-conscious individuals need to find a way to change to a healthier lifestyle through simplified cooking, personalised meal planning, and access to nutritional expertise because they want practical solutions that align with their busy lives and cooking preferences.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GZ0hsapljRSdaOa5Ow3Cjw.jpeg" /></figure><p>Bootcamp Workshop | Role: UX/UI Designer<br>Date: August 2023 | September 2023 (4 week design sprint)<br>Team: Filipe Branco, Julie Haley<br>Platform: Native APP, iOS<br>Tools: Figma, Photoshop, Slack, Zoom</p><h3>Project overview. Working the brief</h3><p>First, let’s address the elephant in the room: there is an immense number of wellness apps in the market. There is an app for almost every user niche and it’s a really hard market to have an app that stands out from the competition. For this workshop we were asked to work on a wellness app for a fictional company called Daily Health Conference, ‘a non-profit Organization dedicated to promoting health and wellness through impactful public talks, participatory workshops, and professional training all over the world.’ <br>The goal is to create a working prototype for a tool that will motivate their members to take action.</p><h3>Choosing the scope</h3><p>To decide what would be the focus of the wellness app, we discussed on our own habits to find out if there were some common ones that could serve as a baseline to build upon. We ended up finding we were both into healthy eating but not the biggest fan’s of the veggies and most of the time having a hard time deciding on what to cook. Based on this, we decided to build our app coming up from a basic recipe and meal planner foundation.</p><h3>Health and wellness is a really crowded space</h3><p>Competitor research started with us searching the web and app store to find similar products and in a matter of minutes we were already overwhelmed by the results… there were lot’s of them! This got us a bit lost on what we would choose to put our product against, because there are apps ranging from single specific purpose usage to others that try to bring ‘everything under the sun’ together in a single product.</p><p>We opted to restrict the scope on three of the most popular apps on the market (and that were also known by our survey respondents), and two other that were more specific and close to the purpose of what we were building.</p><figure><img alt="Feature Competitive Analysis" src="https://cdn-images-1.medium.com/max/1024/1*CTssLbys2LMtfvjGaWOFnA.jpeg" /><figcaption>Feature Competitive Analysis</figcaption></figure><p>All of them are placed in the <em>freemium</em> market, and offer various degrees on what is available for free and what is beyond premium. Because one of the goals of our client was to increase their membership numbers, we looked for opportunities to offer for free a usable product that fills in some empty spaces left by other apps and also to have a standout feature that would be exclusive to our app.</p><h3>What are our users thoughts and behaviours when deciding what to cook and eat on a daily basis?</h3><p>Eighty respondents answered our survey and this brought us very interesting results. Almost all enjoy cooking simple meals and are willing to cook at home everyday. Most had healthy eating in mind and tried to balance the nutritional aspects of their meals during the day, but did not strictly go for calorie counting, except if they were following some dietary plan. They do meal planing to some extent and overall decide on what to cook based on what’s available on the fridge or what they bought at the supermarket the days before.</p><figure><img alt="Highlights from the User Survey" src="https://cdn-images-1.medium.com/max/1024/1*aLcKjv4vqfeB94VuqK1SqQ.jpeg" /><figcaption>Highlights from the User Survey</figcaption></figure><h3>Validating the premium feature idea</h3><p>As a standout and premium feature, we thought about making possible to consult with a Nutritionist inside the app to be able to get expert advice and guidance. We asked our users if they would consider this to be helpful and 60% actually agreed on the idea. Other options, like advanced nutritional tracking and recipes with videos, came around 35%, so they were not scraped, but at this point, put aside for future updates.</p><h3>Gaining further understanding with user interviews</h3><p>We conducted five user interviews that gathered huge amounts of insights that we sorted through an affinity diagram. This pointed us the direction our app should go and what features we needed to value the most. It also validated most of the insights we got from the user survey.</p><figure><img alt="A small snippet of all the insights gathered from the user interviews" src="https://cdn-images-1.medium.com/max/1024/1*Zjh9zJvvi1iPTem-G0OvLA.jpeg" /><figcaption>A small snippet of all the insights gathered from the user interviews</figcaption></figure><h3>Creating a persona that would represent the majority of our users</h3><p>Narrowing the multitude of options we had for our user persona was a tough challenge. Basically, anyone with the goal of healthy eating would be a good prospective user… we resorted back to the user interview answers and the affinity diagram insights and inspected the little details that were most in common between all. In the end, we created «Ruth Abrahamsen, an independent and confident financial advisor, on her late 30’s, with a busy work schedule, that wants to lose some weight but doesn’t have enough knowledge on nutrition to be able to do it by herself. She has already tried some of the most used apps on the market, but has found them too confusing and with too many features she doesn’t need».</p><h3>Defining the MVP of the product</h3><p>With our persona created we just needed to define what would be the characteristics of our Minimum Viable Product (MVP), before proceeding to the ideate stage. With the help of the MoSCoW map, we distributed the features we had gathered from earlier research stages and produced the final MVP Statement</p><figure><img alt="Final MVP Statement for the WiseBites app" src="https://cdn-images-1.medium.com/max/1024/1*gY9mCKzjBGjcyKMsJ-q8zQ.jpeg" /><figcaption>Final MVP Statement for the WiseBites app</figcaption></figure><h3>From low fidelity sketches to mid-fidelity prototype usability tests</h3><p>We kicked off the ideation stage by outlining the user flow for our happy path, that starts with our user answering a survey that will calculate her daily calorie intake, and signing up for premium. The user would then explores the app, looking for recipes and predetermined meal plans, where we assume some usage days have passed. Lastly, the user ends up scheduling a video chat with a nutritionist.</p><p>Bases on this journey we created the low-fidelity screen sketches that were used to do concept testing with four users. The results were mostly positive and we decided that the small changes that needed to be made were pushed to the mid-fidelity wireframe since they were not structural.</p><p>In order to save time later in the project when building the high-fidelity screens and to get as much feedback on the design decisions as early as possible, we decided to build a detailed mid-fidelity prototype that would closely resemble the final product. Everything was already laid out as it would be on the high-fidelity screens, spaced using an 8pt soft grid and also most of the screen elements were created as components always having the next stage in mind.</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%2FW4Io1npseOvMevOwnIu7dU%2FP4-Chameleons---Wellness-app--%257C-Design-File-%28Copy%29%3Fpage-id%3D116%253A10%26type%3Ddesign%26node-id%3D3895-3335%26viewport%3D1478%252C412%252C0.16%26t%3DteyuNpAXh2EpgS9C-1%26scaling%3Dscale-down%26starting-point-node-id%3D3895%253A3335%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FW4Io1npseOvMevOwnIu7dU%2FP4-Chameleons---Wellness-app--%257C-Design-File-%28Copy%29%3Fpage-id%3D116%253A10%26type%3Ddesign%26node-id%3D3895-3335%26viewport%3D1478%252C412%252C0.16%26t%3DteyuNpAXh2EpgS9C-1%26scaling%3Dscale-down%26starting-point-node-id%3D3895%253A3335%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F997af02e-fe33-4c7b-9bf5-29d5125f84a1%3Fheight%3D380%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/00e3626c011f96182b4e4ae7c297a671/href">https://medium.com/media/00e3626c011f96182b4e4ae7c297a671/href</a></iframe><figure><img alt="Some highlights from the changes introduced to the mid-fidelity prototype gathered from usability testing" src="https://cdn-images-1.medium.com/max/1024/1*Jv4NGHzNracFArLsvLtFKQ.jpeg" /><figcaption>Some highlights from the changes introduced to the mid-fidelity prototype gathered from usability testing</figcaption></figure><h3>Putting together the high-fidelity prototype</h3><p>We kicked off by writing down the brand attributes and creating a moodboard for our MVP based on them and also some previously gathered insights. Also, we went back to the start of our research and with the selected competitors, did a visual competitive analysis to look for common characteristics and usability patterns, so we could offer a product that would have innovative elements to make us distinguishable, but that at the same time, maintain a sense of familiarity to ensure ease of use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0pjUkYK4H6bH-aY-lNpeww.jpeg" /><figcaption>Brand Attributes, Moodboard and Colour Pallete</figcaption></figure><h3>The why’s behind our design choices</h3><p>Looking trough the long list of health and wellness apps we detected some common patterns. Most used either green or orange as their primary/brand colour and single sans serifed typefaces. We initially thought about shifting from this, but felt the colours we chose were competing too much for attention in relation to the many colourful pictures of food in each screen. We went back and explored different shades of green and orange to not be too close to other app’s already in the market, but that would still be visually pleasing. We settled on a medium to dark shade of teal green, a colour associated with nature, growth, and freshness. For secondary/accent, we wanted to tap onto the many colours of nature and food, so it made sense to search for a complementary colour. Choice went for a bright shade of orange-yellow, so we could break the overall ‘greenish’ look with a strong contrast also representing the vibrancy of nature.</p><figure><img alt="Style Tile for the WiseBites App" src="https://cdn-images-1.medium.com/max/1024/1*FfkLqdR7W7xUx8EW8Z9TOw.jpeg" /><figcaption>Style Tile for the WiseBites App</figcaption></figure><p>When choosing the typeface, we were divided between going all sans serif or combining a sans serifed body font with big serifed titles. The first option was the most common in all analysed app’s, it was the safe choice, and it gave the app an easy to read and contemporary style, but…</p><p>Research had already showed us that our users were mostly women, aged between 30 and 50, so we felt that we were lacking a touch of elegance and sophistication that would resonate with this target demographic. Also it would be an opportunity to have a visually different app. Although one of our competitors uses the same type of font combination, the overall look is more sober and classic, with the use of darker shades and we wanted our app to look elegant, but at the same time feel vibrant and energetic to appeal to a broader range of users.</p><p>After some typeface explorations taking inspiration from cookbook covers, we decided to use for the titles the ‘DM Serif Display’ font from Google, known for its graceful and refined characteristics, which added the elegance feature we were seeking. For body font we chose ‘Proxima Nova’ a highly popular and versatile sans-serif typeface, designed by Mark Simonson, that offers excellent readability and is characterised by its clean, modern, and friendly appearance.</p><figure><img alt="Some of our final High-Fidelity Screens" src="https://cdn-images-1.medium.com/max/1024/1*1x8IacouRUB7k4xw6Zsm9A.jpeg" /><figcaption>Some of our final High-Fidelity Screens</figcaption></figure><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%2FW4Io1npseOvMevOwnIu7dU%2FP4-Chameleons---Wellness-app--%257C-Design-File-%28Copy%29%3Fpage-id%3D116%253A21%26type%3Ddesign%26node-id%3D4287-4505%26viewport%3D378%252C363%252C0.07%26t%3DY5qJZidTmNxInAZE-1%26scaling%3Dscale-down%26starting-point-node-id%3D4287%253A4505%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FW4Io1npseOvMevOwnIu7dU%2FP4-Chameleons---Wellness-app--%257C-Design-File-%28Copy%29%3Fpage-id%3D116%253A21%26type%3Ddesign%26node-id%3D4287-4505%26viewport%3D378%252C363%252C0.07%26t%3DY5qJZidTmNxInAZE-1%26scaling%3Dscale-down%26starting-point-node-id%3D4287%253A4505%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fc331310a-d421-4b3d-aec0-2de45930bb24%3Fheight%3D380%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/621b45edd8bcd5f7e3b629f17a8a9231/href">https://medium.com/media/621b45edd8bcd5f7e3b629f17a8a9231/href</a></iframe><h3>Final usability iterations and desirability testing</h3><p>With the workshop coming to it’s end, we still managed to do four new usability tests, now with the high-fidelity prototype and at the same time ask out testers to do a desirability test using the Microsoft Reaction Card technique.</p><p>Having previously tested a detailed mid-fidelity, results were not so meaningful now, and mostly revolved around small details or things that users wanted to see or do but that weren’t part of our ‘happy path’ prototype. Still, one significant change was the inclusion of an additional confirmation message before the users do the final submission of the selected day for the nutritionist video chat.</p><figure><img alt="Some highlights from the high-fidelity prototype usability tests" src="https://cdn-images-1.medium.com/max/1024/1*w08gGISn5GOBzDmGKwkbxg.jpeg" /><figcaption>Some highlights from the high-fidelity prototype usability tests</figcaption></figure><p>“Easy to use” and “intuitive” came out as the highest-rated factors among our desirability testers. This feedback shows the significance of these elements in the user interface and highlights the users preference for a design that is user-friendly and simple. We wanted to do some more tests, but, unfortunately, we could not schedule them before the final presentation.</p><h3>Moving forward — Outcomes and takeaways</h3><p>Although this was a ‘fictional client’ project, it was really interesting giving the broad scope which challenged us to address various different aspects all the time. Every decision opened up multiple possible paths and keeping on track sometimes proved to be tougher than expected. The guiding principle that consistently grounded us was ‘keep it simple,’ and it proved to be the key to resolve all complexities that surfaced.</p><p>For next steps, it would be very interesting to pair with a Subject matter Expert to help test the MVP and ‘fill in the gaps’ for further iterations. Also, develop different paths that would open the app’s other functionalities and add new features, for example, more advanced filtering options or video recipes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/101/0*zNkZAtNkg0NdAN_0.png" /></figure><p>If you got all the way down here, I hope you enjoyed reading this case study and that it may be helpful to you somehow. Also, if you got a minute or two to spare, please leave me some feedback in the comments so I can keep making it better or improve for future study’s. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8daa226dc799" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/macronutrients-carbohydrates-or-proteins-sound-foreign-to-you-wisebites-is-here-to-help-8daa226dc799">Macronutrients, carbohydrates or proteins sound foreign to you? WiseBites is here to help.</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[How to help Businesses standout – redesigning a freelancer website]]></title>
            <link>https://medium.com/design-bootcamp/how-to-help-businesses-standout-redesigning-a-freelancer-website-532c183568b6?source=rss-8114cccfb584------2</link>
            <guid isPermaLink="false">https://medium.com/p/532c183568b6</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Filipe Branco]]></dc:creator>
            <pubDate>Tue, 10 Oct 2023 22:56:18 GMT</pubDate>
            <atom:updated>2023-10-17T18:29:13.217Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>How might we design a website that uniquely showcases Harmonie’s expertise in both translation and product management, emphasising her multi-skills as a unique selling point, and effectively differentiating her from other professionals in the industry?</blockquote><figure><img alt="Final UI Website redesign for desktop, tablet and mobile" src="https://cdn-images-1.medium.com/max/1024/1*WsYIAbJEB-WxAMJ4LqD07A.jpeg" /><figcaption>Final UI Website redesign for desktop, tablet and mobile</figcaption></figure><p>Bootcamp Workshop | Role: UX/UI Designer<br>Date: July 2023 (4 week design sprint)<br>Team: Filipe Branco, Flor Lembo, Katayoun Sirbu<br>Platform: Responsive Website<br>Tools: Figma, Photoshop, Slack, Zoom</p><h3>Project overview. Who is Harmonie?</h3><p>Few businesses don’t have any form of digital presence on the internet today. This is true for the largest companies to the the smallest one person business, but having enough available resources to focus on user engagement in different mediums, is one of the main disadvantages to become noticed in the very much crowded web-space for the latter. With this in mind, Katayoun introduced the rest of the team to Harmonie Blondel Henderson, a freelance English and Spanish to French translator and project manager, who needs to make her web presence more meaningful and modern as a way to compete with bigger companies.</p><h3>Gaining first hand insights into the business — shaping the direction of the project</h3><p>We launched the UX design process with an interview with Harmonie, so we could understand her viewpoints, business goals and the story behind her current website. We learned that it no longer served the initial purpose of attracting new clients, it’s outdated and in desperate need of a re-styling. Because of this, Harmonie as long moved to other ways of finding work, most of it coming trough LinkedIn networking and referrals from peers and past clients. We also learned this is common practice among other professionals in the industry. Despite this, she recognised the importance of having an online presence outside social media and would like to improve her website so she could stand out from other freelance translators and appear in web searches along side translating agencies, who she considered to be the main competitors because of their greater resources.</p><figure><img alt="Current Website (as of October 2023)" src="https://cdn-images-1.medium.com/max/1024/1*Rl4TaxzrW44QSusuGhhJTQ.jpeg" /><figcaption>Current Website (as of October 2023)</figcaption></figure><h3>Analysing the website from the user perspective</h3><p>To have a better understanding of what users need to find while searching for translators online and if the shortcomings identified in the previous interview, regarding the website, would be relevant to them, we interviewed three regular users of translating services, and in one of the questions asked them to go Harmonie’s website and see if they would choose to work with her based on what they were seeing.</p><figure><img alt="Quotes from User Interviews" src="https://cdn-images-1.medium.com/max/1024/1*0XILTpd0VMlLzhb26B3GzA.jpeg" /><figcaption>Quotes from User Interviews</figcaption></figure><p>All of them answered that they probably wouldn’t, highlighting navigation issues, missing evidence of the quality of work she would be able to produce and the unprofessional and outdated look of the website. Since they weren’t able to establish trust, they would all move on and not reach out to Harmonie.</p><h3>And how did it stack up against competitors?</h3><p>We did feature and brand analysis against five competitors, two being other freelancers who offer similar services, two small to medium sized translation agencies and a machine translating service.</p><p>Compared to other freelancers there wasn’t much difference between them and they all share similar features, with Harmonie failing to showcase past clients. Branding is very basic and somewhat random in all of them, giving the impression that there wasn’t much thought beyond its creation and that it was amateur made.</p><p>When faced against the agencies, there is a clear differentiation especially regarding the branding and care for visual consistency. Although the ones we chose were not particularly interesting, they still managed to have a ‘corporate’ look. Feature wise, they did not have any standout feature other than being more content heavy and didn’t even feature a portfolio, maybe because of NDA’s or other unknown reasons.</p><p>Machine translating did not really compare to anything other then offering a multi-language website, but Harmonie and all competitors had this option.</p><h3>Problem statement and MVP creation</h3><blockquote>Scaling companies that need effective translation of their products into French while managing the product development process in order to reach the French market.</blockquote><p>With all findings sorted out trough the affinity diagram, primary user persona defined and problem statement already in hand, we prioritised using the MoSCoW method, the features that would make it onto the MVP and ideate and iterate the low-fidelity screens that would support it. After it was built we tested it, and made the necessary changes according to the feedback we got.</p><h3>Conducting usability tests</h3><p>To get early feedback on usability, we created the sitemap and user flow, built a mid-fidelity wireframe prototype of the website and conducted five user tests.</p><figure><img alt="Mid-Fidelity screens" src="https://cdn-images-1.medium.com/max/1024/1*YSIiPojcczBZ2sbv30wHfA.jpeg" /><figcaption>Mid-Fidelity screens</figcaption></figure><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%2FOzJABwzGpFWXjPzZQkzPia%2FP2-G4-E-Commerce-%257C-Design-File-%28Copy%29%3Fpage-id%3D2811%253A1626%26type%3Ddesign%26node-id%3D2900-5273%26viewport%3D740%252C1087%252C0.69%26t%3DanVhwuqIXERacS3F-1%26scaling%3Dscale-down-width%26starting-point-node-id%3D2900%253A5273%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FOzJABwzGpFWXjPzZQkzPia%2FP2-G4-E-Commerce-%257C-Design-File-%28Copy%29%3Fpage-id%3D2811%253A1626%26type%3Ddesign%26node-id%3D2900-5273%26viewport%3D740%252C1087%252C0.69%26t%3DanVhwuqIXERacS3F-1%26scaling%3Dscale-down-width%26starting-point-node-id%3D2900%253A5273%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F66c04aa0-a2ad-48fc-858b-cde279bbe3fd%3Fheight%3D380%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/87f8c48c8cd97f720c6711d18894f604/href">https://medium.com/media/87f8c48c8cd97f720c6711d18894f604/href</a></iframe><p>All testers gave positive feedback on the simple navigation and the way it was structured and the presence of contextual CTA’s available in each page. Negative remarks were mostly about the positioning of content, mainly on the homepage where we had to change the location of the portfolio. Overall feedback on the entire prototype was positive so, with relevant changes made, we moved to define brand attributes and created a moodboard that would guide us trough the visual design of the high-fidelity prototype.</p><figure><img alt="Moodboard for the website redesign" src="https://cdn-images-1.medium.com/max/1024/1*rLmoLJKZkYWji173OKjMWw.jpeg" /><figcaption>Moodboard for the website redesign</figcaption></figure><h3>Be prepared to adapt fast. Sometimes things don’t go according to plan</h3><p>Having just started working on colours and typography, one of our team members fell ill and couldn’t continue working on the project for the remainder of it’s duration. Because we all have our daily jobs and are doing the course part-time, with just a little over a week until the projects due date and final presentation, we decided we had to cut short on the number of high-fidelity screens to prototype and just design the ones more representative of the overall website look and simpler happy path, so we could be able to have all mandatory deliverables by the weeks end. We breathed deep, rolled up our sleeves and dived in.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F25917308&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fpt-PT%2Fview%2Fjack-nicholson-deal-with-it-sunglasses-gif-25917308&amp;image=https%3A%2F%2Fmedia.tenor.com%2FS-s-9qKnviwAAAAC%2Fjack-nicholson-deal-with-it.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/24f3cd3c5a1b53b825d2adf028b2258e/href">https://medium.com/media/24f3cd3c5a1b53b825d2adf028b2258e/href</a></iframe><h3>The why’s behind the style tile</h3><p>We defined our primary brand attributes as Trustworthy, Professional, Confident, Passionate and Feminine, and because trust and professionalism were one of main reasons Harmonies website failed to convince users during research, we chose a slight dark shade of blue as our primary colour, because it’s often seen as a colour that conveys trustworthiness, reliability, and dependability. For the accent colour we chose a vibrant pink. This colour is complementary to the blue and is often associated with femininity.</p><figure><img alt="UI Style Tile" src="https://cdn-images-1.medium.com/max/1024/1*YF1NyDRWEiKal2VRrlYqIg.jpeg" /><figcaption>UI Style Tile</figcaption></figure><p>The same principles guided us while choosing typography, and we decided to have two different typefaces. We opted to search them inside the google fonts repository, because they are free and easily accessible inside figma.</p><p>For titles we chose Petrona Bold, a serifed font that has an overall roundness and small little personality details that sets it appart from other more classical looking typefaces — With this choice we were not only aiming to convey a sense of tradition, lending an air of credibility and reliability to the content, but also by using it with bigger font sizes and colour contrast to prominently display marketing claims and page titles, tap into the confident, passionate and feminine attributes of the brand.</p><p>For body text we chose Lato, because it has semi-rounded details in the letters, making it a good pairing with Petrona, but also because it conveys “a feeling of warmth, while the strong structure provides stability and seriousness”.</p><p>For the overall look we took inspiration from the Bauhaus design style, drawing inspiration from it’s minimalist and grid based layouts and the use of 2d shape patterns. Keeping in mind that this is the work page for a single person, a freelancer and not an agency, we wanted the website to still look professional, but maintain a bit of playfulness, friendliness and a feminine personality, so we made sure that most of the designed website components had soft round corners and added abstract geometric shapes to break the rectangular sections and pinpoint some areas of interest for the user.</p><p>Buy combining all these elements and working on a clearly defined 8pt grid system, with consistent usage of colours, font sizes, spacings, shapes, etc. we tried to make sure everything looked functional, clean, organized, balanced and appealing.</p><h3>Creating the final high-fidelity prototype</h3><p>With only a few days left on the project and still making up for the loss of a team member, we needed to deliver all screens for one happy path and choose one of those screens to do the responsive webdesign layouts for tablet and mobile.</p><figure><img alt="Tablet and Mobile High-Fidelity Screens" src="https://cdn-images-1.medium.com/max/1024/1*2CJV6TWSaEM7qYK7wUmJhA.jpeg" /><figcaption>Tablet and Mobile High-Fidelity Screens</figcaption></figure><p>Our original user flow would require us to design at least eight screens, for which we knew there was no available time, but wanting to not fail on delivering the responsive screens also, we made the hard choice to create a very simple happy path with only three screens for the desktop version — the homepage, the expertise page from the work section, and the contact page — because together they managed to showcase most of the components that would also be available in other pages, thus giving us time to work on the two responsive screens, for which we chose the homepage.</p><figure><img alt="Desktop High-Fidelity Screens" src="https://cdn-images-1.medium.com/max/1024/1*4EypzWI-JJpORlBn0MO9Sw.jpeg" /><figcaption>Desktop High-Fidelity Screens</figcaption></figure><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%2FOzJABwzGpFWXjPzZQkzPia%2FP2-G4-E-Commerce-%257C-Design-File-%28Copy%29%3Fpage-id%3D2%253A4134%26type%3Ddesign%26node-id%3D3373-2183%26viewport%3D1685%252C512%252C0.18%26t%3DoVgej6h4uXCmL5Du-1%26scaling%3Dscale-down-width%26starting-point-node-id%3D3373%253A2183%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FOzJABwzGpFWXjPzZQkzPia%2FP2-G4-E-Commerce-%257C-Design-File-%28Copy%29%3Fpage-id%3D2%253A4134%26type%3Ddesign%26node-id%3D3373-2183%26viewport%3D1685%252C512%252C0.18%26t%3DoVgej6h4uXCmL5Du-1%26scaling%3Dscale-down-width%26starting-point-node-id%3D3373%253A2183%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fb6d9568d-ef24-4d16-a9ae-187a1767ef51%3Fheight%3D380%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/b1f8553d1af3d53d7dfe4dfb7cbc8dff/href">https://medium.com/media/b1f8553d1af3d53d7dfe4dfb7cbc8dff/href</a></iframe><h3>Moving forward — Outcomes and takeaways</h3><p>I enjoyed doing this project because this allowed me to practice more on the UX research methods, expanding on the last workshop and use my previous web design skills inside Figma to help our team create a website design that would meet stakeholder and users needs and expectations.</p><p>Unfortunately we did not have time to do desirability testing, but post presentation critique by our peers and teacher staff was 100% positive on the overall look and feel of the website, which managed to tick all the required boxes.</p><p>After a long period of work and having to put extra time to compensate for the loss of a team member on the final and most demanding part of the project, we felt very proud of ourselves for managing to keep functioning as a team and not to lose track of the end goal while still being able to produce top of the class work.</p><p>Although this was a workshop project, I would really enjoy seeing the stakeholder pick it up and move it forward and use it to improve her website. There is still a big amount of work to be done, but I believe our team was able to produce a very good starting point on redesigning a, standout from the competition, website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/101/1*IybojiOpA6OkGE-NK-bkWg.png" /></figure><p>If you got all the way down here, I hope you enjoyed reading this case study and that it may be helpful to you somehow. Also, if you got a minute or two to spare, please leave me some feedback in the comments so I can keep making it better or improve for future study’s. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532c183568b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-help-businesses-standout-redesigning-a-freelancer-website-532c183568b6">How to help Businesses standout – redesigning a freelancer website</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[Big city problems — Helping European drivers efficiently find the best parking locations]]></title>
            <link>https://medium.com/@filipenbranco/big-city-problems-helping-european-drivers-efficiently-find-the-best-parking-locations-1de649af8488?source=rss-8114cccfb584------2</link>
            <guid isPermaLink="false">https://medium.com/p/1de649af8488</guid>
            <category><![CDATA[uxui-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[low-fidelity-prototyping]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Filipe Branco]]></dc:creator>
            <pubDate>Tue, 29 Aug 2023 01:11:55 GMT</pubDate>
            <atom:updated>2023-08-29T01:25:29.818Z</atom:updated>
            <content:encoded><![CDATA[<h3>Big city problems — Helping European drivers efficiently find the best parking locations</h3><h3><strong>European Frequent Drivers, need to find a way to find best routes and easy parking spots, because driving and parking in big cities is usually very difficult and time consuming.</strong></h3><p>Bootcamp Workshop | Role: UX Designer<br>Date: June 2023 — July 2023 (3 week design sprint)<br>Team: Filipe Branco, Maria Reviriego, Rosanne Baars<br>Platform: Mobile APP<br>Tools: Figma, Google Forms, Slack, Zoom</p><figure><img alt="Research shows that 77,1% of people consider finding available parking spaces is one of the main challenges when driving in big cities." src="https://cdn-images-1.medium.com/max/1024/1*c6tIrDz7EAAd0ZFyeDPyXQ.jpeg" /><figcaption>Research shows that 77,1% of people consider finding available parking spaces is one of the main challenges when driving in big cities.</figcaption></figure><p>Where did this number came from? Why is it such a problem? Why should I care, I don’t even use a car… Lots of different questions, lots of possible answers — welcome to the wicked problem challenge in city mobility.</p><h3>What is a wicked problem?</h3><p>The term was introduced in 1973 by design theorists Horst Rittel and Melvin Webber as a way to describe complex and ambiguous issues that are challenging to resolve because of their numerous interconnections, and conflicting perspectives.</p><h3>City mobility in 2023. Why parking?</h3><p>The challenge was to find “how might we organize the variety of people navigating the streets to provide a more efficient and cleaner city?”. Given that there is no obvious single solution to address this, secondary research led us to a European Commission Study report on <a href="https://op.europa.eu/en/publication-detail/-/publication/adfc18f1-80e1-11ed-9887-01aa75ed71a1">new mobility patterns in European cities</a>, that showed us that «Car is the predominant mode of transport, with an average share of 64% across the 12 Member States where such surveys are available». With this in mind, we set out to find trough user survey if we could validate this result and what this participants would find more challenging when driving, specifically in big European cities.</p><figure><img alt="We got 51 responses from people originating in 15 different European cities" src="https://cdn-images-1.medium.com/max/1024/1*acZkGLh6Vjj8XzyL54bq0A.png" /></figure><p>The majority of respondents answered they were usually the car driver and more than half of them said they use the car on a daily basis, with comfort and flexibility being the main reasons for choosing it as the primary means of transportation.</p><figure><img alt="64,7% reported they are usually the car driver. 52,1% said they use the car on a daily basis, with comfort and flexibility being the main reasons for choosing it as the primary means of transportation, with an average of 84,4%" src="https://cdn-images-1.medium.com/max/1024/1*R1dkJOvMdxz7w-yH0uzVsw.png" /></figure><p>Prior to sending out the surveys, we already had some assumptions on possible challenges drivers face, but we needed to find out if they were the same our prospective users find to be the main pain points, and what would be the one that would stand out and guide us forward with our project.</p><figure><img alt="77,1% of drivers answered that finding available parking is one of the main challenges when driving in big cities, followed by the low availability of free parking spaces (64,6%) and paid parking too expensive (47,9%)." src="https://cdn-images-1.medium.com/max/1024/1*43VL-t6yV_Cd4px4O_weJQ.png" /></figure><p>Finding available parking coincided with our principal assumption, so we decided to pick it as the focus for our project, on <strong>how might we help European frequent drivers find suitable parking spots</strong>, keeping in mind the other most relevant pain points, that would also serve as further refinement on the solution, given that they were all related.</p><h3><strong>Gaining a deeper understanding of our users. Conducting user interviews with frequent drivers</strong></h3><p>To better understand user choices and behaviours, we did five interviews via zoom, to gather qualitative data on people who live and drive in different cities but who share the common profile of being regular car users, and sorted the key findings using an affinity diagram.</p><figure><img alt="Partial image of the Affinity diagram, showing some interview insights and dot voting on the trends our team has identified important to prioritise." src="https://cdn-images-1.medium.com/max/1024/1*-o5RVihvvZKWIgJrOJzRlQ.png" /><figcaption>Partial image of the affinity diagram, showing some interview insights and dot voting on the trends our team had identified important to prioritise.</figcaption></figure><figure><img alt="Key I-statements" src="https://cdn-images-1.medium.com/max/1024/1*qTtQEGalUJDL34O9dEmD0w.png" /><figcaption>Key I-statements</figcaption></figure><h3>Defining the target user. Creating the Empathy map and User Persona</h3><p>Taking insights from the affinity diagram and to have a deeper understanding of our users and their needs, we built an empathy map so we could elaborate on a user persona that would be more detailed and realistic of the different user types.</p><h3>Say hello to “Busy Berta”</h3><p>For this challenge we needed only to create the primary user, so, based on previous findings, we created Berta, a real estate agent living in Madrid, that uses the car on a daily basis and needs to make smart choices when driving and parking to keep her routines on schedule.</p><figure><img alt="Our primary user persona — Berta" src="https://cdn-images-1.medium.com/max/1024/1*FHjFrLaWjPCi2TfIUx1fgA.png" /><figcaption>Our primary user persona — Berta</figcaption></figure><h3>Understanding and mapping out the user experience — <strong>Creating the user journey</strong></h3><p>To create the user journey, we imagined a day in the life of Berta. For this day, Berta is meeting a prospective client, near the city centre, in a part of town she doesn’t know very well. She is excited because there is a possibility of closing a deal, so she doesn’t want to lose much time in traffic driving there and finding a parking spot, risking being late. Planning in advance, she finds the fastest route and the most suitable park.</p><figure><img alt="The user journey" src="https://cdn-images-1.medium.com/max/1024/1*0rtZpqUmthTl6E3GdJRcOw.png" /><figcaption>User journey — a day in the life of Berta</figcaption></figure><h3>Guiding the user’s path and actions — <strong>The user flow for ‘a day in the life of Berta’</strong></h3><p>To facilitate and focus the sketching of the low-fidelity prototype on the problem we were trying to solve, we drafted a user flow based on the user journey we created for Berta, outlining the happy path she would need to complete in order to accomplish her goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ffn_MWzEZ2c6nl6iBb3r3Q.png" /><figcaption>User flow outlining the happy path only (task flow) and omitting different paths</figcaption></figure><h3>Creating concepts for the product’s user interface — <strong>Competitive Analysis</strong></h3><p>Because the app would have similar functionalities to other existing apps already on the market, we did a quick competitive analysis between Google Maps, Apple Maps and Waze, mostly to find out common usability patterns and opportunities to have standout features.</p><p>Unique and differentiating features of our product include:</p><ul><li>Ability to find available parking spaces near set destination, based on user profile/user choice criteria</li><li>Ability to book parking spaces (where available)</li><li>Ability to manage parking costs (start, extend and finish)</li><li>Ability to pay for parking inside the app</li></ul><h3>The final low-fidelity concept sketches</h3><p>Each of us ideated on a couple of screens and afterwards combined the best ideas to draw by hand the final low-fi sketches and built a simple digital paper prototype to do concept testing. This was also the last step that concluded the workshop.</p><figure><img alt="Concept sketches outlining the happy path created in the user journey" src="https://cdn-images-1.medium.com/max/1024/1*FiTnxK-EqfNg6finNRsX6A.png" /><figcaption>Concept sketches outlining the happy path created in the user journey</figcaption></figure><p>Following the yellow dots from left to right, our user taps on ‘Drive &amp; Park’ to find a combined solution. He enters the destination and selects the fastest route and taps ‘choose parking’ to continue. Selects the closest to destination from the results and a modal opens with parking details. This park has the possibility to book in advance, so he chooses it. The user is offered to confirm the selections made and chooses to ‘schedule’. When starting the trip, goes to ‘My Trips’ (green dot) and taps on the scheduled trip card and is taken to GPS mode (screen 8). When arriving close to destination, an automatic timed alert is shown saying that it will now drive to the park (if cancelled it would continue to drive to the original destination). When close to the park, a QR code pop’s up to show at the gate and enter the park. After a pre-defined time interval, a notification is shown asking if the user would like to end the parking and pay in-app or continue with the parking.</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%2FGuLkB5RTDPPlKOJeDtRu8g%2FPaper-Prototype%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D1-2%26viewport%3D624%252C4266%252C1%26t%3DcvY16Rgr799v1s7T-1%26scaling%3Dcontain%26starting-point-node-id%3D1%253A2%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FGuLkB5RTDPPlKOJeDtRu8g%2FPaper-Prototype%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D1-2%26viewport%3D624%252C4266%252C1%26t%3DcvY16Rgr799v1s7T-1%26scaling%3Dcontain%26starting-point-node-id%3D1%253A2%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Ff62ac414-0f0d-406b-af77-9fae07880f40%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/7cb2a64020239b422b1e2f47bd720890/href">https://medium.com/media/7cb2a64020239b422b1e2f47bd720890/href</a></iframe><h3>Moving forward — Outcomes and takeaways</h3><p>With this being the first workshop, it was also the first time we got to put in practice all the methods to conduct UX research. Although we had some prior assumptions on the possible outcomes, approaching the problem using user-centered design methodology, showed us that not all of them were true and this allowed us to focus on the main user pain points to be able to deliver a meaningful and problem-solving product.</p><p>Concept testing was validated by all users we tested, and most praised the idea of being able to manage and pay for parking inside the app. There were also some minor changes suggested to some labels (a revised sketch was not produced because workshop time ended before getting the full results), and if this was to be continued, we would proceed to build a low-fi prototype to start testing for usability issues and iterate on the findings with the purpose of moving forward with the project.</p><p>This workshop highlighted the importance of conducting user research or, if not possible, at least to do as much secondary research as you can before the actual building of the product. The big lesson we learned was never to do anything based on your assumptions only, because they may not be the same as your intended users wants and needs, and in the end, you’ll design for no one but yourself, failing not only to deliver a product that would be useful for your users but also that wouldn’t, probably, meet business goals.</p><p>It was also a great opportunity to practice working as a team and be able to help each other overcome all obstacles that surfaced along the journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/101/1*IybojiOpA6OkGE-NK-bkWg.png" /></figure><p>If you got all the way down here, I hope you enjoyed reading this case study and that it may be helpful to you somehow. Also, if you got a minute or two to spare, please leave me some feedback in the comments so I can keep making it better or improve for future study&#39;s. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1de649af8488" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing Spotify: Prototyping the Search]]></title>
            <link>https://medium.com/@filipenbranco/wireframing-spotify-prototyping-the-search-899571f47848?source=rss-8114cccfb584------2</link>
            <guid isPermaLink="false">https://medium.com/p/899571f47848</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Filipe Branco]]></dc:creator>
            <pubDate>Sat, 20 May 2023 11:01:01 GMT</pubDate>
            <atom:updated>2023-05-20T12:10:29.314Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is an article for Ironhack’s UI/UX bootcamp pre-work.<br>Challenge 2: Wireframing</em></p><p>Picking Spotify for this challenge was a no-brainer. Having a comute of 45min to work and back, it’s my go-to app on a daily basis, and the first I also open when I power on the laptop to star my work day. Every chance I get, music will be playing, and Spotify is one of the main sources for my “soundtrack of life”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gW2V4JpNQbyUBqk0" /><figcaption>Photo by <a href="https://unsplash.com/es/@sgcreative?utm_source=medium&amp;utm_medium=referral">sgcdesignco</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Coming to this challenge, I had never used Figma to sketch or prototype, so I was a little uncertain on how it would play out. I had previously watched some tutorials on basic concepts, grids, auto-layout and components but the lack of practice made everything seem disconnected, although I understood the broader meaning.</p><p>But one as to start somewhere, so I jumped on the app and went straight to the search flow, because it’s one of the ways I use to find new music. Usually when I don’t feel like listening to anything specific, I use the search functionality and just type some random letters or a word that comes to mind and see where it takes me. I grabbed pencil and paper and quickly sketched the user flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwf8R_nYKW8SDe0H1t-nPg.jpeg" /><figcaption>User flow for the Spotify Search</figcaption></figure><p>Analysing the task, if users want to find new artists, music, etc, these are the steps they have to take:<br>- Press the search icon<br>- On the new screen either use the search bar to type whatever they want or choose from one of the predefined categories (I sketched the free search)<br>- Enter the search term(s)<br>- Choose the most relevant result that meets the search<br>- According to the chosen result, either play a track, album, browse podcast show or listen to a single episode.</p><p>Jumping on to figma with screenshots in hand, the first difficulty was not having the code inspector at hand to help find the correct sizes and spacings of the various UI elements, so I had to rely on the grid and visual guides to try and pick things up, but not being pixel perfect renderings, sometimes I had to do some approximate guessing and balance it out visually. In the process I managed to understand that there are common links between different UI elements, either having the same size but different forms, common spacings, and alignments that are consistent between screens. In my wireframe I tried to replicate this small details, but I guess there is the odd pixel or two, or some font sizing that may be out of place, but all in all, I think it’s fairly well balanced. I simplified the UI as much as I could, but for the search flow, I maintained the used fields look a bit more close to their final product counterparts, so as to make it more obvious for the prototype flow testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acYhKOb4DrPtA6DASMg6rA.png" /><figcaption>Wireframing Spotify — The Search</figcaption></figure><p>Also during the construction of the wireframe, I started to remember certain things I had previously seen in some tutorials, and started to get a better sense of their usage, namely, the auto-layout function for coherent and very easy spacing of elements that share the same row or column, or spacings around elements like icons and text, and component creation, that I used to do the menu wires just one time and then reused it on each screen, instead of having to manually redo every link on each frame.</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%2FX1E5zSGc50Zo3PqG4X9tMo%3Fembed_host%3Dshare%26kind%3D%26node-id%3D5-56%26page-id%3D0%253A1%26starting-point-node-id%3D5%253A56&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FX1E5zSGc50Zo3PqG4X9tMo%3Fembed_host%3Dshare%26kind%3D%26node-id%3D5-56%26page-id%3D0%253A1%26starting-point-node-id%3D5%253A56&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F6e6191fd-39f4-44ab-b784-bed3c32655b6%3Fheight%3D379%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/a42c8fccf8d1d824a82928646ee7bc25/href">https://medium.com/media/a42c8fccf8d1d824a82928646ee7bc25/href</a></iframe><p>This exercise was very useful to understand that even small actions we do on an app have to be thought out in detail, because their not all linear like go from A to B and stop, usually it is go from A to B, B to A, but also B to C or B to D and so on. Also it was useful to start understanding the use of some figma concepts, and the much needed preparation we need to have even before opening up the software. I enjoyed the prototyping phase, and it was fun trying to mimic Spotify’s animations. Looking forward for some more challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=899571f47848" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Using public transports will get easier” — Ironhack’s Prework: Filipe_Challenge1]]></title>
            <link>https://medium.com/@filipenbranco/using-public-transports-will-get-easier-ironhacks-prework-filipe-challenge1-5be47b1871ca?source=rss-8114cccfb584------2</link>
            <guid isPermaLink="false">https://medium.com/p/5be47b1871ca</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Filipe Branco]]></dc:creator>
            <pubDate>Thu, 11 May 2023 20:05:56 GMT</pubDate>
            <atom:updated>2023-05-19T22:44:51.289Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Using public transports will get easier”</h3><p><em>This is an article for Ironhack’s UI/UX bootcamp pre-work.<br>Challenge 1: Design Thinking</em></p><p>If you’re not a regular user of public transport systems, are new to a city or are travelling abroad, knowing how to get around quickly becomes one of the major challenges one has to face when there is the need to get somewhere.<br>Long gone are the days of using maps the size of billboards and city guide books, although still selling and used, can become obsolete real fast if they don’t get regular revisions. In contrast, almost everyone has some sort of smart device, most likely a mobile phone, and there are plenty of apps that can help you find your bearing around town.<br>Still, none of them solves one of the bigger issues commuters face — buying tickets for their journey — and this is where Cittymapper comes to the rescue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*5C92-UHT59MmnvLXt-Zidw.png" /><figcaption>Source: Citymapper website</figcaption></figure><h3>What is Citymapper?</h3><p>Citymapper is a transportation app that provides real-time information and directions for public transit, cycling, and walking in cities around the world. The app uses data from multiple sources, including public transit systems, bike-share programs, and ride-hailing services, to help users find the fastest and most efficient routes to their destinations. Citymapper also offers features such as live updates on service disruptions and crowdsourced information on local events and points of interest. The app is available for free on iOS and Android devices.</p><h3>What is the Challenge?</h3><p>Knowing how to get from point A to point B is just the first step when planing a trip in any town, and all apps, either Citymapper or it’s competitors like Google Maps or Moovit give satisfactory results. The problem starts when you want to get aboard — you need a ticket, or probably two — so, where do you go to buy them? What do you do if there is no vending boot nearby? What if there’s a vending machine but it is broken, or if the interface is in a language you don’t understand? What if it only accepts cash but all you’re carrying is your bank card?</p><h3>Empathize</h3><p>After conducting a couple of interviews, it was clear that buying tickets for transports, locating stops and knowing transport times were the major pain points travellers faced, and not having a simple and unified option to solve all these issues, sometimes had pushed them to use other, more expensive ways to travel around, because they were simpler and faster. Most just used Google Maps (and also Apple Maps for iOS users) and didn’t knew about Citymapper or other similar apps, that already solve some of the problems.</p><h3>Ideation and prototype</h3><p>Building on the answers given by the interviewed, I sketched a simple mind map highlighting the choices they made, and concluding that in order for them to use the service it had to be a simple process that wouldn’t require much taught beyond the obvious choices, so I discarded the idea of validating/finishing the purchase requiring the user to go to a vending boot or vending machine (queuing and non working machines were issues pointed out), and fused the other two (pre-paid wallet and in-app purchase) because they can work simultaneously given user choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vtM9LgDrTT--vZL5uVgtw.png" /><figcaption>Ideation phase — Mind map based on user interview responses</figcaption></figure><p>All users preferred a unified ticket for the whole journey (the ‘one ticket to rule them all’ approach) instead of individual tickets in case of multimodal trips, so I chose only this path for simplicity sake, leaving out for a more extended user research the future implementation of individual purchases. This option also adds a layer of complexity to the project because different companies may have incompatible validation systems, and surely it would have to be some kind of business deal between Citymapper and the transport companies, but that is beyond the scope of this exercise. They also highlighted that they would prefer that both payments and ticket management could be done inside the app, not needing any other 3rd party services to complete the tasks. The downsides identified, were not having internet connection to either buy or retrieve the purchased tickets when needed or if the phone battery died out, so having an option to buy in advance, store offline and share trip/tickets to other users are features that must not be neglected.</p><figure><img alt="Prototype phase — Sketch detailing the ticket buying option" src="https://cdn-images-1.medium.com/max/1024/1*TGA-pwaF_Yvl5cHbzVXY0A.jpeg" /><figcaption>Prototype phase — Sketch detailing the ticket buying option</figcaption></figure><h3>Conclusion</h3><p>This exercise proved to be more complex than initially expected. There are so many variables one has to account for, that you can easily lose track of what your final goal is if you don’t stick to the procedures for each phase. If you skip a step, most likely you will end up with a mess that you won’t be able to sort effectively.<br>Conducting interviews was fun, but knowing which are the right questions to ask is a skill that needs to be repeated to be perfected. Also, I think my questions could have been a bit more open, because sometimes I had to make additional questions derived from the first one to have a broader answer.<br>Each phase requires different approaches, and if you let yourself go, you can easily fall into a rabbit hole by the sheer number of options you can have in each one. Although this was a solo task, I believe interdisciplinary teams play a major part in UX research, given that the different skills and backgrounds can bring lots of varied inputs that will ultimately benefit the end user. Overall it was a very insightful exercise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5be47b1871ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>