Category Archive

Advice

How to make a bad UI – Dropdown Edition

 

I’ve seen all of these. Witnessed them with my own eyes. How can a fair and just universe allow such crimes?

Anyway… here’s how to make a bad UI for your fillable forms.

 

1) Be sure to use a dropdown wherever you can.

 

It is so much easier to just include a type-in text box than it is to try and imagine every. Possible. Response to your question. Exceptions are rare: countries, states, shipping speeds, and other static items are suitable for dropdown menus because their numbers are limited. Anywhere or anything else? A dropdown can be a nuisance, especially because you might still miss options if you’re trying to keep your menu short. There’s nothing more irritating than a question asking me to be specific when they don’t have my option!

Dropdowns should also be avoided if the user could want to select multiple items: dropdowns are for single choices. They aren’t meant to act like checklists. Picture trying to order a burger for online pickup, but the ‘extras’ selection menu is a dropdown. I can have extra onion or extra pickles, but not both without calling in the order. Why?!?

 

1.5) Mix unrelated items into the same dropdown menu.

 

Ryanair forces (or at least used to force) their users into adding insurance by putting the opt-out option in the same menu as the location choices. Users who didn’t want the insurance may have already given up on finding the opt-out option by the time they’re picking their insurance, only to discover it near the bottom of the menu. That doesn’t mean they now want the insurance. It just means they’re frustrated by Ryanair.  A yes/no question shouldn’t have the conditionals for ‘yes’ in the same list as a hard ‘no’.

Ryanair’s reputation is garbage because of decisions like these. Is the short-term money worth alienating customers?

 

2) Make the dropdown incredibly long, and don’t organize it alphabetically.

 

Once again, including a typed response or blank box ‘other’ option allows a business a lot more flexibility than listing out every. Possible. Response, but if you have to, arrange it in a way that makes sense. Some UI websites even recommend breaking down your menus into submenus, so Greek users looking for expedited service on your site can select the “Expedited” option from service levels, and then “Greece” from there.  Each menu is shorter and easier to navigate when broken down by relevancy. You don’t need to list Greece twice in the same drop-down for first-class and then expedited shipping.

If you want your users to suffer, don’t arrange your inputs in any logical manner! Numbers can be in any order you want! European countries should be mixed in with the Asian and African ones, and there better not be any alphabetizing going on! Don’t forget to put Sealand at the top!

 

3) No autofill.

 

We die like men, scrolling through that endlessly long dropdown with two or three options for every state or country, to get to where we want to be. Most good dropdowns allow the user to type the first couple of letters of what they want, so they can skip opening the menu entirely. On eBay, I

hit the keys “N V” and I get to NV without needing to even open the menu. However, that’s a good idea. And we’re not doing good ideas today. Bad dropdowns don’t accept typed input. If you’re really feeling evil, make sure the button presses interact with the page in a strange way, like highlighting questions or activating the ‘next page’ button. For some reason.

 

4) Don’t allow users to leave it on “select an option” or blank.

Listen, websites shouldn’t punish users for accidentally clicking on a drop-down only to realize it doesn’t apply to them. If the ‘leave blank’ option disappears after clicking, then it’s poorly designed – for those ‘leave blank’ slots, users should be able to un-click the box or leave it. For example: Users may be coerced into picking ‘sneezing’ if they really can’t leave this question blank.

 

This also applies to question trees. A user should always be able to go back and select ‘no’ for a question that comes with follow-up questions, without having to still answer the follow-ups. Accidentally selecting ‘yes’ to special instructions and then having to type N/A in the pizza delivery place’s special instructions box makes users feel like they’re being annoying!

Similarly, optional multi-choice questions should either be possible to uncheck or have a “none of the above” option. Don’t make users refresh the page to get their correct answer!

 

5) For necessary items, let users skim past.

 

On the other hand, some dropdowns shouldn’t default to an option that allows the computer to continue forward. If you’ve ever checked out from a small website before, you’ll know that sometimes they put the USA and Canada at the top in shipping – their most used options get to go first. However, the USA shouldn’t be in that blank select-a-place box automatically. Locations for shipping are one of the few things absolutely necessary to complete an order, and if the customer misses that, they’re going to have a bad time. After all, there’s a Paris in Texas and an Athens in Georgia! Don’t default to USA just because it’s the most used option, or skimming customers are going to be very angry when their package doesn’t arrive.

 

6) Don’t include Dialogue Boxes When Doing Negative Actions

 

Dialogue boxes prevent mis-clicks from destroying your user’s life, patience, and data. Even a single ‘are you sure’ prevents tons of data loss. Remember, around 30% of the data lost last year was due to human error, and that’s with verification – the number would be much higher without these checks in place.

If you want to do a bad job, go ahead and skip these altogether! No verification questions! No dialogue boxes! Clicking the little trashcan icon once makes the item disappear forever! Now your user is mad!

Alternatively, if you want to do a terrible job subtly, it’s always a bad idea to be vague. Be as vague as possible when designing your verification question. “Are you sure you want to X?” is too many words. Make that question as confounding as possible.

“Complete Action?” “Don’t Delete X?” “Delete?” “Keep X?” and so on. Only having the options of “Cancel” and “No” are also good for maximum confusion.

6.5) Include too many Dialogue Boxes

 

You could also use a dialogue box for every action to make a bad site.

Search for X.

Nice, I have results. Add to Cart? Are you sure you want to do that? Oh, you are? Okay. Oh, you want to add this to the cart too? Are you sure? Hmm, okay. How about leaving this page to go to the next one, are you sure you want to do that? No? See, I saved you a click! Oh, I’m sorry, you must have hit the wrong button, you really did want to go to the next page, heh. Do you really want to narrow down your search results? Are you sure? Are you sure, you’re sure? Are you-

 

7) Make the end user do too many things to access certain information.

 

If you want to waste everyone’s time, make the end user fill out the entire form to get to critical information, such as when appointments are held or what requirements must be met to enter the building. The end user doesn’t even know if they’re even interested in the service yet!

If the business needs to screen appointments, it can do that when the customer is actually going to make the appointment. If the business can only accept certain file types for printing, it needs to make that clear before the customer goes through all the work of selecting the style of banner they want.

If you want your end users to suffer, be completely opaque about whether or not your services will suit them. Heck, you could even go so far as to hide your business hours! “Hah, you’re looking for music lessons, and you want to know what kind of music instructors we have? Too bad, fill out this skill level form before we tell you that we don’t teach the flute here. Or adults, we’re kids-under-14 only.” Do that. If you want your website to cause frustration, do that.

Sources:

https://uxdesign.cc/the-ux-of-security-questions-4edbbb687e83

https://careerfoundry.com/en/blog/ux-design/10-classic-ux-design-fails/

https://uxplanet.org/5-essential-ux-rules-for-dialog-design-4de258c22116

 

 

Apple Wave

Elizabeth Advice December 30, 2020

If you’ve been online a while, you’ve probably heard of Apple Wave, an “update” that “allowed” phones to “charge” in the microwave. Don’t microwave your phone.

The Goal

An anonymous message board known for incredible coordination gets the idea to put together Apple Wave, a fake advertisement campaign. Apple Wave tells users that they can now microwave their phone to charge it. It wasn’t an immediate success; the successful version was several iterations deep as they worked out what an official Apple ads looked like together. The anonymous message board had finally gotten a graphic designer (or at least someone who knew how to assemble high-ish quality graphics) interested in the scheme, and away they went.

The Term “Life Hack”

Don’t microwave your phone. If the information doesn’t come from a respected source, don’t try it before researching. Remember that big explosion of people testing hacks on Youtube? That’s because for a while, life-hack folks were able to get away with just doing stuff or saying things that sound plausible but were usually useless – or dangerous in the worst cases. Nobody pictures molten caramel and a drill when they hear cotton candy, but hack channels slapped the two together. Sugar burns!

But nobody wanted to be wrong in the comments by calling it out – maybe the hack really did work. Many of them are tedious or annoying; nobody wanted to spend time on something that doesn’t work only so that they can say it doesn’t work with complete certainty. That caramel hack, for example, would mean getting a drill out, buying caramel candies if you don’t have them on hand, melting them in a pan (that you also have to wash), and either tending to your burns afterwards or trying to get a bad impression of sugar floss off the insides of a cardboard box, for what? Worse cotton candy? Cotton candy that is worse than the candy that went into making it?

The Youtuber trend of trying hacks might be annoying to some people, but at least someone is trying these things to verify that they don’t work.

Plausibility – “Nobody Made You Microwave Your Phone”

Plausible information is a perfect way to get people to do something they’d never normally do – common sense says you don’t put metal in a microwave, but the fake ad was so compelling people did it anyway. It appealed to authority as the information came from Apple, or at least, the ad had the Apple logo in it, which was as good as branding. A lot of tech seems totally opaque to people, and it’s difficult to blame them for assuming someone else knows their device better than they do. Apple has their Genius Bar for a reason, after all.

“Plausible”

It was plausible to a lot of people that a phone was microwaveable for charging. That’s the other essential part of a plausible troll/disinformation campaign! They completely removed any mention of a microwave’s normal functions to keep people from thinking too hard about what they were actually doing. Even the mechanism charging the phone was a ‘software update’ which could mean anything to a lot of ordinary people. When this troll post first popped up, the iPhone was still pretty new.

It only takes a few seconds in a microwave to seriously damage a phone. A microwave works roughly by shooting microwaves inside the box, where they reflect off the metal walls until they hit your food. This transfers the energy from the waves and causes the food molecules to heat up. When microwaves hit the phone, they either bounce off in a way they’re not supposed to (which causes sparks) or successfully hit the components, which aren’t meant to have that much energy. That causes electrical discharge which is bad for everything inside the phone. It can also cause battery rupture. If you remember that Samsung battery issue a few years back, you’ve seen how destructive lithium batteries are when the insides are exposed to air.

Red Flags

Some red flags you should look for when discovering information: Did it come straight from the suggested source (like the Apple website)? Or did you find it in a graphic somewhere else (like Facebook or Instagram)?

When you try to verify, is the information possible to find? Or does it seem like the graphic is the only source of the info?

Does it make sense with what you already know about that object?

Does it make sense that you’ve never seen or heard of the hack before, or haven’t thought of it yourself?

Are there special instructions in the comments to make the hack ‘work’ that were left out of the graphic?

Are the comments split into complete agreement and complete disagreement, where one party is insisting it works completely and the other is warning people NOT to try the hack under any circumstances?

If so, it might be a troll post.