UI is hard. It got replaced by "UX", but nobody agrees what that really is. So it boils down to whatever impracticality designers dream up. When UI was easy, there were real research, data backing up claims of improvements and laid down rules to enforce some consistency. This became "unfashionable" and was removed.
It was like during the VCR wars of the 80s when consumers wanted the most features but yet the fewest buttons. Then they complained how you had to basically play rachmaninoff on their sleek minimal interface to set the clock.
We need to be like other industries; "that's too bad". Seatbelts are inconvenient? "that's too bad". You don't want to stay home during a pandemic because the weather's nice? "that's too bad" ... you want a bunch of incompatible UX goals that leads to trash? "That's too bad".
Sometimes the opinion of an uninformed public shouldn't matter. We don't go to a doctor and pass around ballots to the other people in the waiting room to democratically decide on a diagnosis. Knowing what to not listen to is important.
Fred Rogers, 1984: "I have always felt that with the advent of all of this new technology that allows people to tape the 'Neighborhood' off-the-air ... they then become much more active in the programming of their family’s television life. Very frankly, I am opposed to people being programmed by others. My whole approach in broadcasting has always been ‘You are an important person just the way you are. You can make healthy decisions’ ... I just feel that anything that allows a person to be more active in the control of his or her life, in a healthy way, is important."
see https://en.wikipedia.org/wiki/Sony_Corp._of_America_v._Unive....
There's definitely non-crazy ways of doing this ... but it requires what at first blush, would appear to be a complicated interface.
Honestly I don’t know why VCRs are so hard to program but all of the buttons can’t help. I might be getting old but the Roku remote seems about right as far as complexity in the device goes and I can see how a nice interface with relative timekeeping could do what you need without a clock per se. Inertial guidance for timekeeping? A self winding DVR?
Two things off the top of my head that I can think of: 1) knowing that a blinking number is indicating some kind of selection and more generally 2) seeing the UI as a glimpse into a larger abstract space that can be navigated. Or in other words, having used computers for many years, what my parents sawzl as just a blinking word, I would see as a menu where up/down/left/right had meaning.
There's also some more abstract thinking involved there - for me it's very spatial so I think of it as being able to keep track of your place in this 'abstract map'. You had to learn some non-obvious things like "if the down button stops working, it probably means I'm at the 'bottom' of my available choices" or "if I start seeing the same choices again, it means I have 'wrapped around' and in a logical sense I'm back to where I've been before".
I actually remember thinking something like this as a child when we got a VCR. I think I remember that realization that "this is a menu I can explore". The exploratory skills you pick up when you have to figure out how to use something technical generalize really well to other technical things.
TL;DR: I think VCRs were hard to program because the limited UI of buttons and a tiny screen meant that you actually needed a fairly built-up mental model of the process to keep track of what you were doing.
The biggest “what were they thinking” part for me is why they cram a whole GUI with config options and menus into a clock when almost every use case for a VCR is already connected to a perfectly workable display which is much better suited to a GUI in the form of the TV. Later VCRs had onscreen rather than on-device GUIs but by then institutional momentum was too far along to redesign the remote when they moved the GUI out of the device and onscreen. Truly a missed opportunity.
I don’t know anyone involved in any VCR product. If I did I’d be asking them a lot of questions. But I have a hard time thinking they meant to make it so hard. They probably were clapping each other on the back and congratulating each other. They were inventing future ways of using content and for that they deserve praise. They just sucked at understanding how hard it is for non experts to put themselves in the mind of experts, someone whose inner mental world has jarringly different contours and whose mental model of reality may have little to no correspondence whatsoever with their own.
Ha, reading that link now one feels a delicious sense of irony. Imagine how Sony would react today seeing that it has become one of the biggest purveyors of video/movie content. ;-)
Many people would keep the manuals near the TV, so they could remind themselves how to use the rarely used features.
The Panasonic VCR we had included a barcode reader in the remote. The printed TV guide has barcodes for each program. This interface was very easy to use -- scan, and press "transmit".
Edit to add a link to an advert: https://www.youtube.com/watch?v=tSGUbE1v5RA -- the sheet of timecodes was necessary if you didn't have a TV guide with them printed, as shown here: http://www.champagnecomedy.com/panasonic-barcodes-saving-you...
That's the outrageous point. You shouldn't need manuals for operation of ordinary domestic appliances! If you do then you automatically know its design is substandard!
(The only reason you should need a manual is for some info or maintenance function that's not normally associated with its user-operated functions.)
*The hard part of programming the Beta(and early VHS) for me was getting the family to leave the tuner on the channel I/we wanted to record.
So now my wristwatch is sitting on the desk.
It's too bad time sync over power lines didn't catch on widely (or broadcast over the radio). It would still be saving everyone from changing their digital clocks during DST.
If they'd included a backup battery to retain the clock, I suspect it'd been less of a thing.
Given that nobody did it, it would appear that even though legally people like Mr. Rogers were making the case for time-shift programming, the industry must have assumed it was a minor use case.
Autoclock setting was done for VCRs. It just happened much later than the case in question.
You mean the same industry that was trying to make time-shifting (and VCRs in general) illegal?
https://en.wikipedia.org/wiki/Extended_Data_Services (NTSC) looks like a 2008 standard and most PBS stations provide "autoclock" time data
https://en.wikipedia.org/wiki/Radio_Data_System (FM radio) I figured this had an implementation considering text has been around for years. Amazingly, I don't think I've ever seen a car stereo use it to set the time!
https://en.wikipedia.org/wiki/Broadband_over_power_lines I know this has been around but has had a lot of hurdles. I figured the current time might be a simpler thing.
The only reliably time-setting tech I've seen integrated is GPS--I'm not 100% sure how time zones work with it, but it does know your location.
On the contrary, the clock needs to be super obvious precisely because it's a pain to set. Otherwise you wouldn't notice until your recordings were messed up.
They're common in Europe, on a midrange bedside clock for example, and typical office/school clocks.
I remember we were foiled by one at school, when someone set the clock 15 minutes forward when the teacher wasn't looking. The hands could only move forward, so a few minutes later they started spinning 11½ hours further forward to set the correct time.
[0] https://en.wikipedia.org/wiki/Video_recorder_scheduling_code
In the 1990s I encountered a hotel TV with that feature. It had a built-in clock with hands (not on screen), which was also the alarm clock for the room. No one had set it up, and I spent about ten minutes with the remote getting it to find a station with time info and set the clock. Then the "alarm set" function on the remote would work and I could set my wake-up time.
I hate that ovens and microwaves have clocks on them. I don't need two devices in my kitchen to tell time. It's ridiculous since they usually next to each other, and most of the time have different displays. Just because there is an LCD/whatever, doesn't mean it always has to display something!
At least on the latest power outage, my microwave stopped showing the time. The oven still flashed, so I set that time and only have one clock in my kitchen now.
Even my vehicle has two clocks in it, one on the instrument cluster and one on the infotainment system. So stupid!!!
What's even more crazy, increasingly often I've started to encounter ovens that don't work until you set the clock. I.e. if the clock was reset and is blinking, the heater won't turn on. Took me a while to figure it out the first time I saw it.
The UX propellerheads come back with statistics from user telemetry that always agree with them.
UX is the problem — designing “experiences” geared around an 80/20 approach is substituted for the harder task of building tools that work.
Correct, that's the 2000+ year old axiom of ignoring the lowest common denominator and seeking the best advice available.
That said, if you're designing software for use by users who are 'lowest common denominator' then, a priori, you have to make it to their measure. If they cannot understand what you've done then you've wasted your time.
(I just now cleaned it up, although there are some icons you can't get rid of.)
It's not at all anymore about presenting consistent mental models, it's solely about the ease or difficulty with which particular isolated tasks can be performed.
It's also not automatically the goal to make all tasks as easy as possible. Instead, discoverability and "friction" are often deliberately tuned to optimize some higher-level goals, such as retention or conversion rates.
This is why we have dialogs where the highlighted default choice is neither the safe one nor the one expected by the user, but instead the one the company would like the user to take. (E.g. "select all" buttons in GDPR prompts or "go back" buttons if I want to cancel a subscription.
You can see that quite often in browsers as well, often even with good intentions: Chrome, for a time, still used to allow installing unsigned extensions but made the process deliberately obscure and in both Chrome and Firefox , options are often deliberately placed into easy or hard to discover locations. (E.g. a toggle on the browser chrome, vs the "settings" screen, vs "about:config", vs group policies)
IOW following metrics optimising for local maxima instead of looking at the big picture in a non-zero sum game. Each task is made easier by itself but in doing so creates a model in conflict with everything else, making everyone miserable. Nash would be sad.
I will readily admit in collective number of clicks and screentime, 37 year old men with advanced degrees in computer science are a super small minority.
But who is the majority then? Who spends the most time on say Reddit and YouTube? Children! Yes, people who we know are dramatically cognitively different than adults.
Why does YouTube keep recommending videos I've watched? That's what a child wants! Why does reddits redesign look like Nickelodeon?
There isn't one user and one interface that's right for everyone when we're talking about 5 year olds, 50 year olds, and 95 year olds.
We can make them adaptable to the screen, we should also do work to make them adaptable, at fundamental interaction levels, to the person using the screen.
And not in a clever way, but in a dumb one.
For instance, here's how you could ask YouTube: "We have a few interfaces. Please tell us what you like to watch:
* Cartoons and video games
* Lectures and tutorials
* Other "
And that's it. No more "learning", that's all you need to set the interface and algorithms.
Let's take Wikipedia, it could be broken up into children, public, and scholar. Some articles I'm sure are correct but are way too wonky and academic for me to understand and that's ok. There's nothing to fix, I'm sure it's a great tool for professionals. However, there should be a general public version.
This proposal quickly falls apart because your categories are ill-defined based on your preconceptions. I watch a ton of lectures about video games on Youtube (e.g. speed run breakdowns or game lore theories). Do I choose the "Cartoons and video games" bucket or the "Lectures and tutorials" bucket?
"We've found adults and teens like different parts of youtube and use it differently. We want to make it the best for you. You can switch at any time, but tell us what best describes you:
* I'm an adult
* I'm not an adult.
"
youtube has this "for kids" app which came out after I first started pointing this difference in earnest around 2013, (https://play.google.com/store/apps/details?id=com.google.and...) but it's not right and they clearly still cater their main interface to the habits of children who watch the same video hundreds of times - the insane repetition is a part of learning nuance and subtly in the context of content they don't have to actually pay attention to. It's all about learning the meta, super important. They know what happens, it's the silence in between they're excited about - that's the nature of play.
This app instead silos the kids into a playskool interface, great for people under 7 or so, but like our playground reform, we've made it completely unappealing for the 8-22 or so demographic (when I was a kid and there were ziplines into a bank of tires, you bet there were 20 year olds lining up to have a good time on those, we all have a need for play; freedom to err wrapped in relative safety).
Instead, it's data-driven UX for adults and data-driven UX for children - it's about separating the data, not a PTA-acceptable UX for overprotective parents.
The easiest thing to do is just allow them on youtube no filter.
The middle ground is the play app. Weird stuff sometimes get through but usually it's more someone dressed as a pretend princess. The good thing it's never really a murder scene or something equally as horrible (which could popup on youtube.com).
What would you do as a parent?
I would avoid youtube unless you setup the video until 7 or 11. After that it depends on the child.
It kinda has this for specific subjects:
https://en.wikipedia.org/wiki/Introduction_to_quantum_mechan...
https://en.wikipedia.org/wiki/Category:Introductory_articles
"Simple English" does a pretty good job. Obviously it's a mix of children/public but for science/mathematical topics where I'm looking just to verify my basic understanding of something, swapping over to Simple English usually gives me what I was looking for if the main article is immediately going down into technical rabbit holes.
It already exists.
Native macOS apps get to be a bit clever for this, in that there are two kind of button-highlight-state per dialog (the "default action" button, which is filled with the OS accent color; and, separately, the button the tab-selection starts off highlighting, which has an outline ring around it.) This means that there are two keys you can mash, for different results: mashing Enter results in pressing the default action (i.e. colored) button–which Apple HIG suggests be the "Confirm" option for dangerous cases; while mashing Space results in selecting the initially-selected (i.e. outlined) button—which Apple HIG suggests be the "Cancel" option for dangerous cases. I believe that, in cases where the action isn't irrevocable, Apple HIG suggests that the default-action and initially-selected attributes be placed on the same button, so that either mash sequence will activate the button.
I really wish that kind of thinking was put into other systems.
What is different in Win32, however, is that if any button is focused, it is also made the default for as long as focus is on it (or, alternatively - Enter always activates the focused button). Thus, there's no visual state for "focused, not default", because there's no such thing.
The distinction still matters, though, because if you tab away from a button to some other widget that's not a button, the "default" button marker returns back to where it originally was - focus only overrides it temporarily.
This can be conveniently explored in the standard Win32 print dialog (opened e.g. from Notepad), since it has plenty of buttons and other things on it. Just tab through the whole thing once.
There were computer keyboards which had a distinction between the button to enter the field and the button to, for example, do the desired action behind the whole dialog. Just like today it is common to expect that Esc is going to cancel the dialog (or the entry form) there was a key that one knew would do the "proceed" (GO) independently of the position in which field your cursor is at the moment (or was). In these operating systems Enter always did just the non-surprising "end of the entering of the current input field, skip to the next" and the "GO" signaled the end of that process and the wish to use everything that has been entered up to any point. It's particularly convenient when entering a lot of numerical data on the numeric keypad, where Enter also just moves to the next field.
I think that concept was right, and better than what we have today. Entering what are basically "forms" in any order (filling the dialogs) and proceed from any point is a basic task and could have remained less surprising.
Yes, and Mozilla has become much worse about this. Turning off "Pocket Integration", or "Shared Bookmarks", or "Mozilla Telemetry", or "Auto update" becomes harder in each release.
Now all you have to do is stick a bone through your beard and pronounce yourself a "UX Guru" and off you go.