<?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 André Rui Moreira Pires on Medium]]></title>
        <description><![CDATA[Stories by André Rui Moreira Pires on Medium]]></description>
        <link>https://medium.com/@andrermpiresbiznet?source=rss-f329ed5c5e04------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*UqcIhk5lw7zhwmeP</url>
            <title>Stories by André Rui Moreira Pires on Medium</title>
            <link>https://medium.com/@andrermpiresbiznet?source=rss-f329ed5c5e04------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:57:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrermpiresbiznet/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[Let it Vibey you…]]></title>
            <link>https://medium.com/@andrermpiresbiznet/let-it-vibey-you-b7af05bc829a?source=rss-f329ed5c5e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7af05bc829a</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[welness]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <dc:creator><![CDATA[André Rui Moreira Pires]]></dc:creator>
            <pubDate>Fri, 05 Apr 2024 18:48:52 GMT</pubDate>
            <atom:updated>2024-04-07T17:13:00.593Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ironhack’s UX UI Project</h4><h3>Wellness app</h3><p>How can we approach the challenge of creating an app focused on such a broad subject like wellness while also emphasizing the importance of being unique, aesthetically pleasing, and sensitive about the content?</p><figure><img alt="Vibey’s App" src="https://cdn-images-1.medium.com/max/1024/1*JMOWM3J_ky4IA-mDVcfxhA.png" /><figcaption>Vibey App</figcaption></figure><h4>The challenge</h4><p>Design a mobile or web app from scratch that tackles a particular wellness-related problem.</p><p>Mandatory:</p><ul><li>Users set up their profile to include important information relevant to their goals.</li><li>Users set goals and track their progress.</li><li>Users receive feedback from the system (error).</li><li>Target a specific device (A native iOS App, native Android App or a responsive web app).</li></ul><p>I <em>must say, my group didn’t follow </em><strong><em>the first </em></strong><em>mandatory rule and </em><strong><em>I will explain why</em></strong><em> in a moment! We had a strong reason for this “defying” rules here. And of course, it was approved by the teaching staff.</em></p><p>Since our cohort had some sub-subjects at our disposal for deciding, after an <strong>extensive brainstorm</strong> we went for one direction: <strong>Create a stress-relief app</strong>.</p><p>The lean survey was our first step:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2P-lLM8nTna7idFcadGFhQ.png" /><figcaption>Lean Survey</figcaption></figure><p>For the <strong>secondary research</strong> we gathered information on well-being related to stress using many different websites. We reviewed articles, reports, and resources to gain insights into best practices for managing stress and promoting well-being across diverse populations and then we clustered our findings.</p><p>With this information gathered, we came up with the questions <strong>for our survey.</strong></p><p>After understanding what questions we wanted to ask, I sent the link to several people. It was the first time applying this quantitative research to my design thinking.</p><p>While we were waiting for a good amount of answered surveys, we moved to the <strong>competitor analysis</strong>.</p><p>Unlike my previous project, this time, after conducting competitor analysis, it became clear to us what we wanted. This process provided us with more guidance because it helped us understand the problems that calm and anti-stress apps face, allowing us to address them and make a difference. We encountered <strong>very cluttered</strong> apps with <strong>complex UIs</strong>, <strong>excessive feature</strong>s, and heavy reliance on payments/subscriptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0N1b_IR3hYocJSS8a9K9Uw.png" /><figcaption>Competitor Analysis</figcaption></figure><p><em>Side note: We conducted the Competitor analysis while we were waiting our surveys to be answered, it turned out to be a very smooth and easy going process to be honest.</em></p><p>It was now time to extract results from our survey, and it was quite revealing! I won’t go through all the questions we had in our survey because they’re not that relevant; the results speak for themselves, as shown below. This stage determined that we would be focusing on a <strong>music-based app</strong>. <strong>Music is indeed the most commonly mentioned relaxation exercise!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hz_B62Z4AmSJw2iJZMaJlw.png" /><figcaption>Survey results</figcaption></figure><p>The survey also revealed that people prefer to <strong>receive suggestions</strong> rather than having to search for specific relaxation exercises or music.</p><p>So, based on this information, <strong>Marta was created.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qm7h-c-YQu0QLPYiPqpqSQ.png" /><figcaption>User Persona: Marta</figcaption></figure><h3>Marta needs an easy-to-access app that allows her to practice stress-relief techniques.</h3><h4>So how could we help Marta?</h4><p>Because we had music as the top 1 priority, we wanted Marta to have a place where she could practice stress-relief techniques.</p><p>For our solutions we thought about having an AI buddy or coach that would ask questions to Marta like “How are you today?”, “Do you like this music?”, “Do you want to move a bit?”. We also thought about having motivational “pop ups” or reminders integrated with a fitness tracker and features like having the ability to choose duration of music, a chatbot and also a voice control system.</p><p><strong>But it was during our Low-fi sketching that we understood that we wanted to get away from pop-ups and reminders and start turning our app into a complete zen and stress-relief environment</strong>. So this is where the <strong>radio</strong> concept approach started to make sense for us. We wanted to have this very <strong>simple and clean app</strong> that Marta would use with pretty much “one click action”. No pop-us, no reminders, <strong>no questions at all</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsvaiZds6UgaZGln_Xo8-A.png" /><figcaption>Lo-Fi Sketching</figcaption></figure><h3>Vibey</h3><p>With this idea on our minds, and taking into consideration our User persona and also the Competitor Analysis (with these apps being very busy and full of features), we decided that our Mid-fi should look precisely the opposite (again, <strong>clean and simple</strong>).</p><p>We came up with the name <strong>Vibey</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*ECjbOTSGmLOVQZXncHuSfA.png" /></figure><p>“<strong>Vibey</strong>” is a word that encourages someone to relax and go with the flow of the moment, allowing themselves to fully immerse in the vibe or atmosphere of their surroundings. <strong>A brand</strong> that suggests embracing the mood or energy of the situation and enjoying a stress-relief processes. It’s a reminder to be present and to let yourself be carried away by the positive vibes!<br>In other words, our app!</p><h3>Mid-Fi Iteration</h3><p>After the User testing, we were left with insights regarding some confusion about the home button in the navigation bar. We had a person saying that “It wasn’t pretty clear that The Vibey button would lead to the homepage”, so we added a gradient. Also for this iteration stage , we decided that it would be better to have dots instead of the swipe bar that we previously had because it shows a more clear separation between the stress levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Q1kmZPdVj2pGxq8u6K19Q.png" /><figcaption>Examples of Mid-Fi screens during iteration process</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O57lyJtqXaDMakKo_33g1A.png" /></figure><p>Our moodboard elements represents:</p><p>. Serene</p><p>. Peaceful</p><p>. Uplifting</p><p>. Refreshing</p><p>. Inspiring</p><p>. Zen</p><p>. Radio concept</p><p>From here we extracted colors and relaxing calm elements, resulting in our style tile. Also the logo that we though it would inspire positive and uplifting vibes.</p><p><em>Side note: Like previously stated, it was mandatory to choose between different target devices. The native iOS App was the one for us.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1mXQm14hisWYqb_LT--7pA.png" /><figcaption>Examples of Hi-Fi screens during iteration process</figcaption></figure><h3>HI-Fi iteration</h3><p>For this iteration part we applied insights from the User Testing regarding the size of the media buttons. We made them bigger! We added the color and numbers to make the stress levels even more clear and animated elements to be a more dynamic experience for Marta.</p><p>We also introduced an <strong>accessibility mode </strong>to ensure that individuals with disabilities or impairments can use the app effectively. It enhances the usability and inclusivity of the app. The animated elements stop and a <strong>dark screen</strong> takes place. Also, the <strong>navigation icons change</strong> to a more universal type <strong>(</strong>as<strong> </strong>showed bellow).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYBrPzlCcYvWZGX0LnvFNA.png" /><figcaption>Accessibility mode</figcaption></figure><h3>Final Hi-Fi</h3><p>I did mention a broken rule at the beginning right? The explanation is simple: Vibey it’s all about having this nice, clean &amp; simple interface where users like Marta don’t have to think about anything but themselves. The profile didn’t make any sense for us to apply. We actually built a screen for that purpose. It just didn’t felt right!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZf2dAA_i2nclCNPWuEn6g.png" /></figure><h3>How does Vibey work?</h3><p>1- Open the app (a loading animated screen will appear);</p><p>2- Select your stress level from 1 to 7;</p><p>3- Music starts to play right away with animated elements;</p><p><strong>That’s it!</strong></p><p>Additionally:</p><ul><li>Users can activate accessibility mode by toggling the top right button;</li><li>Can track the top 5 music genres by accessing “History” (“Statistic” when accessibility mode is enabled)</li><li>Music can be saved and accessed using the “saved” button.</li></ul><p>The app is designed to evolve and adapt based on User interactions. As users engage with the app, it will gather feedback and data to learn their preferences over time.</p><h3>Key learnings</h3><p>A lot of wellness apps suffer from <em>featureitis </em>and are doing way too many things. This inspired us to create an app that is extremely simple and straight to the point.</p><p>There were times during the project that we wanted to make Vibey a bit more complex and we had some issues along the way precisely because it’s simplicity but:</p><blockquote>“Less is more.” -Mies Van Der Rohe, 1886.</blockquote><blockquote>“Make things as simple as possible but no simpler.” -Albert Einstein, 1879</blockquote><h3>Prototype</h3><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%2FPYbNUuAByUEtHyXavyKWcf%2FPower-Rangers---P4-Wellness-Project--%257C-Figma-Design-File%3Fpage-id%3D2405%253A656%26type%3Ddesign%26node-id%3D5355-12319%26viewport%3D797%252C451%252C0.08%26t%3DpV0GfHoZs0J5YY3n-1%26scaling%3Dscale-down%26starting-point-node-id%3D5355%253A12324%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FPYbNUuAByUEtHyXavyKWcf%2FPower-Rangers---P4-Wellness-Project--%257C-Figma-Design-File%3Fpage-id%3D2405%253A656%26type%3Ddesign%26node-id%3D5355-12319%26viewport%3D797%252C451%252C0.08%26t%3DpV0GfHoZs0J5YY3n-1%26scaling%3Dscale-down%26starting-point-node-id%3D5355%253A12324%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F1cacb3eb-ca6a-4e5a-b723-7fc449b8350a%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/a86cb060dbc310276ad79a5705f9464d/href">https://medium.com/media/a86cb060dbc310276ad79a5705f9464d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7af05bc829a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revolut Redesign Case Study: Enhancing User Experience through Heuristic-Based Improvements]]></title>
            <link>https://medium.com/@andrermpiresbiznet/revolut-redesign-case-study-enhancing-user-experience-through-heuristic-based-improvements-e5b7b68ee074?source=rss-f329ed5c5e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5b7b68ee074</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[revolut]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[André Rui Moreira Pires]]></dc:creator>
            <pubDate>Sat, 23 Mar 2024 19:37:05 GMT</pubDate>
            <atom:updated>2024-04-25T21:16:01.895Z</atom:updated>
            <content:encoded><![CDATA[<p>For this assignment, we were tasked with individually redesigning an app. However, as is typical at Ironhack, it’s never that simple. Situations are often more complex than they initially seem. We were required to select a highly popular app with thousands of downloads!</p><p>After spending hours to choose an app, I finally decided on Revolut<em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vD_dnV66x5XALMg1Ig01Xw.png" /></figure><h3>Introduction</h3><p>Revolut is a popular financial technology company known for its innovative approach to banking and personal finance management. However, despite its success, the user experience of the Revolut app could be enhanced through a redesign focusing on improving adherence to Nielsen’s 10 Usability Heuristics.</p><h3>Heuristics &amp; Solutions</h3><h4>Recognition rather than recall:</h4><p>The first heuristic violation that I found was relative to the simple action of show/hide balance. This “process” is very confusing and users may struggle to find the features they need. This can lead to frustration and a poor User experience.<br> To switch on/off this setting, Users must go to the top left circle showing your picture or initials → Security &amp; privacy → Hide balances → tap on the toggle. <br>It violates the “Recognition rather than recall”.</p><p><strong>Solution</strong></p><p>The User doesn’t have to remember this entire process just to do something so simple and common.<br> So I added a show/hide button next to balance. Much better!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*eK1rmrmMBQGIPSyNeRaQ7A.png" /><figcaption>Before &amp;after</figcaption></figure><h4>Match between system and the real world:</h4><p>The APP “Accounts” include savings, and other currency in the same category. It violates the “Match between system and the real world” heuristic. Savings are associated with a money box, treasure chest or a vault (something apart from the other type of money). The APP fails to separate these two concepts by group everything in the same feature or component.</p><p><strong>Solution</strong></p><p>I added to the navigation bar a “vaults” icon for the user to separate the type of money “savings” from the main account general type of money. This is important to create a more clean and organized APP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*fp2_op4IxXUBB9cr58nNdw.png" /><figcaption>Before &amp; after</figcaption></figure><h4>Consistency and standards:</h4><p>When adding money to the account, it shows all the different cards used. <br>It can be a tedious process to eliminate all the cards added, since the majority of them are virtual cards with one-time purpose. The User has to click the “info” icon in order to access a card’s details and then press “Delete”. It violates the “Consistency and standards” heuristic.</p><p><strong>Solution</strong></p><p>The User is customized to have a faster and more intuitive way of a deleting process, so I made a swipe to left action for a much faster and intuitive way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKEH8MjSMtJFZUmurH6F7Q.png" /><figcaption>Screen 1 &amp; 2 showing the process to delete a card. Screen 3 shows my solution</figcaption></figure><h4>Aesthetic and minimalist design:</h4><p>In the “lifestyle” section of the navigation bar, in the“Discover more” feature, the User has to scroll down close to 100 large images to get to the bottom of the page. <br>The APP fails to give a fuctional aesthetic, instead it presents an overwhelming amount of images with the biggest issue being the scrolling due to the large sized images<br>It violates the “Aesthetic and minimalist design” heuristic.</p><p><strong>Solution</strong></p><p>The User should be able to avoid scrolling down extensively so I redesigned the screen as a grid to drastically reduce the “infinite” scrolling making everything more appealing while ensuring they remain easily visible and legible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*d7FMEEvDOkgBp70-4Dc8cA.png" /><figcaption>Before &amp; after</figcaption></figure><h4>Flexibility and efficiency of use:</h4><p>The navigation buttons offer two options for the same action. Here, the icon “Invest” is related to stocks and commodities, but it could also include “Crypto” feature, making a simpler navigation menu. It violates concepts familiar to the User.</p><p><strong>Solution</strong></p><p>I combined navigation icon to lead the User to all investments instead of having 2 separated icons for the same action.</p><p>The User will now access “Invest” in the navigation bar and be led to a screen where the type of investment can be selected (in the now added top section): Stocks, Crypto and Commodities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NkBq__LkMjZNZRYNManu8w.png" /><figcaption>Left side diagram represents the prosses to get to the Hi-fi solution</figcaption></figure><h4>Conclusion:</h4><p>By incorporating heuristic-based improvements into the redesign of the Revolut app, I think that some significant enhancements have been made to the user experience. These changes not only address existing usability issues but also align the app more closely with user expectations and mental models, leading to a more intuitive, efficient, and satisfying financial management for Revolut users.</p><p>That being said, I did struggle at some stages. It’s not easy to find things that could be modified or upgraded in such a huge app!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5b7b68ee074" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Project 2: E-Commerce Website]]></title>
            <link>https://medium.com/@andrermpiresbiznet/ironhack-project-2-e-commerce-website-2d294a2e7f92?source=rss-f329ed5c5e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d294a2e7f92</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[André Rui Moreira Pires]]></dc:creator>
            <pubDate>Sun, 17 Mar 2024 23:58:43 GMT</pubDate>
            <atom:updated>2024-04-25T20:55:39.687Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Challenge</h3><p>In this project, we were assigned to use design thinking methods to solve a real-world business challenge. This involved meeting with the business owner, understanding the users’ perspective, identifying the main problem, generating ideas, creating rough sketches of our solutions ( Low-fi wireframing), refining them further into Mid-fi designs, and finally, producing a polished Hi-fi version alongside with a prototype.</p><h3>Stakeholder Selection</h3><p>As a group of three, each one of us had to propose at least one business to conduct the project.<br>We decided to go with the stakeholder Alexandre, since he’s someone with a closer relationship with one of us in the group.</p><p>Alexandre owns “O Principezinho”, a graphic services and print shop company based in Entroncamento, a small town in Portugal. Customers can ask for various print services such as items for children’s parties, visit cards, flyers, tickets, stickers etc. Although it offers a huge amount of services, the core business mostly targets <strong>wedding stationery</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUQVkguKL4duCRyzETXuWg.png" /></figure><p>After our stakeholder interview (very informal and fruitful), my group was left with precious insights about the business and what could be done to improve Alexandre’s website.</p><p>We were able to understand that customers didn’t reach Alexandre’s company services via website but from other means (mainly Facebook). This insight was crucial to our entire project since we immediately though about addressing this issue by adding a <strong>quote request feature</strong>.</p><p>We undertook a competitor analysis to gain insights into how other companies operate. Surprisingly, this process didn’t provide us with as much information as we had hoped. While we did learn about some unique features of our competitors, overall, it wasn’t as helpful as we had anticipated.</p><h3>Secondary research</h3><p>It was time to start conducting with the secondary research. We discovered some common issues couples face when buying <strong>wedding stationery</strong>. We looked at different sources like reviews, articles discussing societal pressures, online posts about invitation prices, and forum conversations about too many options.</p><p>We conducted interviews with five individuals who were either married or in the process of planning their wedding stationery. These interviews provided valuable insights, allowing us to connect with them on a deeper level and gain a better understanding of their primary challenges and objectives.</p><p>With this in mind, it was now time to create our user persona…</p><h3>Meet Maria, our User Persona!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUwvr3plsQTRPvFP1oYD9A.png" /></figure><p>Maria’s objectives, requirements, and challenges directly resonated with the insights we gathered from our generative research, primarily through user interviews. This alignment allowed us to empathize more profoundly with our users. Moving forward, we focused on designing features that catered to Maria’s needs, ensuring her influence remained prominent throughout the project.</p><h3>The Problem Tree</h3><p>Seeking to understand the main challenges that couples had to face during the process of choosing their wedding stationery. We hoped to get some good</p><p>After we gather our individual thoughts this was our <strong>final draft for the Problem Tree</strong>:</p><p><strong>Sub-problem 1</strong><em>: </em>Difficulty finding the appropriate stationery.</p><p>First, we found out that people struggle to find wedding stationery due to the immense number of options and lack of organization when browsing some websites.<br>For this particular sub-problem we added 2 <strong>sub-sub-problems:</strong></p><ul><li>The amount and variety of options makes it difficult to choose a wedding stationery;</li><li>The amount and extent of the customization options available is not sufficient.</li></ul><p><strong>Sub-problem 2</strong><em>: </em>Lack of transparency regarding the budget for stationery items.</p><p>Next, we learned that some people were not able to have a clear idea of the amount they would be spending immediately after they choose their stationery since the websites didn’t provide that kind of imidiate information.</p><p><strong>Sub-problem 3</strong><em>: </em>Concerns about meeting time constraints while obtaining and organizing stationery supplies:</p><p>The idea of the items not arriving at the appropriate moment was a main concern but not having the idea when their stationery would arrive was an ever bigger problem and constraint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u8liWe0PXec-lmzgXmSC7g.png" /></figure><h3>Ideate</h3><p>At this point we started to extract important insights from all our research and organize our ideas.</p><p>Given the variety of potential solutions available, it became necessary to decide which ones to focus on. To help us with this task, we turned to the <strong>MoSCoW</strong> method.</p><p>The website must have:</p><ul><li>An always visible tracker to understand how much each stationery will cost, while selecting the different options;</li><li>A feature that would show an estimation on time on sending;</li><li>Implement a field dedicated to customer own design.</li></ul><p><strong>User flow</strong></p><p>Having in mind the importance of narrowing down choices and help the user choose the stationery items, we introduced 4 different ways for the user to pick: ”Take a quiz”, “upload reference photos”, “browse portfolio” and a submit button if the user already had a own-design.</p><p>After an insightful conversation with the teaching staff we wanted to pick <strong>wedding invitations</strong> as our subject to be included in our prototype and testing.</p><p>At this stage of the project we also decided to <strong>pick the QUIZ path as a User flow</strong>. This way, the user get suggestions based on the selected preferences.</p><p>With our priorities defined, we went for the Task and User flow. This process was long and laborious but we came up with a very good and clear flow for our next step (Low-fidelity).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_ONtVH6-kYt3iuvPa1KPA.png" /><figcaption>User flow</figcaption></figure><h3>Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aUmLGQBLVG9YxbSJXunBXg.png" /><figcaption>Examples of Low-fi and Mid-fi screen evolution</figcaption></figure><p>By this stage, we understood that the Lo-fi was crucial for the structure of what would be our final wireframing. For example, we decided to maintain the left side separation to show the User the steps of the entire process</p><p><strong>Iteration</strong></p><p>From our interviews we had some good insights for the Iteration. For example we had a person saying that the process steps on the left side were a bit confusing. So we added some sub-steps to be more accurate. We also added a zoomed image for the user to see the chosen card better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YOSrM8mNPLrrdGqOEIZMWw.png" /><figcaption>Iteration 1</figcaption></figure><p>The same went for the personal information and customization. The fields were not so well organized (for example the couple names). Also regarding the right part of the screen for the estimated cost and predicted delivery, we decided to shrunk it so the screen would be cleaner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WPQoi53tmhMjZnhsUgsyYg.png" /><figcaption>Iteration 2</figcaption></figure><p><strong>Moodboard &amp; Styletile</strong></p><p>During this part of the project I had personal issue that made me unable to work during the weekend and Monday (the day before the presentation).</p><p>Joana and Leonardo did a great job during this time and I’m grateful to be in a group with them, they were comprehensive and hardworking. We were reduced to 2 people and they put up extra work for all of us be able to have a presentation prepared on Tuesday.</p><p>The floral and herbal motifs from bouquets and reception gardens were used as inspiration for colors and images. The aim was to select icons and a typeface that embodied an informal yet elegant aesthetic.</p><p>Additionally, a redesign of the company logo to create a simpler and more effective design was conducted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nk5iJtbrBK6cn_LWwzmztQ.png" /><figcaption>Mooboard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ECcwr7gFY1mS5AAefNpMcw.png" /><figcaption>Process of color extraction and proposals</figcaption></figure><p>The <strong>styletile</strong> emerged from our previous process. We decided to go with a subtitle greenish theme since it made sense for us always having in mind a wedding theme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qABZZUpkrvcKvLAIQTMzsg.png" /><figcaption>Examples of Mid-fi to Hi-fi screen evolution</figcaption></figure><h3>The Final Product</h3><p>As a requested part of this project, my group made a responsive in-all screens version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rbVT8Es5eD6sjVN_EzZc4g.png" /></figure><p><strong>Prototype</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FwtUxlsyr6Z0XEMDTsGU6aG%2FUntitled%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D1-3%26viewport%3D48%252C343%252C0.34%26t%3DtHFElfHQ01zVicbw-1%26scaling%3Dscale-down%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FwtUxlsyr6Z0XEMDTsGU6aG%2FUntitled%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D1-3%26viewport%3D48%252C343%252C0.34%26t%3DtHFElfHQ01zVicbw-1%26scaling%3Dscale-down%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fblank.png%3Fheight%3D1%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/715db2b7a3e282577a6527006c7b544a/href">https://medium.com/media/715db2b7a3e282577a6527006c7b544a/href</a></iframe><h3>Next steps and and conclusion</h3><p>Our project was coming to an end, and the last 2 parts included a reflection of what would be our next steps if we were already working for a client.<br>we thought it was important to present our progress and finished prototype to the stakeholder, add the same feature to other stationery items and improve the website itself.</p><p>Once again I was lucky to work with 2 people with diverse skill set, very effective communication, shared vision, respect and flexibility. I take this part of this case study to <strong>thank Leonardo and Joana</strong> for taking care of everything while I wasn’t able to be present.</p><p>It was a challenging from the start until the last day of presentation. I would say it was a good preparation for the <strong>real world</strong> type of work that I aim for after the bootcamp!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d294a2e7f92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In search of the path to culture. Ironhack’s project 1]]></title>
            <link>https://medium.com/@andrermpiresbiznet/in-search-of-the-path-to-culture-ironhacks-project-1-e1c28301cea3?source=rss-f329ed5c5e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1c28301cea3</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[André Rui Moreira Pires]]></dc:creator>
            <pubDate>Sun, 03 Mar 2024 16:09:27 GMT</pubDate>
            <atom:updated>2024-03-04T12:21:43.205Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*VVAqkTqbnF77CD_OFJESTQ.png" /></figure><h3>Overview</h3><p>For our first project at <em>Ironhack’s bootcamp</em> we were presented with the wicked problem about the crisis that museus and cultural heritage are suffering since the 70’s.</p><p>Our challenge was how can we aid museums and other public institutions in connecting people and fulfilling their mission to preserve and activate cultural heritage in the 21st century.</p><h3><strong>Brainstorming</strong></h3><p>We immediately started to relate museus and cultural heritage to declining attendance. Reduced flow of people = crisis</p><p>Among other topics, we came up with some main ones:</p><ul><li>Prices</li><li>Lack of interest</li><li>There is no mystery</li><li>Lack of advertising</li><li><strong>Too many things to see — No clear route</strong></li><li><strong>Lack of interaction</strong></li></ul><h3><strong>No digital options</strong></h3><h3>Research planing and interviews</h3><p>We started to become more focused on <strong>“build the bridges between objects and people, for them to be enjoyed by citizens” (</strong>A quote from our Brief project). We were aiming to understand the lack of user engagement with museums and public institutions and identify the role of technology could have in improving this decline.</p><p>This led us to structure the key questions to conduct our interviews. When we finished the interviews I never thought this phase would be so interesting and enlightening because I would take forever to put into perspective certain aspects that people spoke.</p><p>To group our best insights from the interviews we used the affinity diagram. This gave us the opportunity to visualize our themes in an organized way.</p><p>It was now time to create our user persona.</p><h3>Meet Alex, our persona!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7iB5yChBtd8Ny7Rt1fX8mA.png" /></figure><p>Alex really wants to learn more by going to museums often. She loves interactive and fun experiences in museums, not just looking at things. It’s important for her to easily find her way and not get lost in museums. But sometimes, museums can be a bit boring for her, and she feels anxious with loud noises and lots of people. We want to make sure Alex enjoys her museum visits, learns a lot, and doesn’t feel bored or anxious.</p><h3><strong>Problem Tree</strong></h3><p>This was the time to understand the possible reasons why people don’t visit museums often. The main challenge was figuring out why some people feel uneasy about going to museums regularly. So we started digging into the different reasons behind this hesitation.</p><p>After we gather our individual thoughts this was our <strong>final draft for the Problem Tree</strong>:</p><p><strong>Sub-problem 1</strong><em>: </em>Anxiety triggered by loud noises and crowds.</p><p>First, we found out that some people get nervous because of loud noises and crowds in museums. A scenario with a lot of people talking and moving around (also children). This made us think about how we could make museums more peaceful and welcoming for everyone at the same time.</p><p><strong>Sub-problem 2</strong><em>: </em>Easily disoriented navigating museum exhibits with unclear layouts.</p><p>Next, we learned that some people easily get lost in museums because the layouts are confusing by walking around and not knowing where to go. We realized by now that this would probably be our main focus.</p><p><strong>Sub-problem 3</strong><em>: </em>Lack of interactive and immersive experiences</p><p>People also said they want more fun things in museums. They want to do more than just look at stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TefPyfq25GH6ZkxajQUmJA.png" /><figcaption>Source: <a href="http://www.portal365.org/">www.portal365.org</a></figcaption></figure><h3>Ideation</h3><p>At this point we started to extract important insights from all our research and organize our ideas.</p><p>Our group went for the crazy 8’s to figure out possible solutions for our sub-problems. Many things were put into perspective: Implementation of quiet zones/hours, offer exclusive events and gatherings for adults only, improve signage, personalized fun facts, offer VR experiences, interactive maps, etc.</p><p>This resulted in a nest of many mixed and varied ideas! That’s the reason for the name “<strong>Crazy </strong>8’s”!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tSM5HzezUUbaaa_H5B9ukg.jpeg" /></figure><p>With the disparity of possible solutions, it was now time to prioritize our favorites. We went for the <em>MoSCow </em>method to figure this out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EM-mqGFFlc2TLak0KcFugQ.png" /><figcaption>Feature Prioritization (MoSCoW Method)</figcaption></figure><h3>User Flow</h3><p>Having our solutions organized by importance, the user flow came up. Our vision was an APP that would have <strong>suggested paths</strong> filtered by an initial <strong>survey</strong>, followed by a navigation system (<strong>interactive map</strong>) with <strong>QR code</strong> technology to see more information and detail about exhibits. The chosen path would also include a selected playlist for the entire tour.</p><p>One side note: We also wanted to include a search option for a more customized route.</p><p>This was (for me at least) one of the most important steps in all this process. By now, I had a more clear image of how our app would be. What came next, was my favorite part of the project: Wireframing.</p><h3>Low-Fi and Mid-Fi Designs</h3><p>For this part of the project we made some drawing/sketching of our ideas regarding on how interface would behave.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVjCaJJLV3cX4yRguYuUTg.jpeg" /><figcaption>My initial Lo-fi</figcaption></figure><p>From the Low-fi we went for the Mid-fi wireframing. At this stage we added real information as required. This gave us a more clear overview of the APP and would also be crucial for the concept/usability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*UdOndtcrrSlgxuUl5w4y3g.png" /><figcaption>Mid-fi wireframe examples</figcaption></figure><h3>Concept/Usability Testing</h3><p>An extremely important and interesting point that I learned during the testing of our concept was the fact that we didn’t need many interviews to understand essential points to change in our wireframing.</p><p>For example we had a frame exclusively to end the route. This generated a lot of doubt with only one person interviewed. When analyzing this issue, we decided to <strong>simply delete</strong> this frame and <strong>add a finish button</strong> to the previous frame.<br>This culminated in a more intuitive and simpler interaction for the user.</p><p><strong>Here’s the link to our prototype:</strong></p><p><a href="https://www.figma.com/proto/67SiWRCwNfoMVHT4EAv7Br/Elephant-Seals-%7C-Figma-P1?page-id=901%3A2076&amp;type=design&amp;node-id=4449-1297&amp;viewport=711%2C323%2C0.29&amp;t=2sK8E64tvaZvmveE-1&amp;scaling=scale-down&amp;starting-point-node-id=4449%3A1297&amp;mode=design">https://www.figma.com/proto/67SiWRCwNfoMVHT4EAv7Br/Elephant-Seals-%7C-Figma-P1?page-id=901%3A2076&amp;type=design&amp;node-id=4449-1297&amp;viewport=711%2C323%2C0.29&amp;t=2sK8E64tvaZvmveE-1&amp;scaling=scale-down&amp;starting-point-node-id=4449%3A1297&amp;mode=design</a></p><h3>Conclusion</h3><p>I was lucky to work with 2 people with diverse skill set, very effective communication, shared vision, respect and flexibility.</p><p>The final result is a design that considers everyone’s input and focuses on what users need. It shows that when we work as a team, listen to each other, and stay flexible, we can create something that works well for everyone.</p><p>It was my first bootcamp project and there are some things I will try to do differently already, like the presentation of the project for instance (although time was against us). Everything is new for me and it has been quite the journey!<br>I hope I continue to learn new things and try to do my very best every day!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1c28301cea3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework Challenge 2: Wireframing]]></title>
            <link>https://medium.com/@andrermpiresbiznet/ironhacks-prework-challenge-2-wireframing-b97e61da8f86?source=rss-f329ed5c5e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/b97e61da8f86</guid>
            <dc:creator><![CDATA[André Rui Moreira Pires]]></dc:creator>
            <pubDate>Tue, 06 Feb 2024 15:51:39 GMT</pubDate>
            <atom:updated>2024-02-06T15:51:39.490Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*sOt-xi_suo_NFE07E01Dig.png" /></figure><p>For this challenge I chose MB WAY app as I’m constantly using it to create temporary cards in order to shopping online as well as transfer money to friends, family and other occasions like buying a secondhand item from someone. I also use MB WAY to pay my groceries among other things.</p><h4>User flow</h4><p>I decided to work with the process of creating an online card using MB WAY.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4CGS-nXUe-wYVb1MSw55Cg.png" /><figcaption>User flow lo-fi</figcaption></figure><p>1- Access home page and select MB NET cards;</p><p>2- Choose unique purchase (one time buy);</p><p>3- Insert the amount of the card;</p><p>4- Add a card description;</p><p>5- Preview card;</p><p>6- Created card</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*vJndQRz6q5Ehp42jIjahtg.png" /><figcaption>Wireframing using Figma</figcaption></figure><h4>UI elements in this app</h4><ul><li>Buttons</li><li>Text fields</li><li>Breadcrumbs</li><li>Icons</li><li>Containers</li></ul><h4>The prototype</h4><p><a href="https://www.figma.com/proto/5UciGRRItz4QaSb2k6Ybgw/Untitled?page-id=0%3A1&amp;type=design&amp;node-id=11-1402&amp;viewport=1163%2C628%2C0.38&amp;t=Ub3LP5m11TlHpnSI-1&amp;scaling=scale-down&amp;starting-point-node-id=11%3A1398&amp;mode=design">https://www.figma.com/proto/5UciGRRItz4QaSb2k6Ybgw/Untitled?page-id=0%3A1&amp;type=design&amp;node-id=11-1402&amp;viewport=1163%2C628%2C0.38&amp;t=Ub3LP5m11TlHpnSI-1&amp;scaling=scale-down&amp;starting-point-node-id=11%3A1398&amp;mode=design</a></p><h4>Cnclusion</h4><p>I wasn’t expecting this challenge to be so… challenging! I had a hard time combining certain elements using Figma. The mobile proportions are something that I’m still having trouble with.</p><p>I’m sure that any of this issues that I had won’t represent any problem in the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b97e61da8f86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge 1: Design Thinking]]></title>
            <link>https://medium.com/@andrermpiresbiznet/challenge-1-design-thinking-eac7e15e5e9c?source=rss-f329ed5c5e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/eac7e15e5e9c</guid>
            <dc:creator><![CDATA[André Rui Moreira Pires]]></dc:creator>
            <pubDate>Sun, 28 Jan 2024 03:41:23 GMT</pubDate>
            <atom:updated>2024-01-28T03:41:23.281Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Ironhack’s Prework:[André]_Challenge1</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d49jNGFAqk6K03LlzDzBQw.png" /></figure><h3>Background info</h3><p>Citymapper is the subject of this challenge since I can’t access UrbanGo.</p><p>As a real-time information provider on public transportation, Citymapper’s App simplifies urban travel, making transportation more straightforward. Helps users plan efficient journeys, addressing transit disruptions and providing alternative routes when necessary.</p><p>Citymapper primarily operates in major cities worldwide, with a focus on urban areas.</p><h3>Main problems</h3><p>For this challenge, people aged between 26 and 35 were interviewed, covering the countries of Portugal, Spain, Sweden, UK and Germany.</p><p>Some of the pain-points that were taken into consideration were:</p><ul><li>Foreign language is a barrier: When purchasing tickets <br>it is noticed that issues related to the language itself and/or diction come to the top;</li><li>Alongside with foreign language, another negative aspect is the long queues and the amount of time spent buying physical tickets;</li><li>Efficiency: In some cases, information regarding delays or strikes is missing. This can lead to the person not being able to board and being misguided;</li><li>Visuals: Citymapper’s App can be tricky and not very friendly-user. Also the User Interface may not have taken older devices into consideration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*zJavQTzXn0cBVikm4_VFwQ.png" /></figure><h3>Solution</h3><p>Just like the very purpose of this challenge, it seems clear that the greatest urgency is the addition of a new function capable of offering a ticket purchasing system within the app.</p><p>When planning a journey, users can view available transit options, and upon selecting a particular route, the app provides a convenient option to purchase tickets directly. The button could be strategically placed within the app’s interface, allowing users to complete transactions securely through integrated payment methods.</p><p>Regarding the payment itself, one could buy tickets to anywhere within the city with the implementation of a rechargeable wallet or a direct payment.</p><p>After buying the tickets, a QR code would appear that could be read by the machines on every stage of the route. (Of course, this operating system would have to work smoothly with all the machines to pass through when taking a bus, metro/subway, electric bicycles, ferry, etc.)</p><p>The same example goes to people who will stay longer in a foreign country with the possibility of a public transport pass with different prices for different periods of time.</p><p>This would also come with an improved UI to facilitate all the process as well as giving a nice and clean experience.</p><h3>Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*etEW8fVG71FXhatbaFuyOQ.jpeg" /></figure><p>1- Set the destination point (there’s also an option to access the wallet in order to recharge it)</p><p>2- The different routes will appear. The user chooses one. It’s possible to check the price for all the combined tickets.</p><p>3- The user is guided to a payment section where it’s possible to pay with the in-app wallet or other payment options.</p><p>4- After complete the payment a QR appears and one can pass through all the different QR readers.</p><h3>Real upgrade</h3><p>I find important to mention that I was able to find an article saying that Citymapper will now include a subscription service, which gives unlimited access to various means of transport in the city of London:</p><p><em>“The price of the Citymapper Pass varies between 30 and 40 pounds per week, and includes buses, trains, bicycles, the metro and the Citymapper Ride ride-sharing service.</em></p><p><em>The service is available via a prepaid card and, if the user travels outside the area defined by the subscription, they will be charged on a pay-as-you-go model.</em></p><p><em>The cards are also available in digital format on your smartphone and payments can be made using Apple Pay or Google Pay.</em></p><p><em>This integration of ticketing and payments is a way to improve the convenience of the service, attract more users and have a broader view of daily routes, allowing greater personalization of services.”</em></p><blockquote>Source: <a href="https://supertoast.pt/">https://supertoast.pt/</a></blockquote><p>This is already an improved version of the app despite only existing in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v54QvgXKDV5BLCw8Paxexg.jpeg" /></figure><h3>Key things that I learned</h3><p>First of all I didn’t know that Citymapper existed. I always used google maps or haze as a guide. I found that people that I know is using this app very often to move within the city.</p><p>I also learned on how to <strong>start </strong>applying design thinking on an existing project. It was the first time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eac7e15e5e9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>