<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: What not to do in mobile web design!</title>
	<atom:link href="http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/</link>
	<description></description>
	<lastBuildDate>Wed, 25 Aug 2010 10:01:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/comment-page-1/#comment-831</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 30 Jun 2009 17:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=288#comment-831</guid>
		<description>Hey Martin,

you do have a point. But that link is so small. All buttons are big and chunky, and the link to the full size website is so small.

Moreover, you need 2 clicks in order to get to the full version site.

I think the app should work exactly the opposite way. Provide full site users expect to see, and provide them with means to switch to the mobile version.

The same issue appears in the sites that use Mobify to create mobile versions. Mobify provides a link to the full version of each site, but that link is also located in the footer of the site, and almost nobody will get down there.</description>
		<content:encoded><![CDATA[Hey Martin,<br />
<br />
you do have a point. But that link is so small. All buttons are big and chunky, and the link to the full size website is so small.<br />
<br />
Moreover, you need 2 clicks in order to get to the full version site.<br />
<br />
I think the app should work exactly the opposite way. Provide full site users expect to see, and provide them with means to switch to the mobile version.<br />
<br />
The same issue appears in the sites that use Mobify to create mobile versions. Mobify provides a link to the full version of each site, but that link is also located in the footer of the site, and almost nobody will get down there.]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/comment-page-1/#comment-829</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Mon, 29 Jun 2009 18:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=288#comment-829</guid>
		<description>on Livescore iPhone app click the last (4th) icon, it takes you to &quot;Settings&quot; page. then click on the link &quot;LiveScore.com&quot;, it takes you to the full version of the website if that was your intention.
I personally prefer the iPhone version though, it&#039;s designed for the compact screen and I have no issues with performance.</description>
		<content:encoded><![CDATA[on Livescore iPhone app click the last (4th) icon, it takes you to &#8220;Settings&#8221; page. then click on the link &#8220;LiveScore.com&#8221;, it takes you to the full version of the website if that was your intention.<br />
I personally prefer the iPhone version though, it&#8217;s designed for the compact screen and I have no issues with performance.]]></content:encoded>
	</item>
	<item>
		<title>By: What not to do in mobile web design (#2)</title>
		<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/comment-page-1/#comment-820</link>
		<dc:creator>What not to do in mobile web design (#2)</dc:creator>
		<pubDate>Mon, 15 Jun 2009 08:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=288#comment-820</guid>
		<description>[...] What not to do in mobile web design (1st post of the series) [...]</description>
		<content:encoded><![CDATA[[...] What not to do in mobile web design (1st post of the series) [...]]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/comment-page-1/#comment-815</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 11 Jun 2009 06:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=288#comment-815</guid>
		<description>Hey Neil, thank you for the thumbs up.</description>
		<content:encoded><![CDATA[Hey Neil, thank you for the thumbs up.]]></content:encoded>
	</item>
	<item>
		<title>By: neil</title>
		<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/comment-page-1/#comment-814</link>
		<dc:creator>neil</dc:creator>
		<pubDate>Wed, 10 Jun 2009 08:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=288#comment-814</guid>
		<description>I like this tutorial and the way you explain about mobile web design. That&#039;s helpful if you think about some new concepts in this direction as well. Keep up the good work.</description>
		<content:encoded><![CDATA[I like this tutorial and the way you explain about mobile web design. That&#8217;s helpful if you think about some new concepts in this direction as well. Keep up the good work.]]></content:encoded>
	</item>
	<item>
		<title>By: What not to do in form design</title>
		<link>http://www.webia.info/articles/usability/what-not-to-do-in-mobile-web-design/comment-page-1/#comment-741</link>
		<dc:creator>What not to do in form design</dc:creator>
		<pubDate>Fri, 17 Apr 2009 20:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.webia.info/?p=288#comment-741</guid>
		<description>[...] posted a few days ago an article regarding issues that can arise during mobile web design, and I am now posting an addition to that, regarding some issues that can appear on web form [...]</description>
		<content:encoded><![CDATA[[...] posted a few days ago an article regarding issues that can arise during mobile web design, and I am now posting an addition to that, regarding some issues that can appear on web form [...]]]></content:encoded>
	</item>
</channel>
</rss>
