<?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: 7 future proof assumptions for mobile app developers</title>
	<atom:link href="http://www.themobilemontage.com/2009/09/01/7-future-proof-assumptions-for-mobile-app-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.themobilemontage.com/2009/09/01/7-future-proof-assumptions-for-mobile-app-developers/</link>
	<description>a collection of scattered thoughts on mobile technology and related topics…</description>
	<lastBuildDate>Sun, 16 May 2010 05:35:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Shai Levit</title>
		<link>http://www.themobilemontage.com/2009/09/01/7-future-proof-assumptions-for-mobile-app-developers/comment-page-1/#comment-123</link>
		<dc:creator>Shai Levit</dc:creator>
		<pubDate>Wed, 17 Mar 2010 03:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.cis.gvsu.edu/~engelsma/?p=31#comment-123</guid>
		<description>You forgot to mention how Intel will move into the mobile arena with their new set of smaller and more powerful chip sets. i.e.: i7 or i9 for the mobile platform, making the mobile phone as fast and powerful as today&#039;s PC. That in itself will accelerate the use and ubiquitous of the mobile device.

I still like to see a better hybrid of iPhone and iPad - something inbetween that will operate like a netbook, have an expandable screen and still fold into your pocket.</description>
		<content:encoded><![CDATA[<p>You forgot to mention how Intel will move into the mobile arena with their new set of smaller and more powerful chip sets. i.e.: i7 or i9 for the mobile platform, making the mobile phone as fast and powerful as today&#8217;s PC. That in itself will accelerate the use and ubiquitous of the mobile device.</p>
<p>I still like to see a better hybrid of iPhone and iPad &#8211; something inbetween that will operate like a netbook, have an expandable screen and still fold into your pocket.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: forex</title>
		<link>http://www.themobilemontage.com/2009/09/01/7-future-proof-assumptions-for-mobile-app-developers/comment-page-1/#comment-25</link>
		<dc:creator>forex</dc:creator>
		<pubDate>Thu, 19 Nov 2009 19:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.cis.gvsu.edu/~engelsma/?p=31#comment-25</guid>
		<description>great post as usual .. thanks  .. you just gave me a few more ideas to play with</description>
		<content:encoded><![CDATA[<p>great post as usual .. thanks  .. you just gave me a few more ideas to play with</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.themobilemontage.com/2009/09/01/7-future-proof-assumptions-for-mobile-app-developers/comment-page-1/#comment-4</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Fri, 18 Sep 2009 12:23:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.cis.gvsu.edu/~engelsma/?p=31#comment-4</guid>
		<description>Great article.  I tend to agree with all you say here, however I think you&#039;re slightly too optimistic on point #1.  Device fragmentation is likely going to be a big issue for mobile developers for the foreseeable future.  Check out: http://www.fiercedeveloper.com/story/device-fragmentation-deal-it/2009-09-11</description>
		<content:encoded><![CDATA[<p>Great article.  I tend to agree with all you say here, however I think you&#8217;re slightly too optimistic on point #1.  Device fragmentation is likely going to be a big issue for mobile developers for the foreseeable future.  Check out: <a href="http://www.fiercedeveloper.com/story/device-fragmentation-deal-it/2009-09-11" rel="nofollow">http://www.fiercedeveloper.com/story/device-fragmentation-deal-it/2009-09-11</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
