Comments on: UI Design Patterns: let’s clean up our language http://blog.spinthemoose.com/2010/07/20/ui-design-patterns/ Closer to the glass... Fri, 17 Jun 2011 17:06:55 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Isaac http://blog.spinthemoose.com/2010/07/20/ui-design-patterns/comment-page-1/#comment-155 Isaac Tue, 27 Jul 2010 15:06:19 +0000 http://blog.spinthemoose.com/2010/07/20/ui-design-pattern-resources/#comment-155 Hmmm. IMHO, the MVC, MVVM, and MVP patterns mentioned here have very little to do with UI at all, other than the fact that the UI is a component of the pattern. Really, they're software architecture patterns. The UI has no knowledge of the underlying pattern and is merely a component of said pattern. It doesn't care. So calling it a UI anything seems a misnomer. I do agree completely with your distinction between using the word design versus architecture. Let's be explicit. Hmmm. IMHO, the MVC, MVVM, and MVP patterns mentioned here have very little to do with UI at all, other than the fact that the UI is a component of the pattern. Really, they’re software architecture patterns. The UI has no knowledge of the underlying pattern and is merely a component of said pattern. It doesn’t care. So calling it a UI anything seems a misnomer.

I do agree completely with your distinction between using the word design versus architecture. Let’s be explicit.

]]> By: davidalpert http://blog.spinthemoose.com/2010/07/20/ui-design-patterns/comment-page-1/#comment-153 davidalpert Thu, 22 Jul 2010 17:13:42 +0000 http://blog.spinthemoose.com/2010/07/20/ui-design-pattern-resources/#comment-153 I agree 100% with the value of using language that your audience understands. The point I was making above is that the specific phrase "<strong>UI</strong> design pattern" evokes something different to designers and UX-minded people than it does to server-side or back-end developers while adding the word "architecture" does not change the meaning for those folks already expecting the pattern to be an architectural one. Small steps to clarify our language and speak with more precision can go a long way towards building bridges between audiences. I agree 100% with the value of using language that your audience understands.

The point I was making above is that the specific phrase “UI design pattern” evokes something different to designers and UX-minded people than it does to server-side or back-end developers while adding the word “architecture” does not change the meaning for those folks already expecting the pattern to be an architectural one.

Small steps to clarify our language and speak with more precision can go a long way towards building bridges between audiences.

]]> By: Dylan http://blog.spinthemoose.com/2010/07/20/ui-design-patterns/comment-page-1/#comment-152 Dylan Wed, 21 Jul 2010 05:23:42 +0000 http://blog.spinthemoose.com/2010/07/20/ui-design-pattern-resources/#comment-152 While your terms make sense, the term design pattern is widely understood to mean what you call architectural patterns. For better or for worse, that's it's common usage, and I try to talk in the language that the majority of my audience understands... While your terms make sense, the term design pattern is widely understood to mean what you call architectural patterns. For better or for worse, that’s it’s common usage, and I try to talk in the language that the majority of my audience understands…

]]>