Hidden against disabled: what is best for custom experience?

Зображення до статті Hidden against disabled: what is best for custom experience?
Зображення до статті Hidden against disabled: what is best for custom experience?

Both options - hiding and disconnecting functions - can cause confusion among users. Both options require very good reasons. It is worth considering what we need to take into account when it comes to hiding and disconnecting, as well as possible alternatives that will help improve your custom experience.

🚀 As a rule, turn off if you want the user to know that the feature exists but not available. Hide if the indicated value is currently irrelevant and cannot be used. But never hide buttons or key filters by default as users expect them to be unchanged.

  • 📌 Hiding important functions prevents their detection.
  • 📌 Function disabilities are disappointing without explanation.
  • 📌 Some options may be not important or inaccessible to users.
  • 📌 Users may expect a function but will not find it.
🧩 Summary: Hiding and disconnecting functions in the interface design require a deep understanding of custom experience. It is important to choose the right option depending on the situation, as well as consider alternatives.
🧠 Own considerations: choosing between concealment and shutdown can significantly affect custom experience. I think it is better to give users more control over their experience by allowing them to choose what features they want to see or hide.