<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Shawn Baden &#187; Android</title>
	<atom:link href="http://shawnbaden.com/tag/android/feed" rel="self" type="application/rss+xml" />
	<link>http://shawnbaden.com</link>
	<description></description>
	<lastBuildDate>Fri, 20 May 2011 03:01:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Android Button Order Revisited</title>
		<link>http://shawnbaden.com/2010/12/06/android-button-order-revisited</link>
		<comments>http://shawnbaden.com/2010/12/06/android-button-order-revisited#comments</comments>
		<pubDate>Tue, 07 Dec 2010 04:07:05 +0000</pubDate>
		<dc:creator>shawnbaden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Android]]></category>
		<category><![CDATA[Nexus One]]></category>
		<category><![CDATA[Nexus S]]></category>

		<guid isPermaLink="false">http://shawnbaden.com/?p=634</guid>
		<description><![CDATA[With the launch of the Nexus S by Google, it&#8217;s time to revisit the inconsistency in the button order of Android devices. As I pointed out previously, there&#8217;s seems to be no rhyme or reason to the order, even among manufacturers (ahem Motorola/Verizon). Well, it seems Google isn&#8217;t immune to this either. &#8212; Nexus One: [...]]]></description>
			<content:encoded><![CDATA[<p>With the launch of the <a href="http://www.google.com/nexus">Nexus S</a> by Google, it&#8217;s time to revisit the inconsistency in the button order of Android devices.  As I pointed out <a href="http://shawnbaden.com/2010/06/26/why-no-standard-android-button-order">previously</a>, there&#8217;s seems to be no rhyme or reason to the order, even among manufacturers (ahem Motorola/Verizon).  Well, it seems Google isn&#8217;t immune to this either.</p>
<p> &#8212; Nexus One: Back, Menu, Home, Search</p>
<p> &#8212; Nexus S: Back, Menu, Search, Home</p>
<p>I don&#8217;t care the Nexus One was manufactured by HTC and the Nexus S was manufactured by Samsung &#8212; the Nexus line _IS_ Google&#8217;s phone.</p>
<p>Seriously.  Pick something and stick to it.</p>
<p>(via <a href="http://daringfireball.net/linked/2010/12/06/android-hardware">John Gruber</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnbaden.com/2010/12/06/android-button-order-revisited/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Smartphones On No-Contract Carriers: A Market Waiting to Explode</title>
		<link>http://shawnbaden.com/2010/08/09/smartphones-on-no-contract-carriers-market-waiting-to-explode</link>
		<comments>http://shawnbaden.com/2010/08/09/smartphones-on-no-contract-carriers-market-waiting-to-explode#comments</comments>
		<pubDate>Tue, 10 Aug 2010 04:08:50 +0000</pubDate>
		<dc:creator>shawnbaden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Boost Mobile]]></category>
		<category><![CDATA[Virgin Mobile]]></category>

		<guid isPermaLink="false">http://shawnbaden.com/?p=439</guid>
		<description><![CDATA[I believe there is a sizable market in waiting for &#8220;capable&#8221; smartphones on no-contract carriers. I fall into that market. For as long as I can remember, I have been using a lowly Motorola RAZR for my phone on Verizon Wireless (previously Alltel). I&#8217;d really like a smartphone. But on contract carriers, I just can&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>I believe there is a sizable market in waiting for &#8220;capable&#8221; smartphones on no-contract carriers.</p>
<p>I fall into that market.  For as long as I can remember, I have been using a lowly Motorola RAZR for my phone on Verizon Wireless (previously Alltel).  I&#8217;d really like a smartphone.  But on contract carriers, I just can&#8217;t stomach what they charge.  And that&#8217;s just for voice plans.  Throw in data plans and I get nauseous.  Back to &#8220;the market in waiting.&#8221;</p>
<p><a href="http://www.flickr.com/photos/shawnbaden/4876644524/" title="Google Search for Kyocera Zio by Shawn Baden, on Flickr"><img src="http://farm5.static.flickr.com/4079/4876644524_671071ab8f.jpg" width="500" height="362" alt="Google Search for Kyocera Zio" /></a></p>
<p>There are more searches for &#8220;kyocera zio boost mobile&#8221; and &#8220;kyocera zio&#8221; which I think is telling.  So what&#8217;s so special about the Kyocera Zio?  It&#8217;s the first capable smartphone that&#8217;s going to show up on a no-contract carrier (note: the Motorola i1 on Boost Mobile doesn&#8217;t count as it&#8217;s iDEN).  It&#8217;s <a href=http://www.mycricket.com/android">confirmed on Cricket</a> where it&#8217;s called the Sanyo Zio by Kyocera.  The price has been set for $299 which is very reasonable for a no-contract Android phone.  It&#8217;s also been <a href="http://www.androidguys.com/2010/05/26/rumor-kyocera-zio-m6000-headed-boost-mobile/">rumored</a> for some time to be headed to Boost Mobile as well.</p>
<p>So what makes no-contract carriers so exciting?  Simple: PRICE.  Look at these plans that require no contract:</p>
<table>
<tr>
<th></th>
<th>Talk</th>
<th>Text</th>
<th>Data</th>
<th>Price</th>
</tr>
<tr>
<td>Boost Mobile</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>$50/month</td>
</tr>
<tr>
<td>Cricket</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>$55/month</td>
</tr>
<tr>
<td>Virgin Mobile</td>
<td>1200 Minutes</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>$40/month</td>
</tr>
<tr>
<td>Virgin Mobile</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>Unlimited</td>
<td>$60/month</td>
</tr>
</table>
<p>Here&#8217;s the other little secret with no-contract carriers: <b><u>YOU ONLY PAY SALES TAX</u></b>.  None of those other ridiculous &#8220;other&#8221; fees.  Oh, and <b><u>THERE&#8217;S NO ACTIVATION CHARGES</u></b> on these plans.</p>
<p>Personally, my threshold is $50/month for unlimited* talk, text, and data (unlimited to me means virtually unlimited, meaning 98% of users will never hit some actual limit that is placed on these services).  But having calculated how much talk time my wife and I use, we&#8217;ve never went over 1000 minutes in a single month for BOTH of our phones.  With that knowledge, I think Virgin Mobile&#8217;s $40/month plan with unlimited text and data with 1200 minutes IS KILLER.  Now where&#8217;s a capable smartphone, Virgin Mobile?</p>
<p>Here&#8217;s another no-contract though a co-worker and I keep coming back to.  You know all those Palm Pre&#8217;s on Sprint that were &#8220;stuffed in the channel.&#8221;  Why not roll all those onto Boost Mobile?  Charge $200 to $300 for a Palm Pre, rock the $50/month unlimited everything plan, and you&#8217;re done.  Had Palm gone this route, i.e. be THE phone on no-contract carriers, they might have made a go at it.</p>
<p>This market is real and it&#8217;s waiting.  Get us a &#8220;capable&#8221; smartphone (i.e. Android 2.0 capable or better or Palm Web OS) and keep the price around $300 or less, throw in a $50/month unlimited talk, text, and data plan, and prepare to bank.  Cricket is stepping up to the plate with the Zio.  Who else wants a piece?</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnbaden.com/2010/08/09/smartphones-on-no-contract-carriers-market-waiting-to-explode/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verizon DROID X Commercial</title>
		<link>http://shawnbaden.com/2010/07/12/verizon-droid-x-commercial</link>
		<comments>http://shawnbaden.com/2010/07/12/verizon-droid-x-commercial#comments</comments>
		<pubDate>Mon, 12 Jul 2010 17:45:45 +0000</pubDate>
		<dc:creator>shawnbaden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Advertisement]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Motorola]]></category>
		<category><![CDATA[Motorola Droid]]></category>
		<category><![CDATA[Verizon]]></category>

		<guid isPermaLink="false">http://shawnbaden.com/?p=339</guid>
		<description><![CDATA[I think Google and its Android partners (obviously Verizon since they own DROID) need to continue to differentiate Android from iOS and hammer home the whole android/robot/industrial vibe in marketing. Verizon&#8217;s DROID X commercial is an excellent example of this. It&#8217;s got an &#8220;assimilated by the borg&#8221; feel and is very attention-grabbing (in a good [...]]]></description>
			<content:encoded><![CDATA[<p>I think Google and its Android partners (obviously Verizon since they own DROID) need to continue to differentiate Android from iOS and hammer home the whole android/robot/industrial vibe in marketing.</p>
<p>Verizon&#8217;s DROID X commercial is an excellent example of this.  It&#8217;s got an &#8220;assimilated by the borg&#8221; feel and is very attention-grabbing (in a good way).</p>
<p><object width="499" height="306"><param name="movie" value="http://www.youtube.com/v/gOnC5chCag0&amp;hl=en_US&amp;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/gOnC5chCag0&amp;hl=en_US&amp;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="499" height="306"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://shawnbaden.com/2010/07/12/verizon-droid-x-commercial/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Is There No Standard Android Button Order?</title>
		<link>http://shawnbaden.com/2010/06/26/why-no-standard-android-button-order</link>
		<comments>http://shawnbaden.com/2010/06/26/why-no-standard-android-button-order#comments</comments>
		<pubDate>Sun, 27 Jun 2010 05:03:57 +0000</pubDate>
		<dc:creator>shawnbaden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google Android]]></category>
		<category><![CDATA[Motorola]]></category>
		<category><![CDATA[Motorola Droid]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://shawnbaden.com/?p=257</guid>
		<description><![CDATA[Recently I had a chance to handle a coworker&#8217;s HTC EVO 4G. I was immediately confused by the fact the 4 buttons were in a different order than the Android devices I was used to. Namely the Motorola Droid and the HTC (Google) Nexus One. I started investigating the button order on other Android devices. [...]]]></description>
			<content:encoded><![CDATA[<p>Recently I had a chance to handle a coworker&#8217;s HTC EVO 4G.  I was immediately confused by the fact the 4 buttons were in a different order than the Android devices I was used to.  Namely the Motorola Droid and the HTC (Google) Nexus One.  I started investigating the button order on other Android devices.  This what I found:</p>
<ul>
<li>HTC DROID Incredible: Home, Menu, Back, Search</li>
<li>HTC EVO 4G: Home, Menu, Back, Search</li>
<li>HTC Nexus One: Back, Menu, Home, Search</li>
<li>Motorola DROID: Back, Menu, Home, Search</li>
<li>Motorola DROID X: Menu, Home, Back, Search</li>
</ul>
<p>I&#8217;m still confused.  At least HTC has released its last 2 phones with the same button order.</p>
<p><a href="http://www.flickr.com/photos/shawnbaden/4737100537/" title="DROID DOES... Not Do Consistent Button Order"><img src="http://farm5.static.flickr.com/4115/4737100537_f6742a09fa.jpg" width="500" height="254" alt="DROID DOES... Not Do Consistent Button Order"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://shawnbaden.com/2010/06/26/why-no-standard-android-button-order/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

