<?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: Mobile apps vs. Mobile web</title>
	<atom:link href="http://www.hiddenpeanuts.com/archives/2010/01/07/mobile-apps-vs-mobile-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hiddenpeanuts.com/archives/2010/01/07/mobile-apps-vs-mobile-web/</link>
	<description></description>
	<lastBuildDate>Wed, 21 Jul 2010 16:31:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Alice Sneary</title>
		<link>http://www.hiddenpeanuts.com/archives/2010/01/07/mobile-apps-vs-mobile-web/comment-page-1/#comment-134215</link>
		<dc:creator>Alice Sneary</dc:creator>
		<pubDate>Fri, 08 Jan 2010 19:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenpeanuts.com/?p=632#comment-134215</guid>
		<description>Thanks Chad. We&#039;ve been talking about these very issues with the WorldCat.org site and making it more mobile-ready. So your comments help reinforce what we&#039;ve also been thinking. That said, I do want to make sure your readers know--the WorldCat Mobile pilot IS available as an app for phones that support apps, but is ALSO available as a Web &quot;lite&quot; version for phones that do not support apps. (The www.worldcat.org/m page automatically sniffs what your phone accepts.) The Web &quot;lite&quot; version is not as robust as the full WorldCat.org site functionality, scaled for mobile use. BUT anyone with a Web-enabled phone should at least be able to try out the WorldCat Mobile pilot and send feedback--which is very much encouraged. (No one should be left out in the cold!) We&#039;re still very much in &quot;pilot&quot; stage and take feedback very seriously about the direction we need to go in for mobile.</description>
		<content:encoded><![CDATA[<p>Thanks Chad. We&#8217;ve been talking about these very issues with the WorldCat.org site and making it more mobile-ready. So your comments help reinforce what we&#8217;ve also been thinking. That said, I do want to make sure your readers know&#8211;the WorldCat Mobile pilot IS available as an app for phones that support apps, but is ALSO available as a Web &#8220;lite&#8221; version for phones that do not support apps. (The <a href="http://www.worldcat.org/m" rel="nofollow">http://www.worldcat.org/m</a> page automatically sniffs what your phone accepts.) The Web &#8220;lite&#8221; version is not as robust as the full WorldCat.org site functionality, scaled for mobile use. BUT anyone with a Web-enabled phone should at least be able to try out the WorldCat Mobile pilot and send feedback&#8211;which is very much encouraged. (No one should be left out in the cold!) We&#8217;re still very much in &#8220;pilot&#8221; stage and take feedback very seriously about the direction we need to go in for mobile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Payst</title>
		<link>http://www.hiddenpeanuts.com/archives/2010/01/07/mobile-apps-vs-mobile-web/comment-page-1/#comment-134193</link>
		<dc:creator>Brian Payst</dc:creator>
		<pubDate>Fri, 08 Jan 2010 03:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiddenpeanuts.com/?p=632#comment-134193</guid>
		<description>As you might guess, I couldn&#039;t agree more! Much simpler to use a mobile web interface to pick up a variety of devices and reformat for those as needed. It makes porting new content to mobile dead simple. For example, I took ITS&#039;s labs page, ran it through a little PHP to cut out just the content I wanted and had a mobile computer lab app in under 15 minutes. The native app route would have meant republishing the app through the various stores, getting users to update, etc. Mobile web apps are way more flexible and allow you to roll out new stuff by simply updating the page. Next time someone visits they get the new tools.</description>
		<content:encoded><![CDATA[<p>As you might guess, I couldn&#8217;t agree more! Much simpler to use a mobile web interface to pick up a variety of devices and reformat for those as needed. It makes porting new content to mobile dead simple. For example, I took ITS&#8217;s labs page, ran it through a little PHP to cut out just the content I wanted and had a mobile computer lab app in under 15 minutes. The native app route would have meant republishing the app through the various stores, getting users to update, etc. Mobile web apps are way more flexible and allow you to roll out new stuff by simply updating the page. Next time someone visits they get the new tools.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
