4 ms·
A good UI can only ever have a limited number of discoverable actions. You can try to make a button for everything, but no one is going to try all the buttons,
by Wowfunhappy 7y ago
A good UI can only ever have a limited number of discoverable actions. You can try to make a button for everything, but no one is going to try all the buttons, much less remember what they mean.
So you have to pick which actions are most important, and make those easy to discover. QuickLook is a wholly essential feature. So is navigating up a level—it's very useful in some instances, but the back button does the same thing 90% of the time.
For the rest, what matters most is that the actions are never activated accidentally†. This last point is, IMO, where iPadOS fails the most.
*
However: it is worth noting how far the Mac has fallen in the past decade. Snow Leopard had persistent scrollbars, that were big and blue so you couldn't miss them. Finder's toolbar had a button for activating QuickLook. And of course, the notification center didn't exist yet.
There's a pattern behind all these changes. Scrollbars were modified to match iOS. The QuickLook icon was removed to make room for a share button that mimics iOS. The design of notification center was basically ripped from iOS wholesale.
So yes, I agree that iOS has UI problems.
——————————
† Unless the user can instantly parse how they accidentally triggered the action. If you can turn the accident into a learning experience, that's fantastic.
‡ It's still there, but disabled by default. So in terms of discoverability, it might as well not exist.
- pjc50 7y ago> You can try to make a button for everything, but no one is going to try all the buttons There's a reason people pay lots of money for Bloomberg terminals, with their zillion labeled physical keys. > If you can turn the accident into a learning experience, that's fantastic. On the other hand, if there's no other way for people to discover them than accident ..
- Wowfunhappy 7y ago> There's a reason people pay lots of money for Bloomberg terminals, with their zillion labeled physical keys. And a reason that type of design is only used in specialized, targeted scenarios. They have their place for sure, but it's pretty narrow. > On the other hand, if there's no other way for people to discover them than accident .. If it's a nonessential feature, I don't think that's a problem. You're allowing people to learn the system at a gradual pace. The best interfaces are ones which are accessible to newcomers, but slowly train you to become a power user just via incidental use. OS X used to be very, very good at this, and still does an above average job in many respects.
- samatman 7y agoPractically speaking, Notification Center already existed, it was just called Growl. Everyone I knew with a Mac had it loaded, and Apple adopted the API whole-cloth for Notification Center, for compatibility reasons.
- Wowfunhappy 7y agoYes, but Growl had a very different UI from notification center.
- samatman 7y agoBy now, yes, this is true. When it was first released it was just Apple-flavored Growl. I don't find myself using most of what's been added. I routinely forget that there's a drop-down with all the stale Notifications in it, and other than the evening Do Not Disturb which turns on automatically, I forget (sometimes to my detriment) that I can activate it manually.
- Wowfunhappy 7y agoOther than the addition of Today widgets (aka Dashboard except worse), Notifications Center really hasn't changed much since it was released. Here's what it looked like in Mountain Lion, where it was first introduced: https://512pixels.net/projects/aqua-screenshot-library/os-x-10-8-mountain-lion/#jp-carousel-16160 https://512pixels.net/projects/aqua-screenshot-library/os-x-... And here's Growl: http://growl.info/images/screenshots_images/RollupWhileAway.png http://growl.info/images/screenshots_images/RollupWhileAway....
- samatman 7y agoI stand corrected! I just remember switching over at some point and not really noticing. Messages still made a small noise and slid in from the top right; some would disappear, some wanted me to click on them. Like I said, I barely use the panel, and thought (thank you for the correction) that it was a later addition.
- Treblemaker 7y ago> ‡ It's still there, but disabled by default. So in terms of discoverability, it might as well not exist. Well played my friend; well played.
- eitland 7y ago> A good UI can only ever have a limited number of discoverable actions. Edit: FTR, this comment is kind of hyperbolic. I do not think I can outsmart all UX designers alone or that all UX designers are dumb or that those who designed Ribbon are dumb. I'm just pointing out that 1. I think there was a golden age of discoverability in UX where everything could be discovered and 2. It is over now. Unless I misunderstand something here this should be plain demonstrably wrong (and note for context that I'm not exactly a Windows and Office enthusiast, quite the contrary): In Microsoft Office (and a good number of other application) everything was available through the menus. Toolbar buttons were just shortcuts fot the more important ones. Then "UX" happened on Windows and today we've suffered through - Office automatically hiding half the menus (late pre-Ribbon) - early (but released, not Beta) Ribbon versions where File and Save was hidden behind a round flag that turned out to be a button. - now: Ribbon is actually usable. Nice looking, still less predictable and more visual noise in addition to the leftmost menu (File...?) behaving in a (weirdly IMO) different way. - now: menus are gone in many applications. I belive Chrome is the culprit here. Designers like Chrome it seems and for a number of UX-designers the idea seems to be that whatever Chrome and Mac OS does has to be copied across OS and domain boundaries. If it wasn't clear: UX on Windows used to be great. The OS was closed, slow, annoyingly limited etc, the UI was kind of ugly and business-focused but the UX was discoverable and usable. What should have been done? I don't know but here are a couple of ideas: - search in menus (as implemented in IDE settings, Visual Studio palette etc)? - add fallback with synonyms and slight fuzzing to the search index so you get can the correct tool even if you misspelled it or if you are stuck on a Norwegian or French version. - make enthusiastic videos about how it is best (I'm only half joking here, it seems to have worked for the vim crowd, - a number of people spend weeks learning a decades old editor whos discoverability is so bad no one knows how to even exit it the first time they open it.)
- SAI_Peregrinus 7y ago> You can try to make a button for everything, but no one is going to try all the buttons, much less remember what they mean. That's where old-fashioned hierarchial menus are good. They're categorized lists of actions, where most of the actions are hidden most of the time, but can be read (and ideally have descriptive names). Typically there are also toolbars with buttons for the most commonly used actions. These days it's become popular to hide all the menus behind a "hamburger" icon, which does satisfy the design types without harming usability all that much. The other option is to have a gigantic button for everything, with tabs of buttons, and call it a "ribbon". The more cryptic the icons the better, you've made the decision to go to a ribbon so you wouldn't want to make things easy.