[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”.