<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Android&#8217;s Impact on eBooks, Reading</title>
	<atom:link href="http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/feed/" rel="self" type="application/rss+xml" />
	<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/</link>
	<description>Kindle Review, Kindle Fire Review, New Kindle Review, Kindle 4 Review</description>
	<lastBuildDate>Mon, 13 Feb 2012 15:22:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Android’s Impact on eBooks, Reading « Kindle Review – Kindle 2 Review, Books » andrewsavikas.com</title>
		<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/#comment-22916</link>
		<dc:creator><![CDATA[Android’s Impact on eBooks, Reading « Kindle Review – Kindle 2 Review, Books » andrewsavikas.com]]></dc:creator>
		<pubDate>Fri, 03 Sep 2010 00:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=7157#comment-22916</guid>
		<description><![CDATA[[...] The first reason is that Mobile Devices and Mobile Internet Usage are exploding and are going to dwarf PCs (in some ways,&#160;they&#160;already have).  via ireaderreview.com [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The first reason is that Mobile Devices and Mobile Internet Usage are exploding and are going to dwarf PCs (in some ways,&nbsp;they&nbsp;already have).  via ireaderreview.com [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rumored 2010 Google Phone, eReader for Android &#171; Kindle Review &#8211; Kindle 2 Review, Books</title>
		<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/#comment-7260</link>
		<dc:creator><![CDATA[Rumored 2010 Google Phone, eReader for Android &#171; Kindle Review &#8211; Kindle 2 Review, Books]]></dc:creator>
		<pubDate>Wed, 18 Nov 2009 10:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=7157#comment-7260</guid>
		<description><![CDATA[[...] Rumored 2010 Google Phone, eReader for&#160;Android  Posted on November 18, 2009 by switch11   There have been some big developments related to Android since my post about the impact Android might have on Reading. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Rumored 2010 Google Phone, eReader for&nbsp;Android  Posted on November 18, 2009 by switch11   There have been some big developments related to Android since my post about the impact Android might have on Reading. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Lohrbeer</title>
		<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/#comment-7154</link>
		<dc:creator><![CDATA[Trevor Lohrbeer]]></dc:creator>
		<pubDate>Fri, 13 Nov 2009 20:56:40 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=7157#comment-7154</guid>
		<description><![CDATA[Nice article. The only comment I would make would be the 30% cut to Google for Android Paid Apps doesn&#039;t necessarily mean Apps will have to use browser-based buying.

Ideally the book reader allows browsing from within the reader itself, which could alleviate the need to go through the Apps store to get a book. It would also improve the buying experience, since content like books would not get mixed up with applications as it currently does today.

The only caveat here would be if Google&#039;s terms and conditions stipulate that they get a percentage of any sale that gets made through the app, even if it doesn&#039;t rely on the Apps Store infrastructure. However, even if that does currently apply, I would expect fierce resistance to this as an ongoing practice. It&#039;s one thing to charge for access to the distribution channel, it&#039;s another thing to charge for any downstream income after the software has been installed.]]></description>
		<content:encoded><![CDATA[<p>Nice article. The only comment I would make would be the 30% cut to Google for Android Paid Apps doesn&#8217;t necessarily mean Apps will have to use browser-based buying.</p>
<p>Ideally the book reader allows browsing from within the reader itself, which could alleviate the need to go through the Apps store to get a book. It would also improve the buying experience, since content like books would not get mixed up with applications as it currently does today.</p>
<p>The only caveat here would be if Google&#8217;s terms and conditions stipulate that they get a percentage of any sale that gets made through the app, even if it doesn&#8217;t rely on the Apps Store infrastructure. However, even if that does currently apply, I would expect fierce resistance to this as an ongoing practice. It&#8217;s one thing to charge for access to the distribution channel, it&#8217;s another thing to charge for any downstream income after the software has been installed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Follow the Reader Fridays: Now Featuring Hot Links + Overheard On Twitter &#171; Follow The Reader</title>
		<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/#comment-6827</link>
		<dc:creator><![CDATA[Follow the Reader Fridays: Now Featuring Hot Links + Overheard On Twitter &#171; Follow The Reader]]></dc:creator>
		<pubDate>Fri, 30 Oct 2009 18:04:33 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=7157#comment-6827</guid>
		<description><![CDATA[[...] Android&#8217;s (the wireless phone &#8211; not the robot from the future)  impact on ereading [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Android&#8217;s (the wireless phone &#8211; not the robot from the future)  impact on ereading [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Планета е-книг &#187; Blog Archive &#187; Миллион названий е-книг категории Public domain - серьёзный аргумент в пользу принятия Android в качестве основной ОС </title>
		<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/#comment-6794</link>
		<dc:creator><![CDATA[Планета е-книг &#187; Blog Archive &#187; Миллион названий е-книг категории Public domain - серьёзный аргумент в пользу принятия Android в качестве основной ОС ]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 21:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=7157#comment-6794</guid>
		<description><![CDATA[[...] __________________ Еще один материал об андроид-угрозе (Android’s Impact on eBooks, Reading)  - теперь уже угрозу представляют приспособленные для [...]]]></description>
		<content:encoded><![CDATA[<p>[...] __________________ Еще один материал об андроид-угрозе (Android’s Impact on eBooks, Reading)  &#8211; теперь уже угрозу представляют приспособленные для [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chinese language to dominate Internet five years from now, says Google CEO&#8212;and a Google OS netbook is coming next years &#124; TeleRead: Bring the E-Books Home</title>
		<link>http://ireaderreview.com/2009/10/27/androids-impact-on-ereading/#comment-6788</link>
		<dc:creator><![CDATA[Chinese language to dominate Internet five years from now, says Google CEO&#8212;and a Google OS netbook is coming next years &#124; TeleRead: Bring the E-Books Home]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 13:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=7157#comment-6788</guid>
		<description><![CDATA[[...] you’d rather read about Android and that OS’s impact on e-books, check out a Kindle Review post and an earlier TeleRead [...]]]></description>
		<content:encoded><![CDATA[<p>[...] you’d rather read about Android and that OS’s impact on e-books, check out a Kindle Review post and an earlier TeleRead [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

