Live data from Hacker News

The Windows 95 user interface: A case study in usability engineering (1996)

dl.acm.org

51–60 of 290 posts

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#51
post #37

Wasn't Windows 95 just a copy of Windows NT, which was the real product.

No, Windows NT until 4.0 had the same interface design as Windows 3.x (although there existed a semi-official SP/addon to give NT 3.5 the Chicago interface, making it quite similar to 95), and NT 4.0 came later than 95

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#52
post #37

Wasn't Windows 95 just a copy of Windows NT, which was the real product.

Both OS lines were developed concurrently up until XP release where DOS-based 9x was abandoned and NT became the basis for every subsequent product. Plus of course there's that whole part of the story where MS teamed up with IBM and worked on OS/2.

NT got new 9x shell with 4.0 release but a beta package could be installed on 3.51 as well - tho, that could render some compatibility issues.

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#53
post #25
post #15

Steve Jobs is famous for his 1996 quote about Microsoft not having taste ( https://www.youtube.com/watch?v=UiOzGI4MqSU ). I disagree; as much as I love the classic Mac OS and Jobs-era Mac OS X, and despite my feelings about Microsoft's monopolistic behavior, 1995-2000 Microsoft's user interfaces were quite tasteful, in my opinion, and this was Microsoft's most tasteful period. I have fond memories of Windows 95/NT 4/…

> Microsoft Office 2007 ribbon Ribbon also has a similar research behind it, just like Windows 95. For what they designed it, allowing beginners to discover all the functionality that's available, it works perfectly. I think most of the complaints from the tech circles are completely unfounded in reality. Many non-tech people and younger ones actually prefer using Ribbon. I also like it since it is very tastefully ma…

The Ribbon is a disaster. Compared to conventional toolbars, it fails across several metrics.

When it first came out, I did studies of myself using it vs. the older toolbared versions of Word and Excel, and found I was quantifiably slower. This was after spending enough time to familiarize myself with it and get over any learning curve.

EFFICIENCY

The biggest problem is it introduced more clicks to get things done - in some cases twice as many or more. Having to "tab" to the correct ribbon pane introduces an extra click for every task that used to be one click away, unless the button happens to be on the same tab. Unfortunately the grouping wasn't as well thought out as it could have been. It was designed with a strong bias for "discoverability" over efficiency, and I found with many repetitive tasks that I commonly carried out, I was constantly having to switch back and forth between tabs. That doesn't even get into the extra clicks required for fancier elements like dropdowns, etc. And certain panes they couldn't figure out where to put are clearly "bolted" on.

KEYBOARD SHORTCUTS

At the same time, Microsoft de-emphasized keyboard accelerators. So where the old toolbar used to hint you the keyboard shortcut in a tooltip every time you rested your mouse over a button, the new one doesn't - making it unlikely users will ever learn the powerful key combos that enable more rapid interaction and reduce RSI caused by mousing (repetitive strain injury). In my case this manifests as physical pain, so I'm very aware of wasteful gestures.

SCREEN REAL ESTATE

The amount of text in the button captions on the ribbon is also excessive. It really isn't a toolbar at all, more of a fancy dropdown menu that's been pivoted horizontally instead of vertical. It turned the menu bar, which used to be a nice, compact, single line, into something that now takes up ~4x as much vertical screen real estate. As most users' monitors are in landscape orientation, vertical space is scare to start with; congratulations you just wasted more of those precious pixels, robbing me of space to look at what I really care about which is the document or whatever thing I'm actually working on.

DISCOVERABILITY

You used to be able to get a good sense of most software's major functionality by strolling through all the menu options. Mastery (or at least proficiency) was straightforward. With the more dynamic paradigm Microsoft adopted along with the Ribbon, there's lots of functionality you don't even see until you're in a new situation (or that's hidden to the responsive window layout, which is ironic - instead of making the thing more compact, they made portions of it disappear if your window is too small). I grant some may argue this has benefits for not appearing as overwhelming to new users (although personally I've always found clean, uniform, well thought out menus to be less jarring than the scattered and more artistically inclined ribbon). But easing the learning curve had the trade off of making those users perceptually stuck in "beginner" mode. They can't customize the ribbon as meaningfully (I used to always tailor the toolbar by removing all the icons I already knew the keyboard shortcuts for, adding some buttons that were missing like Strikethrough, and move it to the same row as the menu bar to maximize clientarea space)

In my case, after trying out the new versions for a year, I made an intentional decision to go back to the 2003 versions of Word and Excel, and never look back (forward?). They are my daily drivers. These days, I barely touch modern versions of Word and Excel, except for the very rare instance I actually need a specific new feature (i.e. a spreadsheet with more than 65k rows). If someone asks me to use the new version, I simply refuse (which has never been a showstopper - my work quality is preeminent, and once you get past policy bureaucracy it turns out clients/employers don't care what tool I use to get it done).

The whole point of a toolbar was always to be a place you could pin commands you want instant access to, just a click away. The ribbon shredded that paradigm, and in my opinion took us a marked step backward in computing. It fails across several metrics, compared to regular toolbars. I wanted to blog about it at the time in hopes of convincing the world it was a mistake, but didn't have the free time. 20 years later, I'm curious if more people share these sentiments and acknowledge its shortcomings.

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#54

Look how crisp, professional, and usable it all is. This is a very good write-up. There's no way this level of testing and dedication could have resulted in the execrable shitshow that is Windows today. Mac OS is going backward with accelerating speed, too. They had just started to recover from Jony Ive when they put a packaging designer in charge of UI... resulting in the "Liquid Glass" debacle, and all the other in…

Ranting on UI, I think I might blame MS for this but I feel like many shortcuts for customization in apps and OS are a net negative.

The first example I remember was ~2003ish when MS Office did a big redesign and got much bigger toolbars. That they were big is a matter of taste but that's not where I'm going with this. No, the issue was that they made too easy to ACCIDENTALLY mess up the UI. They added all kinds of customization (which is fine) but then made it so just dragging a little too long an a button would let you move the button somewhere else. So, grandpa drags the button, possible off the bar, deleting it, and now for all intents and purposes the app is unusable to him. IMO, the customization options should be buried deeper where they can't happen by accident.

This "ACCIDENTAL" modification is all the rage now. On iPhone, holding on the lock screen puts the phone in "edit the lock screen mode". Several family members have asked why the image they put on the lock screen was gone. It was because they "butt edited the screen". Put the phone in their pocket and it felt a press and went into edit mode and edited the lock screen. AFAIK, almost no one needs this shortcut. It would be fine to just go into Settings->Wallpaper->Lockscreen or something like that. But, I'm just guessing (1) some UX designer needed something todo (2) someone working on lockscreen options got tired of doing the Settings->Wallpaper->Lockscreen dance and put in a shortcut that no-one but them needs.

This same issue is all over the place. The iPhone's lockscreen while charging mode has the same issue. The user (me) picks the clock face I want. And, one of 10 times I reach for the phone from the charging stand I accidently touch the screen which changes the face. I NEVER NEED THIS. Again, this should be buried in Settings->Lockscreen->Clock Face. The shortcut a net negative.

There are many more.

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#55
post #15

Steve Jobs is famous for his 1996 quote about Microsoft not having taste ( https://www.youtube.com/watch?v=UiOzGI4MqSU ). I disagree; as much as I love the classic Mac OS and Jobs-era Mac OS X, and despite my feelings about Microsoft's monopolistic behavior, 1995-2000 Microsoft's user interfaces were quite tasteful, in my opinion, and this was Microsoft's most tasteful period. I have fond memories of Windows 95/NT 4/…

I'll also give the opinion that Apple consistently creates some absolutely crap designs and when they do this, release something really really mind mindbogglingly stupid that it should be embarrassing they are instead met with applause on the "amazing design". It's a tiresome pattern repeated for decades now. eg. The 'breathing status light' that lit up the room at night due to extreme brightness which meant every ma…

I recently had to get printing working for a family member on an Apple tablet. I'm not an Apple jockey so it took me a while to sort out and I've being using computers since 1980 and consulting since 1995.

You tap an icon that looks like the outline of a rectangle with an arrow pointing up. Then you tap the name of the printer. Then you tap another rectangle with an up arrow and then tap the word "Print".

I may have got the precise steps wrong but it really is that abstruse to print something on a tablet. Never mind that mDNS/Bonjour has done its thing - the steps to actually indicate that you want to print is frankly weird.

What on earth is that box with an up arrow actually supposed to mean? Why does the interface switch from icons to text?

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#56
post #31

I think Windows 95/2000 and the contemporary MacOS (including the then future MacOS X) have the best UI in everything I used in my 30+ years of tech life. I sincerely hope that one day we could go back to that road. If you want that achieved, please support me to join Apple/Microsoft to become the UI boss, fire all flat-design people and hire a small team to implement the older UI, then give a few passionate talks on…

After nearly 30 years of tech life myself, I've come to the realization that the best UIs are not graphical. They can have graphical elements mostly for visualization purposes, but all of them should be as minimal and unobtrusive as possible. Any interactivity should be primarily keyboard-driven, and mouse input should be optional. Forcing users to click on graphical elements presents many challenges: what constitute…

> Forcing users to click on graphical elements presents many challenges: what constitutes an "element"; what are its boundaries; when is it active, inactive, disabled, etc.; if it has icons, what do they mean; are interactive elements visually distinguishable from non-interactive elements; and so on.

There are standards and common conventions for a lot of this in the Windows 9X/2000 design language, and even in basic HTML. These challenges could have been solved (for values of) by using them consistently, and I think we might have been there for a little while, at least within the Windows bubble. The fact that we threw all of those out the window with new and worse design, then did that again a few more times just to make sure all the users learned to never bother actually learning the UI, since it will just change on them anyway, doesn't entail that this is an unsolvable problem (well, it might be now, but I doubt it was back in 1995).

> Like you, I do have a soft spot for the Windows 2000 GUI in particular, and consider it the pinnacle of Microsoft's designs, but it still feels outdated and inneficient by modern standards. The reason for this is because it follows the visual trends of the era, and it can't accomodate some of the UX improvements newer GUIs have (universal search, tiled/snappable windows, workspaces, etc.).

I fail to see why any of these features couldn't be implemented within the design constraints of the Windows 9X/2000 design language. There are certainly technical constrains, but I can't see any design constrains. They were never implemented at the time, and those features didn't become relevant until we'd gone through several rounds of different designs, so we never had the opportunity to see how it would work out.

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#57
post #15

Steve Jobs is famous for his 1996 quote about Microsoft not having taste ( https://www.youtube.com/watch?v=UiOzGI4MqSU ). I disagree; as much as I love the classic Mac OS and Jobs-era Mac OS X, and despite my feelings about Microsoft's monopolistic behavior, 1995-2000 Microsoft's user interfaces were quite tasteful, in my opinion, and this was Microsoft's most tasteful period. I have fond memories of Windows 95/NT 4/…

I'll also give the opinion that Apple consistently creates some absolutely crap designs and when they do this, release something really really mind mindbogglingly stupid that it should be embarrassing they are instead met with applause on the "amazing design". It's a tiresome pattern repeated for decades now. eg. The 'breathing status light' that lit up the room at night due to extreme brightness which meant every ma…

I got no problem with that tiny LED or glowing apple logo personally

But liquid glass and insane amount of bugs that arrived with it is killing me.

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#58
post #37

Wasn't Windows 95 just a copy of Windows NT, which was the real product.

No, Windows NT until 4.0 had the same interface design as Windows 3.x (although there existed a semi-official SP/addon to give NT 3.5 the Chicago interface, making it quite similar to 95), and NT 4.0 came later than 95

From Raymond Chen's Old New Thing:

How did the Windows 95 user interface code get brought to the Windows NT code base?

https://devblogs.microsoft.com/oldnewthing/20251028-00/?p=11...

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#59

Earlier quoted context omitted.

I'll also give the opinion that Apple consistently creates some absolutely crap designs and when they do this, release something really really mind mindbogglingly stupid that it should be embarrassing they are instead met with applause on the "amazing design". It's a tiresome pattern repeated for decades now. eg. The 'breathing status light' that lit up the room at night due to extreme brightness which meant every ma…

I got no problem with that tiny LED or glowing apple logo personally But liquid glass and insane amount of bugs that arrived with it is killing me.

Likely you experienced later gens where they toned it down. ~2010 it was one of the brightest LEDs you could purchase. As in they literally put a torch LED on the all white Intel macbooks of the era and it would shine through the laptop bags, pulsating.

Re: The Windows 95 user interface: A case study in usability engineering (1996)

#60

Look how crisp, professional, and usable it all is. This is a very good write-up. There's no way this level of testing and dedication could have resulted in the execrable shitshow that is Windows today. Mac OS is going backward with accelerating speed, too. They had just started to recover from Jony Ive when they put a packaging designer in charge of UI... resulting in the "Liquid Glass" debacle, and all the other in…

Ranting on UI, I think I might blame MS for this but I feel like many shortcuts for customization in apps and OS are a net negative. The first example I remember was ~2003ish when MS Office did a big redesign and got much bigger toolbars. That they were big is a matter of taste but that's not where I'm going with this. No, the issue was that they made too easy to ACCIDENTALLY mess up the UI. They added all kinds of c…

Apparently, the idea of an edit mode is some foreign concept for a lot of people.
Post reply on HN