<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://jimsegala.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Jim Segala</title>
 <link>http://jimsegala.sys-con.com/</link>
 <description>Latest News from Jim Segala</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 07 Dec 2009 12:50:43 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Thick vs Thin: Different Mobile Apps Need Different Clients</title>
 <link>http://jimsegala.sys-con.com/node/41075</link>
 <description>For many application developers, the fastest, easiest way to introduce a mobile solution was to &#039;chop down&#039; an existing Web-based application. Users that had a device with a browser could then access the applications. However, because the resulting applications were not designed for the navigation capabilities of a mobile device or the smaller bandwidth, the user experience suffered. These problems can be solved by using a thick client instead of a thin client.&lt;p&gt;&lt;a href=&quot;http://jimsegala.sys-con.com/node/41075&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 01 Jan 2000 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://jimsegala.sys-con.com/node/41075</guid>
 <comments>http://jimsegala.sys-con.com/node/41075#feedback</comments>
</item>
</channel>
</rss>
