<?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: Google Gears for Mobile Devices</title>
	<atom:link href="http://weblog.cenriqueortiz.com/mobility/2008/03/04/google-gears-for-mobile-devices/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.cenriqueortiz.com/mobility/2008/03/04/google-gears-for-mobile-devices/</link>
	<description>Thoughts on Mobile Software, Development &#38; Technologies</description>
	<lastBuildDate>Fri, 19 Mar 2010 14:43:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ceo</title>
		<link>http://weblog.cenriqueortiz.com/mobility/2008/03/04/google-gears-for-mobile-devices/comment-page-1/#comment-4939</link>
		<dc:creator>ceo</dc:creator>
		<pubDate>Tue, 04 Mar 2008 23:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.cenriqueortiz.com/mobility/2008/03/04/google-gears-for-mobile-devices/#comment-4939</guid>
		<description>Hey Brad... Ideal minimum would be as follows....

Because the handset is about communicating and sharing with others, having programmatic access to:
&lt;ol&gt;
&lt;li&gt;PIM info,&lt;/li&gt; 
&lt;li&gt;messaging,&lt;/li&gt; 
&lt;li&gt;camera, and,&lt;/li&gt; 
&lt;li&gt;telephony functions.&lt;/li&gt;
&lt;/ol&gt; 

Because the handset is about mobility, having access to location info (potentially GPS or whatever is available) would be great. 

And of course, offline behavior.

Now, if I go back to your original question, the top three for me right at this moment would be: 
&lt;ol&gt;
&lt;li&gt;PIM,&lt;/li&gt; 
&lt;li&gt;camera,&lt;/li&gt;
&lt;li&gt;location/GPS.&lt;/li&gt;
&lt;/ol&gt;

ceo</description>
		<content:encoded><![CDATA[<p>Hey Brad&#8230; Ideal minimum would be as follows&#8230;.</p>
<p>Because the handset is about communicating and sharing with others, having programmatic access to:</p>
<ol>
<li>PIM info,</li>
<li>messaging,</li>
<li>camera, and,</li>
<li>telephony functions.</li>
</ol>
<p>Because the handset is about mobility, having access to location info (potentially GPS or whatever is available) would be great. </p>
<p>And of course, offline behavior.</p>
<p>Now, if I go back to your original question, the top three for me right at this moment would be: </p>
<ol>
<li>PIM,</li>
<li>camera,</li>
<li>location/GPS.</li>
</ol>
<p>ceo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Neuberg</title>
		<link>http://weblog.cenriqueortiz.com/mobility/2008/03/04/google-gears-for-mobile-devices/comment-page-1/#comment-4933</link>
		<dc:creator>Brad Neuberg</dc:creator>
		<pubDate>Tue, 04 Mar 2008 21:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.cenriqueortiz.com/mobility/2008/03/04/google-gears-for-mobile-devices/#comment-4933</guid>
		<description>If you could allow web apps to access certain local mobile features, such as GPS, the address book, etc. what would your top three choices be?

Best,
  Brad Neuberg
  Google Gears
  http://codinginparadise.org</description>
		<content:encoded><![CDATA[<p>If you could allow web apps to access certain local mobile features, such as GPS, the address book, etc. what would your top three choices be?</p>
<p>Best,<br />
  Brad Neuberg<br />
  Google Gears<br />
  <a href="http://codinginparadise.org" rel="nofollow">http://codinginparadise.org</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
