It doesn't sound like you know what software design patterns are. This has absolutely nothing at all to do with design patterns, which is about software design and how to manage complexity and nothing else. UX is not code.

While I agree that the TC intended software design patterns, I don't think a WTF is in order for the confused reply.

The term "design patterns" stems from architecture, not computer science, and is used by designers as well for the common patterns that may be applied for good UI/UX design.

http://ui-patterns.com/patterns

Somebody better let Google know that "design patterns" don't apply to UX.

https://developer.android.com/design/patterns/index.html

https://developers.google.com/web/fundamentals/layouts/rwd-p...

> The term "design patterns" stems from architecture, not computer science

Do you have any references? I find this fascinating, but googling "design patterns" and "architecture" together just results in lots of "software architecture" topics. Who originated the idea?

The origins of patterns in software are actually from architecture. Code is just a medium that we work with, but they've been used in other fields for millennia.

Plus patterns in software are not all about managing complexity, and only some of them are about code construction. Like, do you know what the pattern is before you debug anything?

They're heuristics, basically.

In any case, a good ux pattern would be a top nav, but not fixed to the top.

@mattmanser the op asked specifically for UI patterns: "To give an obvious example of what I'm looking for- I would say, use margins to separate multiple instances of same components (among other uses)."

Question of the day: did design patterns originate with the GoF, or did they originally exist in the world outside of code as patterns to improve human experience?

Code producing bad UX is bad code.

Thank you. While not exactly what I was asking for, this is great to know.