[wruza]

It is discoverable through “g windows tips and tricks”. Reading articles like that went out of fashion too though. Thing with “power” and “advanced” is that you have to learn, because otherwise that info for all features had to be on screen and there’s only so much space on it.

This whole discoverability bs is what has driven UI into intuitive uselessness for everyone, when there’s actually two groups: first (/one) time users and just users (“power” or not). For some reason modern UX designers think everyone is in the first group. Even if an app is naturally multi-time heavy-use.

[eviks]

> because otherwise that info for all features had to be on screen and there’s only so much space on it.

there's practically infinite space on screen since that space has a time dimension and can also be tied to context which also varies. Like with this feature: you can show a tip on the first few searches within a list, you don't need to permanently keep the explanation on screen. Or you can show a hint with ll by having a different style of the second l or something similar

Undiscoverability is precisely one big reason why these things get axed since they're not used, so forgotten about in other contexts (web, new UI framework etc)

And yes, needing to reading random articles like this is a major fail in discoverability as you decrease reach and increase cost for the many poor users

[ryandrake]

I hate the "discoverability" trend. I don't want discoverable UI. I want UI that is consistent with all my other apps, which I have already learned. I should not have to have an app nudge me to "discover" its oh-so-cleverly-hidden features. I'm not Dora the fucking Explorer, I'm a computer user who expects everything on the platform to behave predictably and consistently.

And while we are at it, "lack of use" is not a good reason to axe features. Some things, by their nature, just don't get used as much but when they are needed they are needed. Product designers have become slaves to their telemetry and metrics, and are letting the tail wag the dog.

[eviks]

I wasn't talking about a trend, but real discoverability, so your rant is misplaced.

> expects everything on the platform to behave predictably and consistently.

and poor discoverability makes this expectation even less likely to be met

Similarly

> "lack of use" is not a good reason to axe features.

But it is a great reason not to implement features in the new framework since you're not even aware of them because they're undiscoverable! (I know, I know, not to you, you've already wasted time doing the discovery the hard way by reading some obscure blog, but then you go teach the devs of those new frameworks!)

Also, what is this imaginary telemetry that is able to track that I want ll to land on llama instead of blindly following invisible-mode#1? It would be awesome if product designers were that competently informed, we would've gotten universally great UIs!

[wruza]

Real discoverability is as real as discoverability of subj, so we’re all misplaced. That bugs me the most, much talks, crap UIs. Empty rationalizing it to death instead of cultivating feature cultures that already work and do not require “design”.