Differences between revisions 2 and 3
Revision 2 as of 2010-10-14 18:55:25
Size: 259
Editor: shoobe01
Comment:
Revision 3 as of 2011-04-19 01:52:47
Size: 1696
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:



This all needs to be tied together as a single thought. What's a pattern, this, the style and so on. So we can expand on thoughts like: The patterns were developed by observing and analyzing a large number of devices -- featurephones, smartphones, pdas, tablets, gps's, etc. Key components were observed to be true in most devices, and used pretty consistently. Those were generally considered to be patterns.

The patterns themselves were then analyzed to assure they meet the basics for good UI/UX design. When gaps are found, or are simply exposed from our own knowledge and observations (from lab tests, etc.) these common practices ended up being anti-patterns, and the best practice is written up instead.

In general, best practice that is not implemented anywhere is not described, as it does not rise to the level of a pattern. Only real world items are patterns by our thinking, not clever concepts. There may therefore be some odd cases where an antipattern has general solutions listed, but no specific solutions in the body of the pattern. The antipattern is listed as it's a known problem, but no single solution has emerged.

Other times, this is simply described as such in the pattern. Other gaps, such as emerging technologies or interesting implementations that could use a pattern, but do not yet do so -- or do not do so consistently -- are likewise left out, or are noted as being not yet a pattern.

This page is a stub. It's just something to get notes down, and is not final in any way.

Chat about this. We don't repeat stuff just because it's used everywhere. If it's common, but awful, we include it, but with warnings...

This all needs to be tied together as a single thought. What's a pattern, this, the style and so on. So we can expand on thoughts like: The patterns were developed by observing and analyzing a large number of devices -- featurephones, smartphones, pdas, tablets, gps's, etc. Key components were observed to be true in most devices, and used pretty consistently. Those were generally considered to be patterns.

The patterns themselves were then analyzed to assure they meet the basics for good UI/UX design. When gaps are found, or are simply exposed from our own knowledge and observations (from lab tests, etc.) these common practices ended up being anti-patterns, and the best practice is written up instead.

In general, best practice that is not implemented anywhere is not described, as it does not rise to the level of a pattern. Only real world items are patterns by our thinking, not clever concepts. There may therefore be some odd cases where an antipattern has general solutions listed, but no specific solutions in the body of the pattern. The antipattern is listed as it's a known problem, but no single solution has emerged.

Other times, this is simply described as such in the pattern. Other gaps, such as emerging technologies or interesting implementations that could use a pattern, but do not yet do so -- or do not do so consistently -- are likewise left out, or are noted as being not yet a pattern.

Common Practice Versus Best Practice (last edited 2013-04-08 20:01:47 by shoobe01)