<?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>Simon Whatley &#187; reference</title>
	<atom:link href="http://www.simonwhatley.co.uk/tag/reference/feed" rel="self" type="application/rss+xml" />
	<link>http://www.simonwhatley.co.uk</link>
	<description>The opposite of every great idea is another great idea</description>
	<lastBuildDate>Wed, 02 Nov 2011 09:28:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>User Interface Guidelines for Mobile and Tablet Devices</title>
		<link>http://www.simonwhatley.co.uk/user-interface-guidelines-for-mobile-and-tablet-devices</link>
		<comments>http://www.simonwhatley.co.uk/user-interface-guidelines-for-mobile-and-tablet-devices#comments</comments>
		<pubDate>Mon, 20 Dec 2010 16:49:17 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[bada]]></category>
		<category><![CDATA[Blackberry]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[ios]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[motorola]]></category>
		<category><![CDATA[Nokia]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[samsung]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[Symbian]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[userinterface]]></category>
		<category><![CDATA[WebOS]]></category>
		<category><![CDATA[windowsphone]]></category>

		<guid isPermaLink="false">http://www.simonwhatley.co.uk/?p=3796</guid>
		<description><![CDATA[The official user interface (UI) and user experience (UX) guidelines from the manufacturers, links to which you can find below, are a source of inspiration for mobile web and application design. Here, you will find guidelines, samples, tips, and descriptions of common mistakes. Many of the guidelines focus on native application development, but we can apply most parts of them to mobile web design.]]></description>
			<content:encoded><![CDATA[<p>The official user interface (<abbr title="User Interface">UI</abbr>) and user experience (<abbr title="User Experience">UX</abbr>) guidelines from the manufacturers, links to which you can find below, are a source of inspiration for mobile web and application design. Here, you will find guidelines, samples, tips, and descriptions of common mistakes. Many of the guidelines focus on native application development, but we can apply most parts of them to mobile web design.</p>
<p>To provide the best possible experience on each platform, don&#8217;t deliver an iPhone experience to a BlackBerry or Android user. Every platform has its own <abbr title="User Interface">UI</abbr> and usability guidelines that every user is expecting from your application. For example, the popular Twitter application TweetDeck has a different user interface and therefore user experience between its iPhone and Android versions, albeit the TweetDeck team aims to provide a similar user experience on both devices. The same can be said between mobile an tablet devices with <a href="http://reederapp.com/" title="Reeder App" target="_blank" rel="nofollow">Reeder</a> and <a href="http://www.alphonsolabs.com/" title="Pulse from AlphonsoLabs" target="_blank" rel="nofollow">Pulse</a> prime examples on iOS devices.</p>
<h2>Apple (iOS)</h2>
<ul>
<li><a href="http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html" title="iPhone Human Interface Guidelines" target="_blank" rel="nofollow">iOS Human Interface Guidelines</a> or the <a href="http://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/MobileHIG.pdf" title="iPhone Human Interface Guidelines PDF Version" target="_blank" rel="nofollow">PDF version</a> (PDF 12.9MB, pp. 150)</li>
</ul>
<h2>BlackBerry</h2>
<ul>
<li><a href="http://docs.blackberry.com/en/developers/deliverables/17965/index.jsp?name=UI+Guidelines+-+BlackBerry+Smartphones6.0&amp;language=English&amp;userType=21&amp;category=Java+Development+Guidelines&amp;subCategory=" title="UI Guidelines for BlackBerry 6.0 Smartphones" target="_blank" rel="nofollow">UI Guidelines for BlackBerry 6.0 Smartphones</a> or the <a href="http://docs.blackberry.com/en/developers/deliverables/17964/BlackBerry_Smartphones-UI_Guidelines-T893501-980426-0721013746-001-6.0-US.pdf" title="UI Guidelines for BlackBerry 6.0 Smartphones PDF version" target="_blank" rel="nofollow">PDF version</a> (PDF 9.2MB, pp. 109)</li>
<li><a href="http://docs.blackberry.com/en/developers/deliverables/20196/index.jsp?name=UI+Guidelines+-+BlackBerry+Smartphones2.5&amp;language=English&amp;userType=21&amp;category=Java+Development+Guidelines&amp;subCategory=" title="UI Guidelines for BlackBerry 4.x, 5.x Smartphones" target="_blank" rel="nofollow">UI Guidelines for BlackBerry 4.x, 5.x Smartphones</a> or the <a href="http://docs.blackberry.com/en/developers/deliverables/20195/BlackBerry_Smartphones-UI_Guidelines-T1011811-1011811-0903100131-001-2.5-US.pdf" title="UI Guidelines for BlackBerry 4.x, 5.x Smartphones PDF Version" target="_blank" rel="nofollow">PDF version</a> (PDF 7.4MB, pp. 89)</li>
<li><a href="http://docs.blackberry.com/en/developers/deliverables/4305/BlackBerry_Browser-4.6.0-US.pdf" title="BlackBerry Browser Content Design Guidelines" target="_blank" rel="nofollow">BlackBerry Browser Content Design Guidelines</a> (PDF 356KB, pp. 29)</li>
</ul>
<h2>Google (Android)</h2>
<ul>
<li><a href="http://developer.android.com/guide/practices/ui_guidelines/index.html" title="Android User Interface Guidelines" target="_blank" rel="nofollow">Android User Interface Guidelines</a></li>
<li><a href="http://developer.motorola.com/docstools/library/Best_Practices_for_User_Interfaces/" title="Motorola's Best Practices for Android UI" target="_blank" rel="nofollow">Motorola&#8217;s Best Practices for Android UI</a></li>
</ul>
<h2>Microsoft (Windows Mobile, Windows Phone 7)</h2>
<ul>
<li><a href="http://msdn.microsoft.com/en-us/library/bb158602.aspx" title="UI Guidelines for Windows Mobile" target="_blank" rel="nofollow">UI Guidelines for Windows Mobile</a></li>
<li><a href="http://msdn.microsoft.com/en-us/library/cc872774.aspx" title="Windows Touch UI Guideline" target="_blank" rel="nofollow">Windows Touch UI Guideline</a></li>
<li><a href="http://www.google.co.uk/url?sa=t&#038;source=web&#038;cd=3&#038;sqi=2&#038;ved=0CC0QFjAC&#038;url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F7%2F7%2F3%2F77371bbd-6613-4c1a-acbf-08365c09d5fa%2Fui%2520design%2520and%2520interaction%2520guide%2520for%2520windows%2520phone%25207%2520v2.0.pdf&#038;ei=bIMPTY7WHIOqhAe3rpG3Dg&#038;usg=AFQjCNF76tSvSGaMqRhGRYVRBlm-r1tcjg&#038;sig2=JsJWTzAEW6cn1vhO9q1jfQ" title="UI Design &amp; Interaction Guide for Windows Phone 7 version 2.0" target="_blank" rel="nofollow">UI Design &amp; Interaction Guide for Windows Phone 7 version 2.0</a> (PDF 11.9MB, pp. 101)</li>
</ul>
<h2>Nokia (Symbian)</h2>
<ul>
<li><a href="http://library.forum.nokia.com/index.jsp?topic=/Design_and_User_Experience_Library/GUID-A8DF3EB8-E97C-4DA0-95F6-F464ECC995BC_cover.html" title="Nokia Design &amp; User Experience Library" target="_blank" rel="nofollow">Nokia Design &amp; User Experience Library</a></li>
<li><a href="http://www.forum.nokia.com/dp?uri=http%3A%2F%2Fsw.nokia.com%2Fid%2Fa80c6de9-d56c-472d-af19-7a3eca265f50%2FSymbian_3_UI_Style_Guide_v1_0_en.pdf" title="Symbian^3 UI Style Guidelines" target="_blank" rel="nofollow">Symbian^3 UI Style Guidelines</a>  (PDF 4.5MB, pp. 105)</li>
<li><a href="http://www.forum.nokia.com/Design/" title="Forum Nokia Design Portal" target="_blank" rel="nofollow">Forum Nokia Design Portal</a></li>
<li><a href="http://developer.symbian.org/wiki/User_Interface" title="Symbian UI Wiki" target="_blank" rel="nofollow">Symbian UI Wiki</a></li>
<li><a href="http://www.forum.nokia.com/info/sw.nokia.com/id/73e935fe-8b59-43b2-ab3e-1c5f763672db/Series_40_UI_Style_Guide.html" title="Nokia Series 40 UI Style Guide" target="_blank" rel="nofollow">Nokia Series 40 UI Style Guide</a></li>
<li><a href="http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html" title="Hildon UI Guidelines for Nokia Maemo" target="_blank" rel="nofollow">Hildon UI Guidelines for Nokia Maemo</a></li>
</ul>
<h2>Palm/Hewlett Packard (webOS)</h2>
<ul>
<li><a href="http://developer.palm.com/index.php?option=com_content&amp;view=article&amp;id=1836" title="webOS UI Guidelines" target="_blank" rel="nofollow">webOS UI Guidelines</a></li>
</ul>
<h2>Sony Ericsson</h2>
<ul>
<li><a href="http://developer.sonyericsson.com/cws/download/1/716/984/1262667210/DW-102212-UI_Rulebook.pdf" title="Sony Ericsson UI Rulebook" target="_blank" rel="nofollow">Sony Ericsson UI Rulebook</a></li>
</ul>
<h2>Others</h2>
<ul>
<li><a href="http://dpimg.ospos.net/contents/docs/resources_1004/com.osp.appuiguide.help/html/FramesetMain.html?menu=MC01010403&amp;mtb1=&amp;mtb2=" title="Bada Application UI Guide" target="_blank" rel="nofollow">Bada Application UI Guide</a></li>
<li><a href="http://meego.com/developers/ui-design-guidelines/handset" title="MeeGo UI Design Guidelines" target="_blank" rel="nofollow">MeeGo UI Design Guidelines</a></li>
</ul>
<p>If you know of any other examples of <abbr title="User Interface">UI</abbr> guidelines for mobile or tablet devices or have any general thoughts, please feel free to add them to the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simonwhatley.co.uk/user-interface-guidelines-for-mobile-and-tablet-devices/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>jQuery 1.2 API Reference</title>
		<link>http://www.simonwhatley.co.uk/jquery-12-api-reference</link>
		<comments>http://www.simonwhatley.co.uk/jquery-12-api-reference#comments</comments>
		<pubDate>Wed, 09 Apr 2008 10:55:25 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[AJAX]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[Framework]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[jquery]]></category>
		<category><![CDATA[lightweight applications]]></category>
		<category><![CDATA[reference]]></category>

		<guid isPermaLink="false">http://www.simonwhatley.co.uk/?p=419</guid>
		<description><![CDATA[Among the plethora of JavaScript libraries to have been released, few have been recognised to be as effective as jQuery. This lightweight library has been the subject of different discussions since it was launched in 2006. Basically, jQuery has the ability to flawlessly string together JavaScript together with HTML. Because of its effectiveness, there have different types of lightweight applications and plug-ins launched using jQuery. Ajax based websites that offers simple interface would virtually work together using jQuery's simple interface.]]></description>
			<content:encoded><![CDATA[<p>Among the plethora of JavaScript libraries to have been released, few have been recognised to be as effective as <a href="http://jquery.com/" title="jQuery" target="_blank" rel="nofollow">jQuery</a>. This lightweight library has been the subject of different discussions since it was launched in 2006. Basically, jQuery has the ability to flawlessly string together JavaScript together with <acronym title="HyperText Markup Language">HTML</acronym>. Because of its effectiveness, there have different types of lightweight applications and plug-ins launched using jQuery. Ajax based websites that offers simple interface would virtually work together using jQuery&#8217;s simple interface.</p>
<p>Download the <a href='http://www.simonwhatley.co.uk/blog/wp-content/uploads/2008/02/jquery12_api_reference.png' title='jQuery 1.2 API Reference'>jQuery 1.2 API Reference</a> (360KB).</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<p>More information can be found on the <a href="http://jquery.com/" title="jQuery" target="_blank" rel="nofollow">jQuery Website</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simonwhatley.co.uk/jquery-12-api-reference/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ActionScript 3 RIA Reference Guide</title>
		<link>http://www.simonwhatley.co.uk/actionscript-3-ria-reference-guide</link>
		<comments>http://www.simonwhatley.co.uk/actionscript-3-ria-reference-guide#comments</comments>
		<pubDate>Mon, 07 Apr 2008 08:46:21 +0000</pubDate>
		<dc:creator>Simon</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[ActionScript]]></category>
		<category><![CDATA[Adobe]]></category>
		<category><![CDATA[Adobe Flash Player]]></category>
		<category><![CDATA[Adobe Integrated Runtime]]></category>
		<category><![CDATA[AIR]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[Flash Player]]></category>
		<category><![CDATA[Flex]]></category>
		<category><![CDATA[Framework]]></category>
		<category><![CDATA[Internet application development]]></category>
		<category><![CDATA[PDF]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[Rich Internet Applications]]></category>
		<category><![CDATA[runtime]]></category>
		<category><![CDATA[the Flash Player]]></category>

		<guid isPermaLink="false">http://www.simonwhatley.co.uk/?p=484</guid>
		<description><![CDATA[The ActionScript reference for rich Internet application development provides an alphabetical reference for all native ActionScript APIs for the Adobe technology platform runtimes: Adobe Flash Player and Adobe AIRâ€”as well as the Adobe Flex framework APIs. Use this guide both as an API reference and a tool to learn about the ActionScript APIs available within the runtimes.]]></description>
			<content:encoded><![CDATA[<p>The ActionScript reference for rich Internet application development provides an alphabetical reference for all native ActionScript <acronym title="Application Programming Interface">API</acronym>s for the Adobe technology platform runtimes: Adobe Flash Player and Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym>â€”as well as the Adobe Flex framework <acronym title="Application Programming Interface">API</acronym>s. Use this guide both as an <acronym title="Application Programming Interface">API</acronym> reference and a tool to learn about the ActionScript <acronym title="Application Programming Interface">API</acronym>s available within the runtimes.</p>
<p>Download the <a href='http://www.simonwhatley.co.uk/blog/wp-content/uploads/2008/04/actionscript_ria_guide.pdf' title='ActionScript reference for RIA development'>ActionScript reference for RIA development</a> (PDF 1.3MB)</p>
<p>The Adobe technology platform contains two primary runtimes. Flash Player is browser-based, and Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym> is desktop-based. Because Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym> is built on top of Flash Player, the Flash Player <acronym title="Application Programming Interface">API</acronym>s are available within Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym>. Consequently, Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym> <acronym title="Application Programming Interface">API</acronym>s are not available within Flash Player. The Flex framework is built on top of the Flash Player <acronym title="Application Programming Interface">API</acronym>s, so it runs in both Flash Player and Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym>. However, a number of Flex <acronym title="Application Programming Interface">API</acronym>s take advantage of <acronym title="Adobe Integrated Runtime">AIR</acronym> <acronym title="Application Programming Interface">API</acronym>s, and thus work only within Adobe <acronym title="Adobe Integrated Runtime">AIR</acronym>.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-6475233631580417";
/* 468x60 Basic */
google_ad_slot = "7117418273";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<p>More information about this guide can be found on the <a href="http://www.adobe.com/devnet/actionscript/articles/atp_ria_guide.html" title="Adobe Developer Centre Website" target="_blank" rel="nofollow">Adobe Developer Centre Website</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simonwhatley.co.uk/actionscript-3-ria-reference-guide/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

