> The point of UI/UX/HUI guidelines is to ensure consistency of applications' look&feel. That's not the focus of UX, at all. Consistency is not an end in itsel

> The point of UI/UX/HUI guidelines is to ensure consistency of applications' look&feel. That's not the focus of UX, at all. Consistency is not an end in itself, it's just a way to achieve predictability and, in consequence, ease-of-use. It's important but not that much (not everyone is an engineer or homo logicus - people do tolerate inconsistency, as incredible as it might seem). Maybe you're thinking this or focusing on UI implementation guidelines. UI/UX (I don't know what you mean by HUI) guidelines should be heuristics/rules of the thumb aimed at ensuring your digital product serves your users in their usage contexts. e.g. saying the button should be blue isn't that much relevant; however, saying "you need an explicit button to confirm a given kind of action" is. > Under detailed guidelines, two applications doing exactly the same thing should look exactly the same. I just quoted this to illustrate how wrongly you are conceiving UX: you're focusing only on the "thing" being done. But UX - even the most square definitions of usability such as ISO 9241 - cares about "who" does it and in which context. So, two applications doing the same thing may look radically different, if used by different people and/or in different contexts. I also think you focus too much on the "look" aspect.