<?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 Saffad Khan on Medium]]></title>
        <description><![CDATA[Stories by Saffad Khan on Medium]]></description>
        <link>https://medium.com/@saffad?source=rss-71831281ee97------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2ILZywND50zRWV4IhfeP3A@2x.jpeg</url>
            <title>Stories by Saffad Khan on Medium</title>
            <link>https://medium.com/@saffad?source=rss-71831281ee97------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:11:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saffad/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[How side projects can make you a better designer at work]]></title>
            <link>https://medium.com/deliveroo-design/how-side-projects-can-make-you-a-better-designer-at-work-cf0e8a201bd6?source=rss-71831281ee97------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf0e8a201bd6</guid>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[deliveroo]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Saffad Khan]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 13:46:21 GMT</pubDate>
            <atom:updated>2019-02-08T10:35:05.841Z</atom:updated>
            <content:encoded><![CDATA[<p>I want to share how designing, building and supporting my own side project has exposed me to lesser known parts of the product development process and accelerated my learning and development. And how I’ve leveraged this experience as a Product Designer at Deliveroo.</p><p>The industry talks about the importance of side projects a lot. Some great posts have already been written on the subject. Here are a couple:</p><ul><li>Julie Zhou says that <em>“side projects give me an outlet for exploring new challenges and new ways to be creative.”</em> — <a href="https://medium.com/the-year-of-the-looking-glass/the-importance-of-side-projects-cf9f63954031">The importance of side projects</a></li><li>Tanner Christensen says that “<em>Side projects can be immensely rewarding to talk about. They demonstrate a lot about how you work.”</em> — <a href="https://medium.freecodecamp.org/how-to-talk-about-your-side-projects-18b96f192817">How to talk about your side projects</a></li></ul><p>I didn’t anticipate how much working on my side project would positively impact my every day work at Deliveroo.</p><h4>My side project</h4><p>Three years ago <a href="http://twitter.com/@ablinov">Alexey</a> and I partnered up to solve a problem for ourselves: How can we quickly see movies showing in cinemas nearby? In early 2016, while working full-time, we launched our first iOS app: <a href="https://itunes.apple.com/gb/app/cinemap/id1112309274?mt=8">Cinemap</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*QHeJTHFwvR1d1fCUdLQRng.png" /></figure><p>It’s been growing steadily ever since and is now the<strong> top rated Cinema Showtimes app in the UK</strong>. We couldn’t be prouder. But this post isn’t about how we built it (a lot of hard work) or why you should get it (you definitely should!).</p><p>Instead, I want to share the top three things I learned on the way that changed my approach to product design:</p><ol><li>Collaborate with engineers</li><li>Focus on the “90/10” solution</li><li>Talk to your users</li></ol><h4><strong>Collaborate with engineers</strong></h4><p>Your design isn’t solving anything if it’s sitting in a design file. It has to be built and released into the hands of users to solve the problem you set out to solve. Unless you’re confident building your own product, your engineers will be the ones to make it a reality. It’s easy to blame the engineers when the shipped product doesn’t align with your designs or expectations. But that isn’t the best mindset. Your design should be the product that ships, and the best way to get there is by working closely with the engineers who build it.</p><p><strong>Building partnerships<br></strong>With a lot of help from Alexey, I learnt how to use Xcode, taught myself Swift, made pull requests, did my own testing and read a lot on StackOverflow. I’ve come to appreciate the engineering process a lot more.</p><p>I’ve leveraged this at Deliveroo by contributing directly to the code by making design tweaks and partnering with an engineer to solve problems. You’d be surprised how helpful and patient your engineers can be when you are as invested as they are. The experience is rewarding because you’re learning how to be better partners. As a bonus, being close with engineers pays off when you want to polish a UI or take an idea and build something together. It’s the fastest way to get things done.</p><p><strong>Understanding constraints<br></strong> Assuming you have identified an opportunity or an important problem to solve, the first step is usually understanding the engineering constraints.</p><p><em>Do we have the data?</em></p><p><em>If we don’t, how can we get it?</em></p><p><em>How reliable is it?</em></p><p><em>How complex is the existing UI?</em></p><p>Identifying the unknowns early will help you adjust your plans later on. The worst outcome is spending a tonne of time perfecting a design that can’t be built in the given constraints. Always ask an engineer before you design.</p><p><strong>A transparent design process<br></strong>Behind every feature on Cinemap is a transparent design process. My default is share often and early. I learned a while back how valuable sharing early work can be and I use the same approach at Deliveroo.</p><p><em>What about sharing to non-designers?</em></p><p>Alexey and I have been working on Cinemap for a while now. He’s the engineer but he really cares about design. We talk about user experience and UI, we make quick decisions and bounce ideas off each other. The shipped product is always better as a result.</p><p>At Deliveroo, designers and engineers sit together. We have design reviews with different disciplines. We also <a href="https://medium.com/deliveroo-design/the-power-of-the-design-doc-fbf5070163f8">write design docs</a> to have a clear source of truth and all <a href="https://medium.com/deliveroo-design/4-reasons-we-love-figma-at-deliveroo-7a6db84b5239">designs are on Figma</a> for colleagues to view and leave feedback. Working closely with engineers and being better collaborators is invaluable in building better products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sFby7R9O36SgwjzgsqzYqQ.jpeg" /><figcaption><a href="https://medium.com/u/5bb9021d4764">Stefan Dougan-Hyde</a> and I polishing transitions on the Deliveroo app</figcaption></figure><h4><strong>Focus on the “90/10” solution</strong></h4><p>Given that Cinemap is a side project, we only have weekends and evenings to work on it. This forces us to use our time effectively by working on the thing that delivers the most value to our users. We don’t have a product manager so I quickly learnt what it means to define scope, say no and stay focussed.</p><p>The “90/10” solution has worked really well for us and changed the way I approach product design. YCombinator explains it best:</p><blockquote>Look for a way in which you can accomplish 90% of what you want with only 10% of the work/effort/time. If you search hard for it, there is almost always a 90/10 solution available. Most importantly, a 90% solution to a real customer problem which is available right away, is much better than a 100% solution that takes ages to build. — <a href="https://en.wikipedia.org/wiki/Paul_Buchheit">Paul Bunchiet</a> (YCombinator)</blockquote><p>It’s harder than it sounds. You have to talk to your users and ask “Why?” a lot. You’ll learn a lot from your users by releasing a simple solution that solves a problem <em>really well</em>. For my work at Deliveroo this would mean understanding the engineering constraints and designing the “90/10” solution first. The learnings on release will inform your future iterations.</p><p>To save more time, don’t reinvent patterns. Reuse UI and take advantage of platform capabilities where possible to get to your solution faster. This has saved me many hours and is one of the reasons why we are investing in a growing <a href="https://www.youtube.com/watch?v=6C0yvuWJc84">design system</a> at Deliveroo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eySeQ9n1YDtdtdOxrOOzUw.png" /></figure><h4><strong>Talk to your users</strong></h4><p>A lot of startup advice centers around talking to your users to ensure that the product you’re building is is what they want. There’s a <a href="https://mastersofscale.com/brian-chesky-handcrafted/">great story</a> on how the founders of Airbnb offered to professionally photograph customers’ homes as an opportunity to talk to them.</p><p>Our simple method of talking to users is the Feedback tab. I tell people that it’s the single most important feature we have built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GPwA1eC7UzCV5-Mpt7rWLg.jpeg" /></figure><p>People message us with their pain points, what they like and what they want. We’re small enough to reply to every one and ask for details. We’ve also become customer service reps overnight, learning how to deal with frustrated users. Listening to feedback has been essential in Cinemap’s growth and has taught me two things:</p><ul><li>Passionate users will love talking to you</li><li>What users say they want isn’t always what you should build</li></ul><p>Uncovering the real user need is a core part of my design process at work. <a href="https://www.intercom.com/blog/using-job-stories-design-features-ui-ux/">Jobs to be done</a> is a good framework to help with that. I’m also lucky enough to have a great <a href="https://medium.com/deliveroo-design/research/home">research team</a> at Deliveroo to gather user needs and help me answer questions.</p><p>Whether you’re a small team or corporation, pay attention to your users and get to know them. It’s invaluable in designing an empathetic experience.</p><p>So to summarise, here are the top learnings from my side project that I leverage every day at Deliveroo:</p><ol><li>Be a better partner to other disciplines</li><li>Solve the right problems efficiently</li><li>Talk to your users</li></ol><p>You’re only accountable to yourself on a side project, so make sure it’s something you’re passionate about to stay motivated. It’s also okay to make mistakes because you can’t learn unless you allow yourself the freedom to fail.</p><p><strong>Side projects are an excellent way to level up your skills whether you’re a designer or engineer. It will accelerate your learning and development in ways you won’t anticipate, and hopefully enjoy the journey too.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf0e8a201bd6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/deliveroo-design/how-side-projects-can-make-you-a-better-designer-at-work-cf0e8a201bd6">How side projects can make you a better designer at work</a> was originally published in <a href="https://medium.com/deliveroo-design">Deliveroo Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A year of designing at Hailo, a startup in London]]></title>
            <link>https://medium.com/@saffad/a-year-of-designing-at-hailo-a-startup-in-london-4958b4a23247?source=rss-71831281ee97------2</link>
            <guid isPermaLink="false">https://medium.com/p/4958b4a23247</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Saffad Khan]]></dc:creator>
            <pubDate>Wed, 07 Oct 2015 13:14:48 GMT</pubDate>
            <atom:updated>2016-08-15T20:58:40.231Z</atom:updated>
            <content:encoded><![CDATA[<h4>And what I learnt as a Product Designer</h4><blockquote>Learn Early and Learn Often</blockquote><p>One year ago I joined <a href="http://hailoapp.com/">Hailo</a> from <a href="http://monitisecreate.com/">Monitise Create</a> as a Product Designer. I was super excited at the move from agency to startup but also anxious about what designing at a top startup in London would be like. Here I am a year later thankful and smarter about my craft.</p><p>There’s a tonne of stuff I’ve learnt, like how to photoshop your boss into a <a href="https://www.dropbox.com/s/t4b0iyai7pr0n8o/Uxjedi.jpg?dl=0">jedi</a> or how to set up usability rooms but I’ll try to cover the most important bits. This post also covers things I would have loved to known before starting at Hailo. Here it goes:</p><h3>A-Players</h3><p>The very first thing that was apparent to me on day one was the abundance of talent and <em>really </em>smart people. Not just incredibly good at their craft, but the whole lot: technical, business and creative aspects. There’s a real entrepreneurial vibe and I witnessed the huge importance of culture in a business. We had small teams, but it was clear to me that small teams with big ideas can have massive impact. One of the things that are great about the culture is that everyone is an <a href="http://blog.capwatkins.com/the-ownership-problem">owner</a>. Individuals aren’t siloed and are encouraged to share WIP work. <a href="http://alistapart.com/article/sharing-our-work-testing-feedback-in-design">Sharing</a> is caring and ideas can come from anywhere!</p><h3>The Product Designer</h3><p>So what do I do as a Product Designer? Here at Hailo, because we’re a small design team it’s quite simply <strong>whatever is required to meet the goal of the product</strong>. Sometimes I gotta retrieve and understand data, sometimes I gotta interview our drivers, some days I’ll be prototyping, cutting assets or copywriting! It’s no longer just brainstorming and visual + interaction design. I get to touch so many parts, heck, I even shipped production code for WatchOS! It might sound daunting but I love it as it gives me a deep understanding of building products, not just the surface. As a product designer working on all those parts can improve your product and if you’ve got a small team like us it can be achieved with the right personality, a little training and practice.</p><p>At first it was a little overwhelming, but there are excellent design processes on the web that I find to be absolutely invaluable especially for fast-paced and small team environment like Hailo. I always aim to incorporate these into my workflow:</p><ul><li><a href="http://www.gv.com/sprint/"><strong>Google Ventures Design Sprints</strong></a>: Developed by Jake Knapp and his colleagues at Google Ventures. It’s a 5 day product design process aimed at helping businesses solve problems and answer questions. They‘ve got a bunch of very useful <a href="http://www.gv.com/library/">articles</a> and <a href="https://developers.google.com/design-sprint/downloads/DesignSprintMethods.pdf">methods</a> that I refer to. I also can’t wait for the <a href="http://www.amazon.co.uk/dp/150112174X">book</a>.</li><li><a href="http://jobstobedone.org/"><strong>Jobs to be Done</strong></a><strong>: </strong>“It is a way of looking at the motivations of customers in using a product, rather than the traditional marketing techniques of slicing and dicing customers according to demographics” (<a href="https://blog.intercom.io/using-job-stories-design-features-ui-ux/">Intercom</a>). I like using this framework to help me frame my solutions better.</li></ul><h3>Start with the Whys</h3><p>As designers we can fall into the trap of designing solutions towards the end of the product development cycle “We need a new menu for this feature”. At Hailo we usually start with “Let’s understand more about x” which then leads to discovery type questions “Why do you use this?”. Often, we think we discover a problem in the product then dive into solutions, but constantly asking yourself <em>why </em>tends to reveal a deeper problem that needs to be solved.</p><p>Why are you even bothering to work on this? What problem are you solving? I’ve been forcing myself to get into the habit of always asking these questions. To achieve this, I write down everything I can before starting any design so I can begin to frame the problem better and communicate it with others.</p><h3>Customer is King</h3><blockquote>“We need to stop calling people users<em>.</em>” — Julie Zhou</blockquote><p>That really stuck with me and is especially true at Hailo. One of the most important processes we have is <strong>customer research</strong>. That can involve anything from interviews to usability studies.</p><p>Coming from a background where I hadn’t done much usability studies or customer interviews, and then having it on almost every piece of work became a revelation. No longer are your designs pixels that only you and your colleagues see. We prototype and invite our customers or drivers to <em>use</em> it. We question them. We have honest discussions. We’re constantly reminded that we’re designing for everyone else, people that count on our product. Every. Day. A broken flow or an unintuitive UI can really screw someone’s day and interviews or usability studies are a constant reminder of who we’re designing for.</p><p>There’s a real skill in interviewing and probing customers with past experiences and memories to uncover insights. I’ve learnt many interview skills, but my favourite one is:</p><p><strong>What they say is usually not what they do.</strong></p><p>We believe conducting field research is a great way to get an even better understanding of our customers and drivers behaviours, influences and motivations.</p><p>Despite a small team, investing in research provided a solid foundation for my designs and as a product designer, I can’t live without it. After all, learn early and learn often.</p><p>Saff</p><p><em>Huge “big up” to the awesome design team at the time: </em><a href="https://twitter.com/robwinters"><em>Rob</em></a><em>, </em><a href="https://twitter.com/GiddyFingers"><em>Mara</em></a><em> &amp; </em><a href="https://twitter.com/Stace_Ann1"><em>Stacey</em></a><em>.</em></p><p><em>Have questions? Happy to have a </em><a href="http://twitter.com/saffadkhan"><em>chat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4958b4a23247" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hamburger Paradigm]]></title>
            <link>https://medium.com/@saffad/the-hamburger-paradigm-ebb695b5da86?source=rss-71831281ee97------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebb695b5da86</guid>
            <dc:creator><![CDATA[Saffad Khan]]></dc:creator>
            <pubDate>Wed, 03 Sep 2014 16:23:39 GMT</pubDate>
            <atom:updated>2014-12-20T21:11:55.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*7LNZhgIinoyCY6dvwWU8KA.jpeg" /><figcaption>Lost Tourist by John Siegel (flickr)</figcaption></figure><h4>What makes our apps easy to navigate and why</h4><p>You could have mistaken the title off an episode straight from The Big Bang Theory but as much as I’d love to write about Sheldon’s love for hamburgers and The Cheesecake Factory this post is about <strong>navigation in apps. </strong>What makes them easy to navigate and why I believe hamburger menus, side-navs, basements etc are terrible primary navigations. I shall refer to this pattern from now as the <em>navigation drawer</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PKQilMl8S3YbU5WvnoAlZA.png" /><figcaption>Facebook for iPhone. (Drawer vs Tab bar)</figcaption></figure><p>First seen at <a href="http://www.cultofmac.com/272311/apple-borrowed-ioss-hamburger-icon-xerox-parc/">Xerox Parc</a>, this list-menu interaction was popularized by Facebook and Path in what seemed like a great a way to navigate around an app. It saves space, looks greats and you could fit a bunch of stuff in there! Awesome. In the last few years many apps jumped on board and now the ‘three-lined-symbol’ sitting at the top has become a familiar mobile pattern to people.</p><p>But now those apps have taken a turn. Many high usage apps have already redesigned their navigation on iOS into a tab bar. These apps include Path, Foursquare, Vine and even Facebook (see above). This got me thinking. Why the change?</p><p>I used to think the drawer wasn&#39;t always the best solution for primary navigation. There are already compelling arguments against the drawer. Those include task efficiency (number of taps), lower discoverability, <a href="https://scotthurff.com/images/posts/fb-paper/iPhone5c-small.jpg">thumb zone</a>s and <a href="http://thenextweb.com/dd/2014/04/08/ux-designers-side-drawer-navigation-costing-half-user-engagement/">engagement metrics</a>:</p><blockquote>What’s out of sight is out of mind</blockquote><p>The best case against the navigation drawer I&#39;ve seen, is from a WWDC 14 talk by Mike Stern of Apple “<a href="https://developer.apple.com/videos/wwdc/2014/"><strong><em>Designing Intuitive User Experiences</em></strong></a><strong><em>”</em></strong><em>. </em>I agreed with Mike and it made me think. He talked about easy navigation being an important factor for an intuitive app and it boiled down to three simple questions:</p><p><strong>Where am I?</strong></p><p><strong>Where else can I go?</strong></p><p><strong>What will I find when I get there?</strong></p><p>Many of the interactions in our screens nowadays are metaphors of real world experiences — it’s what makes them <strong>intuitive</strong>. Suppose I place a plate in front of you of some food you don&#39;t like, you’re instinct would be to slide it away. In the real world, you are swiping away something you don&#39;t want like just like you are <em>swiping to delete </em>an email<em>. </em>Turning on a power socket switch is a lot like <em>tapping switches </em>on or off. These are the kinds of intuitive interactions we should be aiming for.</p><h3>So how do we make navigation intuitive?</h3><p>I found myself thinking a lot about those three questions framed by Mike and came to realisation that easy navigation in app is a lot like…</p><blockquote>…navigating in the real world.</blockquote><p>Turns out the real world does a great job of all three of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*9VDClKDpBBUXPfIGBjjANg.jpeg" /></figure><p>Imagine yourself in an unfamiliar town. You immediately look around to find out where you are. You spot places — perhaps a church, the train station or even some signs. Pretty quickly you’ve built a sense of understanding of where you are. Now you know you have a choice of places to go to and you know what to expect once you get there. You walk right up to the bus stop and expect to catch a bus. How’s that for intuitive navigation?</p><p>Tab bars on iOS also do a pretty good job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fk0MKSaNDQ3FkTJnkBPkMw.png" /><figcaption>Designing Intuitive UX by Mike Stern (16:50)</figcaption></figure><p>The active state of a tab bar tells you where you are. It also shows you where else you can go, presenting all of your choices and progressively disclosing the rest of your app’s content. The icons and labels also provide a good explanation of whats inside of each section of the app. Pretty intuitive.</p><p>Navigation drawers, however do a terrible job of the first two questions especially.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*s_VQi5y-Lfq4hYQSlzPcCg.png" /><figcaption>Designing Intuitive UX by Mike Stern (32:00)</figcaption></figure><p>As a form of primary navigation it sucks because you have no idea where you are in the app and what choices you have, because the actual menu is <strong>off the screen</strong>. This gets amplified when you dive into a view and that familiar hamburger icon gets replaced with the back button and now you&#39;re lost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0QtYwXCnXaTm1d9kTbAgQ.png" /></figure><p>Instead of having a chest of draws with labels on them you now have one mysterious draw with <em>all</em> of your stuff. If your primary navigation is a metaphor for a drawer (to expose content beneath), they are likely to be…</p><blockquote>… filled with junk.</blockquote><h3>Do we kill the hamburger?</h3><p>Don&#39;t go writing off navigation drawers just yet because I do believe it is an interaction that has some use - perhaps not so much for primary navigation but more so for <strong>secondary</strong> content. An example I like is Slack for iOS. They use the drawer to show <em>Open Channels </em>on one side and <em>Files</em> on the other. It works because it isn&#39;t your primary navigation, it saves much needed space for the messages, the icon never gets replaced with anything and you always know where you are with the title in the Nav Bar. Sweet. (Note how they went for hashtag icon instead of the hamburger)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVLRiITr1R6jPpd5JRyEHg.png" /></figure><p>Saying that, there are apps where I feel the navigation drawer may be a bad choice. I wanted to look at one I feel could benefit with a redesigned tab bar. So purely for experimental purposes I wanted to see if I could redesign the information architecture of one of my highly used apps — Pocket. I love using Pocket but one of my biggest gripes with their app is the lack of discoverability for <strong>primary content </strong>and the number of taps it requires to navigate around as I tend to go to <em>Archive </em>&amp; <em>Favorites </em>a lot. That takes at least twice as many taps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVCWIyL0KbKX6gu1ODvd8Q.png" /></figure><p>With a tab bar it is far more discoverable and quicker to switch between sections with just <strong>one tap. </strong><a href="http://www.nngroup.com/articles/progressive-disclosure/">Progressive disclosure</a> can be used for secondary content under <em>More. </em>The result I believe is a far easier to use app and increase engagement.</p><p>Stashing your <strong>primary</strong> navigation into a drawer with an hamburger icon is where it gets confusing. Using the pattern where it makes sense could be useful. Before thinking up your navigation system it may be useful asking yourself questions on what your apps <a href="http://blog.jaredsinclair.com/post/86111225660/basement-menus-and-breaking-the-rules-of-app-design">goals and needs</a> are.</p><h3>Is tab bar the only solution?</h3><p>Mobile interfaces are fairly new and we are only just seeing the potential of Natural User Interfaces. On mobile we are still exploring many ways of navigation through the use of <a href="http://alistapart.com/column/better-navigation-through-proprioception">transitions</a> and gestures.</p><p>Naturally, the current constraints of mobile is that everything sits in our screens of which we directly manipulate with our fingers. What’s really exciting is what we come up with in the future. What intuitive navigation systems will exist combined with the <a href="http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesign/">future of our interfaces</a> ?</p><p>Every app will have it’s own goals and needs. It’s up to you to take all of that into account and design an intuitive navigation. Don&#39;t feel like you are limited in solutions but just remember easy navigation is a lot like navigating in the real world:</p><p><strong>Where am I?</strong></p><p><strong>Where else can I go?</strong></p><p><strong>What will I find when I get there?</strong></p><p><em>Thanks for reading. If you haven&#39;t yet watched Mike Stern’s talk I highly recommend you check it out — “</em><a href="https://developer.apple.com/videos/wwdc/2014/"><em>Designing Intuitive User Experiences</em></a><em>”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebb695b5da86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing Without Thinking]]></title>
            <link>https://medium.com/@saffad/doing-without-thinking-2e357b3a7870?source=rss-71831281ee97------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e357b3a7870</guid>
            <dc:creator><![CDATA[Saffad Khan]]></dc:creator>
            <pubDate>Sun, 09 Mar 2014 16:51:21 GMT</pubDate>
            <atom:updated>2014-03-10T10:22:17.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*AvVohgorSYvhX7u52zHgtA.jpeg" /><figcaption>The familiar shopping  trolley</figcaption></figure><h4>Testing the expectation of users, with Pocket as a case study</h4><p>I’ve been a Pocket user for a while now (RIL anyone?). Many people have different uses for it, which is what makes it great. I’m the person who adds to Pocket “stuff I want to read later when I get time”. Recently I’ve been into tagging my stuff whilst exploring some IFTT recipes. For the first time I tagged an article on the Pocket app for iPhone. <strong>I found it difficult</strong>. I was intrigued at why it was difficult, and this is what I’m going to try to answer along with my solution too.</p><p>Couple of months back I read an interesting <a href="http://getpocket.com/blog/2013/10/tiny-impacts-the-case-of-the-accidental-archive/">blog post</a> by Max Weiner of Pocket on Android user expectations. Max explained that in an older version of the Android Pocket app, they decided to replace the <strong>Up</strong> button with an <strong>Archive</strong> button when reading your article. Through some user testing they soon discovered that users were tapping on Archive without thinking, <strong>expecting to go back</strong>. The actual outcome is that the article would be dismissed (and archived) displaying their reading list with the article gone:</p><blockquote>“wtf just happened”</blockquote><p>That was the response from users. This got me intrigued, so I asked myself just how important is meeting users expectation and following conventions?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*r8m4CHHXFZo78QBxlMEKvw.gif" /><figcaption>The impact of having the Archive button instead of the Up button forced Pocket to think otherwise.</figcaption></figure><p>After the finding, Pocket changed the interaction and saw an increase in continued usage. In mobile, it is especially essential to give your users a good first impression. Anything confusing or unintuitive is cognitive drain, and in the case above conventions should be respected especially when users are already familiar with them.</p><p>This brings me to my experience using Pocket on iPhone. Specifically, tagging an item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*1fz9BQ3osVe-b16IbZYzTQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pgo9ymTWSJ6l7OkXMkB55A.png" /><figcaption>Tagging flow broken down. Step 1 (left) &amp; Step 2 (right)</figcaption></figure><p>The above is the current flow for tagging item. After choosing to tag an article from my reading list I am presented with a modal view. I ran some short random user testing around the office asking colleagues to tag an item ‘design’. After figuring out how to select the ‘design’ tag, most people often stumbled on the second step. Subconsciously, they were reaching for the top right ‘New’ button. When they realised what it was, they made a quick turn to the left for ‘Save’. It got even more confusing when asking users to tag another item instead.</p><blockquote>“save or new…where’s cancel?!”</blockquote><p><a href="https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/Modal.html">iOS Interface Guidelines</a> states that <em>“Always provide an obvious and safe way to exit a modal task”</em>. When designing for mobile, remember that you are <strong>designing for interruption and partial attention</strong>. The ability to lock your phone for 30 seconds and coming back to it without ever feeling lost in the app is crucial. There are many mobile UX constraints and one of them is varied environments. People use their mobile phones everywhere and usually won’t have the time or the mental effort to figure out the interface you’ve given them. What they can do is use something they are already familiar with — something that is intuitive.</p><p>When using products people are expected to use their initial knowledge of any given function.</p><ul><li>Pushing a shopping trolley, I expect it to go forward.</li><li>In iOS modal views, I expect Cancel to be on the top left.</li></ul><p>There are conventions that should be learned and respected. Breaking out of the convention involves really understanding them first, and the impact when implementing a different solution. When going against conventions, we should be aware of potential confusions, have a deep understanding of its purpose — from that we can innovate.</p><p>With everything that I have mentioned above in mind, this is my proposed solution. I have tweaked the modal task of tagging an item in Pocket for iOS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*n5U0TRaeUQ1K3Q8uwdCnMA.gif" /><figcaption>Proposed solution</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PVt9vLt5y8NymogWFhc_KQ.png" /></figure><p>I’ve taken the primary goal of this screen and attempted to make it clearer whilst following the conventions of iOS. The introduction of checkmarks provides the obvious affordance that you can select or unselect multiple tags. Displaying tags as small labels provides anticipation and better expectation as the same label style is used in the List view.</p><p>The result, I believe, is a much clearer and easier to complete task. I’d love to hear what you think. If anyone is interested I’ve put together both the original and my solution for comparison, into a Flinto prototype <a href="https://www.flinto.com/p/b98c74b7">https://www.flinto.com/p/b98c74b7</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e357b3a7870" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>