<?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>PixelMEDIA &#187; Users</title>
	<atom:link href="http://www.pixelmedia.com/blog/tag/users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pixelmedia.com/blog</link>
	<description>The official staff chatter blox</description>
	<lastBuildDate>Thu, 22 Dec 2011 15:55:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Information Architecture for Mobile</title>
		<link>http://www.pixelmedia.com/blog/information-architecture-for-mobile/</link>
		<comments>http://www.pixelmedia.com/blog/information-architecture-for-mobile/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 13:09:21 +0000</pubDate>
		<pxlAuthorId>1</pxlAuthorId>
		<dc:creator>PixelMEDIA</dc:creator>
				<category><![CDATA[Mobile design]]></category>
		<category><![CDATA[Information Architecture]]></category>
		<category><![CDATA[interaction design]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[Navigation]]></category>
		<category><![CDATA[Users]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=389</guid>
		<description><![CDATA[Mobile users tend to be focused on quickly finding answers to burning questions as opposed to simply &#8216;surfing&#8217; the Web as they do on a PC or laptop. Given the smaller resolution and disparate browser capabilities across mobile devices, designing &#8230; <a href="http://www.pixelmedia.com/blog/information-architecture-for-mobile/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><span>Mobile users tend to be focused on quickly finding answers to burning questions as opposed to simply &#8216;surfing&#8217; the Web as they do on a PC or laptop. Given the smaller resolution and disparate browser capabilities across mobile devices, designing the navigation becomes more difficult.</span></p>
<p class="MsoNormal"><span>Not everyone has an iPhone or Blackberry Storm. A lot of users have simple smart phones, requiring careful thought into how deep content lies within the Mobile Experience and how many clicks it takes to get to it.<span id="more-389"></span><br />
</span></p>
<p class="MsoNormal"><span>Information Architecture and Interaction Design for Mobile needs to take this into account and requires the structure to contain a number of &#8220;either/or&#8221; choices and tailoring the navigation (modified from the work of <a title="Click to view Christian Crumlish's website &gt;" href="http://www.christiancrumlish.com" target="_blank">Christian Crumlish</a></span><span>):</span></p>
<ul type="disc">
<li class="MsoNormal"><span>If at all possible, limit the number of categories to      five (5)</span></li>
<li class="MsoNormal"><span>To help users access links quickly, choose the top 10      per page to assign numerical access<br />
</span></li>
<li class="MsoNormal"><span>Minimize the number of levels of navigation: the deeper      the content is, the harder to drill in and out<br />
</span></li>
<li class="MsoNormal"><span>Reorder the site categories by priority to best suit      the needs of the Mobile audience. Speaking to users will help determine      the best approach for this.</span></li>
<li class="MsoNormal"><span>Make telephone numbers links:<br />
&lt;a href=”tel:+19995551234”&gt;+1 999 555-1234&lt;/a&gt;</span></li>
</ul>
<p class="MsoNormal"><span>Be prepared to spend time working through the navigation and interaction modeling for the Mobile Experience. In order to simplify the structure into an intuitive experience that breaks the content down into digestible chunks takes patience. Ironically, simplification is one of the more complicated processes, but the payoff at the end of the day is worth it. Just ask your happy users.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/information-architecture-for-mobile/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

