<?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:go='http://ns.gigaom.com/'
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: Qualcomm Breaks the Gigahertz Barrier on Smartphones</title>
	<atom:link href="http://gigaom.com/2009/11/12/qualcomm-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2009/11/12/qualcomm-2/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 06:01:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Vídeo del nuevo Qualcomm MSM 7&#215;30 - Moveo</title>
		<link>http://gigaom.com/2009/11/12/qualcomm-2/#comment-230255</link>
		<dc:creator><![CDATA[Vídeo del nuevo Qualcomm MSM 7&#215;30 - Moveo]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 12:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/?p=79448#comment-230255</guid>
		<description><![CDATA[&lt;p&gt;[...] Xataka Móvil, GigaOM, Slash Gear  [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] Xataka Móvil, GigaOM, Slash Gear  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McGuire&#8217;s Law &#187; Blog Archive &#187; Enabling Technology: December 23, 2009</title>
		<link>http://gigaom.com/2009/11/12/qualcomm-2/#comment-230254</link>
		<dc:creator><![CDATA[McGuire&#8217;s Law &#187; Blog Archive &#187; Enabling Technology: December 23, 2009]]></dc:creator>
		<pubDate>Thu, 24 Dec 2009 00:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/?p=79448#comment-230254</guid>
		<description><![CDATA[&lt;p&gt;[...] MSM7&#215;30 [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] MSM7&#215;30 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Mansilla</title>
		<link>http://gigaom.com/2009/11/12/qualcomm-2/#comment-230253</link>
		<dc:creator><![CDATA[Neil Mansilla]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 17:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/?p=79448#comment-230253</guid>
		<description><![CDATA[At PayPal Innovate conference in San Francisco a week or so ago, I attended the forum on the future of mobile app stores, with panelists from Qualcomm, Motorola, and the CEO of GetJar, Ilja Laurs. After the panel session, I asked him what he thought about the future of mobile browser based applications.  He discussed the lack of support of rich native functionality such as location awareness and other rich features, that now are only accessible through the respective proprietary APIs (i.e. Xcode, BlackBerry JDE, etc.).  But we also touched on the lack of processing power on mobile phones to drive apps on the mobile browser, the same way that we drive browser-based apps on the desktop.

Hearing news like this (Qualcomm breaking GHz barrier for smart phones) is encouraging.  Desktop browser based apps are becoming main stream in our every day work flow, and pushing beyond our previous expectations of what applications can do inside the browser.  We use mapping and office applications in our browser and receive a fairly consistent experience across different platforms.. and that is where we&#039;ll be heading in the future with mobile application development, too.  It&#039;s only a matter of time that we have Opera, Firefox, Safari and IE working on our smart phones, with additional plug-ins to access our devices&#039; rich native functions, rather than completely different development platforms for each device.]]></description>
		<content:encoded><![CDATA[<p>At PayPal Innovate conference in San Francisco a week or so ago, I attended the forum on the future of mobile app stores, with panelists from Qualcomm, Motorola, and the CEO of GetJar, Ilja Laurs. After the panel session, I asked him what he thought about the future of mobile browser based applications.  He discussed the lack of support of rich native functionality such as location awareness and other rich features, that now are only accessible through the respective proprietary APIs (i.e. Xcode, BlackBerry JDE, etc.).  But we also touched on the lack of processing power on mobile phones to drive apps on the mobile browser, the same way that we drive browser-based apps on the desktop.</p>
<p>Hearing news like this (Qualcomm breaking GHz barrier for smart phones) is encouraging.  Desktop browser based apps are becoming main stream in our every day work flow, and pushing beyond our previous expectations of what applications can do inside the browser.  We use mapping and office applications in our browser and receive a fairly consistent experience across different platforms.. and that is where we&#8217;ll be heading in the future with mobile application development, too.  It&#8217;s only a matter of time that we have Opera, Firefox, Safari and IE working on our smart phones, with additional plug-ins to access our devices&#8217; rich native functions, rather than completely different development platforms for each device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Friends of Dave (friendsofdave) 's status on Thursday, 12-Nov-09 16:47:46 UTC - Identi.ca</title>
		<link>http://gigaom.com/2009/11/12/qualcomm-2/#comment-230252</link>
		<dc:creator><![CDATA[Friends of Dave (friendsofdave) 's status on Thursday, 12-Nov-09 16:47:46 UTC - Identi.ca]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/?p=79448#comment-230252</guid>
		<description><![CDATA[[...]  http://gigaom.com/2009/11/12/qualcomm-2/        a few seconds ago  from api [...]]]></description>
		<content:encoded><![CDATA[<p>[...]  <a href="http://gigaom.com/2009/11/12/qualcomm-2/" rel="nofollow">http://gigaom.com/2009/11/12/qualcomm-2/</a>        a few seconds ago  from api [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

