<?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 Smartphones Should Libraries Support?</title>
	<atom:link href="http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=what-smartphones-should-libraries-support</link>
	<description>Stephen Abram&#039;s Posts About Library Land</description>
	<lastBuildDate>Fri, 10 Feb 2012 10:58:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2264</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2264</guid>
		<description>I agree with doing a survey but asking just people you meet in the library isn&#039;t sufficient.  My own research shows that virtual users have quite a different profile than on-site users.  You can determine who is using your site by tracking browser types, etc. but that&#039;s only useful if you&#039;ve promoted your site as mobile friendly to your key target audiences.

I agree that HTML5 will be wonderful. It would be nice if we could always design for the future and ignore the present installed base and just expect people to upgrade.  I still get pushback about killing IE6!

SA</description>
		<content:encoded><![CDATA[<p>I agree with doing a survey but asking just people you meet in the library isn&#8217;t sufficient.  My own research shows that virtual users have quite a different profile than on-site users.  You can determine who is using your site by tracking browser types, etc. but that&#8217;s only useful if you&#8217;ve promoted your site as mobile friendly to your key target audiences.</p>
<p>I agree that HTML5 will be wonderful. It would be nice if we could always design for the future and ignore the present installed base and just expect people to upgrade.  I still get pushback about killing IE6!</p>
<p>SA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Tay</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2263</link>
		<dc:creator>Aaron Tay</dc:creator>
		<pubDate>Wed, 17 Feb 2010 15:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2263</guid>
		<description>Supporting Iphone and android seems to be a safe bet. Not sure about BBs. But instead of guessing why not just do a quick survey, or just have a quick count everyday by looking at the people approaching you at a desk?

I make a game of it, taking noticing  the number of times, patrons whip out a phone to show me some call no. 

So far, Iphone is leading</description>
		<content:encoded><![CDATA[<p>Supporting Iphone and android seems to be a safe bet. Not sure about BBs. But instead of guessing why not just do a quick survey, or just have a quick count everyday by looking at the people approaching you at a desk?</p>
<p>I make a game of it, taking noticing  the number of times, patrons whip out a phone to show me some call no. </p>
<p>So far, Iphone is leading</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Czerniak</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2262</link>
		<dc:creator>Brad Czerniak</dc:creator>
		<pubDate>Wed, 17 Feb 2010 14:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2262</guid>
		<description>&lt;a href=&quot;http://www.businessweek.com/news/2010-02-16/rim-to-debut-new-blackberry-web-browser-to-compete-with-iphone.html&quot; rel=&quot;nofollow&quot;&gt;RIM Unveils WebKit Internet Browser to Compete with iPhone&lt;/a&gt; - literally yesterday&#039;s news.

Blackberry users have been conditioned to believe surfing the web on a smartphone is an inconsistent and unpleasurable experience. iPhone OS and Android have creatively destroyed RIM&#039;s monopoly of the smartphone market, and it&#039;s hurting their bottom line. I&#039;m surprised they hadn&#039;t released a better browser sooner (though it isn&#039;t even out yet).

Internet Explorer 6 was and is still with us (now in the sub-10% range) after 8 grueling years. With mobile browsers, hit percentages are already fairly low, and turnover lies somewhere around a 2-year contract term. It would be a painful waste to develop proprietary apps and sites when all major smartphone platforms will soon be using the same browser engine.

Since they are full-featured browsers, a mobile presence must either be additive and optional, or express the full feature set of a site. Otherwise, users would probably be more satisfied with the non-mobile version, which is both familiar in layout and has all the expected features and content.

Platform apps should only be used when features from device APIs not expressed in the browser are needed. Creating three or more platform apps in three different languages/environments is likely not worth the marketing effort, since one web app would usually suffice. The common contract player in the Enterprise will soon be on board with this.</description>
		<content:encoded><![CDATA[<p><a href="http://www.businessweek.com/news/2010-02-16/rim-to-debut-new-blackberry-web-browser-to-compete-with-iphone.html" rel="nofollow">RIM Unveils WebKit Internet Browser to Compete with iPhone</a> &#8211; literally yesterday&#8217;s news.</p>
<p>Blackberry users have been conditioned to believe surfing the web on a smartphone is an inconsistent and unpleasurable experience. iPhone OS and Android have creatively destroyed RIM&#8217;s monopoly of the smartphone market, and it&#8217;s hurting their bottom line. I&#8217;m surprised they hadn&#8217;t released a better browser sooner (though it isn&#8217;t even out yet).</p>
<p>Internet Explorer 6 was and is still with us (now in the sub-10% range) after 8 grueling years. With mobile browsers, hit percentages are already fairly low, and turnover lies somewhere around a 2-year contract term. It would be a painful waste to develop proprietary apps and sites when all major smartphone platforms will soon be using the same browser engine.</p>
<p>Since they are full-featured browsers, a mobile presence must either be additive and optional, or express the full feature set of a site. Otherwise, users would probably be more satisfied with the non-mobile version, which is both familiar in layout and has all the expected features and content.</p>
<p>Platform apps should only be used when features from device APIs not expressed in the browser are needed. Creating three or more platform apps in three different languages/environments is likely not worth the marketing effort, since one web app would usually suffice. The common contract player in the Enterprise will soon be on board with this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Libraries and Smartphones&#8230;02.17.10 &#171; The Proverbial Lone Wolf Librarian&#39;s Weblog</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2259</link>
		<dc:creator>Libraries and Smartphones&#8230;02.17.10 &#171; The Proverbial Lone Wolf Librarian&#39;s Weblog</dc:creator>
		<pubDate>Wed, 17 Feb 2010 04:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2259</guid>
		<description>[...] Excerpted from Stephen&#8217;s Lighthouse post What Smartphones Should Libraries Support?: [...]</description>
		<content:encoded><![CDATA[<p>[...] Excerpted from Stephen&#8217;s Lighthouse post What Smartphones Should Libraries Support?: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2256</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 17 Feb 2010 02:27:21 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2256</guid>
		<description>As for the BB vs iPhone debate, it&#039;s truly one of the market you are targeting.  If you&#039;re listening to special librariansn and their inranets, then BB is more common. iPhones seem to be more popular in PLs and education.</description>
		<content:encoded><![CDATA[<p>As for the BB vs iPhone debate, it&#8217;s truly one of the market you are targeting.  If you&#8217;re listening to special librariansn and their inranets, then BB is more common. iPhones seem to be more popular in PLs and education.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2255</link>
		<dc:creator>Anne</dc:creator>
		<pubDate>Wed, 17 Feb 2010 01:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2255</guid>
		<description>Brad, just to play devil&#039;s advocate, maybe there are more iPhone users hitting sites because the sites work better on iPhones? I know that my Blackberry browser does not have a great track record for working with a lot of websites, especially library websites. Because the browser isn&#039;t great, I hardly even try to go to a lot of sites. Perhaps others do the same?</description>
		<content:encoded><![CDATA[<p>Brad, just to play devil&#8217;s advocate, maybe there are more iPhone users hitting sites because the sites work better on iPhones? I know that my Blackberry browser does not have a great track record for working with a lot of websites, especially library websites. Because the browser isn&#8217;t great, I hardly even try to go to a lot of sites. Perhaps others do the same?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Czerniak</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2254</link>
		<dc:creator>Brad Czerniak</dc:creator>
		<pubDate>Wed, 17 Feb 2010 00:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2254</guid>
		<description>Firstly - why platform apps? A well-designed web app with a root-level icon works just as well and is multi-platform out of the box.

Secondly - market share does not accurately reflect either web or app demand. Even though there are more blackberries out there, I&#039;ve consistently heard webmasters say their analytics point to more iPhone/iPod Touch users hitting their sites than any other platform.</description>
		<content:encoded><![CDATA[<p>Firstly &#8211; why platform apps? A well-designed web app with a root-level icon works just as well and is multi-platform out of the box.</p>
<p>Secondly &#8211; market share does not accurately reflect either web or app demand. Even though there are more blackberries out there, I&#8217;ve consistently heard webmasters say their analytics point to more iPhone/iPod Touch users hitting their sites than any other platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave H</title>
		<link>http://stephenslighthouse.com/2010/02/16/what-smartphones-should-libraries-support/comment-page-1/#comment-2252</link>
		<dc:creator>Dave H</dc:creator>
		<pubDate>Wed, 17 Feb 2010 00:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://stephenslighthouse.com/?p=3149#comment-2252</guid>
		<description>Why even make an app anymore if so many browsers on mobile devices are capable of HTML5? iPhones, Android phones, Palm Web OS based phones, and in the near future Blackberries - all capable of HTML5 rendering.  For a library with limited resources, wouldn&#039;t it make sense to create mobile sites that take advantage of HTML5?</description>
		<content:encoded><![CDATA[<p>Why even make an app anymore if so many browsers on mobile devices are capable of HTML5? iPhones, Android phones, Palm Web OS based phones, and in the near future Blackberries &#8211; all capable of HTML5 rendering.  For a library with limited resources, wouldn&#8217;t it make sense to create mobile sites that take advantage of HTML5?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

