large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

<p>Published on <a href="https://blog.prototypr.io/common-ux-mistakes-made-by-business-developers-e837d0b31379?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Jason Teunissen </p>
<h4>You know who you are…</h4>
<h4>Introduction</h4>
<p>In my job as UX Consultant for <a href="http://www.appronto.nl">a Mendix partner</a>, I often come across self organized teams creating awesome internal applications. My job involves improving the UX within their applications.</p>
<p>The best days are when I am completely blindsided by the ingenuity of the creative ways some problems are solved, forcing me to explain why some logical solutions are a <em>bad</em> idea.</p>
<blockquote><p>The solutions given by me are not a “single truth”, there are always exceptions, don’t quote me on anything written here, but use it as inspiration to start the conversation.</p></blockquote>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VF2iPv49_j42ky2jhs55cw.png"></p>
<h3>Everything in a single screen.</h3>
<p>This is the most commonly implemented UX bad practice.</p>
<p>You start your little app with a tight interface, add a couple of features and before you know it, you have a screen full of buttons.</p>
<p>Don’t feel bad, we’ve all been there.</p>
<blockquote><p><strong>Arguments:</strong><br />“Less clicks”</p></blockquote>
<blockquote><p>“I can see everything, creates overview”</p></blockquote>
<blockquote><p>“Users hate scrolling”</p></blockquote>
<p>When ever I see this interface solution it reminds me of a swiss army knife with all the tools unfolded, and the only one that is used is the bottle opener.</p>
<h4>Overwhelming</h4>
<p>Having all the options spread out seems like it creates overview, but the problem is that your brain can only understand 9 options at best, and lets be honest the user probably doesn’t use 95% of the buttons that often.</p>
<h4>Proximity</h4>
<p>Another problem is that buttons should be close to the data that they influence. Having more buttons means losing visual proximity.</p>
<h4>Users dont hate scrolling</h4>
<p>The “users hate scrolling argument” is often a side effect of not having the right context at the right time and solving it by craming as much information in a single screen to help create context.</p>
<p><em>“but in our analytics we see that only 10% of the users scroll to the bottom of our landing page”</em> seems like a safe bet to conclude that 90% of your audience hates scrolling.<br />The problem is not the scrolling, its the amount of information. Having more information higher on the page doesnt mean that users will absorb that information but will burn out quicker and make them leave.</p>
<p><a href="https://lawsofux.com/millers-law">Millers law</a> by Laws of UX</p>
<p><a href="https://lawsofux.com/law-of-proximity">Law of proximity</a> by Laws of UX</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LJ-C14KwD9aIneIQcl3YyQ.png"></p>
<h3>Dropdown buttons</h3>
<p>So you’ve cleaned up your screen and put all the buttons in dropdowns.</p>
<blockquote><p><strong>Arguments:</strong><br />“More Focus”</p></blockquote>
<blockquote><p>“Less clutter, easier to find what I need”</p></blockquote>
<h4>Balance is key</h4>
<p>Think about your interface as a physical space, if you hide a page in a set of drawers, you need to open every drawer until you find what you are looking for. This is the same for digital UI.</p>
<p>If your drawers are logical and are in the right place this works well, but having garden supplies in a drawer in your garden shed sounds smart, so should your bbq supplies go in there too? Or in the kitchen? Or both?</p>
<p>A good balance goes a long way. How often you use your bbq determines if it should go in the shed or kitchen.</p>
<p>If you only have 5 buttons, they might not need to go in a dropdown, but 6 buttons, that’s a different story.</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLbi3ZbNivkB2NPOwFDWaA.png"></p>
<h3>Where am I?</h3>
<p>You have a consistent design system and brand style, all pages feel the same. Soon you feel like you are walking through a forest of pages, not knowing if you have seen this page before, or if this is a different page with similar states.</p>
<blockquote><p><strong>Arguments:</strong><br /><em>“Consistent visual style”</em></p></blockquote>
<blockquote><p><em>“Design Systems driven design”</em></p></blockquote>
<blockquote><p><em>“Efficient use of screen real-estate”</em></p></blockquote>
<p>It’s friday afternoon, you have A.D.D and are bouncing between social media, colleagues, some private messages and trying to do your work. The last thing on your mind is what link you just clicked and where you are in the flow or process.<br />Create every screen for this user.</p>
<ul>
<li>Give pages clear headers or page names</li>
<li>Implement breadcrumbs if you are more than 1 level deep</li>
<li>If the flow has multiple steps, show those steps.</li>
</ul>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Sb-EmMJahUEWjeylFcAyA.png"></p>
<h3>Long lines and tiny text</h3>
<p>Another example of wanting to get the most out of your screen.</p>
<blockquote><p><strong>Arguments:</strong><br />“Users hate scrolling”</p></blockquote>
<blockquote><p>“Efficiant use of screen real estate”</p></blockquote>
<p>The web typography rule of thumb is to have no more that 9 words per line. When you are finished reading a line your eyes need to be able to find the next line, if this is too long it is hard for your eyes to do this.</p>
<p>“<em>But look at all the screen realestate we are wasting</em>”<br />You are reading this on medium, have you ever noticed how much screen realestate they <em>waste</em>?<br />Guess what, what you call <em>waste </em>is actually an investment, if you can afford to invest that much whitespace, it means that the text must be super important, if not you should get rid of it anyway.</p>
<p><a href="http://blog.weare1910.com/post/78113100010/a-typographic-approach-to-email">A Typographic Approach to Email</a> by 1910</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMtGw7l6KyEv-xhcl9DNJw.png"></p>
<h3>Popup in popup</h3>
<p>To save space, you have a button with a notification.<br />In the notification there is a button that leads to another popup.</p>
<blockquote><p><strong>Arguments:</strong><br />“More context awareness”</p></blockquote>
<h4>What happens when I…</h4>
<p>The problem with this is that the user loses his mental model of where he is in the process. If he finishes the second popup, will he go to the original popup or back to the original screen?</p>
<p>Either the first popup should be a screen, or the second popup should be an inline error message.</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W7h7nPkOpNywFkNvNpqEUQ.png"></p>
<h3>Card in card</h3>
<p>Cards are trending at the moment, so what could be better than a single card? how about a card in another card… mind blown.</p>
<blockquote><p><strong>Arguments:</strong><br />“Cards are nested to create visual hierearchy”</p></blockquote>
<p>UXers often talk about visual hierarchy. The way in which elements are organized on a screen portraying their importance to the user.<br /> Along the way physical symbolism such as cards were introduced.</p>
<p><strong>In a traditional card deck, cards are all equal of size</strong>.<br />Cards are placed on, under or next to other cards to communicate certain states or relationships.</p>
<p>When you nest a card inside another card, the users mental model of what you can do with cards starts to breakdown. The user subconsciously starts to question relationships of other objects in the interface, and all logic is thrown out the window.</p>
<p>The solution is easy though!<br />Dont nest cards, but place them close to each other, next to each other, or placed within an ontline (like laying cards down on a casino table).</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RF6tlvfX_tkqUqHNjqz8kA.png"></p>
<h3>Form fields, what do i do with them.</h3>
<p>Should I have a long list of form inputs? Maybe break it up in to multiple steps? Or have 3 columns of form inputs so it all fits in a single screen?</p>
<blockquote><p>“Users hate scrolling”</p></blockquote>
<p>The main problem isnt the amount of pages or the amount of forms, it is how many forms are visible on the screen at a single time. Like buttons, this should be reduced to the minimal amount possible that still gives context and ease of use.</p>
<h4>Always use a single column</h4>
<p>Best practise is to always put intput fields in a single colomn.<br />The users eyes have an easy time to flow down and check off each section.</p>
<h4>Are you telling a story</h4>
<p>Sometimes your input fields are about the journey the user is about to embark on (onboarding), or maybe they have important consequences (tax slips). This is the best time to break up your fields into multiple pages.<br />This gives you some visual space to create some breathing room and explain to the user what they are doing and why its amazing or important.</p>
<h4>Dropdowns</h4>
<p>If there are only 1–5 items to choose from please don’t put them in a dropdown. I know it might look elegant and all, but its just not worth the users effort. Placing radio buttons is a friendlier approach.</p>
<p><a href="https://uxdesign.cc/design-better-forms-96fadca0f49c?epik=0KSYeE_IWH4Bw#.8jscxsce1">Design better forms</a> by UX Collective</p>
<p><a href="https://ux.stackexchange.com/questions/36956/single-page-or-multi-page-forms">Single page or multi-page forms?</a> by Stackoverflow</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O90hfUOPd9Nl5DnSVIYfLw.png"></p>
<h3>What does this button do?</h3>
<p>Certain elements on a page help you orient what page you’re on, other elements should be as consistant and as clear as possible.</p>
<blockquote><p>“but apple/google does it like that”</p></blockquote>
<p>The most common example of this, are the accept and cancel buttons and which one do you put left or right. The rule of thumb is that when you are moving forward in the flow, that button is green, on the right and has copy that explains what it does such as “accept”, “proceed” or “order”.</p>
<p>This gets confusing with “destructive tasks” such as when you would like to cancel your subscription “cancel” and “cancel subscription”?</p>
<p><a href="https://uxdesign.cc/the-microcopyist-cancellation-confirmation-conflagration-8a6047a4cf9">Writing microcopy for destructive actions</a> by UX Collective</p>
<h3>Recap, Quickrules</h3>
<ul>
<li>No more than 9 buttons</li>
<li>Only use drop downs as a last resort</li>
<li>Give every page a header</li>
<li>When a page is more than 1 deep, give it breadcrumb</li>
<li>When in multiple steps, show the steps</li>
<li>No more than 9 words per line.</li>
<li>Never use popup in a popup</li>
<li>Never nest a card in a card</li>
<li>Keep form fields in a single column</li>
<li>Have descriptive names for buttons</li>
</ul>
<p><a href="https://dribbble.com/jasonteunissen">Jason Teunissen</a></p>
<p><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=e837d0b31379" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://blog.prototypr.io/common-ux-mistakes-made-by-business-developers-e837d0b31379">Common UX Mistakes Made by Business Developers</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Common UX Mistakes Made by Business Developers

Common UX Mistakes Made by Business Developers

You know who you are…

Introduction

Top Stories