<?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: App is Crap (why Apple is bad for your health)</title>
	<atom:link href="http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/</link>
	<description>Entrepreneur turned VC</description>
	<lastBuildDate>Mon, 14 Nov 2011 23:37:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Goletas en Ibiza</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-22527</link>
		<dc:creator>Goletas en Ibiza</dc:creator>
		<pubDate>Wed, 26 Jan 2011 02:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-22527</guid>
		<description>The problem with &quot;mobile web&quot; is that it&#039;s currently not good enough. It&#039;s mostly read-only, with some keyboard data entry.&lt;br&gt;&lt;br&gt;The sensor part of mobile phones will be very important: location, compass, video-camera, audio microphone, photo (barcode scanners), other devices like heart-rate monitors, credit-card readers, chemical sensors, temperature, rfid, etc. The mobile phone will be your mobile data entry device, digitizing the outside world.&lt;br&gt;&lt;br&gt;For the &quot;mobile web&quot; to succeed we need good javascript access to all the sensors on a mobile phone. Some progress is being made in this area (location eg), but a lot more is needed.</description>
		<content:encoded><![CDATA[<p>The problem with &#8220;mobile web&#8221; is that it&#39;s currently not good enough. It&#39;s mostly read-only, with some keyboard data entry.</p>
<p>The sensor part of mobile phones will be very important: location, compass, video-camera, audio microphone, photo (barcode scanners), other devices like heart-rate monitors, credit-card readers, chemical sensors, temperature, rfid, etc. The mobile phone will be your mobile data entry device, digitizing the outside world.</p>
<p>For the &#8220;mobile web&#8221; to succeed we need good javascript access to all the sensors on a mobile phone. Some progress is being made in this area (location eg), but a lot more is needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hoteles</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-22204</link>
		<dc:creator>Hoteles</dc:creator>
		<pubDate>Tue, 18 Jan 2011 20:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-22204</guid>
		<description>With the exception of A, all of things you mention should concern a &quot;regular&quot; website as well and will more and more as time goes by. For example -- a mapping website should be able to know where I am regardless of whether I am accessing it via a phone. And I would hope that hardware vendors and browser vendors will collaborate to make this happen. Some devices will not have some capabilities (e.g. motion) but that should be the exception rather than the rule in the future.</description>
		<content:encoded><![CDATA[<p>With the exception of A, all of things you mention should concern a &#8220;regular&#8221; website as well and will more and more as time goes by. For example &#8212; a mapping website should be able to know where I am regardless of whether I am accessing it via a phone. And I would hope that hardware vendors and browser vendors will collaborate to make this happen. Some devices will not have some capabilities (e.g. motion) but that should be the exception rather than the rule in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julius</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-4301</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Thu, 18 Mar 2010 03:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-4301</guid>
		<description>This was an excellent article. Thanks.</description>
		<content:encoded><![CDATA[<p>This was an excellent article. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julius</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-11229</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Thu, 18 Mar 2010 03:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-11229</guid>
		<description>This was an excellent article. Thanks.</description>
		<content:encoded><![CDATA[<p>This was an excellent article. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julius</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-4297</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Wed, 17 Mar 2010 22:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-4297</guid>
		<description>This was an excellent article. Thanks.</description>
		<content:encoded><![CDATA[<p>This was an excellent article. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McGuire&#8217;s Law &#187; Blog Archive &#187; Observations: Applications - March 10, 2010</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-4292</link>
		<dc:creator>McGuire&#8217;s Law &#187; Blog Archive &#187; Observations: Applications - March 10, 2010</dc:creator>
		<pubDate>Wed, 10 Mar 2010 21:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-4292</guid>
		<description>[...] App is Crap (why Apple is bad for your health) [...]</description>
		<content:encoded><![CDATA[<p>[...] App is Crap (why Apple is bad for your health) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Giant Consulting: High Tech Marketing Consultant</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-4291</link>
		<dc:creator>Red Giant Consulting: High Tech Marketing Consultant</dc:creator>
		<pubDate>Wed, 10 Mar 2010 19:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-4291</guid>
		<description>[...] know I’m not a big fan on just jumping on the app bandwagon, but Mark Suster said it best, “App is Crap…Absolute Power Corrupts Absolutely.” I’m with you Mark, mobile web is going to be the new king and Apple’s power play is going [...]</description>
		<content:encoded><![CDATA[<p>[...] know I’m not a big fan on just jumping on the app bandwagon, but Mark Suster said it best, “App is Crap…Absolute Power Corrupts Absolutely.” I’m with you Mark, mobile web is going to be the new king and Apple’s power play is going [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Hall</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-11230</link>
		<dc:creator>Jamie Hall</dc:creator>
		<pubDate>Sat, 06 Mar 2010 22:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-11230</guid>
		<description>Couldn&#039;t agree more, and this has been our strategy building MocoSpace, our mobile social network with over 10 million members, the vast majority of which use us on the mobile Web (and from the US). So it&#039;s definitely possible to build a viable, successful product on the mobile Web, even today.</description>
		<content:encoded><![CDATA[<p>Couldn&#39;t agree more, and this has been our strategy building MocoSpace, our mobile social network with over 10 million members, the vast majority of which use us on the mobile Web (and from the US). So it&#39;s definitely possible to build a viable, successful product on the mobile Web, even today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Hall</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-4290</link>
		<dc:creator>Jamie Hall</dc:creator>
		<pubDate>Sat, 06 Mar 2010 16:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-4290</guid>
		<description>Couldn&#039;t agree more, and this has been our strategy building MocoSpace, our mobile social network with over 10 million members, the vast majority of which use us on the mobile Web (and from the US). So it&#039;s definitely possible to build a viable, successful product on the mobile Web, even today.</description>
		<content:encoded><![CDATA[<p>Couldn&#39;t agree more, and this has been our strategy building MocoSpace, our mobile social network with over 10 million members, the vast majority of which use us on the mobile Web (and from the US). So it&#39;s definitely possible to build a viable, successful product on the mobile Web, even today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Entrepreneurship, Reminders and Legal Aid - The Advisor</title>
		<link>http://www.bothsidesofthetable.com/2010/02/17/app-is-crap-why-apple-is-bad-for-your-health/comment-page-5/#comment-4289</link>
		<dc:creator>Entrepreneurship, Reminders and Legal Aid - The Advisor</dc:creator>
		<pubDate>Fri, 05 Mar 2010 22:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=1947#comment-4289</guid>
		<description>[...] App is Crap (why Apple is bad for your health) [...]</description>
		<content:encoded><![CDATA[<p>[...] App is Crap (why Apple is bad for your health) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

