<?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[Design Bits - Medium]]></title>
        <description><![CDATA[Thoughts and inspiration about design. - Medium]]></description>
        <link>https://medium.com/design-bits?source=rss----8f974cfd971a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8YjWtIWPhYRfdO92.jpeg</url>
            <title>Design Bits - Medium</title>
            <link>https://medium.com/design-bits?source=rss----8f974cfd971a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:14:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/design-bits" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Make Decisions.]]></title>
            <link>https://medium.com/design-bits/make-decisions-d71768a08b69?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/d71768a08b69</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Caryn Vainio]]></dc:creator>
            <pubDate>Thu, 17 Dec 2015 16:55:20 GMT</pubDate>
            <atom:updated>2015-12-18T00:39:35.549Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5J_ZrIPCSIOPONfy5HcFLQ.jpeg" /></figure><p>I recently saw <a href="https://twitter.com/zachklein/status/676473160464633856">this tweet</a> about the agreement that Avis Rent-a-Car had with their advertising agency back in the 1970s, when they had great success with their “We Try Harder” ad campaign. I loved everything in this agreement, but I especially loved it for this line:</p><blockquote>To this end, DDB will only submit for approval those ads which they as an agency recommend. They will not “see what Avis thinks of that one.”</blockquote><p>This really shows that Avis understood what they were paying their ad agency to do and, maybe more importantly, what <em>not</em> to do. After all, the ad agency knows advertising, and Avis knew all about renting cars. Theoretically, a designer — or a design agency — knows design work, and their client (or boss) does not. That’s why you hire a designer, to do the work you don’t know how to do.</p><p>This statement in Avis’ agreement highlights something I think is important in design work, something that I think designers forget: never do a bunch of variations on something and give them all to your client or boss to “see what they think of them.”</p><p>The novice designer does the above. The experienced designer makes design decisions based on their experience and knowledge of the project goals, executes a design that fits that to the best of their abilities, and then presents it to the boss or client for approval or disapproval. Then they get feedback on that and apply it as necessary.</p><p>(Note that this <em>does not</em> suggest that a designer should never do variations, only that those variations are part of the early ideation phase of a project. Early variations are not for public consumption — they’re for you and your design feedback team to use internally as you spiral in toward the design target.)</p><p>If you’re a designer, you’re getting paid to do design. That means making design decisions. And that means cutting out all the stuff that you as a designer, using the skills you’ve acquired as your speciality, know will not work. When you make a bunch of variations to present to someone else to decide on, you’re abdicating your role as a designer and asking your client or your boss to do the design work, not you. You’re saying, <em>I don’t know how to make decisions that I’m trained to know how to make, or I’m too afraid to make them.</em></p><p>As a designer, you need to have conviction in your ability to design. And that’s why this is the distinction between a novice designer and an experienced one. Design is not the act of putting pixels into a pretty arrangement on the screen; <em>design is a process of decision making </em>that culls bad ideas in favor of working ideas.</p><p>Yes, you’re likely at some point to put a design in front of a client or a boss and the client or your boss hates it. But that, too, is still productive. In that scenario, your client or boss is going to tell you why they think it doesn’t work, and it’s up to you to take your own collection of design decisions and evaluate them in the face of new knowledge from the client, and then figure out how to adjust your design navigation accordingly.</p><p>That’s not failure. That’s just design work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d71768a08b69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bits/make-decisions-d71768a08b69">Make Decisions.</a> was originally published in <a href="https://medium.com/design-bits">Design Bits</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Roles A Designer Should Take On]]></title>
            <link>https://medium.com/@philchairez/4-roles-a-designer-should-take-on-a37d651be861?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/a37d651be861</guid>
            <dc:creator><![CDATA[Phil Chairez]]></dc:creator>
            <pubDate>Fri, 31 Jan 2014 21:12:24 GMT</pubDate>
            <atom:updated>2014-02-13T19:47:23.781Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OKo51EHtumGOBNbaYfq-mw.jpeg" /></figure><h4>Some simple ideas on how to be more than a designer</h4><p>The following quote is from <a href="http://www.miltonglaser.com/files/Essays-designlegends-8250.pdf">Milton Glaser</a>, in a presentation to the AIGA NY chapter. I first read this on <a href="http://www.cameronmoll.com/">Cameron Moll’s blog</a>.</p><p>“While I was in the doctor’s office I noticed a document on his wall called ‘What A Surgeon Ought to Be’ written in the 14th century. I’ve changed a word or two but it seems like good advice for our profession.</p><blockquote><strong><em>Let the designer be bold in all sure things, and fearful in dangerous things; let him avoid all faulty treatments and practices. He ought to be gracious to the client, considerate to his associates, cautious in his prognostications. Let him be modest, dignified, gentle, pitiful, and merciful; not covetous nor an extortionist of money; but rather let his reward be according to his work, to the means of the client, to the quality of the issue, and to his own dignity.</em></strong><em> ”</em></blockquote><p>I wish I could have read this years ago. It’s a great foundation to have. When I first started as a graphic designer I didn’t know where my boundaries were. No one told me because I think no one knew, at least in South Texas. I thought it was do as your told, design it like this, get it done tomorrow.</p><p>Whether you’re a design student, web designer, or creative director, I think we should try to better define what a designer ought to be which in turn will change what people expect out of a designer.</p><p>I’m going to give you 4 roles that have helped me grow as a creative, as a business owner and definitely as a designer.</p><blockquote><strong><em>Be a Problem Solver<br>Be an Owner<br>Be a Communicator<br>Be an Adventurer</em></strong></blockquote><h3><strong>1. BE A PROBLEM SOLVER (or Problem Finder)</strong></h3><p>If there was a zombie apocalypse tomorrow and all technology was suddenly destroyed, no internet, no phones, no computers, designers could still design. There would be people who could solve problems creatively. Solving problems is the essence of what we do. It’s not that perfect masking job you did in photoshop or that gorgeous font that took you an hour to find.</p><p>It’s the process you went through to identify what problem you’re solving, and how you solved it that makes you a designer.</p><p>During my first jobs, I waited. I waited for someone to tell me what to design. I waited for someone to decide the colors I was using were good. I waited for someone to tell me the problem I’m trying to solve. My design work was about pleasing the client and my boss.</p><p>These days I establish the problem. And you don’t need to be in a position of management to do so. If you’re a new designer working for someone, you are there to solve problems. Defining those problems is where your skills should be focused first and foremost. You’re there to think of issues to overcome that your client or boss haven’t or can’t think of. Think about things differently and you’ll bring value to the project.</p><h3><strong>2. BE AN OWNER</strong></h3><p>You don’t have to be the owner of your company to be the owner of what you do. When we say owner, we’re talking about someone who doesn’t wait to be told to do something. We’re talking about someone who goes beyond what’s asked of them to produce a better product. We’re talking about someone who can initiate, who can motivate and someone who questions things in an intelligent way.</p><p><a href="https://twitter.com/jasonfried">Jason Fried’s</a> gives the advice “Make something for yourself”. Making something for yourself gives you a reason to pour your passion into it because it’s yours. I challenge you to try to apply that passion to work that comes from a client or a manager. Sometimes it takes the right client to understand what you’re trying to do but good clients understand good ideas. If you give them an option they haven’t thought about, they’ll listen and consider it.</p><h3><strong>3. BE A COMMUNICATOR (or Storyteller)</strong></h3><p>Knowing how to communicate a message in the clearest way possible is one of the best tools a designer can have. We take images and words and we communicate an idea to someone. “Who is your audience” is something we were taught early on, but I think as designers we can take it farther than that. What is your audience’s motivations? What is your client’s motivations? What are the goals you are trying to achieve with your design? What is the single most important thing you want your audience to get from your design?</p><p>Every time we begin a new project at <a href="http://www.barrelrollcreative.com/">Barrel Roll Creative</a>, whether that’s a <a href="http://www.brlrl.com/work/">website, a mobile app or even marketing material </a>for a client, those are the questions we ask. Those answers fuel your work and give you the ammunition to make your design decisions.</p><p>So try to write more. Try to read more. The more you study language and people, the better you’ll be at getting your message across clearly.</p><h3><strong>4. BE AN ADVENTURER</strong></h3><p>For me, one of the best parts of this field is how quickly it changes. Technology is always improving and what was possible a year ago is significantly different than what’s possible today. So with every new project I try to explore new territory. Don’t get stuck doing the same things over and over. Try a new process, improve on an old one, or experiment with something you’ve always wanted to try. As designers we want to be adaptable and ever-improving.</p><p>At my company, after every project we asses how that project went. What went wrong? What went right? How can we adjust our process in the next project so both the client and our team have a better experience?</p><p>Don’t be afraid to really swing for the fences in your work. Granted, some projects will have strict requirements that could limit that. But pick your battles and don’t forget to enjoy what you do. Don’t be afraid to try something and fail. You’ll get it right the next time around. And the fulfillment from the success will be all the richer.</p><p>When I first started out I didn’t know what I could be as a graphic designer. No one told me. But it’s these roles I’ve discovered that have contributed to better clients, higher quality work, a better working environment, less stress and a general sense of happiness. Stepping into these roles now removes a lot of problems I ran into early on.</p><p>At <a href="http://www.brlrl.com/about">Barrel Roll Creative</a> I think we’ve established ourselves as problem solvers, owners of our work, communicators and adventurers. For me that’s exciting every day.</p><p>So going back to Milton Glaser’s quote What a Designer Ought to Be he says “let his reward be according to his work”. We receive our joy and fulfillment from our work. So get out there and do it in a way you love.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a37d651be861" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 things designers wish their clients from hell knew]]></title>
            <link>https://medium.com/@KeiraBui/5-things-designers-wish-their-clients-from-hell-knew-dac7a4126a53?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/dac7a4126a53</guid>
            <dc:creator><![CDATA[Keira Bui]]></dc:creator>
            <pubDate>Tue, 09 Jul 2013 22:19:16 GMT</pubDate>
            <atom:updated>2013-07-09T22:27:01.800Z</atom:updated>
            <content:encoded><![CDATA[<p>The long, painful battle between graphic designers and clients never ends. There are lots of things designers want to say to their clients, but it seems they never say that directly to their clients (of course, who would?). After asking some of my fellow designers what they wish their clients from hell knew, I compile a list that would be useful if you are considering hiring a designer:</p><ol><li><strong>Freelance ain’t free</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*rimtP7zEEP3YOj12.jpeg" /><figcaption>Designed by Ena Bacanovic</figcaption></figure><p>Just because you hire freelance designers doesn’t mean they will work for free. That’s why you should never hold a design contest unless you want to waste your time and money. Crowdsourcing competitions only attract hobbyist designers, amateurs and designers who are not serious about their work. Most of the designs you get from the contests will be based on the designer’s personal tastes, not those of your targeted market. In contrast, a professional graphic designer will do research about your company, your competitors and the industry to make sure the design match your business goals and stand out from the rest.</p><p>Once again, don’t expect professional designers to invest time, energy and resources in working for free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/0*noJ34mLOOCia_d02.png" /><figcaption>Designed by Pfahlert Creative Labs</figcaption></figure><p>Or even better:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/0*e5Xi66lZ6Zz1YGK4.jpeg" /><figcaption>Designed by Ams Design Studio</figcaption></figure><p>2. <strong>You get what you pay for</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*mVS0TpJP_uN-RCVF.jpeg" /><figcaption>Designed by Colin Harman</figcaption></figure><p>Don’t expect to get a great and cheap graphic design done in half an hour. Enough said.</p><p>3. <strong>Designers are not mere tools (or Photoshop monkeys)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*A_S-yLWbezV-HoFG.png" /><figcaption>Designed by Daniel Levanon</figcaption></figure><p>After working as a freelance graphic designer for 5 years, I come to understand that some clients don’t know how to get the most out of their designers. For instance, when giving feedback, just voice your impression, like how that blue color makes you feel, and that you want a more feminine color. Tell your designer that you want a color that will attract female customers, but don’t say you want pink. Unless you have more years of training in graphic design than your designer, don’t tell him or her exactly what to do. Your designer who is packed with years of education, training and experience will know how to solve the problem based on your impression. Trust your designer more and you’ll be amazed with what he or she can come up with.</p><p>Fact is, designers don’t only know how to use graphics software, they know all the principles and elements of good design. If you don’t take advantage of that, you are throwing your money away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*nNO9XrQoCDgG7ZGM.jpeg" /><figcaption>Designed by Jennifer Farley</figcaption></figure><p>4. <strong>Less is more. Respect white space.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*kh3nDeNTKDzIZWm0.jpeg" /><figcaption>Designed byMark + Paddy</figcaption></figure><p>Uneducated clients tend to cram as much information as possible in a design. They are afraid that the lack of information would drive away customers, but in fact, what they really need is a design that stands out. Once the customer is interested, he or she would go to the company’s website to get more information. The era of passive consumer is long gone.</p><p>So why do you have to respect white space? There are numerous benefits, but in general, white space helps attract attention and creates elegant, sophisticated designs. Here are some very good articles in case you want to learn more about white space:</p><p><a href="http://webdesignledger.com/tips/whitespace-the-underutilized-design-element">White space in web design</a><br><a href="http://psychology.wichita.edu/surl/usabilitynews/62/whitespace.htm">How white space improves readability</a><br><a href="http://designmodo.com/white-space-graphic-design/">Why white space is good in graphic design</a></p><p>5. <strong>Hire those who believe what you believe</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*ZaZ5f0s_E49mJoPR.jpeg" /><figcaption>Designed by InkSurge</figcaption></figure><p>This is unrelated to graphic design but it’s a very interesting point indeed. I hope you can find a designer who looks at the same direction as you.</p><h3>Conclusions</h3><p>So that’s my guide on how NOT to be a client from hell. I know it’s not complete yet and would like to know what you all think. I’m always on <a href="https://www.facebook.com/KeiraBui.Design">Facebook</a> / <a href="https://twitter.com/KeiraBui">Twitter</a>, or you can send me an email via my <a href="http://keirabui.com/5-things-designers-wish-their-clients-from-hell-knew/">website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dac7a4126a53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best thing to do when clients don’t listen]]></title>
            <link>https://medium.com/@KeiraBui/best-thing-to-do-when-clients-dont-listen-e84cbefacec?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/e84cbefacec</guid>
            <dc:creator><![CDATA[Keira Bui]]></dc:creator>
            <pubDate>Tue, 09 Jul 2013 05:59:17 GMT</pubDate>
            <atom:updated>2013-07-14T13:41:11.503Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sometimes clients don’t really know what they want, which ends up wasting lots of time and money. But it’s not good either when they know exactly what they want and start to make all the design decisions for you – the designer. So what should you do now?</h4><p>Just do as told.</p><p>No I’m not kidding. Just do exactly what they tell you to. But besides that, also pursue your own solution.</p><p>When it’s time for presentation, show the clients both. This will help them compare two solutions and (hopefully) they would know that yours is far better. Clients will see that you are not a designer with a big ego because you actually listen to them and execute their idea.</p><h4>When negotiating, always listen before you speak</h4><p>This is the number one negotiating tactic. If you just keep talking about how great your concept is the whole time and close your mind, you will eventually lose the negotiation. Remember it is you who need the money, not them. There are numerous designers out there and you can’t afford losing clients because of your ego, not because of your skills or your experience.</p><h4>What you should do</h4><p>First, listen to the other party. Don’t voice your opinion about how bad their design aesthetic is. Absorb the information. When you let them finish what they have to say, they would feel more relaxed and be open to your ideas. At this moment, they would ask you back, “What do you think?”.</p><p>This is where you should start talking. And what you say now will have far more weight compared to your talking at the beginning of the conversation.</p><h4>Remember</h4><p>When your clients don’t listen, listen to them. When they insist on their idea, don’t refuse it, but still develop your own solution. Show them both. If you don’t show them what they want, they will have no idea what it would look like. They will not know that their idea is bad (if it is), since you don’t give them the option to compare.</p><p>Besides, there are times that I find the client’s idea is actually better than mine. This keeps me very open-minded compared to when I first started freelancing. Now I am more convinced that clients are not always wrong, and designers are not always right either.</p><h4>Learn how to negotiate</h4><p>Art schools don’t teach us how to deal with clients, and that’s why we struggle to learn it on our own. Out of all the books about negotiating that I’ve read, I find <a href="http://www.amazon.com/Getting-Yes-Negotiating-Agreement-Without/dp/0143118757">Getting to yes</a> very helpful. It is like a negotiating bible to me, and even though the content is not very concise, it offers great eye-opening advice that would help you a lot with your freelance career.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/0*ek1Q4FaV8WaQzUBN.jpeg" /><figcaption>One of the best books on negotiation.</figcaption></figure><p>In business, clients are the boss</p><p>If you don’t know how to please them, you will be fired.</p><p>Now it’s your turn. Tell me how you tamed those difficult clients. I’m always here on <a href="https://twitter.com/KeiraBui">Twitter</a> / <a href="https://www.facebook.com/KeiraBui.Design">Facebook</a>, or you can send me an email via my <a href="http://keirabui.com/negotiate-when-your-clients-dont-listen/">website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e84cbefacec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Android’s 3 UX Design Principles and 2 Jars of Marbles]]></title>
            <link>https://medium.com/@KeiraBui/google-androids-3-ux-design-principles-and-2-jars-of-marbles-4a08d6afe0a1?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/4a08d6afe0a1</guid>
            <dc:creator><![CDATA[Keira Bui]]></dc:creator>
            <pubDate>Tue, 09 Jul 2013 06:48:39 GMT</pubDate>
            <atom:updated>2013-07-12T03:19:34.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Mn4c7FaWdOsQk3hP.jpeg" /></figure><h4>In their presentation at Google I/O, the designers share their design principles and how they make important UX decisions based on 2 jars of marbles.</h4><p>Their UX design key points are divided into 3 categories: <strong>Enchant</strong>, <strong>Simplify </strong>and <strong>Amaze.</strong></p><h3>ENCHANT ME</h3><p><strong>Delight me in surprising ways: </strong>A simple animation or a well-timed sound effect can bring joy to the users. Pay attention to these subtle effects because they create a sense of effortlessness for users.</p><p><strong>Real objects are more fun than button and menus: </strong>Users feel more emotionally satisfied when they can directly touch and manipulate objects in your app (This must sound good to skeuomorphic designers).</p><p><strong>Let me make it mine: </strong>Everyone wants to add personal touches because it makes them feel in control. Provide defaults, but don’t forget fun, optional customizations.</p><p><strong>Get to know me: </strong>Learn users’ preferences and avoid asking them for the same feedback over and over. Previous choices should be within easy reach.</p><h3>SIMPLIFY MY LIFE</h3><p><strong>Keep it brief: </strong>Short phrases and simple words are strongly preferred over technical jargons. People tend to skip long sentences.</p><p><strong>Pictures are faster than words: </strong>Pictures catch people’s attention and get ideas across more easily than words.</p><p><strong>Decide for me but let me have the final say: </strong>Guess what the users want and do it rather than asking first. Allowing them to undo your decision is better than asking too many questions.</p><p><strong>Only show what I need when I need it: </strong>To avoid overwhelming people with too much information at once, hide non-essential options and break tasks into small chunks. Teach people as they go.</p><p><strong>I should always know where I am: </strong>Places in your app should look different. There should be transitions among screens to show a strong hierarchy. Don’t make the users feel lost.</p><p><strong>Never lose my stuff: </strong>People should be able to access to their creations, settings, personal touches,… whenever they want. Or they’ll never update your app.</p><p><strong>If it looks the same, it should act the same:</strong> Help people distinguish different functions by making them look distinct rather than subtle. Don’t use modes, which are places that look alike but act differently on the same input.</p><p><strong>Only interrupt me if it’s important: </strong>Unless it’s crucial and time-sensitive, don’t bother your users with lots of interruptions.</p><h3>MAKE MY LIFE AMAZING</h3><p><strong>Give me tricks that work everywhere: </strong>Use visual patterns from other Android apps, such as making the swipe gesture as a navigational shortcut. It makes it easier to use your app, and when people figure things out themselves, they feel good!</p><p><strong>It’s not my fault: </strong>Don’t put the blame on your users and make them feel bad. Be nice when the users forget to insert SIM card or when they reach your 404 page.</p><p><strong>Sprinkle encouragement: </strong>Break complicated tasks into small chunks and let the users know that their actions took effect, even if it’s just a subtle sound.</p><p><strong>Do the heavy lifting for me:</strong> Users will feel very grateful if you give them shortcuts that can do more than they expect.</p><p><strong>Make important things fast: </strong>Key elements in your app should be easy to find and easy to use. They should be more prioritized than others.</p><p>According to psychologist <a href="http://www.unc.edu/peplab/barb_fredrickson_page.html">Barbara L. Fredrickson</a>, it takes three positive emotions to outweigh every negative one. Based on this, the Google design team set up two jars of marble to examine the costs and benefits. For every positive emotion that the design makes, they put a marble in the good emotion jar. However, if the design causes a negative emotion, they’ll put 3 marbles in the bad emotion jar. Their goal is to get an empty negative jar and a full positive jar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MQ84FvO2Ow-56OKW.png" /><figcaption>Two jars of emotion help Google make UX decisions.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wJ_O1bTUaRadT0Tx.png" /><figcaption>It takes three positive emotions to outweigh every negative one.</figcaption></figure><p>The team also has a writer that helps them write “positive” messages which don’t place the blame on users. Android’s tone is human-like, friendly and approachable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mfY7apQJRs6w3QBW.png" /><figcaption>Short and simple words are preferred over technical jargons.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-XKGvjI0qiPzXOry.png" /><figcaption>One friend is more important than 76 strangers.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*921pcPgymqNqVst1.png" /><figcaption>Very human-like, conversational tone.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_avqhLkHw_MOQ_E6.png" /><figcaption>Too much “hello” and “thank you” can be tiring.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DzYybmd4MdZO1P1i.png" /><figcaption>Allow users to make final decisions.</figcaption></figure><p>Their Ice Cream Sandwich’s UX design principles are also shown <a href="http://commondatastorage.googleapis.com/androiddevelopers/design/android-ics-2012-ux-awards.pdf">i</a>n this <a href="http://commondatastorage.googleapis.com/androiddevelopers/design/android-ics-2012-ux-awards.pdf">PDF</a> or on their <a href="http://developer.android.com/design/get-started/principles.html">website</a>.</p><p>Overall, I think Google is very smart to share its design process. This is a great way to advertise their products, while making sure it doesn’t look like advertising. Their process exemplifies that even a small decision can cause big changes in user experience, because one negative emotion equals three positive emotion. Of course we shouldn’t stick to these rigid numbers, but still, asking yourself, “What emotion will this design create? Is it positive or negative? How and why?” will help you a lot in UX design.</p><p>Let me know what you think. I’m always here on <a href="https://twitter.com/KeiraBui">Twitter</a> / <a href="https://www.facebook.com/KeiraBui.Design">Facebook</a>, or you can send me an email via my <a href="http://keirabui.com/google-androids-3-ux-design-principles-and-2-jars-of-marbles/">website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a08d6afe0a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make Every Pixel Count]]></title>
            <link>https://medium.com/@DesignPete/make-every-pixel-count-1d43938263e9?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/1d43938263e9</guid>
            <dc:creator><![CDATA[Pete]]></dc:creator>
            <pubDate>Tue, 02 Jul 2013 09:21:33 GMT</pubDate>
            <atom:updated>2015-01-15T17:28:01.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*5SLD39VpvLsxzdRL.jpeg" /></figure><p>Your eyes were designed to explore a rich and physical world. But you’re looking at a screen right now. In fact, you probably spend a lot of your day looking at a screen.</p><p>Bottom line: what’s on this screen matters.</p><p>Ever stare out at a beautiful natural landscape and feel charged with energy just looking at it? As an engineer, I’ve marveled at the incredible amount of information the real world contains. And somehow, unlike your messy room, all this visual information is in harmony. It’s food for not just the eyes, but the soul.</p><h3>Virtual and Proud</h3><p>Flat design hails from the print world, and it’s now making significant in-roads into interactive apps. This trendy methodology kicks real world metaphors and rich 3D visuals to the curb. The argument is that these artifacts of the real world tie us to the past, and hold us back from what could be.</p><p>Flat designs are virtual and proud of it, with a heavy emphasis on text, bold colors, and solid backgrounds. Are they our future? Is the goal to totally abstract ourselves from physical reality?</p><h3>Keep It Real</h3><p>We are physical creatures, and we are made to interact with physical things. The more time we spend on screens, the more disconnected we can feel from the physical world around us.</p><p>The best solution is to unplug. Put down the phone, step away from the computer, and be a part of the real world. But that’s not the direction our world is spinning right now.</p><p>We’re spending more time with our screens, not less. Our touchscreen devices are becoming the interface for… everything. The question becomes, how do we stay grounded in physical reality – while we’re interacting with a virtual one?</p><h3><strong>Retina to the Rescue</strong></h3><p>Our devices should not separate us from our world. They should connect us more deeply with it.</p><p>We have an amazing technology that can help us with this. It’s called a Retina display, with pixels so tightly packed and colors so brilliant, that it offers the closest approximation of reality we’ve ever had.</p><p>So why waste it?</p><p>In photo and video apps, we can maximize the benefit of these pixels from the real world, and fill as much of the screen as we can with them.</p><p>In apps without visuals, we have an opportunity to add them. I’m not talking about cartoon leather or green felt or dark linen. They were problematic choices that pushed the pendulum to swing too far in the <a href="https://medium.com/wwdc-round-up/ec5a42b4e5e6">other direction</a>. And they were obviously fake.</p><p>To satisfy our craving for reality, we need visuals that look real.</p><h3>Flat vs. Skeumorphic?</h3><p>Flat design and skeuomorphism are not goals. They are tools. Whether they are appropriate depends on the situation.</p><p>The real question is: did you make the best use of your pixels? Did you bring the user closer to their world and connect with them emotionally, or did you put a monochrome wall in their way?</p><p>Flat designs can work brilliantly when used with images from the real world. Skeuomorphism, the use of satisfying physical metaphors, can provide visual relief from an otherwise mundane experience. It can create joy where there would otherwise be boredom.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d43938263e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Two Corners of Unsolicited Redesigns]]></title>
            <link>https://medium.com/@jdjohnson/the-two-corners-of-unsolicited-redesigns-8e8a40407c12?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e8a40407c12</guid>
            <dc:creator><![CDATA[Jarad Johnson]]></dc:creator>
            <pubDate>Mon, 01 Jul 2013 02:29:41 GMT</pubDate>
            <atom:updated>2016-06-09T17:35:24.028Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JxQ1lX9XfCHvytCe.png" /><figcaption>iOS 7 Redesign BY Leo Drapeau: http://dribbble.com/shots/1109343-iOS-7-Redesign?list=highlights</figcaption></figure><h4>The split between designers who post unsolicited redesigns and those who wish they wouldn’t.</h4><p>Like most overly obsessed Apple fans, I watched the 2013 WWDC keynote live, sharing a screen with my Twitter stream. The opening was a predictable recap to get the audience up to speed and announce small updates. Then we were told about Apple’s latest innovation, a cylinder-shaped MacPro. Twitter lit up with approval.</p><p>As exciting as the MacPro update was (it had been a while), we were still on the edge of our seats. The design community, and especially those who I follow on Twitter, were interested in one thing—the iOS 7 design as reimagined by newly named director of Human Interface design and famed product designer, Jony Ive. Finally we were there. Following a short introduction and overview of iPhone stats and highlights, Tim Cook passed to a prepared video with Ive to introduce us to iOS 7 and the annoyingly coined, new<em> flat </em>design.</p><blockquote>“With what we’ve been able to achieve together, we see iOS 7 as defining an important new direction, and in many ways, a new begining.”— Jony Ive</blockquote><p>Twitter lit up with approval. And disapproval. And anger. And confusion. And then dissaproval of the anger and confusion. Perhaps the best tweet came from Wilson Miner, “’Polarizing’ indeed.” Outside of those who hang in the middle, we tend to see the same thing happen every time a controversial design is released.</p><p>We see designers run to their corners.</p><p>On one side, wearing the blue trunks, we have designers who believe the subpar work they’ve seen should be redesigned by the community, to show how easily improvements could be made. In the opposing corner, wearing the almost-unnoticeably-lighter-but-they-swear-the-color-is-a-different-blue trunks, we have the (mostly more established) designers who believe these unsolicited redesigns are both unwarranted and unbeneficial.</p><h3>It All Starts Innocently</h3><p>Some of the folks who watched iOS 7&#39;s unveiling in horrified astonishment opened their copies of Photoshop (definitely not pirated) and launched the Teehan+Lax iPhone 5 template PSD (slow bastards hadn’t released the iOS 7 template for another day). Within hours, redesigned versions of icons and complete screens appear in the wild and began to spread on Twitter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CXaKa5tbvxfpRACK.png" /><figcaption>iOS 7 Control Center Redesign by <a href="http://dribbble.com/samnissinen">Sam Joonas Nissinen</a></figcaption></figure><p>Most redesigns started on Dribbble—the number one resource for unsolicited redesigns. Featured above is a beautiful version of control center by <a href="http://dribbble.com/shots/1111484-iOS-7-Control-Center-Redesign?list=users">Sam Nissinen</a>, which is one of <a href="http://dribbble.com/shots/1109343-iOS-7-Redesign?list=highlights">many</a>, <a href="http://dribbble.com/shots/1109500-iOS-7">many</a> <a href="http://dribbble.com/shots/1110146-iOS-7-Photos">redesigns</a> <a href="http://dribbble.com/shots/1109303-iOS-7-Safari-Icon-and-grid">posted</a> to <a href="http://dribbble.com/shots/1110960-iOS-7-Icons">Dribbble</a>. <a href="http://dribbble.com/shots/1112094-iOS-7">Seriously</a>, <a href="http://dribbble.com/shots/1111540-Safari?list=highlights">there</a> are an <a href="http://dribbble.com/shots/1111319-I-know-I-know">unbelievable</a> <a href="http://dribbble.com/shots/1116744-iOS7-Redesign">amount</a> of <a href="http://dribbble.com/shots/1117094-Safari-icon">these</a>. They pretty well hijacked Dribble for a few days, which has become common practice when major design overhauls are announced to the public.</p><p>Most of the mockups are stunning. Do they take into account the thousands of factors Apple designers had to consider while making the icons, control center, and lock screens for iOS 7? Absolutely not, but they’re still pretty, and that grabs the attention of designers around the world. As of writing, the number one redesign post on Dribbble is by Leo Drapeau, with 2,472 likes and 1,104 shares on Twitter, Facebook, and Pinterest. That’s quite impressive for a mockup completed within 24 hours after Apple’s announcement. However, likes and shares can be achieved by many top designers without actually solving a single issue outside of window-dressing, which opens the door to the other corner’s rebuttal—what exactly are these designers trying to solve?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PbgGLeM3-zsZVPTO.jpeg" /><figcaption>iOS 7 Redesignby <a href="http://dribbble.com/leodrapeau">Leo Drapeau</a></figcaption></figure><h3>The Response</h3><p>Mike Monteiro, designer and guy who complains on twitter a lot, spearheads the fight against unsolicited redesigns, tweeting:</p><blockquote>“To designers posting mockups of what you think iOS 7 OUGHT TO look like, I assume you’re good with clients doing this to your work as well?”— <a href="https://twitter.com/mike_ftw">@Mike_FTW</a></blockquote><blockquote>“Let me stop you right there, son. That iOS 7 redesign you’re working on is NOT better. And you have other things to do.”— <a href="https://twitter.com/mike_ftw">@Mike_FTW</a></blockquote><p>Mike wasn’t the only person to call out the flood of redesigns hitting Dribbble, but he’s a popular guy, so he garners a lot of attention. Although Mike has made his opinion of unsolicited redesigns public on more than one occasion, I reached out to him to get an answer to the question of why.</p><h4>Why Do You Take Issue with Unsolicited Redesigns?</h4><blockquote>1. You have no idea what the brief was.</blockquote><blockquote>2. A designer’s hardest job is selling their work to the people who need to approve it.</blockquote><blockquote>3. You never throw another designer under the bus.</blockquote><blockquote>Anybody can do something that’s visually appealing, post it to Dribbble, and get a favorable response. But that’s not what design is. Design is the solution to a problem within a set of constraints. And unsolicited work ignores the biggest constraint of all: your ability to get your work through the approval process. That’s not design, it’s jerking off in a vaccuum.</blockquote><p>While Mike talked about <a href="http://www.muleradio.net/mistakes/96/">why he loved iOS 7</a>, some established designers, such as Erik Spiekermann, were outspoken on what they thought sucked about it. Erik’s initial critique was centered around the use of Helvetica Light, which he tweeted the day of the iOS 7 announcement.</p><blockquote>“Wish someone at Apple knew that one should track light typefaces to make them more legible.”</blockquote><blockquote>“1. Helvetica sucks for OS<br>2. Helvetica Light sucks more<br>3. Helvetica Light &amp; tight übersucks.”</blockquote><p>Given Erik’s disagreement with iOS 7&#39;s typography, as well as a few other design decisions, I wondered if his opinion of unsolicited redesigns would differ from Mike’s.</p><h4>What is your take on unsolicited redesigns?</h4><blockquote>I firmly belive that most projects cannot be designed without the client’s involvement. There may be cases, however, where common sense or collective experience may give us enough information to come up with a better solution. That could apply to IRS forms, public signage — all those things that almost any designer with half a brain could improve. But commercial projects should not be honoured by solving them for free. We cannot possibly know all the constraints and usually end up making something pretty but pretty irrelevant. Designing something without knowing everything about it perpetuates the existing prejudice about designers just making things pretty superficially.</blockquote><h4>Do you think there are benefits to young designers posting redesigns on Dribbble?</h4><blockquote>They get practise and exposure but will ultimately just throw away their talent. If you’re a graphic window-dresser, this may be fine. If you consider yourself a problem-solver, see above.</blockquote><p>These answers lead to a new question. A question to those posting redesigns to Dribbble. Are these posts meant as practice and to gain exposure, or do they believe these designs are actually solving a problem Apple was unable to solve?</p><p>I contacted many designers who contributed to the iOS 7 redesigns on Dribbble, ranging from icon adjustments to entire screen designs. <a href="http://dribbble.com/samnissinen">Sam Nissinen</a>, who redesigned the control center screen along with the Safari icon, provided answers that both explain what he hoped to accomplish and why he thinks unsolicited redesigns are a positive response for the community.</p><h4><strong>What were you hoping to accomplish with your redesign?</strong></h4><blockquote>To be perfectly honest, I saw the control center as a unfinished design, and wanted to put my design skills to the test. Subconsciously I might have also been thinking about the possibility of Apple actually seeing the design. I have a feeling that they will be tweaking parts of iOS and if they do, it would be interesting to see how my version fares with their possibly upgraded one.</blockquote><h4><strong>Do you think your version could be implemented by Apple?</strong></h4><blockquote>I did take a few liberties with the design, but with some tweaks, I don’t see any reason why it couldn’t be implemented into iOS 7.</blockquote><h4><strong>What would you say to people like Mike Monteiro who believe it is wrong to redesign other people’s work unsolicited?</strong></h4><blockquote>I dont think using clients as a comparison is very fair. Apple has formed a huge part of their brand with good design, and if they fail to deliver in the eyes of the design community, the community will start taking action in the form of redesigns. This is comparable to politics where a party would take a stance to something proposed by the parliament, in this case the party being the community of designers and apple the “parliament of design”. These redesigns are simply a result of Apple not delivering something that the lot of designers would consider excellent. Nevertheless, I believe redesigns are like playing cover music or creating remixes of songs, it’s a great way for a designer to skill up and also feeds alternate views on design decisions. In my opinion there are only benefits to that.</blockquote><p>Outside of believing these designs could be implemented with just some tweaks, Sam seems to understand the purpose of his redesigns. In Sam’s opinion, designers are providing feedback to a company that, if the past is any indication, will be a force in driving design trends and direction for years to come. If the designers creating these unsolicited redesigns truly understand their lack of information, client direction, pitches, revisions, and general process, what is the harm of throwing up a redesign that looks better than what Apple has shown?</p><p>This is where I believe the two arguments begin to become more clear. It’s not merely the redesign that Mike, Erik, and other experienced designers disapprove of. And it’s not that the younger designers don’t understand they are lacking information. It’s that the more experienced designers know where this leads.</p><p>My guess is that many of the designers behind unsolicited redesigns have not been in a room with a client that hated a certain shade of blue. Or an art director that, after 20 minutes of arguing your point, demanded the padding in that icon follow the established grid. Or being put on a team where usability and customer feedback outweigh what every designer in the group agrees <em>looks</em> best. These situations exist and they require skills outside of Photoshop and Illustrator. Design is problem solving, design is communication, and design is selling your work. When we, as designers, confuse the public by briefly saying design is simply window-dressing when we’re unsatisfied, we’re providing a disservice to ourselves. A proper response would be to explain why <a href="http://mrgan.tumblr.com/post/53308781143/wrong">Apple’s icon design is wrong</a> by putting yourself in the shoes of the designer, rather than taking a few minutes to adjust visuals without much additional thought.</p><p>For many designers there is a turning point when design changes from making things pretty to making things work. It is at this time in a designer’s career that unsolicited redesigns start to make a lot less sense.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e8a40407c12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three Excuses You Give (When You Know Your Art Sucks)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@lastres0rt/three-excuses-you-give-when-you-know-your-art-sucks-ae145b3477dc?source=rss----8f974cfd971a---4"><img src="https://cdn-images-1.medium.com/max/2062/1*Rw0UJz4T97aiM4OTSgcx4A.jpeg" width="2062"></a></p><p class="medium-feed-link"><a href="https://medium.com/@lastres0rt/three-excuses-you-give-when-you-know-your-art-sucks-ae145b3477dc?source=rss----8f974cfd971a---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@lastres0rt/three-excuses-you-give-when-you-know-your-art-sucks-ae145b3477dc?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae145b3477dc</guid>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[Raye Keslensky]]></dc:creator>
            <pubDate>Mon, 04 Jan 2016 22:31:07 GMT</pubDate>
            <atom:updated>2016-06-10T23:58:28.276Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Drag & Drop: Think Twice]]></title>
            <link>https://dfeldman.medium.com/drag-drop-think-twice-49e7bf3e6b31?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/49e7bf3e6b31</guid>
            <dc:creator><![CDATA[Dave Feldman]]></dc:creator>
            <pubDate>Tue, 18 Jun 2013 16:57:38 GMT</pubDate>
            <atom:updated>2013-12-20T20:42:50.009Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s not a UX panacea.</h4><p>Nothing embodies the graphical user interface like drag &amp; drop. You use a mouse pointer (or, more recently, a finger) to select an object and move it to a new location. Often the object, its original location, and the destination are abstract concepts, mapped onto physical ones via familiar metaphors. It’s relatively easy to learn and, once learned, easy to extend to unfamiliar situations. (Some would say <em>intuitive </em>but that’s not really accurate; some training is required.) It adapts the strange world of the digital to the peculiarities of the human brain.</p><p>Drag &amp; drop also epitomizes all the disadvantages of a GUI:</p><ul><li>It’s inefficient. It takes time and focus to pick an object up and put it down somewhere else.</li><li>It’s imprecise. (And, its efficiency and precision are inversely proportional.) Watch a skilled designer work in Photoshop and you’ll be surprised by how often he moves things with the keyboard: arrow keys to nudge by one pixel, Shift-arrow keys to nudge by ten. There’s just no good way to achieve that level of accuracy with the mouse.</li><li>It’s physically awkward. Moving a mouse with the button down strains the hand, and it’s a real physical challenge if you run out of room and need to lift the mouse. Dragging long distances over a touch screen while maintaining contact is equally difficult, and exacerbated by the fact that your figure is obscuring both the object being dragged and the drop target. If you accidentally release the button, or hit a greasy spot on your touchscreen and lose contact, you end up in a situation that’s confusing at best and often requires effort to undo. As smartphones get bigger and bigger, this problem worsens: what if you need to reposition the phone mid-drag just to reach the target?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*MFq5LVTgLd947BoF.jpeg" /><figcaption>Uninstalling an Android app involves a lengthy, awkward, error-prone drag operation.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*X7NZ2MMT0afpzT5r.jpeg" /><figcaption>iOS is much better: press and hold to get an X button and uninstall in place.</figcaption></figure><ul><li>Its order of operations doesn’t always match the user’s thought process. Suppose I’m looking at a file on my desktop and want to move it to Documents. In the real world I’d pick the file up, walk over to Documents, open it, and drop the file in. In the virtual world I have the equivalent of one hand: once I’ve picked the file up, I don’t have a second hand with which to open Documents. So I have to set the file back down, pull up Documents, position it next to the file’s current location, and <em>then </em>perform the drag. Apple has alleviated this problem somewhat with things like Exposé but it’s still awkward, and one begins to understand the allure of cut-and-paste.</li><li>It doesn’t play well with scrolling. Reordering list items over long distances is an exercise in frustration: either the canvas scrolls slowly enough for the drag operation takes forever, or it scrolls fast enough to be efficient and you overshoot your target, sometimes repeatedly.</li></ul><p>So should you implement drag &amp; drop? If not, what’s the alternative? As always, a little <a href="http://boxesandarrows.com/a-truly-ambitious-product-idea-making-stuff-for-people/">Downward Arrow</a> is a good place to start. What’s your user trying to accomplish? How well-suited is drag &amp; drop to that task? What interactions might be better-suited to it?</p><h4><strong>Case Study: Stky Task Drawer</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*z9HQWm562QKgz0JD.png" /><figcaption>Stky’s daily sticky: most tasks are hidden in the drawer.</figcaption></figure><p>My own task-management app, <a href="http://bit.ly/stky">Stky</a>, which you should <a href="http://bit.ly/stky">totally go download right now</a>, provides a perfect example. Stky is designed to keep disorganized people organized. Tasks go in a big drawer that’s usually closed. Each morning you fill your daily sticky note from there, and it’s automatically wiped clean the following morning – everything’s back in the drawer.</p><p>So your drawer gets pretty full. It’s sorted by date, with newer items first, and one of my most requested features was the ability to reorder it. I decided it was a worthwhile addition.</p><p>iOS has a standard way to do this: press and hold a list item and it “pops out”, after which you can drag to reorder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*VFL4jZcATuFCjtr_.png" /><figcaption>iOS’s standard drag-to-reorder approach from the built-in Reminders app.</figcaption></figure><p>But as I did the <a href="http://boxesandarrows.com/a-truly-ambitious-product-idea-making-stuff-for-people/">Downward Arrow</a> thing I started to wonder. Why was this such a popular request? What made it worthwhile? Well, the task drawer works much like a Facebook newsfeed: new items push older items down. Often that’s fine: weeks-old items you marked as “Soon” are really just “Whenever” items whose loss you haven’t come to terms with. But sometimes, an item in need of attention gets crowded out by newer stuff, and you need to move it up. More specifically, you need to <em>bump </em>it up to the top of the drawer where it won’t get lost.</p><p>So it’s unlikely a user would need to move a task by one or two slots (remember, these aren’t hyper-organized people I’m targeting) but likely she’d want to move it all the way to the top. And the longer the distance, the more scrolling involved, the more frustrating drag &amp; drop becomes. My solution? A simple bump-to-top item in the swipe menu. It’s far less flexible than drag &amp; drop, but for the core case I identified, far more efficient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*JQiAhz1yD5FLJ5da.png" /><figcaption>Tap the arrow to bump a task to the top of the drawer.</figcaption></figure><p>There’s no reason I couldn’t have implemented drag &amp; drop too: the gesture in question isn’t being used for anything else. But it turns out to be more difficult than I’d anticipated: Apple expects users to go into an Edit mode before they start dragging, and I didn’t want to complicate the app that way. Implementing drag &amp; drop <em>without </em>Edit mode proved surprisingly complex, and given my hypothesis that more flexible reordering isn’t necessary, the enhancement wasn’t worth the development time. But I suspect many situations are similar: if the effort required to implement drag &amp; drop isn’t significant, including it alongside another interaction won’t hurt.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49e7bf3e6b31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI: It’s Not the Tool.]]></title>
            <link>https://medium.com/@hellchick/ui-its-not-the-tool-4d761c3adad4?source=rss----8f974cfd971a---4</link>
            <guid isPermaLink="false">https://medium.com/p/4d761c3adad4</guid>
            <dc:creator><![CDATA[Caryn Vainio]]></dc:creator>
            <pubDate>Tue, 18 Jun 2013 05:26:59 GMT</pubDate>
            <atom:updated>2015-11-06T17:13:45.314Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*CmpbCg2qOJizvhz3.jpeg" /><figcaption>if only such a button existed.</figcaption></figure><h4>When good mock-up tools go bad.</h4><p>There are many times in professional life when those who are not UI/UX designers are called upon to do the job of one. It may be that your team lacks the resources to hire someone specialized in that field, or you’re an indie app or game maker who just needs to find a way to get the job done with limited resources (i.e, <em>you</em>).</p><p>When I encounter someone who is or has been in this kind of position, they inevitably ask me, “so what mock-up tool do you use?” If they’re cocky, there’ll be a little bit of an edge in their voice. A note of, <em>let’s see what kind of UI designer you really are. </em>It’s like asking someone at the gym, “so what do you bench press?” It’s a test.</p><p>Sometimes they’ll follow this up with, “I use Balsamiq.” Or, “I’m an Omnigraffle person.” There are some developers who’ll say this proudly, as if to show that, despite the lack of the title on their resume, they know the lingo, and they don’t need some fancypants UI designer to do what they think they already know how to do, <em>thank you very much.</em></p><p>And they’re sometimes surprised when my answer is, “I actually don’t use one.” As the discussion gets deeper, it usually becomes apparent to me that, for most people outside of the UI/UX field, the Holy Mock-up Tool has become the entirety of their relationship with UI design.</p><blockquote>But tools like Balsamiq and others don’t make UI; people make UI. UI is not a page of boxes and buttons and text fields laid out Tetris-style to make it all fit; UI is made of decisions and choices. It’s made of research and experience and a hell of a lot of work that got thrown away.</blockquote><p>We live in a world where the tools to make anything are at everyone’s fingertips. User interfaces have become an area of design in which many people feel confident enough to roll up their sleeves and sink their hands, especially when tools that purport to make it<em> just so easy</em> are a download away.</p><p>But tools like Balsamiq and others don’t make UI; people make UI. UI is not a page of boxes and buttons and text fields laid out Tetris-style to make it all fit; UI is made of decisions and choices. It’s made of research and experience and a hell of a lot of work that got thrown away. UI is not what you add to the page; UI is, very often, what is left when you sculpt away the marble that reveals the right design choices.</p><blockquote>It’s easy to overestimate its power and conflate a mock-up tool with the experience and knowledge required to make a good, usable user interface.</blockquote><p>Mock-up tools lack this foundation of experience and understanding, so they can only take you so far. They can be a rope that helps to pull you out of the quicksand you might find yourself suddenly standing in when a project manager says, “we don’t have a UI designer, so…I guess <em>you’re</em> doing it.” But along with the sense of security they offer in providing ready-to-use widgets comes the danger of being too constrained by the limitations of a tool — even a meager attempt at <a href="https://medium.com/design-bits/5689ce1e1e9e">sketching something</a> cool and different with just a pen and paper can yield something you might not have thought of while just placing boxes. It’s easy to overestimate its power and conflate a mock-up tool with the experience and knowledge required to make a good, usable user interface.</p><p>Make your time, your skill set, and your product more valuable, and spend time beefing up your UI and UX design principles instead of mock-up tool tips and tricks:</p><ul><li>Spend some time with <a href="http://www.amazon.com/Universal-Principles-Design-Revised-Updated/dp/1592535879/ref=sr_1_1?ie=UTF8&amp;qid=1371532903&amp;sr=8-1&amp;keywords=universal+principles+of+design">basic books on design</a>.</li><li>Instead of writing your ideas down, <a href="https://medium.com/design-bits/5689ce1e1e9e">sketch them</a>. Do it even if you think you can’t draw.</li><li>Read up on the latest UI and UX design articles. (I happen to keep an <a href="https://www.evernote.com/pub/hellchick/uianduxarticles">Evernote shared notebook of articles</a> on this subject, and I add to it almost daily.)</li><li>Study why a game’s UI works if it’s noted for its UI. Don’t just study the look; look deeper into the usability and flow.</li></ul><p>Break out of the mock-up tool cage and see where these skills can take you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d761c3adad4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>