<?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 Avi Mair on Medium]]></title>
        <description><![CDATA[Stories by Avi Mair on Medium]]></description>
        <link>https://medium.com/@avimair?source=rss-a3afca5af9e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*l7sv87BDNQkWRn9o.</url>
            <title>Stories by Avi Mair on Medium</title>
            <link>https://medium.com/@avimair?source=rss-a3afca5af9e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:17:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avimair/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[Interaction Design of Complex Applications]]></title>
            <link>https://medium.com/@avimair/interaction-design-of-complex-applications-a65d21fddd01?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a65d21fddd01</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Sat, 28 Apr 2018 16:25:21 GMT</pubDate>
            <atom:updated>2018-04-28T16:25:21.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JEKFpOmUl79tToa0BtmwQ.jpeg" /></figure><p>At this month’s IxDA meetup, we learned about designing interactions for complex data applications, with talks from UX designers working with Sherlock ML, Bloomberg and Quantum Black. Here were a few of my key takeaways.</p><h4>Ways of working when designing complex applications</h4><ol><li>Collaborate: with teams and people from all across the business.</li><li>Fundamental principles of design definitely apply: mental models, progressive disclosure and reusable widgets etc.</li><li>Use analogies with physical objects when dealing with abstract things, to help others and yourself to understand complicated concepts.</li></ol><h4>The intuitive and user-centric Bloomberg terminal (arguably)</h4><p>Whilst this became a point of contention in the group, we saw that whilst the Bloomberg terminal might be incredibly cryptic, visually unappealing UI and unintuitive to the novice user, but it is actually very user-centric indeed. If we take the term user-centric in its purest sense, it means to design a product with a core focus on the needs, behaviours and mental maps of the specific set of users for whom the product is intended. The Bloomberg terminal’s users have invested a great deal of time and effort to learn how to use the terminal to get the job done as quickly and efficiently as possible through training. The interaction system has not changed much at all since the 80s so the modus operandi are very deeply engrained in these users. They go on long and arduous training courses to learn how to use the terminal and pride themselves on their competency.</p><p>Hence, if Bloomberg were to completely redesign the terminal so that it were easy for a complete novice user with no training, this would force the existing users to completely relearn how to use the product and would result in it taking them longer to get their tasks done. With such an engrained way of interacting with the terminal and a strong emphasis on spending as little time within the application as possible to complete the given task, it seems that the Bloomberg terminal’s interaction design is actually very user-centric indeed, contrary to popular belief. “User-friendly” and “intuitive” are contextual.</p><p>Bloomberg’s goal is to unfrustrate their users, not delight them.</p><h4>Less ≠ more</h4><p>The widely held tenet “less is more”, doesn’t necessarily hold true for high usage applications like the Bloomberg terminal (it has 22,000 features and is continuing to grow). This is because its users consider having access to more datasets than anyone else as a competitive advantage in their market. The more data they have to back up their hypotheses, the more sure of their decisions they feel that they can be.</p><h4>Designing for work vs. fun</h4><p>When designing for applications that people would use for work, bear in mind that the user’s focus is completing a task that probably has interactions and implications beyond your product. Hence contrary to most consumer products or games, the designer’s focus is actually to have the user spend as little time as possible within the application itself.</p><h4>Lessons learned working with data scientists at Quantum Black</h4><p>Data is the raw material that has no intrinsic value: insight and value is derived when data is understood as part of a complex system.</p><p>Design is an action, not just a deliverable. Understanding this helps to develop a design-led organisation.</p><p>Communication and strong soft skills are critical when designers need to challenge assumptions and biases, pushing the envelop to problem solve.</p><p>Storytelling with data enable decision making and creates business impact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a65d21fddd01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX at the BBC: Voice, VR and the Future of Media]]></title>
            <link>https://medium.com/@avimair/ux-at-the-bbc-voice-vr-and-the-future-of-media-89e92344bbad?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/89e92344bbad</guid>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Sun, 22 Apr 2018 13:56:09 GMT</pubDate>
            <atom:updated>2018-04-23T18:36:24.687Z</atom:updated>
            <content:encoded><![CDATA[<p>This month, the UX Crunch hosted a meetup at the BBC’s headquarters in Central London. Here are my key takeaways from the evening.</p><h4>Where we find ourselves in UX today — Colin Burns, CDO @ BBC</h4><p>“It’s not enough to be the best at what you do. You must be perceived as the only one who does what you do” — Jerry Garcia (The Grateful Dead).</p><p>Currently, we’re at peak web UX and late in Kano’s adoption curve:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*9CyIMWorrgUGgSiWMyR79g.png" /></figure><p>After analysing all of the web layouts that they use at the BBC, Colin’s team found that there were only really <strong>3 main layouts</strong>:</p><ol><li><strong>Things:</strong> pieces of content</li><li><strong>Things that point at things: </strong>homepages/search tools</li><li><strong>Strings:</strong> of content and data</li></ol><p>Because of all this, we need to push boundaries a lot more to do really innovative work. <strong>Colin broke down innovation into 3 categories:</strong></p><ol><li><strong>Incremental innovation:</strong> the kind of iterative UX work done by agile teams</li><li><strong>Sustaining innovation: </strong>not remarkable but is effectively keeping up with the tech that your competitors or peers are using, to remain relevant</li><li><strong>Discontinuous innovation</strong>: paradigm shifts in approach or the status quo</li></ol><p>It is in the discontinuous innovation, where the truly great work is done but as a field, we’re not focussing on it enough at the moment.</p><h4>Embodiment in VR — Nick Ritchie</h4><p>Well known and established pillars of achieving a feeling of <strong>presence for the user in VR:</strong></p><ol><li><strong>Place illusion:</strong> the environment they are in seems realistic</li><li><strong>Plausibility:</strong> the events that take place in that environment have believability</li><li><strong>Body ownership</strong></li></ol><p>To immerse users into the story, Nick’s team added another pillar of their own — <strong>response:</strong> how the experience makes users feel.</p><p>They tested 3 modes of VR experiences and scored them against these 4 pillars of presence to assess which mode offered the most present experience.</p><p>3 modes:</p><ul><li>Embodied as the character in the VR and able to control movement</li><li>Included in the experience but unable to control the main character</li><li>Observing the story</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E8VHsaMCdDsWiTXuqFXTlA.jpeg" /></figure><p>So when users were embodied in the experience, they were much more likely to be engaged and present in the VR experience.</p><h4>3 elements of designing for voice — Stevey Robertson &amp; Gar Thomas</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QYpPuzlIABPF9o3ktV2elw.jpeg" /></figure><p>What are the key areas when <strong>ideating for voice experiences?</strong></p><ul><li><strong>Context:</strong> when/where/how people are using voice interfaces, changing all the time (used to be just limited to the bedroom or in the home but now it’s being used more on the go, with kids etc)</li><li><strong>Role play:</strong> using the “Wizard of Oz” approach to act through conversation and identify a script</li><li><strong>Visualising a voice experience</strong></li></ul><p>When writing for voice, <strong>UX plays a key role in:</strong></p><ul><li><strong>Content discovery</strong></li><li><strong>Universal navigation</strong></li><li><strong>Storytelling</strong></li></ul><p>We don’t yet have an established universal navigation for voice where users intuitively know how to interact with the UI (no version of the hamburger menu or pagination from mobile web design/apps). A lot of their job is experimenting with many ideas of navigation options for voice interfaces.</p><p>Prototyping: they use Sayspring - <a href="https://www.sayspring.com/">https://www.sayspring.com/</a></p><p><strong>Greatest challenges in voice UX at the moment:</strong></p><ol><li><strong>Establishing a consistent design </strong>that works across all platforms (Alexa, Siri, Google Home, Cortana…)</li><li><strong>Providing a seamless experience </strong>from beginning to end</li><li><strong>Personalisation</strong></li></ol><h4>Definition of service design — Karen Ly</h4><p>“The design of the right service for the right group of people, with a group of people”</p><h4>Use A-frame to design VR experiences — Alex Nelson, FXR</h4><p>Using a Google Cardboard VR headset and what looked like some very simple code in A-frame and Google’s library of elements, Alex showed us how to build a simple VR experience. It was absolutely mind-blowing an something that I really need to try soon!</p><p><a href="https://aframe.io/">A-Frame - Make WebVR</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_R_uLnV_zVQ4wUaBvAaSsw.jpeg" /></figure><p>It was a deeply insightful evening, offering a sneak peak at the incredible work that is being done at the BBC in UX. Like most great UX, as consumers we often don’t even notice it, it just fits into our lives seamlessly. As these emerging technologies of voice and VR grow to maturity, it will be really interesting to see where this all goes next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89e92344bbad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI in Healthcare @ Foolproof]]></title>
            <link>https://medium.com/@avimair/ai-in-healthcare-foolproof-1e56f6c63ccc?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e56f6c63ccc</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Thu, 22 Feb 2018 15:03:19 GMT</pubDate>
            <atom:updated>2018-02-22T15:03:19.696Z</atom:updated>
            <content:encoded><![CDATA[<h4>The opportunity is in closing the empathy gap between artificial intelligence and human empathy</h4><p>Once again, Foolproof hosted The UX Crunch for an event discussing the challenges and opportunities in designing UX for the healthcare sector with artificial intelligence (AI). The speakers included Foolproof’s very own Tim Caynes, Jane Vance, and Joseph Wolanski from Ada Health. For those of you who missed out, shame on you, but here are some of my key takeaways from the evening.</p><h4>Foolproof’s hypothesis for AI in healthcare</h4><p>One of our biggest challenges and opportunities is closing the gap between artificial intelligence and human empathy (the empathy gap). How do we use potentially intelligent systems to enable patients to get they help they need with care and compassion in potentially difficult times, even when they don’t know they need it? Foolproof are leveraging AI to bring systems and humans together for better outcomes and are using a thorough understanding of context to infer those better outcomes.</p><h4>Three questions to ask at any point in a journey to help understand that context</h4><p>Where are users in a journey? What did they do to get there? Where can they go next?</p><h4>Use dynamic pathways</h4><p>When designing the journey through a system, most designers might use static pathways that are set to be the same for each user, guiding where they go from one screen to another. Foolproof are using dynamic pathways with some degree of intelligence, so that users can manage their own pathways and effectively create their most desired path through the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tRLAyZtuGpE9ZdEwRPQGnA.jpeg" /><figcaption>Tim Caynes on dynamic pathways</figcaption></figure><h4>Better still, use behavioural pathways</h4><p>Behavioural pathways enable designers to understand and infer certain information about users from their interaction with the service, such as where they’ve been, where they are and where they might go next (remember the three questions for context above). We can infer users’ behaviours to understand what their next desired outcome might be.</p><h4>Implement AI in systems with “the experience stack”</h4><p>An invention of Tim Caynes, the experience stack abstracts the experience from the platform itself (where the intelligence is applied), from the data that is used. Separating these three elements, we can architect systems that allow for behavioural pathways much more clearly because of the ability to follow a pathway from information provided by the user, through to an outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lsEe1sci6zn8PNxGtcQ0ZQ.png" /></figure><h4>With the limited resources of healthcare practitioners, designers can improve the experience of patients by:</h4><ul><li>Understanding their experiences of people with various health conditions.</li><li>See the journey that they go on.</li><li>Define the phase of that journey.</li><li>Identify the courses of information that they need across those phases.</li></ul><p>However when deciding when users need specific types of information, it can be very difficult to identify exactly where people are in their journey and when they are transitioning from one stage to another.</p><h4>Opportunities to improve experiences in healthcare using AI</h4><ul><li>Provide relevant information at the relevant time.</li><li>Provide a frictionless experience for people who are unwell and are feeling stressed (absorbing information whilst stressed due to a health condition can be very difficult).</li></ul><h4>Foolproof’s work with SimplyHealth</h4><p>Foolproof applied these methodologies to a product called <a href="https://www.simplyhealth.co.uk/careforlife/">Care For Life</a>, which is run by SimplyHealth. The idea was to provide relevant information to support carers of elderly family members over the long term and across the various stages of care.</p><p>In the research stage, they identified three groups of users whose behaviour and needs differed depending on where they were in relation to their loved one’s ageing:</p><ul><li>Pre-active carer: they are aware that care might be needed in the future so are starting to look into it.</li><li>Active carer: an incident has happened which means that they have needed to increase the levels of care.</li><li>Committed carer: they have been caring for their elderly family member for some time now and may have even transitioned into full-time care for them.</li></ul><p>The experience stack enabled the Foolproof team to develop a different interface for each user type, changing depending on where they are throughout that journey. Whilst the general theme and brand of course remained the same, changes between the three interfaces manifested in colours, content and the copy used.</p><p>One key challenge was to assess which group users fit into as they came to the website. As a general rule of thumb, most people are not particularly proficient or impartial when identifying with a group, so system needed to use well-crafted questions to present users with the most important of the three interfaces.</p><p>In this way, users progressed along the journey being provided with the most relevant information to them, when they needed it with minimal sorting or searching on their part — using intelligent systems for the desired outcome, from a bedrock of behavioural data.</p><h4>The Gartner Hype Cycle as it related to the adoption of AI in the healthcare ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YET4eH6cwJ4EnoUA2Xj2kQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e56f6c63ccc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is emotion so important in UX?]]></title>
            <link>https://medium.com/@avimair/why-is-emotion-so-important-in-ux-1db4945cfdb5?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1db4945cfdb5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Sun, 28 Jan 2018 15:39:23 GMT</pubDate>
            <atom:updated>2018-01-28T15:39:23.237Z</atom:updated>
            <content:encoded><![CDATA[<h4>A summary of what I learned from The Interaction Design Foundation’s course on emotion and experience, from their latest HCI program</h4><p>It all starts with Maslow’s hierarchy of needs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7snC7VDxpRXhaCEqPkQyjQ.png" /></figure><p>Before beginning the design, we need to establish which levels of the hierarchy that our product will fulfil, why those needs over others, how they will appear in the design, how the user will feel and how will they satisfy these needs from your design.</p><h3>Emotion theory</h3><p>Psychologists distinguish between:</p><ul><li><strong>Emotion:</strong> Physiological and neurological state of the body.</li><li><strong>Feeling:</strong> More of a subjective experience.</li><li><strong>Mood:</strong> Longer term positive or negative feelings based on chemical and other factors in the body.</li></ul><p>Going deeper, there are several kinds of emotion to experience:</p><ul><li><strong>Basic emotions:</strong> Fear, anger, happiness — stemming from the limbic system aka the reptilian brain.</li><li><strong>Complex emotions:</strong> Shame, anxiety, regret — involves making sense of our lower emotions and influencing them.</li><li><strong>Arousal:</strong> Adrenaline, momentary fear, laughter, fight or flight response — manifestations of high levels of excitement.</li><li><strong>Valance:</strong> Signs that something has been a positive or negative experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lUCaaUi3eVq6MPfoOeblYw.png" /><figcaption>Best performance at medium arousal — not too much, not too little</figcaption></figure><p>To tap into the emotions that we plan to target, we need to understand and strategically implement the four threads of experience, made famous by McCarthy and Wright’s theory of enhancement:</p><ul><li><strong>Sensual:</strong> Visual and tactile elements of the experience. Consider how the look and feel captivates the user’s senses.</li><li><strong>Emotional:</strong> Does your design elicit certain emotions and feelings or does it engage the user’s personal relationships in the experience?</li><li><strong>Compositional:</strong> How the design makes sense and fits into the user’s life.</li><li><strong>Spacio-temporal:</strong> Consider which times and places it makes sense to use the design, and the where and when of optimal use-cases.</li></ul><h3>Designing for peak experience</h3><p>Whilst it might be tempting to make your product appeal to as many people as possible, because each person’s preferences and needs are so different, your product’s experience will only be “good enough” for everyone. Just being good enough really is not enough. Other products which offer a peak experience for a limited few will be far more likely to win the hearts, minds and cash of this small group than your standardised product. Hence, it is important to design peak experiences into your product or to be a peak product for a small number of people, because the peak product will always win. Here is a diagram to help illustrate:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0UzkJjkBp-Cq9W7RfnqKWw.png" /></figure><p>Designing for peak experiences requires a different approach to traditional interface design. Rather than taking average and typical user profiles with central personas, design for individuals, niches and extreme use-case personas. If you get your design a 100% right fit for one person, it will likely to be great for a select few others around them. This will beat the just “good enough” incumbent experience for these users.</p><p>However it is possible to capture a large proportion of the market with this strategy, Facebook does this very well. Their open API allows developers to design little apps for niche groups of users, so this engages many different groups but it’s still all encapsulated in the same product.</p><h3>Extended episodic experience</h3><p>A key issue with most design literature is that it often permits designers to fall into the trap of considering experiences singular and unrelated. However this is never the case, each experience flows into others, like a stream. So what makes up an extended episodic experience?</p><p><strong>Interlinked events:</strong> Each event results in retrospection (looking back to past experiences) and prospection (looking forward to future ones).</p><p>We can break this down further into:</p><ul><li>First order experiences: Direct and simple — for example, enjoying a picture whilst browsing a photo gallery.</li><li>Second order experiences: Reflective — eliciting deeper emotions, being prospective and retrospective.</li><li>Higher order experiences: Reflexive — considering how others will view your actions or how you will think about them in the future.</li></ul><p><strong>Intertwined threads:</strong> One experience spilling into another. This could manifest between individuals (as events have effects on many individuals) or across the many threads which we all experience simultaneously, tied to other events or media platforms.</p><p><strong>Significant places or people:</strong> Spaces of experience become places of significance. This is true of not only physical places but interfaces, apps, websites and the like.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1db4945cfdb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Fitts’ and the Furious]]></title>
            <link>https://medium.com/@avimair/the-fitts-and-the-furious-b4e70fb508db?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4e70fb508db</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 22:25:23 GMT</pubDate>
            <atom:updated>2018-01-24T22:25:23.090Z</atom:updated>
            <content:encoded><![CDATA[<h4>A neat little formula to help users navigate your website/app faster and more efficiently</h4><p>The idea of Fitts’ Law is to calculate how long it takes for a user to get to a target element which you want them to interact with. This target could be a call-to-action button, a button to close the current window or anything you want them to use really. Your aim should be to minimize the target’s average selection time.</p><p><strong>The Law</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K3GoSfd2qqQcRgm4FwVckQ.png" /></figure><p>t: time it takes user to move to the target</p><p>a + b: used to take into account the size of the tool that the user has to interact with the interface, e.g. stylus, mouse, finger</p><p>A: amplitude, how far away the target is from the user’s start point in the interface</p><p>W: the width of the target, giving an indication of how accurate the user needs to be once they get to the target</p><p><strong>Laying Down the Law</strong></p><p>The goal for the designer should be to minimize the amount of time it takes for the user to reach the target. Most applications of the rule ignore the <em>a + b</em> term, which refers to the size of the selection tool. We are left with the terms <em>A</em> and <em>W.</em></p><p>Hence, to minimize <em>t</em>, we can do one of two things:</p><ol><li>Make <em>A</em> smaller</li><li>Make <em>W</em> bigger</li></ol><p>Making <em>A</em> smaller is pretty simple, use shortcuts embedded into the keyboard or the right-click. When the user executes the shortcut or right-clicks, make one of the options whatever your target is, e.g. Delete File. Instead of having to drag the file all the way to the trash can icon, they can right-click and delete.</p><p>Making <em>W</em> bigger is more interesting. An effective way to do this with mouse-enabled interfaces is to locate target points in the corners of your screen. By doing this, you have created a target that is infinitely wide. In the case of the right-hand corner, no matter now far up and how far right the user goes, they will always be on that target. Hence <em>W </em>= ∞.</p><p><strong>Applied to touch screens</strong></p><p>Whilst this tip to maximize <em>W</em> only applies to mouse-enabled interfaces and our world is increasingly being dominated by touch screens, Fitts’ Law can still be applied, its application just needs to be altered slightly for these platforms.</p><p>I would suggest placing the most important targets in places which align with the user’s ergonomics on their device. On a smaller device like a smartphone, you could minimized <em>A</em> by placing the target in the bottom middle of the screen, if they tend to use your app one-handed, on the go, using their thumb.</p><p>You could maximize <em>W</em> by placing the target in the middle of both the left and right edges of the screen, like Tinder does with its swipe interface.</p><p>As you would with any design decision, consider where the user will be when they are using your interface, who they are, the why, when and how etc.</p><p>Get creative!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4e70fb508db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role of Memory in HCI]]></title>
            <link>https://medium.com/@avimair/the-role-of-memory-in-hci-f92204a6980d?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f92204a6980d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[memories]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Tue, 23 Jan 2018 20:12:34 GMT</pubDate>
            <atom:updated>2018-01-23T20:12:34.004Z</atom:updated>
            <content:encoded><![CDATA[<h4>My key takeaways from the IDF’s lessons on memory from their latest HCI course</h4><p>A key but often overlooked element of the user experience is accounting for the nuances of user memory. Memory can be fickle if not properly understood, it varies from person to person and can cause some serious stumbling blocks if an interaction continues across multiple screens.</p><p>I have noticed this issue is most often in data input forms. Sometimes the form is split onto multiple pages or it can be just one long, continuous page of questions and fields. Both require the user’s recall of memory, so we need to design for it.</p><h4>The timescale of memory</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*r_U2ctAhEexO0oimLCcLDQ.png" /></figure><h4>Short-term memory</h4><p>Properties:</p><ul><li>Rapidly accessed</li><li>Rapidly recalled</li><li>Rapidly decays</li><li>Limited capacity</li></ul><p><strong>Miller’s 7</strong>±<strong>2</strong> rule helps to add some context to the limited capacity of short-term memory. Coming from the field of psychology, it states that the human memory can optimally handle 7 pieces of information at a time (give or take 2). Whilst this has been misused when it comes to limiting navigation elements to 7±2, it is completely valid for short-term memory. This includes not only remembering lists of numbers but also passwords and how deep into the navigation flow that a user goes.</p><p>The key to surmounting this hurdle, is to <strong>make the groups of information meaningful.</strong></p><p>E.g. Try to remember and recall the following chain of letters: HEC ATRA NUPT HET REET</p><p>Pretty hard isn’t it? Now consider that this seemingly random chain of letters actually spells out “The cat ran up the tree”, with the first “t” moved to the end. Now just remember the number of letters in each group and it’s easy!</p><p>Applying this to interface design, if we make the information provided meaningful to the interaction or ask for information in a data form which follows some logical flow, our users will be far more likely to recall.</p><h4>Long-term memory</h4><p>Properties:</p><ul><li>Slowly accessed</li><li>Slowly created</li><li>Slowly decays</li><li>Much larger/theoretically unlimited capacity</li></ul><p>We have two major forms of long-term memory:</p><p><strong>Episodic</strong></p><ul><li>Serial memory which follows a sequence, such as a story or the way most children learn their times tables.</li><li>However, this information is often hard to recall out of order.</li></ul><p><strong>Semantic/declarative</strong></p><ul><li>Structured memory of facts, concepts and skills</li></ul><p>There are also a few ways in which long-term memory can manifest or is triggered:</p><p><strong>Associative memory</strong></p><ul><li>Concepts which are linked to one another are triggered, like a domino effect.</li></ul><p><strong>Explicit memory</strong></p><ul><li>Conscious memory, you know that you know it.</li><li>Includes episodic and semantic memory.</li></ul><p><strong>Implicit/tacit knowledge</strong></p><ul><li>Motor memories — e.g. playing an instrument.</li><li>Automatic reactions — e.g. Pavlov’s dogs.</li><li>Expert knowledge of a domain.</li></ul><p>It is possible to turn explicit knowledge into implicit by proceduralisation and practice, so that it becomes automatic. There are also benefits to making implicit knowledge explicit, such as in the case of correcting bad habits. We can do this by introspection and examining ourselves to pick up on subconscious issues.</p><h4>Mezzanine memory</h4><p>Mezzanine memory is often overlooked and unfortunately has not been studied much outside of airplane cockpits to test for situational awareness in a simulated crisis.</p><p>It sits between short and long-term memory, of the last 20–30 minutes.</p><h4>How reliable is your memory really?</h4><p>Whilst we may believe that our memories are finely tuned, accurate representations of the world, all memories are constructed by our brains. They take in an input stimulus, perceive, encode it into alanguage which our neurons can understand and reconstruct those signals into memories for us to recall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*2lESDgnLKdE3cXUKu0LnMA.png" /></figure><p>Just be aware that this allows for a margin of error, which can lead to confabulation or false memories. Our memories are not pure, they are interpreted through the lens of our moods, the world, wider context and our preconceive notions.</p><h4>Memory: in action</h4><p>Taking AirBnb’s search tool from their iOS app, I thought it would be useful to outline how all of this theory on memory has been applied by one of the best forms I’ve ever seen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HZ6G9cY-Nc-tXOaDmAjNAQ.jpeg" /></figure><p>Deciding “where to go” with this screen, I felt that I could have been using short-term, mezzanine and long-term memory depending on how long it had been since I was inspired to visit the specific destination which I had in mind.</p><p>It could either be associative or explicit too. I would use associative memory if I entered a search query for a location related to one that appears in the default suggestions. On the other hand, it could be explicit memory if I came to the app with a preconceived idea of specifically where I wanted to go.</p><p>In terms of the form layout itself, I would be using implicit/tacit knowledge to navigate the form and to know how to input information from my experience with other similar forms.</p><p>AirBnb have kindly helped to support my mezzanine and long-term memory by helping to remember specific places, dates and the number of guests for which I have searched in the past, sorted by the most recent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0icTYle4MtJpYLtVrnZy6w.jpeg" /></figure><p>Scrolling through the results of my search query, I was using semantic/declarative memory to assess whether a house that I see matches my needs or not. However, there could be an element of sensory memory if I scroll past a house that immediately catches my eye.</p><p>I can also feel Miller’s 7±2 rule working on me, as I forget results which were passed more than 5/7 scrolls ago. I might remember them if they really stood out from the others, but even then my memory was vague and not specific.</p><p>AirBnb clearly identified this as an issue and used the heart button (that you can see in the top right of each featured photo), to save the house and add it to my wish list. In this way, it supports my short-term memory and does the mezzanine and long-term memory for me.</p><p>Thanks AirBnb for setting such an awesome example!</p><h4>Icon credits</h4><p>Brain: <a href="https://thenounproject.com/search/?q=brain&amp;i=355285">https://thenounproject.com/search/?q=brain&amp;amp;i=355285</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f92204a6980d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cognition and Perception in HCI]]></title>
            <link>https://medium.com/@avimair/cognition-and-perception-in-hci-e134e3b4401f?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e134e3b4401f</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Mon, 22 Jan 2018 21:24:59 GMT</pubDate>
            <atom:updated>2018-01-23T20:15:15.759Z</atom:updated>
            <content:encoded><![CDATA[<h4>My key takeaways from the IDF’s lessons on human cognition and perception from their HCI course</h4><p>First of all, let’s take a look at the basics of human cognition, to form the building blocks of our interfaces.</p><p>Whilst it might seem intuitive to think of our reaction to stimuli and the resulting action as a linear function (we perceive a stimulus, our brain processes and we output an action), a computational analogy like this does not offer a full picture. Think of it more as a cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ocTkOhkXeydBXCwKj0SBYg.png" /></figure><h4>The 5 Senses Applied to HCI</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y_RibW4wdfwzKJ5O_em-7g.png" /></figure><p>In the age of graphic and voice interfaces, sight and sound are widely accepted as the two most important senses for us to design for.</p><p>This is closely followed by touch, which we tend to use to enhance an experience, rather than building the experience around it. We can indirectly use the elements of<strong> pain, temperature, pressure and texture</strong> to inspire our design and solve a problem which people experience in the real world caused by these elements, consider their impact on how users interact with our product or factor them in to craft the wider experience itself.</p><p>As one would imagine, smell and touch are almost exclusively used indirectly when designing a computer system. Consumer technology has not yet got to the stage at which we can reproduce them accurate and designing for these senses requires a high level of accuracy because of how sensitive these senses are. This might be one of the most significant hurdles to creating fully immersive VR in the future.</p><h4>The 3 Dimensions of Sense</h4><p>I like to think of the following as the 3 dimensions of sense:</p><ul><li>Exteroception</li><li>Interoception</li><li>Proprioception</li></ul><p><strong>Exteroception</strong> is all about sensing as a result of outer-body stimuli, from the outside. This could be smelling the unique aroma of frying garlic and onions, or seeing the love of your life for the first time.</p><p><strong>Interoception</strong> covers senses which are prompted from the inside. These could include headaches, hunger, intuition or conscience. Whilst not explicitly used in designing interfaces, it helps to build up a complete picture of the user’s interaction.</p><p><strong>Proprioception</strong> senses where your body is in relation to the space around it and the environment. This could blend a little with the sense of touch and can be used when considering how users might hold a device whilst using your design or more subtle levels of interaction.</p><h4>The Eye</h4><p>Whilst most designers wouldn’t think of themselves as biologists, it’s important to understand the components of the human eye to fully understand the implication that our designs are having.</p><ul><li><strong>Pupil:</strong> a lens covering the hole into the eye.</li><li><strong>Iris:</strong> the muscles which change the pupil’s shape, to help us focus or zoom out.</li><li><strong>Rods &amp; cones:</strong> detect dim and bright light respectively.</li><li><strong>Optic nerve:</strong> sends signals to the brain but also creates a blind spot, which our imagination fills in, to always provide a complete picture, hence we rarely notice this partial blindness.</li></ul><p>The key takeaway from this is that what we think we see and what is actually in front of us, are often not the same. Here are a couple of <strong>optical illusions</strong> to show what I mean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*CP7eABvTO1IMsJqPp4uzTw.png" /><figcaption>The Muller Lyler illusion — which straight line is longer?</figcaption></figure><p>Hence, to avoid confusion, we need to design icons in our interfaces which users can easily identify by relating to the action in the real world.</p><h4>Sound</h4><p>Sound is less used than sight in user interfaces because it is less directional and not as targeted to the specific user. Random sounds can be annoying for others in the vicinity who are not using the product, so <strong>sound should be considered a secondary element,</strong> not central to the interaction, because many users might prefer to put their device into silent mode.</p><p><strong>How sound is used in an interface:</strong></p><ul><li>Simple sounds: to grab user’s attention and feedback — buzz, ring, beep.</li><li>Ecological sounds: to tell the user what us happening by emulating real-world sounds — e.g. the trash can sound whenever a user sends a document to trash on their PC.</li><li>Speech and music.</li><li>Buttons.</li><li>Setting the mood: to immerse a user in an environment or provide a general sense of context — e.g. the soundtrack of a Playstation game.</li></ul><p>Next, we’ll take a deep dive into how memory works and how we can apply this to designing interfaces.</p><h4>Icon credits</h4><p>Brain: <a href="https://thenounproject.com/search/?q=brain&amp;i=355285">https://thenounproject.com/search/?q=brain&amp;amp;i=355285</a></p><p>Action: <a href="https://thenounproject.com/search/?q=action&amp;i=1396548">https://thenounproject.com/search/?q=action&amp;i=1396548</a></p><p>Eye: <a href="https://thenounproject.com/search/?q=eye&amp;i=387224">https://thenounproject.com/search/?q=eye&amp;i=387224</a></p><p>World: <a href="https://thenounproject.com/search/?q=world&amp;i=61831">https://thenounproject.com/search/?q=world&amp;i=61831</a></p><p>Ear: <a href="https://thenounproject.com/search/?q=ear&amp;i=687334">https://thenounproject.com/search/?q=ear&amp;amp;i=687334</a></p><p>Smell: <a href="https://thenounproject.com/search/?q=smell&amp;i=537889">https://thenounproject.com/search/?q=smell&amp;i=537889</a></p><p>Touch: <a href="https://thenounproject.com/search/?q=touch&amp;i=607656">https://thenounproject.com/search/?q=touch&amp;i=607656</a></p><p>Taste: <a href="https://thenounproject.com/search/?q=lick&amp;i=1175843">https://thenounproject.com/search/?q=lick&amp;i=1175843</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e134e3b4401f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Basics of Interaction Design]]></title>
            <link>https://medium.com/@avimair/the-basics-of-interaction-design-c324a0b68e1e?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c324a0b68e1e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Fri, 19 Jan 2018 11:41:53 GMT</pubDate>
            <atom:updated>2018-01-20T14:04:09.697Z</atom:updated>
            <content:encoded><![CDATA[<h4>My key takeaways from the Interaction Design Foundation’s course on HCI: Interaction Design</h4><h4>Design interactions, not just interfaces</h4><p>Let’s start with an obvious one which despite being so, is forgotten by so many designers every day! Remember that we are designing interactions, which can be defined as a series of things a user does with our product, getting them to some goal or endpoint.</p><p>Zooming even further out from single interactions, we need to intentionally design the whole flow of interactions and how they all fit together. This includes the interactions which the user had with our website or our Facebook ad before downloading the app itself.</p><h4>Design = achieving goals within constraints</h4><p>This definition of design prompts a few questions which we can ask to drive our design process:</p><ul><li><strong>Goals </strong>need a purpose in order to be accurately defined, so we need to work out who we are designing for and why do they want what we are designing?</li><li><strong>Constraints </strong>can be thought of as the resources we have available to us, so which materials and platforms will we use? What kind of expertise, money, time and team do we have available to us?</li></ul><p>In order to achieve our goals within the given constraints, we have to make trade-offs between what we would want in a Utopian world and what we can realistically achieve. So, design is all about making decisions about trade-offs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3X4KukbbjQU5zxp2b4R-w.jpeg" /><figcaption>Achieve the goal but don’t underestimate constraints</figcaption></figure><h4>The interaction design process</h4><p>Whilst there are plenty of different interaction design processes and each designer may have unique nuances to their own, most tend to follow this general recipe:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oB4HWAgAnsn6AtMB1xRc9w.png" /></figure><p>If you come across a perfect design, that would imply a poor design process because if it’s too good, it might mean that the designer has probably spent too much time and effort, without consideration for constraints. Of course the extent to which this applies depends on the budget, time and resources made available to the designer, but it’s worth bearing in mind.</p><h4>Get to know your users: personas and probes</h4><p>First of all, we need to accept that even though we might count ourselves as a user of our product/service, most other users probably have very different characteristics to you, like most other human beings you walk past on the street. So before we do anything else, we need to understand who our users are.</p><p>Most designers use personas to craft a story around their users. Having done thorough research, you will probably unearth some prominent characteristics and similarities that many users share, which can help to split them into sub-groups. <strong>Crafting a story around the characteristics of these groups and building them up as though they were a character in a novel, is the art of a colourful and informative persona.</strong></p><p>The Interaction Design Foundation seemed to lean more towards written descriptions of personas but there are many different approaches. You can use data which you’ve collected through your research, analyse their user journey and even base them on assumptions. Just make sure that you add enough colour and clarity for the whole team to design with these personas in mind.</p><p>Probes allow for observation and data collection on prospective users. Typically, they split into cultural probes and technology probes.</p><p><strong>Cultural probes</strong> are there to help when direct observation of users proves difficult, such as around the home. Test participants are given a probe pack containing things which encourage them to examine their lives and record relevant events or thoughts. These could include a camera, notebook etc. The aim is to enculture yourself into the user’s life, to inform other interviews, not to replace traditional research methods.</p><p><strong>Technology probes</strong> can be used to give test participants a taster of what your new technology/design might be like. This is not the same as prototyping! The idea is to expose potential, rather than show what the idea will be like.</p><h4>What users do: scenarios</h4><p>Whilst personas aim to describe a specific individual, scenarios are more about exploring their behavior and what our users do to achieve a particular aim.</p><p>Your scenarios should answer the following questions:</p><ul><li><strong>What can they see?</strong> This could take the form of sketches or screenshots.</li><li><strong>What do they do?</strong> Use the keyboard, mouse or touchscreen hotspots to illustrate this.</li><li><strong>What are they thinking?</strong> Go really descriptive here, develop richness and craft a story.</li></ul><p>Why use scenarios?</p><ul><li>Explore the interaction: understand what happens when.</li><li>Explore their cognition: understand what users are thinking at each stage.</li><li>Explore the architecture: understand how the user’s mental models measure up against the way you have structured the information architecture.</li><li>Communicate with the team: many stakeholders (especially business folks), will not understand most of what you are doing, so scenarios are a fantastic visual and colourful way to help them see the way your users do.</li></ul><p>Scenarios are great but just make sure that you use several, do not just rely upon one or two. Otherwise, you could miss alternative branches of action which users could take or errors which they could encounter whilst using your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ye3xr2741G4fXqlwn9g9IQ.jpeg" /></figure><h4>Navigation design</h4><p>Think about how the following contribute to your app/website’s navigation:</p><ul><li>Widget choice: menus, buttons and elements for the user to interact with.</li><li>Screen/page design: consider where these elements should be placed.</li><li>Structure.</li><li>Environment: how your product fits into the ecosystem of other related apps or websites which the user might interact with too, or in tandem with yours.</li></ul><p><strong>At all times, your users should know:</strong></p><ul><li>Where they are in the navigation of the app/website.</li><li>What they can do there, with the controls presented.</li><li>Where they are going or what will happen if they select one of these controls.</li><li>Where they have been or what they have done once a particular action has been taken, providing sufficient feedback to prevent them from trying to perform a task over and over. This could cause serious problems especially in cases like ordering an online product or sending a bank transfer payment.</li></ul><p><strong>Hierarchical diagrams</strong> should be used to map out the screens of the application, illustrating everything that is contained in the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLCAz4hSoP5QY4nvjdTe9Q.png" /></figure><p><strong>Miller’s 7±2</strong> is a rule from psychology which has been severely overused when it comes to navigation design. It states that the human memory can only handle 7 pieces of information at a time (give or take 2). So many designers have taken this to mean that they should never design menus with more than 7±2 items. It might be true that if a user goes 7±2 stages deep into your website’s hierarchy, then they will probably begin to forget some of the earlier screens which they came into contact with because this requires short term memory recall. However if the user is presented with more than 7±2 menu options, they do not have to recall anything, all the information they need is visually presented at the same time. So don’t fall for this old wives tale!</p><p><strong>Network diagrams</strong> differ from hierarchical diagrams in that they show different paths through a system. They are about the actions and tasks that the user can execute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IOSUCEj9Hxdqkox7TLS8g.png" /></figure><p><strong>Remember, it’s not all about you!</strong> The user’s experience is not just limited to your application. You need to consider how the user got there or if they use other products in tandem with yours. Consider how yours fits into the wider ecosystem of the world around it.</p><h4>Users and layouts</h4><p>Whilst a particular layout of content may make sense to us, we need to organise it from the user’s point of logic, especially when it comes to the them entering information or data. We can use task analysis to work out which tasks the user will be undertaking and in which order, then talking to them about which pieces of information which they consider to be related. In this way, the user will feel a natural progression to entering the information and will hence be far more likely to complete it.</p><p><strong>Consistency is key.</strong> When considering how to communicate to users what is active and what is passive, stick to your design rules and do not deviate, or you’ll just end up with a confused and frustrated user. This goes the same for consistency in typography, colour and language.</p><p>In this course, they defined <strong>affordances </strong>as the actions that are possible to perform with something and the appearance that it can do this thing. It’s a rather loose definition and you’d find a more refined one in <em>The Design of Everyday Things</em>, but it offers a rough idea from which the uninitiated can proceed. However, the core idea is that we should carefully design our affordances so that they are easy for the user to identify, especially if they do not follow convention.</p><p>Whilst aesthetics should never supersede utility, it is an undeniable fact that aesthetically pleasing designs improve user satisfaction and make people want to use it more. If something is incredibly usable but looks terrible, no one will use it, and visa versa. <strong>Design is about finding the meeting point between utility and aesthetic.</strong></p><h4>Iteration and prototyping</h4><p>The key takeaway from this course’s discussion on prototyping was that in order to make the iteration and subsequent redesign worth it, you need to start with a design which is already fairly good. If not, when you test your new prototype with users, there will be improvements but your product may not be the best it could have been because you did not have a good starting point. Another round of iteration may be in order.</p><p>Whilst this course’s introduction to interaction design didn’t teach me much which I did not already know, it helped to crystallise some of my knowledge, reiterating its importance and how these all fit together under the umbrella of interaction design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3vlxneAo50hBQYOZbT_ug.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c324a0b68e1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Crash Course in App Design]]></title>
            <link>https://medium.com/@avimair/your-crash-course-in-app-design-61a79e9d7b55?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/61a79e9d7b55</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 15:18:50 GMT</pubDate>
            <atom:updated>2018-01-12T15:18:50.140Z</atom:updated>
            <content:encoded><![CDATA[<h4>A summary of Steven Gates’ crash course in app design from The Crazy One podcast</h4><p>Most UXers will know Steven Gates as the creative yet frank and pragmatic mind behind design at Citi Bank, Starwood Hotels and Apple but few might know that he actually runs his own podcast discussing some of the meatiest and crucial but overlooked aspects of being a designer (<a href="http://podcast.stephengates.com/">The Crazy One podcast</a>).</p><p>Episode 42 gave a crash course on his methodology to approach app design, some of the mistakes he sees designers making and how to avoid these yourself. Many of these points might seem obvious after-the-fact but I can guarantee that unless you are a UX mastermind like Gates, you’ll learn something from this post which will completely change the way you craft your apps.</p><p>If you fancy a quick overview of the content, <a href="http://podcast.stephengates.com/episode-42-app-design-how-to-design-a-great-mobile-app/">click here to see his show notes</a>. If you’d like the detail … well that’s what this post is for!</p><h4>Part 1: User primer</h4><p>As any UX designer worth their salt will know, the very first step is research. You need to understand who is going to use your app, how, when and why. Even if you’re not designing your app from scratch, it is imperative that each time you run research, you do so with fresh eyes and seek to learn, not just to confirm your original hypotheses.</p><p><strong>Gates suggests starting with two simple questions:</strong></p><ul><li>What is it that I’m designing?</li><li>What is the goal that the average person would achieve with this app?</li></ul><blockquote>“Look for the trend-line, not the headline”</blockquote><p>In order to help answer these questions, you need to understand the 5 segments of the device ecosystem and the <strong>time horizon</strong> on each. The time horizon is an approximation of the age of the work you will be doing on these devices. For example, a time horizon of 1 year means that you will be working creating, editing or updating files on this device for the next year in the future, which might have been created up to a year in the past.</p><p><strong>5 segments of the device ecosystem</strong></p><ul><li>The Cloud: time-horizon may be eternal (the Cloud is generally used for storing and archiving files)</li><li>Desktop/laptop: 1 year time-horizon</li><li>Tablet: 3–5 month time-horizon</li><li>Smartphone: 1 month time-horizon</li><li>Wearables: live time-horizon (wearables are about what we are doing right now, in this moment)</li></ul><p>CAUTION: Gates insists that this does not mean that our wearable apps should devolve into clumsy messaging apps. Instead, we need to carefully and intentionally curate the content in our apps in a way that will actually make it useful in the moment.</p><p><strong>3 crucial artifacts to build before doing anything else</strong></p><ul><li>Personas — Some teams even create life-sized cardboard cutouts of these personas as a physical representation of the user, so they can refer to them whilst coming up with ideas and ask “is this what people really want?”</li><li>User scenarios — Stories and cases to establish how the persona is going to act and interact with the world around them as it refers to our our app.</li><li>Experience maps — A document that allows you to explore all the possible different conditions for a single interaction. These are useful because no app is one-dimensional, because no user is one-dimensional. I used an experience map to organise insights from usability testing when I was redesigning the British Museum’s app in a recent case study.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKyPOzbMH60PnrHt3wk7QA.jpeg" /><figcaption>Yes, I built an experience map on my cupboard!</figcaption></figure><h4><strong>Part 2:</strong> <strong>Designing for different platforms</strong></h4><p>Whilst iOS may be the choice of most designers, we should remember that the vast majority of smartphone devices in circulation actually use Android.</p><p>Not only do we have to design for both iOS and Android, but Gates reminds us that we have to <strong>design for both iOS and Android! </strong>If we do not design for these two platforms separately, users will feel as though the design has just been ported over and is not a native experience. The reason for this is that iOS and Android use a completely different set of usability and interaction patterns. This applies to not just the placement of buttons but how screens transition, how buttons react when selected, unsaid rules for how the interface should react which all users of those platforms know.</p><p>Designing separately or Android is especially important and often more challenging because of the <strong>device fragmentation</strong>. Apple have the advantage of producing all of the devices which their OS runs on. However Android is used on a myriad of different devices, so the way buttons react differs from device to device.</p><p><a href="https://developer.android.com/guide/practices/ui_guidelines/index.html">Click here</a> to check out Android’s design guidelines</p><p><a href="https://developer.apple.com/ios/human-interface-guidelines/overview/themes/">Click here</a> to check out iOS’ design guidelines</p><h4>Part 3: Be different … selectively</h4><p>This reminded me of Facebook’s motto of “move fast with a stable infrastructure”. Having gone through the guidelines of the platform/s you are designing for, you now have to decide where you are going to stick to the interaction guidelines and where you are going to break the rules to reflect the brand you are designing for or your unique functions.</p><p>From his time at Apple, Gates lets us in on the secret that nothing will make them less likely give yours the status of ‘Featured App’ in their App Store, than if you design an app which looks exactly like it was made by Apple. In order to stand out, they want your app and your design, they want you to use your brain.</p><p>However, you need to ensure that these breaks with platform conventions are consistent throughout your app and that they are necessary, not just because you think that they are cute or would look cool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AnmQd3T5y_k9M0e0rAfxYQ.jpeg" /></figure><h4>Part 4: Basics of design</h4><p>Gates feels that too many designers think of the following points as an afterthought, when they should actually be decided first and form the basis for your design.</p><p><strong>Which orientation are you going to build your app in? </strong>Some apps looks great in portrait, others in landscape, some in both, but you have to decide which works best for yours. Consider how users are going to hold their device whilst using your app. Is there going to be an advantage to changing orientations? If not, is there any point is using resources to design for both? Spotify’s iOS app is only portrait.</p><p><strong>What is your target app size? </strong>If a user is on-the-go, and your app’s file size is too large, they will not be able to download or update it without connecting to WiFi. Depending on how you anticipate users will interact with your app and where they will typically be when using it, you will want to consider if you really need to make the file size so large or could it be small enough to update whilst they are riding the bus into work?</p><p><strong>Which device models and screen sizes will you support? </strong>Use data and analytics to work out which devices the bulk of your users operate with. Gates sees many designers fall into the illusion that just because we always have the latest generation iPhone as techy designers, we assume that everyone else does too. The reality is that many people are 3 or more generations behind. We need to optimise their experience too.</p><p><strong>What are the ergonomics or your chosen orientation? </strong>Depending on whether you’ve chosen to go for portrait or landscape, consider the ergonomics of your interface. Are any important buttons too tricky to reach with one hand?</p><h4>Part 5: Interaction design basics</h4><p>As it applies to designing a great app, Gates offers 6 elements to focus on most:</p><p><strong>1. Have goal-driven design: </strong>Tailor your workflow to suit the specific goals which the app allows your users to complete and which make your offering unique.</p><p><strong>2. Usability: </strong>People keep apps which are both desirable and usable, so don’t get caught up in designing cool interactions which look good on Dribble but which confuse most users, or you’ll end up with lots of likes on Dribble and a 1-star app store review.</p><blockquote>“Usability … makes a product useFUL, which is the first step in being desirable”</blockquote><p><strong>3. Define and repeat signifiers: </strong>Whilst anyone who has read Donald Norman’s famous book <em>The Design of Everyday Things</em> will already be familiar, Gates defines signifiers as “what are the things that I’m going to teach people that whenever they see it, whenever they experience it, that it means something”. You could use a specific colour to indicate which pieces of content are actionable, eliminating the need for flashy arrows and excessively obvious signage. Just make sure you are clear on the rules you set and protect them, do not make exceptions or users will throw their device against the nearest wall in confusion.</p><p><strong>4. Learnability: </strong>This is where the design guidelines for iOS and Android can come in useful, so first time users can instinctively use your app. Make your app easily learnable by making users aware of the functions with not only visual design but also the design patterns so they recognize how to perform interactions from screen to screen.</p><p><strong>5. Feedback and response time: </strong>Users expect apps to respond quickly, but design does not exist in a vacuum, we might need to make database calls and image loads if we do not want to automatically load these into the app due to concerns over it’s file size. Just ensure that the design does not become a barrier to people achieving what they want to with this app.</p><p><strong>6. Make sure your app is accessible: </strong>As an American, Gates refers to ADA compliance but this applies to any designer around the world. Ensure that your app is accessible for those with colour blindness or other disabilities listed in your region’s compliance documentation. You can still design an elegant app by being compliant, it does not mean you have to compromise and end up with a shitty result.</p><h4>Part 6: Visual design and branding</h4><blockquote><em>“Great design is a visual expression of great thinking”</em></blockquote><p>Gates highlights some of the key elements of visual design which anyone should bear in mind and put intention behind when designing any app.</p><p><strong>1. Consistency: </strong>We referred to consistency earlier as regards signifiers but another crucial element is to design everything on a grid. This helps us design with consistency and also ensure that the user does not have to re-learn the same things as they move from screen to screen.</p><p><strong>2. Create visual hierarchy with colour, lines, type and type weighting: </strong>Using these elements to show people what you want them to focus on, helps to minimize the amount of navigation and copy you need, lending itself to a far more elegant and intuitive design.</p><p><strong>3. Typography: </strong>Keep your typography simple and consistent, critically analyzing where you really need to use fonts which are specific to your brand and where you can use the standard fonts. In the spirit of making our app’s file size as small as possible, you can make the typeface’s file itself much smaller for your developers. An easy way to do this is to in and take out alternative languages and characters which you do not need to use.</p><p><strong>4. Branding: </strong>Gates tell us that once users of his apps have downloaded and opened them, there is never a visible logo on any of his designs. He feels that this is an archaic remnant from web design, and that we can claim back this real estate to use it for informational content which users can act on.</p><p><strong>5. Reinforcing the brand: </strong>If we’re not reinforcing the brand through the logo, then we can do so through tone of voice and interaction design. In terms of interaction design, the animations and the way elements behave can be all you need. Will your elements be styled and react fast or slowly, fancy or intricate, colourful or conservative?</p><h4>Part 7: Onboard like your app depends on it … it does</h4><p>The onboarding experience should not be the afterthought that it so frequently becomes with most designs.</p><blockquote>“The average person will decide if an app has value and they will decide if they are going to keep it in the first 2–3 minutes of using an app”</blockquote><p>So we cannot afford to mess up first impressions with a mediocre onboarding experience.</p><h4>Part 8: Develop short-term memory loss</h4><p>As advised in Steven Krug’s fantastic book <em>Don’t Make Me Think</em>, designers need to step out of our own heads and ask ourselves, “if I didn’t know anything about this app, does this make sense?”</p><p>I referred to a similar phenomenon in my article <a href="https://medium.com/@avimair/design-smarter-with-vu-jad%C3%A9-a91d56c21d0b">Design Smarter with “Vujade”</a>, in which I expand on a term that I stole from IDEO’s Tom Kelley, to look at your/your team’s designs with fresh eyes, even though you’ve spent weeks if not months toiling over the details in endless meetings. It’s a hard skill to master but one which we should all strive for and can start practicing today.</p><p>Thanks for reading this overview of Stephen Gates’ crash course in app design, I hope you learnt something valuable. Make sure to check out his podcast for more, <a href="http://podcast.stephengates.com/">The Crazy One</a>. Until next time, adios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KbdyW7pP8jGaZZheYXf1xw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61a79e9d7b55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Design of Everyday Things — Part 1]]></title>
            <link>https://medium.com/@avimair/the-design-of-everyday-things-part-1-26d0ea12e3f7?source=rss-a3afca5af9e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/26d0ea12e3f7</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Avi Mair]]></dc:creator>
            <pubDate>Fri, 29 Dec 2017 19:31:09 GMT</pubDate>
            <atom:updated>2017-12-31T13:47:51.421Z</atom:updated>
            <content:encoded><![CDATA[<p>To almost every UX designer, <em>The Design of Everyday Things</em> by the great Donald Norman is gospel. Out of all the books that I have read on design, whilst it has undoubtedly taught me the most, it can be a rather hefty read, so even though I would recommend anyone who works with product to read the full book themselves, I thought the following posts would help give a brief overview to the uninitiated or a jolt of caffeine to those in need of a revision.</p><p>This revision of The Design of Everyday Things will be released in chapters, so as to include as much of my key insights as possible, but also to provide it in a consumable, bitesize fashion.</p><p>DISCLAIMER: this is my interpretation of The Design of Everyday Things, unless bookended in quotation marks, these are my own words.</p><p>The tools, models and systems which Norman provides, help us to empathise with and understand our users with unique insights, which can be found in very few other contemporary pieces of work. One of my favourite insights was that whenever human error is blamed for an accident or problem with the use of a product, <strong>it is very seldom an issue of the user’s incompetency, it is almost always a design problem</strong>. When we shift blame away from users and inspect each error as a design problem, we can begin to uncover opportunities for improvement, growth and innovation. It is with seemingly small paradigm shifts such as this, that have made this book such a core component to the UX designer’s toolkit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CtOATbW-ewf3UHbrZVi7Iw.jpeg" /><figcaption>It’s a design problem … most of the time</figcaption></figure><p><strong>Discoverability &amp; Understanding</strong></p><p>Norman kicks off the first chapter with what he believes to be the two most important characteristics of good design: <strong>discoverability and understanding</strong>. All of the principles outlined in the rest of the book sprout from adopting this lens, so it’s important to comprehend the difference between the two.</p><p>Discoverability (the what, where and when): Can the user easily work out what the product can do and how to get it to perform the tasks required?</p><p>Understanding (the deeper how and why): What does it all mean (the controls, settings etc.)? How does this work?</p><p><strong>The Fundamental Principles of Interaction</strong></p><p>Following on from this, it is important to understand <strong>the fundamental principles of interaction</strong> to help designers to produce pleasurable experiences.</p><p><strong>Affordances</strong>: “What actions are possible” between the user and the design.</p><p><strong>Signifiers</strong>: “Communicate where the action should take place” or how to activate the affordance.</p><p>An example of poor design of signifiers could be whenever you see a “push” or “pull” sticker pasted onto a door handle at a department store. The inherent design should make it more obvious how the user can interact with this door (the affordances), we should not have to use instructions to help them along the way.</p><p><strong>Mapping</strong>: The relationship between the controls on a design and the result they produce. Natural mappings often give users the quickest understanding of how to use a design.</p><p>As I swipe my finger to the left when turning to the next page of a Kindle book, this mimics the action of turning a page of a physical book as I would open the next page, turning the current page to the left. This is an example of a natural mapping.</p><p><strong>Feedback</strong>: Somehow informing users that the system is working on their request. E.g. a button on a website shifting down and up slightly or changing colour as the user clicks on it.</p><p>CAUTION: However, Norman warns us that “too much feedback can be even more annoying than too little”, especially when it comes to persistent beeping sounds!</p><p><strong>Conceptual model</strong>: A simplified understanding of how something works. E.g. the files and folders displayed on a computer help the user to understand where their work is being stored and how it is organised.</p><p><strong>System image</strong>: The combined information available to the user, which the designer uses to communicate everything about how to use the product to the user (as the designer cannot be there in-person to show each individual how to use it). The system image bridges the gap between the designer’s conceptual model and the user’s conceptual model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yKKELK_gHw2G9L3QFSvpTQ.png" /><figcaption>The system image is how the designer communicates</figcaption></figure><p>COMING SOON: The Design of Everyday Things — Part 2</p><p><strong>Credit for icons</strong></p><p>Spanner: <a href="https://thenounproject.com/search/?q=tool&amp;i=894573">https://thenounproject.com/search/?q=tool&amp;i=894573</a></p><p>Nail: <a href="https://thenounproject.com/search/?q=nail&amp;i=1405234">https://thenounproject.com/search/?q=nail&amp;i=1405234</a></p><p>Bolt: <a href="https://thenounproject.com/search/?q=bolt&amp;i=926205">https://thenounproject.com/search/?q=bolt&amp;i=926205</a></p><p>Checklist: <a href="https://thenounproject.com/search/?q=checklist&amp;i=1146169">https://thenounproject.com/search/?q=checklist&amp;i=1146169</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26d0ea12e3f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>