<?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 Joao Campos on Medium]]></title>
        <description><![CDATA[Stories by Joao Campos on Medium]]></description>
        <link>https://medium.com/@johnnyfields?source=rss-9bfcc3032411------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qi_ZJXtXSfgE3zwjVRF1uQ.png</url>
            <title>Stories by Joao Campos on Medium</title>
            <link>https://medium.com/@johnnyfields?source=rss-9bfcc3032411------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:53:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@johnnyfields/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[LineUp — Team Sports App]]></title>
            <link>https://medium.com/@johnnyfields/lineup-team-sports-app-f446009d0f95?source=rss-9bfcc3032411------2</link>
            <guid isPermaLink="false">https://medium.com/p/f446009d0f95</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[sports]]></category>
            <dc:creator><![CDATA[Joao Campos]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 13:03:55 GMT</pubDate>
            <atom:updated>2019-11-04T13:05:53.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsPUzJya1_z3wxRuAFUulw.png" /></figure><h3><strong>LineUp — Team Sports App</strong></h3><h4><strong>Ironhack UX/UI Bootcamp</strong></h4><p>For my last project at <a href="https://www.ironhack.com/en/locations/berlin">Ironhack Berlin</a> UX/UI Bootcamp I’ve chosen to focus on people playing <strong><em>team sports</em></strong>. More specifically, what kind of blockers or problems do they face. This was a two-week project where students were expected to develop an end-to-end project by implementing all that’s been learned throughout the Bootcamp.</p><h3>1. Why team sports?</h3><p>In the past, my group of friends and I used to play indoor football every Saturday and we had a WhatsApp group to organize it. Despite the fixed date, we would always struggle with one or two things: having enough players to play 5-a-side or find a pitch that was available at the time which was more convenient for us.</p><p>Although I moved to another country, I’m still part of this group and I still see my friends struggling with the same problem week after week. This got me wondering if we were the only ones and it sparked my interest in working towards a solution.</p><p>On the other hand, now that I’m settled in Berlin, I haven’t been able to keep playing football as my social group of friends is not interested in team sports.</p><h3><strong>2. UX Research:</strong></h3><p>I knew that being so close to the topic and my user could work both as an advantage and against me. It was important to let go of my assumptions while conducting my research and really being open to listen and empathize with the people that I reached out to.</p><h4><strong>2.1. User Surveys and Interviews:</strong></h4><p>With over 40 survey respondents and many personal interviews I was able to gather a lot of quantitative and qualitative information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jo1YxETA0Hv3sYYlPM4iuQ.png" /></figure><p>Below are some quotes taken from the User Interviews:</p><blockquote>“I’ve stopped being the organizer or taking part in it just so that I don’t go through all that trouble.”</blockquote><blockquote>“I know I need to start planning the games far in advance and recruiting people to avoid stressing out very last minute looking for the missing players.”</blockquote><blockquote>“I don’t find so many options for a female team (also I don’t know where to look).”</blockquote><blockquote>“I’m new in town, I don’t have friends to play with.”</blockquote><h4><strong>2.2. Affinity Diagram</strong></h4><p>Creating an Affinity Diagram has helped me clustering all the gathered information into groups and also to structure and organize my ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fml_jg0DLNrG-iCT" /></figure><h4>2.3. Define the problem to target</h4><p>My research has shown that the problems my friends and I face are common to many others. In short, the main blockers can be listed as follows:</p><ol><li>Finding a booking a venue that’s available;</li><li>Gathering the minimum number of participants to play a match;</li><li>Not having a network or knowing a group to play with.</li></ol><p>Although my research validated my assumptions, I still didn’t have clarity on which topic to pursue: finding a place to play or finding/organizing a group of people to play with. I knew I couldn’t explore both of them in a two-week span so I had to get back to my users once again.</p><p>Through a second shorter survey, I got the answer I was looking for. For my users, the hardest part to handle is finding <strong><em>People (70%).</em></strong></p><h4>2.4. User Persona</h4><p>Having covered the previous steps enabled me to have a clear understanding of the problem, the frustrations and goals of my users. My <em>primary</em> and <em>secondary</em> Personas originated from a combination of these factors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84hAGzmbqKKhOz9utmdekA.png" /></figure><h4><strong>2.5. User Journey &amp; User Stories:</strong></h4><p>Creating a User Journey for <strong><em>Chris</em></strong> that represented the actual steps he goes through when organizing a game was essential to empathize with him and also identify possible high-level touchpoints for my solution. Below we can see a possible scenario of Chris’ current journey when organizing a game with his friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*novVwstmLUR3BlVSPM6sUQ.png" /></figure><p>For <strong><em>Matt</em></strong>, no User Journey was developed.<strong><em> </em></strong>In his situation, he doesn’t even begin to organize a match or look for players, he doesn’t know where to start. For Matt, I’ve created a User Story to describe what he wants to accomplish.</p><blockquote><em>As an expat that moved to a new city I want to join sports games that are taking place near me so that I can play my favourite sports and connect with people.</em></blockquote><h3>3. Benchmark Analysis</h3><p>If most of the users I interviewed are facing the same problem, it was certain that others have already tried to solve it and also come up with their own proposed solutions. I had to get informed, learn more about them and, most importantly, understand why they were never brought up in my surveys and interviews (i.e. why people don’t seem to be using them).</p><p>This benchmark analysis would also help me set my solution apart from what’s already out there, both visually and in terms of the value proposition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yvA1Dt1DLIxX41eGe4VKkg.png" /></figure><p>I’ve come across an immense number of Apps and tried to evaluate each one and identify any trends or similarities:</p><ul><li>Excessive features that turn the product into <em>Feature creeps</em> (i.e. the product becomes complicated and difficult to use);</li><li>The previous point has a huge impact on learnability;</li><li>Inconsistent interface across screens;</li><li>Some UI elements could be refined.</li></ul><p>Also, I gave it a try to look at these Apps under the <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">Usability Heuristics for User Interface Design</a> defined by Jakob Nielsen. In my opinion, there’s room for improvement in some of these broad rules set by Nielsen. For example (#4) Consistency and standards; (#6) Recognizing rather than recall; and (#8) Aesthetic and minimalist design.</p><h3><strong>4. Information Architecture (IA)</strong></h3><p>Every website and mobile app wants to be as simple and easy to navigate as possible, there’s simply no point in aiming for the opposite. However, it’s much easier said than done and, for this project, this is where I’ve struggled, tested and iterated the most.</p><p>Through open and closed card sorting (and iterating) I’ve sorted and grouped the information and defined the <em>Taxonomy </em>in order<em> </em>to set the naming convention and vocabulary to be used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JnXnNp-grpQY8H0M" /></figure><p>In green, one can see “create new game” and “book a pitch” as these would be pivotal sections of my app to entice users to generate opportunities for others to play. The more games created the more value this app brings to its users.</p><h3><strong>5. Branding &amp; visual elements</strong></h3><p>As mentioned before, my solution had to stand out from its competitors. To achieve this, I needed a strong Brand Personality and to develop a UI that matched its attributes and tone.</p><h4><strong>5.1 Logo design and Brand Attributes</strong></h4><p>The word <strong><em>sports</em></strong> is immediately connotated with movement, adrenaline and being dynamic, energetic and bold. When we take it further into <strong><em>team sports</em></strong>, then we imagine pushing our limits, challenging our opponents and winning over them.</p><p>All of these terms and feelings are very powerful. LineUp brand attributes are a direct result of these associations: <em>Daring &amp; Energetic, but never Ordinary.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lzi8b1ieZWtSDQNisVRc1A.png" /></figure><h4><strong>5.2 Moodboard</strong></h4><p>My moodboard goes in the same direction as my attributes. One thing that fascinated me and is present in every single team sport were the lines. They define the boundaries and different sections of the fields/pitches. They’re very visible, geometrical, and with sharp edges and would inevitably influence my visual direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A2qcgtAk5mzIFroj" /></figure><h4><strong>5.3 Style Tile:</strong></h4><p>My style tile derives from that feeling of power and movement. With a bold typeface, dark background and white text and <em>electric</em> <em>green</em> elements for high contrast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sEbMgAPtbVdGD1Kk" /></figure><p>For better usability of the app, I’ve considered different Form field states, defined how error messages would look like (yellow), primary/secondary buttons that are very wide for impact and a progress bar that shows a different color and shape (bolder) as you advance.</p><h3><strong>6. Hi-fi Wireframes &amp; Interactive Prototype</strong></h3><p>After determining the visual elements and structure of my LineUp’s mobile app, I’ve created all the screens which are part of the happy flow I imagined for my Persona — <em>Chris</em>. Below are some of the screens I created. In them, we can see the elements present in the style tile coming together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G8_ISFL6uowziRPk" /></figure><p>LineUp and all the screens I created came to life with the help of principle, where I could already define the animations and micro-interactions, turning this prototype into an experience that really translates the real feel of actually using the App.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fwnm-WHFz6kA%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dwnm-WHFz6kA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fwnm-WHFz6kA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/08df286625d619b4990d2fc04dd6e856/href">https://medium.com/media/08df286625d619b4990d2fc04dd6e856/href</a></iframe><p>This flow consists of creating an account, exploring the app and creating a game that he can then share with his friends on WhatsApp and that other LineUp members can also join.</p><p>In this happy flow, one can also easily picture the happy path for my other persona, <em>Matt</em>, as he just has to create a profile and join any game near him.</p><h3><strong>7. Learnings and Next steps</strong></h3><h4><strong>7.1 Next steps</strong></h4><p>This was a case study developed academically. If LineUp was a real product, the next step would be to pair up with local pitches and venues and provide an online booking experience (commission-based). This could be the business model or one could ideate on paid accounts for users.</p><h4><strong>7.2 Learnings</strong></h4><p>I’ve touched upon a topic that has way more variables and complexity that I could have expected. To reach my final concept and MVP I had to stay as close as possible to the problem my research pointed as the most pressing one and a Design Principle that inspires me: <strong>“<em>Direction over choice”</em></strong>.</p><p>Many screens had to be dropped due to time constraints but also to keep LineUp as a fully functional but simple and intuitive product. With no over the top features or settings such as skill rating, rankings, gender differentiation, public/private options, etc. LineUp can be used by anyone who wants to play team sports.</p><p>That’s all folks! These two weeks were intense but so much fun at the same time. A perfect ending to nine long weeks of learning and becoming a UX/UI Designer!</p><p>Thank you for reading and clap if you like it. Cheers! ❤</p><p><strong>Now, go out and play!</strong></p><p><a href="https://www.linkedin.com/in/joaoclacampos/">João Campos - Ironhack - Berlin, Berlin, Germany | LinkedIn</a></p><p><strong><em>Important Notes: </em></strong><em>This project was developed with the purpose of exposing research results and solution proposal for a specific problem. For development and implementation, the icons should be developed from scratch for greater consistency.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f446009d0f95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tchaca Tchaca Party]]></title>
            <link>https://medium.com/@johnnyfields/tchaca-tchaca-party-6dc1b75cd519?source=rss-9bfcc3032411------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dc1b75cd519</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Joao Campos]]></dc:creator>
            <pubDate>Sat, 05 Oct 2019 14:19:46 GMT</pubDate>
            <atom:updated>2019-11-01T09:37:51.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-k-wlQGfKgEvfQHn6TzMTw.png" /></figure><h3>Responsive Microsite — Tchaca Tchaca Party</h3><h4>Ironhack UX/UI Bootcamp</h4><p>During Week 6 of our UX/UI Bootcamp at <a href="https://www.ironhack.com/en/locations/berlin">Ironhack Berlin</a>, we were challenged to pick an event and create a curated <em>Responsive Microsite</em> for it. At first, I was a little bit confused with the term Microsite so the first step was to actually understand what it stands for and what’s the purpose of having one:</p><blockquote>“A small auxiliary website designed to function as a supplement to a primary website”.</blockquote><blockquote>“A microsite is an individual web page or small cluster of web pages that act as a separate entity for a brand”.</blockquote><p>Now that I had my 101 on the basics, it was time to choose the brand or event to work on. After some deliberation, I’ve decided to move forward with <em>Tchaca Tchaca</em>, a birthday celebration that has been taking place since 2013. Although <em>Tchaca Tchaca</em> is a birthday celebration, it’s also become some sort of a brand and most anticipated event for the people that know my client (aka Bruno). Below, you can find a direct link to some of the poster designs that I’ve developed for previous <em>Tchaca Tchaca</em>’s:</p><p><a href="https://www.behance.net/gallery/78345197/Tchaca-Tchaca-Poster-Design">Tchaca Tchaca Poster Design</a></p><p>That said, this felt like the right move to make and I must admit that this has been the most pleasurable project that I’ve worked on during my bootcamp and I hope you enjoy reading about it.</p><h3><strong>1. Research and purpose</strong></h3><p>Why does <em>Tchaca Tchaca</em> need a website? It might seem irrelevant at first, everyone can use Facebook or a WhatsApp group to invite their friends to their party. That’s exactly the point, <em>Tchaca Tchaca</em> has always been about stepping aside from the obvious and going above and beyond to get people filled with anticipation about the event.</p><p>It’s also a way to make the invitation more personal and fun. It allows participants to have a better pre and post-party experience and, last but not least, enable new invitees to learn more about the party and its previous years.</p><h4><strong>1.1 Research</strong></h4><p>For my research, I’ve reached out to people that have attended previous <em>Tchaca Tchaca</em>’s to understand what was not so clear to them in past editions, what information they expected to see and have in advance and, lastly, how would they describe and rate <em>Tchaca Tchaca</em> as a party.</p><ul><li><strong><em>91%</em></strong><em> — About the party;</em></li><li><strong><em>82%</em></strong><em> — Gallery section to view/add photos;</em></li><li><strong><em>82%</em></strong><em> — Location and how to get there;</em></li><li><strong><em>73% </em></strong><em>— Playlist section (add/upvote songs).</em></li></ul><p>Although some of these were already sort of “mandatory” and “obvious”, others, such as the gallery and playlist, were a great finding that helped me tailor my proposal to what the users want.</p><p>For the host, other than getting suggestions for the playlist in advance and access the photos that the guests took during the event, the most important piece of information is the number of people attending. This is why the microsite should have a BIG focus on urging the invitees to confirm or cancel their attendance (<em>RSVP</em> button).</p><h3><strong>2. Brand and UI</strong></h3><p>Since the beginning of the project, given that I have created at least 5 posters for the party, I already had a good understanding of the tone and feel of the part. Nevertheless, My research has helped me consolidate this and stick to the vision that the users already have of the product.</p><h4><strong>2.1 Brand Attributes</strong></h4><p>Taking into account what was said in the previous paragraph, the brand attributes just came naturally. <em>Tchaca Tchaca</em> is <strong><em>Fun</em></strong> and <strong><em>Unpredictable</em></strong> but never <strong><em>Uptight</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nYD3FxHZBr5JhIIS" /><figcaption>Core values that represent the essence of Tchaca Tchaca.</figcaption></figure><h4><strong>2.2 Moodboard</strong></h4><p>With the brand attributes in mind, the tagline for this years event <em>“Sing and dance for your life”</em> (paraphrasing Ru Paul’s Drag Race) and the posters from previous editions, I’ve moved forward into creating a moodboard which would serve as inspiration for the UI of the Microsite.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*umGt1l6zxN7n2cxs" /><figcaption>Moodboard used to inspire and convey a general idea and feel about this years party.</figcaption></figure><p>My goal was to respect the geometric shapes that the previous editions displayed, the playful colors and the plain background which allows bringing focus into the host. On the top left corner, you can see the result of the photo session for this year&#39;s poster. As mentioned before, the tagline is inspired by <em>Ru Paul’s Drag Race</em> and the visuals for the poster by Kylie Minogue’s <em>Fever</em> album cover.</p><h4><strong>2.3 Style tile</strong></h4><p>Given that this was a 4-day project, I had to speed up my workflow, which is why I’ve created a <em>Style Tile</em> that contained most of the visual elements that my project use. In it, you can find the color scheme, the typefaces to use, the buttons and form fields and their different states, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LUVgMgSKZOnnzxPm" /><figcaption>Style tile that informed and directed the UI.</figcaption></figure><h3><strong>3. Responsive Design &amp; Interactive Prototype</strong></h3><p>For this project, it was also intended that we created a responsive microsite. This raised the bar of the challenge and made us think beyond static screen size. Although we usually read that designers should follow the <em>mobile-first </em>rule in product design, I’ve decided to build from Desktop to Mobile.</p><h4>3.1 Responsive design</h4><p>Apart from the responsive example at the beginning of this article, below is another example. For responsiveness, I’ve tried to think in terms of modules so that I could stack them vertically or side by side, which could easily be accomplished in code by using CSS Grid or Flexbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*adu0rHRdRr1W5SG-NZedaw.png" /><figcaption>Example of responsive design with block stacking — Microsity history page.</figcaption></figure><h4>3.2 Interactive prototype</h4><p>For the last part of our challenge, we should aim to create interactions that would appeal to the target audience. Again, looking back at the brand attributes, I wanted the microsite to have bold and contrast heavy interactions, bringing out the fun and unpredictable side of the party.</p><p>To accomplish that, I’ve explored <em>Principle</em> and, after having many objects flying around due to my lack of attention to layer naming in <em>Sketch</em>, I was able to build an interactive prototype that matched my vision and felt complete.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F364463635%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F364463635&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F819898380_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc076d0e4e5c5b8f0353b78148c30951/href">https://medium.com/media/fc076d0e4e5c5b8f0353b78148c30951/href</a></iframe><h3>4. Key learnings and takeaways</h3><p>This has been one of the most pleasurable projects that I’ve developed during this bootcamp. I was able to work with a fun project and really let my imagination flow, without having to be too concerned about rules or a strict brief. It was also a project where we could all explore our UI skills and interaction ideas and put together a product that’s very complete.</p><p>As for my main learnings, I must admit that I am careless when putting together my projects in Sketch and I’ve paid the bill when moving to Principle. Renaming my layers has been way more time consuming than doing it right from the get-go. Other tools that I want to explore and master within Sketch are the symbols and layer/text styles.</p><p>That’s a wrap! Thank you for reading and please clap if you like it ❤</p><p><a href="https://www.linkedin.com/in/joaoclacampos/">João Campos - Ironhack - Berlin, Berlin, Germany | LinkedIn</a></p><p><em>Note: This is a project with an educational purpose, only.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dc1b75cd519" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart People: Online Summer Camp]]></title>
            <link>https://medium.com/@johnnyfields/smart-people-online-summer-camp-8e138e0262df?source=rss-9bfcc3032411------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e138e0262df</guid>
            <category><![CDATA[summer-camp]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Joao Campos]]></dc:creator>
            <pubDate>Tue, 01 Oct 2019 17:30:54 GMT</pubDate>
            <atom:updated>2019-10-05T08:38:13.408Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ironhack UX/UI Bootcamp</h4><p>This week at <a href="https://www.ironhack.com/en/locations/berlin">Ironhack Berlin</a>, <a href="https://medium.com/@thaddeusemu">Thaddeus Emu</a> and I worked as a pair and we were challenged to work with <em>Smart People Inc.</em>, a fictional company that runs Summer Camps in English or Spanish for adolescents aged between 12 and 18. However, they’re noticing that many students are unable to attend the summer camp due to cost and time reasons.</p><p>As an alternative, <em>Smart People Inc. </em>wants to create an engaging online platform that replicates a Summer Camp experience and that can be accessed by students all over at a lower cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eRfNBZGOk9odFTFLOpE00Q.png" /></figure><h3><strong>1. Research</strong></h3><p>We’ve conducted a <em>Competitor Analysis</em> of both Online Summer Camps and Language Apps. Below are our main findings:</p><ul><li>Online Summer Camps (DIY, Connected Camps, Brain Chase, etc.) aren’t really focused on language learning. Instead, they aim to develop other skills such as math, cooking, engineering, art, etc.</li><li>When it comes to Language Apps (Duolingo, Babel, Memrize, Drops, etc.), they don’t promote interaction between users or meeting new people. Most are not time-limited or deadline-oriented and the feedback is usually right/wrong without further details such as why.</li></ul><p>This leads us to conclude that <em>Smart People Inc.</em> is in a very interesting position market-wise as there aren’t many services out there providing the same service.</p><p>On the <strong><em>user</em></strong> side, we’ve reached out to adolescents and parents to understand what are their needs, goals and pains. We’ve asked teens how they learn better, their interests and what would drive them to learn a new language online during the summer. Below are the main findings we got after sending out <em>User Surveys</em> and conducting <em>User Interviews</em>:</p><h4>1.1. Adolescents</h4><ul><li>Videos, games and activities are the best enhancers for their learning;</li><li>Teenagers enjoy chatting and playing with their friends;</li><li>They prefer content that’s meaningful to them and tailored to their interests;</li><li>Many mentioned that flexibility to learn at any time and anywhere without a tight scheduled would be important.</li></ul><h4>1.2. Parents</h4><ul><li>Parents are concerned about the safety of their children in an online platform;</li><li>They are worried about their children spending too much time on their phones;</li><li>The parents showed interest in getting involved in the experience;</li><li>They also mentioned the relevance of being able to have an overview of the children’s progress.</li></ul><h4><strong>1.3 User Personas</strong></h4><p>We used an <em>Affinity Diagram</em> to summarize the main findings of our research and group them in different categories. After that, we created an <em>Empathy Map</em> and finalized our <em>User Personas</em>.</p><p><strong>Charlie</strong> is 14 years old and he likes to play and chat with his friends. For him, learning is not fun and he’s bored during the summertime when he has to stay at home. His interests are games, movies and sports.</p><blockquote>“I learned that staying at home is boring and that I should go outside more but I don’t know where to.”</blockquote><p><strong>Bianca</strong> is 16 years old and she wants to improve her English so that she can travel in the future. She’s motivated and wants to connect with other people from different cultures. Her interests include reading, cooking and culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vnnqWphEoy7u0Lv0" /><figcaption>User Personas — photo credits to Anton Darius @thesollers and <em>Rahmani Kresna</em> @maskresna (unsplash.com)</figcaption></figure><p>At this point, with a better understanding of the business and our users, we were able to define our “<em>How Might We” </em>statement (HMW): <em>How might we help kids improve their language skills in a way that’s aligned with their interests and simulates a fun summer camp experience online.</em></p><h3><strong>2. Ideate</strong></h3><p>Since over 90% of our survey replies were made via a smartphone or tablet and many or interviewees mentioned the interesting in having greater flexibility in their learning path we’ve established that our product would be a mobile application.</p><p>During our ideation stage, we’ve tried to note down as many features and ideas that this app could have. We prioritized the features based on our research results and used the <em>Moscow Method</em> to determine which ideas were essential. We only moved forward with the <em>“must have”</em> and <em>“should have”.</em></p><p>After that, we ran several open <em>Card Sorting</em> tests to. This step was fundamental to determine<strong> </strong>the<em> Information Architecture </em>of the app and the main categories that would serve as navigation anchors for our users. Below is our final version of the site map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rr-JKRawKH3f9ZSe" /><figcaption>Smart People’s site map</figcaption></figure><h3><strong>3. Interactive prototype and testing</strong></h3><p>Based on the <em>Site Map</em> and considering the <em>User Flow</em> of our primary Persona, we started ideating on paper and created a <em>Low-fidelity </em>paper prototype. After several rounds of testing and iterations, our main findings were the following:</p><ul><li>Some of the terms used were not clear to testers and caused some confusion;</li><li>Progress bar was changing from the lesson to the quiz that follows and this led testers to wonder what was going on. This was bad progress feedback and we had to change it;</li><li>Possible actions on encouragement page at the end of lessons were not clear to testers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l6mSe1o-sDFeEL1n" /><figcaption>Some wireframes that we developed for our low-fi prototype</figcaption></figure><p>We then moved on to creating <em>mid-fidelity</em> wireframes in <em>Sketch</em> and a prototype with <em>InVision</em>. Below are some of the developed wireframes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9DO7f33WTRdfUfYK" /><figcaption>Some of our mid-fi wireframes made in Sketch</figcaption></figure><p>We moved on to testing once more and we fine-tuned the prototype after a few test runs. This time around, the changes were minor and not worth mentioning. We believe that this is due to the heavy testing that we did with our <em>low-fidelity</em> paper prototype.</p><h3>4. Smart People: Online Language Camp</h3><p>Now it’s time to showcase our proposal. The students would <em>Sign up/Log in</em>, select their preferences so that the app tailors the content to their interests and, after this, they would be able to start exploring the app.</p><p>In the video below, it’s possible to follow this flow and then we made a small <em>“tour”</em> of the app showing the profile section, the chat section and also how the lessons and games would be structured.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FP8UDr5ZBXjg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DP8UDr5ZBXjg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FP8UDr5ZBXjg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3da558e95bbb30f9efb043e601f7be80/href">https://medium.com/media/3da558e95bbb30f9efb043e601f7be80/href</a></iframe><p>There are four levels for each field of interest. This is meant to replicate the four-week summer camp experience, and users are not able to jump to the next level without completing the previous one or any time in advance. Ideally, there would be a language level assessment test during the account creation process and also a limit on how much time users can use the app per day.</p><h3>5. High-fidelity Wireframes</h3><p>As a little bonus, we agreed on a final sprint before our project presentation in order to create some high-fidelity wireframes for our project. We wanted to convey the look &amp; feel we wanted Smart People’s app to have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qcqRq6eg56bcxJMyrQ-yCA.png" /><figcaption>Suggestion of how the high-fidelity wireframes could look like</figcaption></figure><p>This is a fictional project developed for Learning Purposes only. All illustrations are the property of their creators.</p><h3><strong>6. Key learnings</strong></h3><p>This has been a challenging and interesting project to develop. We got to apply all that we’ve learned so far and I’m proud of the final outcome.</p><p>I feel like we ended up distancing ourselves from the brief. I wouldn’t say completely but I’d definitely like to take one step back and iterate with the intent to give this app a greater feel of a <em>Summer Camp experience</em>. That said, my key learning from this week is to always keep in mind both the results from our research and the business/brief.</p><p>Thank you for reading. Cheers!</p><p><a href="https://www.linkedin.com/in/joaoclacampos/">João Campos - Ironhack - Berlin, Berlin, Germany | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e138e0262df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Evaluation and Site Redesign]]></title>
            <link>https://medium.com/@johnnyfields/usability-evaluation-and-site-redesign-11c0e8dd856a?source=rss-9bfcc3032411------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c0e8dd856a</guid>
            <category><![CDATA[kayak]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Joao Campos]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 16:31:59 GMT</pubDate>
            <atom:updated>2019-08-04T14:40:19.329Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ironhack UX/UI Bootcamp</h4><p>Nowadays, the power to book a flight, hotel, and activities is literally at the tips of our fingers. It’s becoming more common that people use their phones and mobile apps available to book their dream journeys. This post is part of Ironhack’s UX/UI Bootcamp prework (challenge 3).</p><h3>1. User type</h3><p>For this case study, I’ve selected a user type defined as “<em>Young group — 20 to 40 y/o”</em> (4 participants). This group wants to have a blast and spend quality time together with a mix of leisure and culture. Everybody has saved for the trip so it’s time to spoil themselves while still being price-conscious.</p><p>Next winter, they want to escape the cold and grey weather of <em>Berlin</em> and just have fun in a tropical paradise. Their chosen destination is <em>Cancun</em>, where they can party, relax and immerse in the Mayan Civilization (<em>Chichen Itza</em>). All they need is their flight, accommodation and a car to get around!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i3ab5CuDMPJVaFcBh55pHg.jpeg" /><figcaption>Photo from Unsplash — by <strong>Philip Gielda</strong></figcaption></figure><h3>2. Benchmarking</h3><p>With the user and their needs (flight, hotel, car rental) in mind, I’ve compared the offers given between 4 different mobile apps: <em>Tripadvisor</em>, <em>Skyscanner</em>, <em>Hopper</em>, and <em>Kayak</em>. Since it’s not possible to book accommodation with <em>Hopper</em> or rent a car with both <em>Hopper</em> and <em>TripAdvisor</em>, I’ve ruled them out from the get-go.</p><p>In my opinion, both <em>Skyscanner</em> and <em>Kayak</em> performed well in the <strong><em>heuristic evaluation</em></strong>. The apps are very similar giving you clear visibility of the system status (progress bar for loading results), follow platform conventions in terms of wording (consistency and standards), offer good user control and freedom (go back arrow, new search icon), present an aesthetic design (lots of white space and good hierarchy), etc.</p><p>That said, my final decision was to go ahead with <strong><em>Kayak</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VrX0nHQfRMItUz74CR5EYA.png" /><figcaption>Kayak logo</figcaption></figure><h3>3. User tasks</h3><p>Apart from the <em>five</em> seconds home screen test, I’ve asked the interviewees to complete the following tasks:</p><ol><li>Book a round-trip of one week for any time during the next winter;</li><li>Book a hotel — 2 rooms, 4 stars, and all-inclusive;</li><li>Book a car rental — SUV with the same pick-up and drop off.</li></ol><h3>4. Test results</h3><p>During the testing, apart from observing their actions, I’ve encouraged the users to think out loud and tell me what they were doing. I’ve avoided influencing them with leading questions or giving assistance.</p><h4>4.1. Home screen look and feel:</h4><p>The users get a five-second glimpse of the home screen of Kayak and, after that, the phone is locked. My questions were <em>“What did you see?”, “What can you do with the app?”</em></p><ul><li><strong><em>4/4 — </em></strong>noticed that you can use the App to book<strong> </strong>flights and that you can select the starting point, destination, one-way trip, round trip, and multi-city;</li><li><strong><em>1/4 — </em></strong>noticed all three sections that you can book (flight, hotel, car). The others mentioned only two out of three;</li><li><strong><em>1/4 — </em></strong>noticed that further down you have the option to measure your bag and check the status of your flight.</li></ul><p>All in all, the interviewees were able to capture the scope of the app after just five seconds of looking at the home screen. It’s also been mentioned by the users that there isn’t a lot of scrolling needed, the interface is clean and easy to understand and also that the search button is very large and catchy.</p><h4>4.2. Task completion:</h4><p>I’ve created a comparative chart with all the users (four columns) and the tasks (three rows). For each, I noted down what I observed and what they said aloud during the testing. This made it easy to compare and look for patterns or common pain points across the users for each task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOmSc1gyppNKncjRJcDdMw.png" /><figcaption>Usability testing comparative chart</figcaption></figure><p>After the testing session, it was obvious that the app performs really well, at least when it comes to these three tasks. All users, even those that never used the app, managed to go through until the end and were pleased with the look and feel of it. It’s clearly intuitive and easy to understand.</p><h3>5. Problem definition</h3><p>Considering what was said in Point 4 of this post, I haven’t found any major problem to be addressed. Out of all the tasks, the ones that seemed to cause more friction were tasks 1 and 2. That might also be due to the fact that the app was new to some of the users and they were still getting acquainted.</p><p>In my opinion, a few small tweaks could improve the already great overall experience of the app and will focus on the <strong><em>“Select dates”</em></strong> section of flights. Some of my users didn’t understand the flexible date picker at the bottom and others ignored it thinking it was a confirmation of the selected dates. The users also failed to notice the <em>green dots</em> on the date picker which represent the cheaper deals meaning that this feature so subtle that it’s invisible.</p><p>That said, my goal is to make the date selection process more intuitive and also ensure that the user gets visual feedback on which dates would result in a cheaper deal.</p><h3>6. Redesign</h3><p>For the purpose of this exercise, I’ve taken screenshots of <em>Kayak</em> and built my proposed modifications on top of them in <em>Sketch</em>. I’m listing some of the modifications that I see as worthy to test in a second-round with users.</p><h4>6.1. Select dates section</h4><ul><li>Include color differentiation on date picker for flights (with legend);</li><li>Include an option to have a chart view of the dates and prices.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DBqW-hQxwGzA4NY1sI2xg.png" /><figcaption>Left: original UI with flexible dates buttons; Center: proposed price differentiation and flexible dates buttons; Left: chart view</figcaption></figure><ul><li>Change flexible dates section from departure/return to<em> “Add flexible dates”;</em></li><li>Unify the selection of flexible dates in one single pop-up window.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWPeCQd0b7YFOHHr8XXqwQ.png" /><figcaption>Left: original flexible departure and return selector; Right: proposed solution</figcaption></figure><ul><li>When users click on “<em>See cheapest dates”</em> set the default to <em>Soonest</em> other than <em>Cheapest</em>. In <em>Cheapest</em> the dates/months are confusingly displayed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kY2TPjLAsQn_780kg-N24g.png" /><figcaption>Left: main screen; Center: sorted by cheapest; Right: sorted by soonest</figcaption></figure><h4>6.2. Hotels section</h4><ul><li>Test different color/size for the filter button in order to increase visibility;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgwsLY7Ta3yEC8AX-gpkMg.png" /><figcaption>Left: original; Right: proposed solution</figcaption></figure><h4>6.3. Future developments</h4><p>There were other small friction points noticed during the usability testing that I believe are worth mentioning for future reference.</p><ul><li>Memorize the number of participants from flights to hotels, etc.;</li><li>Include <strong><em>Board basis</em></strong> in the hotel filters (all-inclusive, breakfast, etc.);</li><li>Allow filtering for a specific number of Hotel Star rating. “<em>4 stars”</em> and not <em>“4 stars and up”</em>;</li><li>Test the effect of removing the price next to the checkboxes inside the filter screen.</li></ul><h4>6.34. Prototype</h4><p>I’ve created a small prototype in <em>InVision</em> to reproduce the proposed <em>look &amp; feel</em> of the new flight search (date selection) process.</p><p><a href="https://invis.io/DSTAF6C4KCQ#/377211746_Home_Screen">Click here to view the project `Kayak Redesign`</a></p><h4>7. Key Learnings</h4><ul><li>Conducting the heuristic evaluation of <em>Kayak</em> and <em>Skyscanner</em> was both interesting and difficult. Better analysis skills will come with practice;</li><li>The app Kayak performs really well and the user tests proved it. I found hard to decide on what to tackle as none of the friction points seemed to be of <em>high relevance. </em>I also believe I need to get better at defining tasks;</li><li>Looking back at my process, I would still include the color differentiation for the flight dates (green, yellow, red) but I don’t believe that the <em>“add flexible dates”</em> was a step towards a better experience. Testing would tell;</li><li>I kept thinking that these changes, no matter how small, could have an impact on how users perceive Kayak’s app. That said, ideally, they should be made sequentially, trying to validate one at a time;</li><li>During the interviews, you see that each user has their own way of thinking and navigating. There’s always room to improve but, at the same time, one can’t adapt the whole design to one user and that is why interviewing many helped me get a better sense of the patterns and the bigger picture.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11c0e8dd856a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking]]></title>
            <link>https://medium.com/@johnnyfields/design-thinking-87363a0b75ea?source=rss-9bfcc3032411------2</link>
            <guid isPermaLink="false">https://medium.com/p/87363a0b75ea</guid>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[mobility]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joao Campos]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 17:23:16 GMT</pubDate>
            <atom:updated>2019-07-24T17:23:16.215Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>Design Thinking: Urban Mobility App</em></h3><h4>Ironhack UX/UI Bootcamp</h4><p>In this post, I’ll be going through my process and findings for the <em>Challenge1</em> of Ironhack’s UX/UI Bootcamp. This Design Thinking challenge is part of the UX module of the Prework for the Bootcamp.</p><h3>The Client: UrbanGo</h3><p>UrbanGo is a public transit and mapping startup and their goal is to offer the quickest and cheapest transport routes to their users.</p><p>The company developed a mobile application but there is still one main pain point which is having to purchase different public transport tickets via different channels or providers. Often, it’s necessary to buy different public transport tickets to go from point A to B (e.g. one bus ticket and one tram ticket).</p><h4>1. The users and their needs:</h4><p>At this stage of the Design Thinking Methodology, the main objective is to gain an understanding of the user&#39;s needs and who we’re designing for. The research has been centered in public transport users ranging from 18 to 50 years old. Below are some of the questions made during my interviews:</p><ul><li>When you travel, within your city or abroad, which methods of transportation do you use?</li><li>How or where do you buy your tickets?</li><li>What are your pain points when doing it?</li><li>How do you feel before/after going through the process of buying tickets?</li><li>How would you feel when you have to buy a new ticket for each type of public transport you used?</li></ul><p>Some pain points and feelings that were common or transcendent amongst the interviewees are listed below:</p><ul><li>In general, all pointed out that purchasing transport tickets <em>in situ </em>can be a stressing experience. It combines the pressure of buying a ticket considering the queues to access the machines and the psychological effect of not wanting to miss the next transport;</li><li>Some interviewees used to Google Maps in advance to get a visual feeling of which direction they’re going and the <em>depart at/arrive by</em> option to get an understanding of the timetables and estimated arrival time;</li><li>Difficulty in operating the ticket machines or interacting with a salesperson (e.g. language barriers, understanding the ticket types, deciding either going for a single ticket or daily, etc.);</li><li>On-site, the range of payment options not suitable for many scenarios (e.g. no change, only large bills, bank card not accepted);</li><li>When abroad, the users I interviewed are most likely to buy tickets directly from a machine than download a local app (discouraged by the need to register, enter a payment method, etc.);</li><li>It was consensual that having a separate ticket for each transport type would be annoying.</li></ul><h4>2. Proposed solution to the problem &amp; rapid prototyping:</h4><p>The scope of this challenge consisted in<em> </em>creating a feature for the UrbanGo app that solves the pain of having to purchase different public transport tickets by different channels.</p><p><em>How might we spare our users from buying each ticket individually?</em></p><p>With this in mind, I’ve tailored the checkout process in such a way that the users don’t have to buy different tickets with each vendor. It’s been considered that the app would present the different possible routes (fastest, cheapest, etc.) and would then offer the user the option to buy all tickets with one touch.</p><p>The different tickets would be automatically purchased from each vendor in the back end and stored in the app’s <em>ticket wallet</em> where the user could check the route map and also access each of the tickets that are part of their journey (e.g. bus, train tickets). Below is a visual representation (prototype) of the app and the process of buying tickets for a trip from start to finish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tkcsc3FJbOv59Fpan_lPRw.jpeg" /></figure><h4>4. Key learnings:</h4><ul><li>In this exercise, it was easy to empathize with the users as I could see myself in their stories. Having been in the same situation many times has made it easy to understand and relate to their pains. I’m curious to understand how it would be on a different topic, something I’ve never experienced;</li><li>For the same reason as above, I wonder if the problem statement defined as well as the solution presented could be biased by my own experiences;</li><li>During the process, I’ve had difficulties in coming up with many solutions or any that I saw as innovative. For this reason, I believe I’ve failed on the task to “<em>ideate possible solutions through sketching”</em>; and</li><li>The rapid prototyping was fun and I started to notice how visual conventions applied to signifiers are important so that users will immediately understand what actions can be taken.</li></ul><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87363a0b75ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>