<?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>GWT Blog - GlobalWorldTech &#187; Mobile Web Architecture</title>
	<atom:link href="http://www.gwtindia.com/tag/mobile-web-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gwtindia.com</link>
	<description></description>
	<lastBuildDate>Sun, 29 Jan 2012 06:20:51 +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>Architecture for Mobile Web</title>
		<link>http://www.gwtindia.com/architecture-for-mobile-web/</link>
		<comments>http://www.gwtindia.com/architecture-for-mobile-web/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 08:08:06 +0000</pubDate>
		<dc:creator>Satinder</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Mobile Web]]></category>
		<category><![CDATA[Mobile Web Architecture]]></category>

		<guid isPermaLink="false">http://www.gwtindia.com/?p=570</guid>
		<description><![CDATA[Even at 3G speeds data retrieval on a mobile phone takes significantly longer than we are accustomed to on a desktop PC. It doesn’t take long for users to become frustrated with lengthy sequences of retrievals, and give up. So getting this right is extremely important. In the mobile context it is especially important to [...]]]></description>
			<content:encoded><![CDATA[<!-- Start Shareaholic LikeButtonSetTop Automatic --><!-- End Shareaholic LikeButtonSetTop Automatic --><p>Even at 3G speeds data retrieval on a mobile phone takes significantly longer than we are accustomed to on a desktop PC. It doesn’t take long for users to become frustrated with lengthy sequences of retrievals, and give up. So getting this right is extremely important. In the mobile context it is especially important to structure information as simply as possible. Placing the right information in the right place is an important part of providing a usable experience; getting it wrong means providing a poor experience.</p>
<p>On the other hand, a user presented with a clear goal and intelligent ways to reach it, may tolerate latency issues and the time taken to reach the goal. This is best done by setting user expectations. Every link should use clear labels to communicate to the user what to expect on the resulting page, thereby lowering the risk of click disappointment.</p>
<h3>Keep It Simple</h3>
<p>The best advice for creating a strong mobile information architecture is to keep it as simple as possible. The following two approaches work well when structuring your IA for mobile presentation:
<ul>
<li>Limit choices. Take the content that’s relevant to a mobile user and discard the rest. This results in a simple and focused IA that cuts down the risk of the user getting lost. This approach works well with small, focused sites.</li>
<li>Create a simple site drill-down architecture, nesting content into well-labeled categories. While this sounds straightforward, it’s necessary to plan carefully before taking this approach. A typical Web site has sub-pages &#8211; users follow a link to reach the sub-page. This is drilling down to find the information the user seeks on the Web site.</li>
</ul>
<h3>Drill-Down Recommendations</h3>
<p>Here are a few suggestions to keep in mind when considering a drill-down approach for your site:
<ul>
<li><strong>Limit categories as much possible:</strong> Users become increasingly disoriented as they go deeper into a site. With a Mobile Web site, their tolerance often stops at about five levels – the fewer levels the better You should adjust this number upwards when targeting more capable devices.</li>
<li><strong>Attempt to limit links to ten per page</strong> unless you know that the device can present more information well: You should code your links with accesskeys, so that the user can use the phone keypad to navigate links. We recommend a assigning up to ten accesskeys to any page (0–9) to ensure compatibility with older devices. You should adjust this number upwards when targeting more capable devices that can display this information better.</li>
<li>Provide at least one content item with each category page i.e. <strong>avoid empty links:</strong> Giving users at least one sample of the content within a category is a good way to make sure that users get to the right place. Consider placing a link to the featured content with a one or two sentence overview. The shorter, the better.</li>
<li><strong>Prioritize links by activity or popularity:</strong> This is often referred to as “deck placement.” Sorting links in order by frequency of access ensures that the most sought-after content appears first on the list. You improve a user’s chances of getting to the right destination. </li>
</ul>
<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.gwtindia.com%2Farchitecture-for-mobile-web%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.gwtindia.com%2Farchitecture-for-mobile-web%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
Reads:738<div class="shr-publisher-570"></div><!-- Start Shareaholic LikeButtonSetBottom Automatic --><div style="clear: both; min-height: 1px; height: 3px; width: 100%;"></div><div class='shareaholic-like-buttonset' style='float:none;height:60px;'><a class='shareaholic-fblike' data-shr_layout='box_count' data-shr_showfaces='false' data-shr_href='http%3A%2F%2Fwww.gwtindia.com%2Farchitecture-for-mobile-web%2F' data-shr_title='Architecture+for+Mobile+Web'></a><a class='shareaholic-googleplusone' data-shr_size='tall' data-shr_count='true' data-shr_href='http%3A%2F%2Fwww.gwtindia.com%2Farchitecture-for-mobile-web%2F' data-shr_title='Architecture+for+Mobile+Web'></a><a class='shareaholic-tweetbutton' data-shr_count='none' data-shr_href='http%3A%2F%2Fwww.gwtindia.com%2Farchitecture-for-mobile-web%2F' data-shr_title='Architecture+for+Mobile+Web'></a></div><div style="clear: both; min-height: 1px; height: 3px; width: 100%;"></div><!-- End Shareaholic LikeButtonSetBottom Automatic -->]]></content:encoded>
			<wfw:commentRss>http://www.gwtindia.com/architecture-for-mobile-web/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

