<?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"
	>
<channel>
	<title>Comments on: Mobile Developement Simplification</title>
	<atom:link href="http://blog.landspurg.net/mobile-developer-simplification/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.landspurg.net/mobile-developer-simplification/</link>
	<description>Technology, wireless, games...and more.....</description>
	<pubDate>Wed, 19 Nov 2008 11:56:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Everything and the Mobile Software Universe&#8230; &#187; Performance vs Developper productivity and ease of coding : Why can&#8217;t we choose both?</title>
		<link>http://blog.landspurg.net/mobile-developer-simplification/#comment-15467</link>
		<dc:creator>Everything and the Mobile Software Universe&#8230; &#187; Performance vs Developper productivity and ease of coding : Why can&#8217;t we choose both?</dc:creator>
		<pubDate>Sat, 18 Nov 2006 00:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.landspurg.net/mobile-developer-simplification#comment-15467</guid>
		<description>[...] For sure, as said at TomSoft we need Mobile Developement Simplification(and yes widget standardization can help), but the traditional vision of &#8220;one model&#8221; fits all seems clearly not relevant for our industry, and more innovative frameworks have to emerge to trully allow the explosion we are all waiting around mobile services (see this entry about skype failure to deliver&#8230;). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] For sure, as said at TomSoft we need Mobile Developement Simplification(and yes widget standardization can help), but the traditional vision of &#8220;one model&#8221; fits all seems clearly not relevant for our industry, and more innovative frameworks have to emerge to trully allow the explosion we are all waiting around mobile services (see this entry about skype failure to deliver&#8230;). [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TomSoft</title>
		<link>http://blog.landspurg.net/mobile-developer-simplification/#comment-11161</link>
		<dc:creator>TomSoft</dc:creator>
		<pubDate>Sat, 28 Oct 2006 07:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.landspurg.net/mobile-developer-simplification#comment-11161</guid>
		<description>Mobile2.0 is of course about accessing these kind of API. But the way it is accessed (J2ME, Symbian, Borwser,etc...) it's another and secondary question....</description>
		<content:encoded><![CDATA[<p>Mobile2.0 is of course about accessing these kind of API. But the way it is accessed (J2ME, Symbian, Borwser,etc&#8230;) it&#8217;s another and secondary question&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olli</title>
		<link>http://blog.landspurg.net/mobile-developer-simplification/#comment-11006</link>
		<dc:creator>Olli</dc:creator>
		<pubDate>Thu, 26 Oct 2006 19:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.landspurg.net/mobile-developer-simplification#comment-11006</guid>
		<description>This is the most important point '..if hardware dependent telephony and GEO APIs are easily exposed?'

And if not you can’t really do Mobile 2.0, and thus Symbian or J2ME is and will be best choice.

Oliver

P.S. Sorry, I'm too stupid to use HTML</description>
		<content:encoded><![CDATA[<p>This is the most important point &#8216;..if hardware dependent telephony and GEO APIs are easily exposed?&#8217;</p>
<p>And if not you can’t really do Mobile 2.0, and thus Symbian or J2ME is and will be best choice.</p>
<p>Oliver</p>
<p>P.S. Sorry, I&#8217;m too stupid to use HTML</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olli</title>
		<link>http://blog.landspurg.net/mobile-developer-simplification/#comment-11005</link>
		<dc:creator>Olli</dc:creator>
		<pubDate>Thu, 26 Oct 2006 19:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.landspurg.net/mobile-developer-simplification#comment-11005</guid>
		<description>This is the most improtant point &lt;blockquote&gt;

And if not you can’t really do Mobile 2.0, and thus Symbian or J2ME is and will be best choice.

Oliver</description>
		<content:encoded><![CDATA[<p>This is the most improtant point<br />
<blockquote>
<p>And if not you can’t really do Mobile 2.0, and thus Symbian or J2ME is and will be best choice.</p>
<p>Oliver</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olli</title>
		<link>http://blog.landspurg.net/mobile-developer-simplification/#comment-11004</link>
		<dc:creator>Olli</dc:creator>
		<pubDate>Thu, 26 Oct 2006 19:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.landspurg.net/mobile-developer-simplification#comment-11004</guid>
		<description>This is the most important point &lt;blockquote&gt; 

And if not you can't really do Mobile 2.0, and thus Symbian or J2ME is and will be best choice.

Oliver</description>
		<content:encoded><![CDATA[<p>This is the most important point<br />
<blockquote>
<p>And if not you can&#8217;t really do Mobile 2.0, and thus Symbian or J2ME is and will be best choice.</p>
<p>Oliver</p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>
