<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mockery Blog &#187; Mac</title>
	<atom:link href="http://getmockery.com/blog/archives/tag/mac/feed" rel="self" type="application/rss+xml" />
	<link>http://getmockery.com/blog</link>
	<description>GetMockery.com company blog - Mockery, UI, and more.</description>
	<lastBuildDate>Fri, 16 Dec 2011 19:48:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A roundup of UI guidelines and reference documents</title>
		<link>http://getmockery.com/blog/archives/72</link>
		<comments>http://getmockery.com/blog/archives/72#comments</comments>
		<pubDate>Tue, 10 Nov 2009 00:11:07 +0000</pubDate>
		<dc:creator>Joel Anair</dc:creator>
				<category><![CDATA[GUI]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://getmockery.com/blog/?p=72</guid>
		<description><![CDATA[As UI designers, we are responsible for playing nicely with the operating systems that our software runs on. While blind adherence to any rule is obviously not a good idea, uniformity gives applications greater learnability and makes users feel at home. If you&#8217;re doing something in your app differently than other apps do the same [...]]]></description>
			<content:encoded><![CDATA[<p>As UI designers, we are responsible for playing nicely with the operating systems that our software runs on. While blind adherence to any rule is obviously not a good idea, uniformity gives applications greater learnability and makes users feel at home. If you&#8217;re doing something in your app differently than other apps do the same thing, you should have a good reason.</p>
<p>If you&#8217;re developing software that will run on multiple platforms, in most cases the technology you&#8217;re using will handle rendering controls and widgets in a platform-appropriate way. But using platform-specific design patterns is still up to you. Luckily, most major platforms provide guides for designing UIs that feel right. Here is a list of useful documentation broken out by OS.</p>
<h3>Windows</h3>
<ul>
<li><a href="http://msdn.microsoft.com/en-us/library/aa511440.aspx">Windows User Experience Interaction Guidelines</a> include sections on controls, windows, commands (by which they mean menus and toolbars), text, handling input devices, and more.</li>
<li><a href="http://msdn.microsoft.com/en-us/library/aa511275.aspx">The Aesthetics section of the above document</a>, in particular, has some really useful information about UI layout and the graphic design side of UI.</li>
<li><a href="http://msdn.microsoft.com/en-us/library/aa511443.aspx">Microsoft&#8217;s overview of the Windows Environment</a> will be particularly helpful for anyone who hasn&#8217;t been able to keep up with the Windows UI over the past few revisions.</li>
<li><a href="http://msdn.microsoft.com/en-us/library/bb328626.aspx">MS&#8217;s Visual Index of controls</a> provides screenshots and brief descriptions of UI controls as they appear in the modern Aero Windows graphical theme.</li>
<li><a href="http://msdn.microsoft.com/en-us/library/aa511331.aspx">Top Guidelines Violations </a> serves as an example of what not to do in your UI design.</li>
<li><a href="http://msdn.microsoft.com/en-us/library/aa511335.aspx">How to Design a Great User Experience</a> offers 19 pieces of advice. I&#8217;m not certain that Microsoft is the best source for advice on creating <em>great</em> UIs, but they have been successful, and most of these points are fairly self-evident.</li>
</ul>
<h3>Mac OS X</h3>
<ul>
<li><a href="http://developer.apple.com/mac/library/DOCUMENTATION/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html">The Apple Human Interface Guidelines</a> are the grandfather of all UI guidelines and pretty much a one-stop-shop for information of best practices in Mac OS UI development.</li>
<li><a href="http://developer.apple.com/mac/library/DOCUMENTATION/UserExperience/Conceptual/AppleHIGuidelines/XHIGPartIII/XHIGPartIII.html#//apple_ref/doc/uid/TP40002723-TPXREF101">The Aqua Interface</a> deals specifically with the controls and widgets available to UI developers on the Mac.</li>
<li><a href="http://developer.apple.com/mac/library/DOCUMENTATION/UserExperience/Conceptual/AppleHIGuidelines/XHIGMOSXEnvironment/XHIGMOSXEnvironment.html#//apple_ref/doc/uid/TP40002721-TPXREF101">The Mac OS X Environment</a> provides a run-down on the Dock, Finder, Desktop, and more Mac-specific OS-level features that may be unfamiliar to Windows-only developers or designers.</li>
<li><a href="http://developer.apple.com/mac/library/DOCUMENTATION/UserExperience/Conceptual/AppleHIGuidelines/XHIGDesignProcess/XHIGDesignProcess.html#//apple_ref/doc/uid/TP40002718-TPXREF101">The Design Process</a> is a good, quick read with some good, though often obvious, advice.</li>
</ul>
<h3>Linux/Other</h3>
<ul>
<li><a href="http://library.gnome.org/devel/hig-book/stable/">The GNOME Human Interface Guidelines</a> are similar in layout and organization to MS and Apple&#8217;s guides, but cover the GNOME desktop environment.</li>
<li><a href="http://developer.kde.org/documentation/standards/kde/style/basics/index.html">The KDE User Interface Guidelines</a> provide the same for the KDE environment.</li>
</ul>
<p>This is not intended to be an exhaustive list of UI reference materials; rather, it is a list of official reference materials provided by platform providers. If you know of other useful platform-specific UI guideline documents, please post them in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://getmockery.com/blog/archives/72/feed</wfw:commentRss>
		<slash:comments>141</slash:comments>
		</item>
	</channel>
</rss>

