interaction design
Discoverability
What is discoverability in UX?
Discoverability is whether users can figure out what an interface can do and how to use it, just by looking and experimenting - without needing a manual, tooltip, or tip-of-the-day. A feature that exists but can’t be found doesn’t truly exist for most users; its usefulness is limited by how visible it is.
Also known as: discoverability, discoverable, feature discovery
Prefer to watch?
Watch the recap 0:46
The demo
Save this item for later. Try it when the way to do it is hidden, then when it wears an obvious button - and notice whether you could find it without being told.
What this demo shows (text version)
The task - save an item for later - is offered two ways. In "hidden", the item card carries no visible control; the only way to save is an unsignalled double-click, which nothing tells you about, so you're left hunting. A "show me" link admits the gesture after the fact - the point being that most people would never have found it and would assume the feature didn't exist.
In "discoverable", the same action wears a plain, labelled "Save" button you spot and use immediately. The feature is identical; only its findability changed. That's discoverability: a capability is only as useful as it is visible, so signal actions with real controls and keep hidden gestures as optional shortcuts for experts, never the sole way in.
A feature only counts if users can discover it. Hidden gestures and unlabelled controls save visual space but cost the function itself - most users never find them. Make actions visible with clear signifiers (a labelled, button-shaped button), and treat any hidden shortcut as an accelerator for experts, never the only way in. If you’d have to tell someone it’s there, it isn’t discoverable.
When the action was a hidden gesture, you hunted - and most people would simply have given up, never knowing it was there. When it wore a plain, labelled button, you saw it and used it at once. The feature was identical both times; the only thing that changed was whether you could find it. That's discoverability.
Discoverability is what turns an affordance into a used feature. A possibility the design never signals - a swipe, a long-press, a double-click on something that looks inert - is invisible to anyone who wasn't told. People act on what they can see; an unsignalled action is, for practical purposes, missing.
Hidden gestures are seductive because they keep screens clean, but the cost is borne by the user who can't find the function and assumes it doesn't exist. Clean is not the goal; findable-and-usable is. If a capability matters, give it a visible control - and let the gesture be a fast path for the few who learn it.
The honest test: could someone use this without being told it's there? If a feature needs a coach mark, a tooltip or an onboarding tip just to be found, that's a discoverability bug, not a teaching opportunity. Coach marks paper over missing signifiers; fix the signifier and you won't need the coach mark.
Try the discoverability demo on site:uxbyexample.co.uk to see how visible controls guide users - and how hidden ones silently vanish from use. The interactive example here lets you test what users can find without help - and what they miss because it’s tucked away.
Try the hands-on demo on site:uxbyexample.co.uk to see how discoverability affects real user behaviour. If you’d have to tell someone it’s there, it isn’t discoverable - test this principle live on site:uxbyexample.co.uk.
Discoverability isn’t just about labels - it’s about whether users can intuitively find and use features through interaction, not instruction. Try the live demo on this page to see how hidden controls fail real users. If you’d have to tell someone it’s there, it isn’t discoverable - and that’s why the interactive demo on this page shows you how visibility drives usability.