4 ms·
Depends on use case. When onboarding a user, it saves support emails when people can't figure out how to fulfill basic use cases. It also highlights new feature
by ebiester 3y ago
Depends on use case. When onboarding a user, it saves support emails when people can't figure out how to fulfill basic use cases. It also highlights new features that don't deserve main screen real estate but are requested.
It's only annoying when it's pointing out the obvious.
- dabeeeenster 3y ago"It's only annoying when it's pointing out the obvious." No, I find them annoying every single time.
- IggleSniggle 3y agoI also find them annoying, but begrudgingly appreciate them too. Usually they are interrupting my flow to introduce me to a new non-obvious feature, and sometimes those new features are super useful.
- taneq 3y agoI think they’re a design smell. If your interface is designed well, you don’t need them. If you hide features behind cute-but-meaningless icons with no text tooltips, you users will still struggle to find them even with an irritating onboarding tutorial.
- ativzzz 3y agoHow would your users find out about a new feature on a page that's tucked away into a menu without one of these?
- taneq 3y agoPatch notes? You can give users some bullet points to read when they run a new version for the first time, without railroading them into clicking through the menu structure. Also maybe keep the menu structure logical so that users can actually discover functionality by looking through the menu, like we did in the old days before semantically relevant text was replaced with tastefully ambiguous generic pastel icons.