<?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: BlackBerry or Droid?</title>
	<atom:link href="http://peachies.net/2010/03/11/blackberry-or-droid/feed/" rel="self" type="application/rss+xml" />
	<link>http://peachies.net/2010/03/11/blackberry-or-droid/</link>
	<description></description>
	<lastBuildDate>Sun, 01 Jan 2012 01:28:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: tony</title>
		<link>http://peachies.net/2010/03/11/blackberry-or-droid/#comment-30</link>
		<dc:creator>tony</dc:creator>
		<pubDate>Thu, 11 Mar 2010 09:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://peachies.net/?p=2416#comment-30</guid>
		<description>I love nerdy questions so here&#039;s my take: don&#039;t get the bberry for the hardware keyboard. I&#039;ve had a bberry and three different android phones and can tell you the form factor for all smartphones are moving toward the software keyboard. I had the same reservations so finally got rid of my bberry this year and decided to embrace the trend (typing this on a nexus one).  The main selling point for the bberry is their dedicated RIM servers in Canada which you don&#039;t need if you&#039;re not a business.  The browser blows and they have a closed app development environment. One warning on the Droid though. While I like the heft of the body, the keyboard is set up as a grid, as opposed to staggered, so there&#039;s less room for error and you can&#039;t get faster the more you use it like with a software keyboard.  I&#039;m biased bc I used to work for Google but get an android, perhaps htc&#039;s latest.</description>
		<content:encoded><![CDATA[<p>I love nerdy questions so here&#8217;s my take: don&#8217;t get the bberry for the hardware keyboard. I&#8217;ve had a bberry and three different android phones and can tell you the form factor for all smartphones are moving toward the software keyboard. I had the same reservations so finally got rid of my bberry this year and decided to embrace the trend (typing this on a nexus one).  The main selling point for the bberry is their dedicated RIM servers in Canada which you don&#8217;t need if you&#8217;re not a business.  The browser blows and they have a closed app development environment. One warning on the Droid though. While I like the heft of the body, the keyboard is set up as a grid, as opposed to staggered, so there&#8217;s less room for error and you can&#8217;t get faster the more you use it like with a software keyboard.  I&#8217;m biased bc I used to work for Google but get an android, perhaps htc&#8217;s latest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny Kim</title>
		<link>http://peachies.net/2010/03/11/blackberry-or-droid/#comment-29</link>
		<dc:creator>Jenny Kim</dc:creator>
		<pubDate>Thu, 11 Mar 2010 09:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://peachies.net/?p=2416#comment-29</guid>
		<description>DROID!!! =) I was in the same situation as you and got the Motorola Droid. Indeed, the Droid is best for websites and blogging b/c it doesn&#039;t have an archaic browser. It doesn&#039;t have the pinch zoom like on the iphone, but it does have a - + side that you just have to tap, and it will zoom out or in. Not a biggie. It&#039;s nice having a physical  keyboard and touch screen.</description>
		<content:encoded><![CDATA[<p>DROID!!! =) I was in the same situation as you and got the Motorola Droid. Indeed, the Droid is best for websites and blogging b/c it doesn&#8217;t have an archaic browser. It doesn&#8217;t have the pinch zoom like on the iphone, but it does have a &#8211; + side that you just have to tap, and it will zoom out or in. Not a biggie. It&#8217;s nice having a physical  keyboard and touch screen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

