<?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>Canyon R &#187; Google</title>
	<atom:link href="http://canyonr.com/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://canyonr.com</link>
	<description>Standing on the corner of Technology and Reality</description>
	<lastBuildDate>Mon, 16 Aug 2010 01:00:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>To Write the Unreadable Review Post</title>
		<link>http://canyonr.com/2010/05/to-write-the-unreadable-review-post/</link>
		<comments>http://canyonr.com/2010/05/to-write-the-unreadable-review-post/#comments</comments>
		<pubDate>Sun, 09 May 2010 17:32:07 +0000</pubDate>
		<dc:creator>Canyon</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>
		<category><![CDATA[Phone]]></category>

		<guid isPermaLink="false">http://canyonr.com/?p=53</guid>
		<description><![CDATA[On the verge of receiving my Nexus One I mused about posting a review after a week of use. I have tried to write this post THREE time. Three times I&#8217;ve tried to write about how much I&#8217;m enjoying my Nexus One and all the great things I&#8217;m able to do with it. But every [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: medium;">On the verge of <a href="http://canyonr.com/2010/04/why-i-bought-a-nexus-one/">receiving my Nexus One</a> I mused about posting a review after a week of use. I have tried to write this post THREE time. Three times I&#8217;ve tried to write about how much I&#8217;m enjoying my Nexus One and all the great things I&#8217;m able to do with it. But every time it was udeniably, unacceptably, and unrepairably BORING. I just couldn&#8217;t make it interesting or compelling in any way at all. There are <a href="http://www.engadget.com/2010/01/04/nexus-one-review/">many</a> good <a href="http://www.boygeniusreport.com/2010/01/09/google-nexus-one-review-android-thoughts/">reviews</a> already <a href="http://smarterware.org/4308/android-2-1s-best-features-in-screenshots">available</a>. I just didn&#8217;t feel that I could get a fresh or different perspective on any of them. I hope that you will understand that I tried, really tried to make it readable. The <a href="http://www.google.com/phone">Nexus One</a> is amazing and provides everything that a smartphone should be. I just couldn&#8217;t write about it in any way that I would actually expect you to read.</span></p>
<div><span style="font-size: medium;"><br />
</span></div>
<div><span style="font-size: medium;">More interesting are the accessories and apps that I have purchased and how they are directly affecting my enjoyment of the Nexus One. So that&#8217;s where I&#8217;m going to start. I&#8217;ll post, over the next few weeks, my reviews of the assorted parts that have really helped make my Nexus One whole. I&#8217;m planning on a two part accessories review and one application roundup. I hope I can make this more useful and ultimately readable than my previous efforts.</span></div>
<p class="akst_link"><a href="http://canyonr.com/?p=53&amp;akst_action=share-this"  title="E-mail this, post to del.icio.us, etc." id="akst_link_53" class="akst_share_link" rel="nofollow">Share This</a>
</p>]]></content:encoded>
			<wfw:commentRss>http://canyonr.com/2010/05/to-write-the-unreadable-review-post/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why I bought a Nexus One.</title>
		<link>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/</link>
		<comments>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/#comments</comments>
		<pubDate>Mon, 12 Apr 2010 04:19:30 +0000</pubDate>
		<dc:creator>Canyon</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>
		<category><![CDATA[Phone]]></category>

		<guid isPermaLink="false">http://canyonr.com/?p=51</guid>
		<description><![CDATA[I&#8217;m on the eve of the next major gadget event in my life. Tomorrow my new Nexus One will be delivered. This is something I&#8217;ve been waiting for since shortly after getting my G1 almost 2 years ago. I want to take this opportunity to talk about my reasons for choosing the Nexus One. I [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m on the eve of the next major gadget event in my life. Tomorrow my new <a href="http://www.google.com/phone">Nexus One</a> will be delivered. This is something I&#8217;ve been waiting for since shortly after getting my <a href="http://www.t-mobileg1.com/">G1</a> almost 2 years ago. I want to take this opportunity to talk about my reasons for choosing the Nexus One. I hope to follow this up with a report after my first week of using it on how things have gone.</p>
<p>First, a bit of background. In 2007 I was a heavy Macintosh user and I had been an <a href="http://en.wikipedia.org/wiki/MacUser">Apple fanboy</a> since the early 90&#8242;s. I had lived through the <a href="http://news.cnet.com/2100-1001-202143.html">dark times</a>, survived OS 8 &amp; 9, and then basked in the triumphant <a href="http://en.wikipedia.org/wiki/Mac_OS_X_v10.2">transition to OS X</a>. Yet after proselytizing the Mac for many years, both personally and <a href="http://en.wikipedia.org/wiki/CompUSA">professionally</a>, I actively avoided the iPhone when everyone around me was <a href="http://solution.allthingsd.com/20070626/the-iphone-is-breakthrough-handheld-computer/">loving theirs</a>. So when the <a href="http://www.android.com/">android OS</a> was <a href="http://techcrunch.com/2007/11/05/breaking-google-announces-android-and-open-handset-alliance/">first announced</a> I was sure this would be a promising replacement for my <a href="http://na.blackberry.com/eng/devices/archived/7130e.jsp">aging blackberry</a> and might give me the features I wanted without binding me eternally to iTunes. I had already heavily invested into the Google provided services and I hated AT&amp;T with deliberate determination. (aside: this stems from them <a href="http://www.networkworld.com/edge/news/2005/0131attsbc.html">being SBC</a> and not the AT&amp;T we all grew up with.) Then when the G1 was released, three different people in my office bought them within a few days of each other. I was awestruck at what android provided, including copy and paste. I waited a month and a half until the end of our <a href="http://www.uscellular.com/">current cell phone contract</a>, then my whole family went to <a href="http://www.t-mobile.com/">T-Mobile</a> to get new phones. My wife, unfortunately, picked a <a href="http://gizmodo.com/5030676/t+mobile-sidekick-2008-review">sidekick</a> and my daughter got a <a href="http://www.phonedog.com/products/htc-shadow/">windows mobile phone</a>. But that was all a distant distraction, I finally had my G1. The <a href="http://reviews.cnet.com/smartphones/t-mobile-g1-black/4505-6452_7-33283585.html">early days</a> of the G1 were a trying time, spent mostly waiting for applications to be released. Over the course of the last 18 months I have had uncountable twitter clients, to do apps, and notepads programs. I have watched the evolution of the ipod as a gaming platform, and the release of ever <a href="http://droiddoes.com/">better android phones</a>. All the while my G1 got slower and less stable.</p>
<p>So why, in the context of these problems and the ever widening <a href="http://blogs.eweek.com/storage_station/content/general/90k_iphones_sold_per_day_straining_worlds_flash_supply.html">dominance of the iPhone platform</a>, would I choose to reinvest in android? I believe it will offer me the best solution for my needs. I will explore the three biggest factors in this conclusion: Integration, flexibility, and community. Yet to me the most telling point is that my biggest hesitation doesn&#8217;t come from the newly announced <a href="http://www.engadget.com/2010/04/08/live-from-apples-iphone-os-4-event/">iPhone OS 4</a> or the <a href="http://www.suntimes.com/technology/ihnatko/2134139,ihnatko-ipad-apple-review-033110.article">recently released iPad</a> but from the speculation that Google may release a <a href="http://phandroid.com/2010/01/10/nexus-one-pro-world-phone-with-keyboard-bigger-battery/">Nexus One Pro</a> with a keyboard. This speaks volumes about the decision I&#8217;ve made and how confident I am that android is the right solution for me.</p>
<p>As I said, even before my first android phone, I was deeply invested into Google&#8217;s services. GMail was my primary email, Calendar organized my time, and I practically lived in Reader. Since living with android and the integration into these services that it offers, I have become even more dependent on them and I don&#8217;t regret it a bit. My Google Contacts list is the way I keep track of the people I want and need to stay in touch with. Picassa is where my photos live online and Docs holds everything that the &#8220;My Documents&#8221; folder was designed to hold. Even when I <a href="http://www.everymac.com/systems/apple/consumer_electronics/stats/ipod_3rdgen.html">had an iPod</a> it&#8217;s biggest use was for <a href="http://twit.tv/">Podcasts</a>. Now I swear by <a href="http://listen.googlelabs.com/">Google&#8217;s Listen app</a>. It&#8217;s Podcast done better that iTunes ever could. This level of integration has given me more than just a connected device, it&#8217;s really a connected system. A startling side effect is that my Laptop had become mostly just a host for my browser. The majority of apps I run are web pages turned to apps with Chrome&#8217;s &#8220;<a href="http://www.google.com/support/chrome/bin/answer.py?hl=en&amp;answer=95710">Create Application Shortcuts</a>&#8230;&#8221; feature. I am almost living with <a href="http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html">Google&#8217;s Chrome OS</a> already.</p>
<p>For me, though, this connected system really shines because it&#8217;s open and therefore more flexible than Apple&#8217;s solution. As an example I&#8217;ll discuss exchange integration. I recently started a new job where they offer the ability to connect a personal smartphone to the company&#8217;s <a href="http://msexchangeteam.com/">exchange server</a>, provided it supports certain security features. If I had an iPhone I would have to choose between <a href="http://www.google.com/support/mobile/bin/answer.py?hl=en&amp;answer=138740">syncing with my Google information</a> or my <a href="http://support.apple.com/kb/ht2480">work&#8217;s exchange server</a>. On the android platform there are several exchange solutions, some baked in from the <a href="https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/37232/display_style/redesign/prod_id/6703">handset makers</a> and others from <a href="http://www.wrike.com/g1-exchange-sync.html">third parties</a>. I found <a href="http://www.nitrodesk.com/index.aspx">Nitrodesk&#8217;s Touchdown</a> and was elated. Not only did it provide a <a href="http://www.nitrodesk.com/dk_touchdownFeatures.aspx">complete exchange solution</a>, including all the security required by my company, but it kept all my work info separate from my personal Google stuff. It&#8217;s basically Outlook for android. This app, by virtue of it&#8217;s &#8220;<a href="http://www.wired.com/epicenter/2009/08/apple-att-and-google-respond-to-feds-on-google-voice-rejection/">duplication of built in features</a>&#8220;, would never be approved onto the iTunes App Store, regardless of the number of users who would like it. I&#8217;ve found this to be the case numerous times with android applications. There are third party solutions for accessing <a href="http://www.gdocs.mobi/">Google Docs</a>, <a href="http://newsrob.blogspot.com/">Google Reader</a>, and <a href="http://sites.google.com/site/ssi4and/">GMail tasks</a>. How many solutions does the iPhone have for accessing iDisk or Mobile Me content outside of apple&#8217;s built in apps? And that&#8217;s when they eventually <a href="http://www.appleinsider.com/articles/10/04/08/ichatagent_note_syncing_over_mobileme_discovered_in_iphone_4_0.html">provide a solution</a>.</p>
<p>But what, you may ask, about the future developments which are <a href="http://gigaom.com/2010/03/18/the-mobile-os-market/">clearly leaning toward the iPhone</a>. Most new apps are debuting there and it&#8217;s <a href="http://gigaom.com/2010/01/12/the-apple-app-store-economy/">adoption rate</a> isn&#8217;t showing any signs of slowing. To that I would answer with the <a href="http://www.xda-developers.com/">community</a> which has grown up around android and <a href="http://twit.tv/twig">Google&#8217;s services</a>. I can say it was liberating when I first <a href="http://forum.xda-developers.com/showthread.php?t=442480">Rooted my G1</a> and installed a custom ROM from <a href="http://www.cyanogenmod.com/">Cyanogen</a>. I was able to take my mobile computing into my own hands and, while excepting the risks involved, get better performance and functionality. Ever since then I have had a steady stream of new features and even updates from newer android versions that T-Mobile wouldn&#8217;t have sanctioned. And when there was a <a href="http://phandroid.com/2009/09/25/cyanogen-gets-cd-from-google/">clash between Cyanogen and Google</a> it wasn&#8217;t the Zero Tolerance policy that Apple has aggressively enforced. The end result was an amicable agreement that allowed <a href="http://phandroid.com/2009/10/30/cyanogen-emerges-releases-new-rom/">new ROMs to be released</a> and allowed Google to <a href="http://android-developers.blogspot.com/2009/09/note-on-google-apps-for-android.html">protect the components</a> they had promised to their distributors. Because the parent company isn&#8217;t hostile to the moding community, many more high quality mods are available, including many <a href="http://forum.xda-developers.com/forumdisplay.php?f=450">impressive themes</a> and several <a href="http://forum.xda-developers.com/forumdisplay.php?f=448">custom ROMs</a>. This is most strongly evidenced by the existence in the android market of apps to <a href="http://code.google.com/p/cyanogen-updater/">download Cyanogen&#8217;s ROMs</a> and <a href="http://relentlessaddictions.com/android/node/4">third party themes</a>. Both of which require a Rooted phone to work. Would Apple ever allow that?</p>
<p>I still maintain that the iPhone is a wonderfull solution, I tried to convince my wife that It would be a great solution for her needs just a month ago. She did eventually however choose a <a href="http://na.blackberry.com/eng/devices/blackberrycurve8500/">Blackberry 8520</a>, which she has come to love. For me though the android philosophy is a closer fit and a better solution for my needs. So now I wait for FedEx to bring me my own <a href="http://www.wired.com/gadgetlab/2010/01/google-debuts-android-powered-nexus-one-superphone/">Superphone</a> and open the next chapter in my mobile computing life.</p>
<p class="akst_link"><a href="http://canyonr.com/?p=51&amp;akst_action=share-this"  title="E-mail this, post to del.icio.us, etc." id="akst_link_51" class="akst_share_link" rel="nofollow">Share This</a>
</p>]]></content:encoded>
			<wfw:commentRss>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>The ubiquity of Google Wave</title>
		<link>http://canyonr.com/2009/10/the-ubiquity-of-google-wave/</link>
		<comments>http://canyonr.com/2009/10/the-ubiquity-of-google-wave/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 13:40:59 +0000</pubDate>
		<dc:creator>Canyon</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Wave]]></category>
		<category><![CDATA[web2.0]]></category>

		<guid isPermaLink="false">http://canyonr.com/?p=43</guid>
		<description><![CDATA[No it doesn&#8217;t make thousands of Julienne fries I understand the problem everyone is having with Google Wave. I really do. From cries of &#8220;I don&#8217;t get it&#8221; to &#8220;This isn&#8217;t going to replace email&#8221; there is a roar of dissatisfaction with the initial release of Google Wave. I think this comes from people trying [...]]]></description>
			<content:encoded><![CDATA[<p><strong>No it doesn&#8217;t make thousands of Julienne fries</strong></p>
<p>I understand the problem everyone is having with <a href="http://wave.google.com">Google Wave</a>. I really do. From cries of &#8220;<a href="http://twitter.com/search?q=%22Google%20Wave%22%20and%20%22don%27t%20get%22">I don&#8217;t get it</a>&#8221; to &#8220;<a href="http://scobleizer.com/2009/10/03/google-waves-unproductive-email-metaphors/">This isn&#8217;t going to replace email</a>&#8221; there is a roar of dissatisfaction with the initial release of Google Wave. I think this comes from people trying to set it into their current modes and methods. Wave doesn&#8217;t really replace any existing product completely. Wave won&#8217;t kill twitter or get you away from email. But I think <a href="http://twit.tv/">Leo Laporte</a> put it best on several of his Netcasts &#8220;Maybe for a paradigm shift it needs to be a product that we don&#8217;t get initially&#8221;. This sums up the disconnect many people feel with Wave. They have a hard time fitting Wave into their current view of work and communication because it isn&#8217;t the same as the tools they have used before. <span id="more-43"></span></p>
<p>Just as &#8220;<a href="http://en.wikipedia.org/wiki/Law_of_the_instrument">When all you have is a hammer, everything looks like a nail</a>&#8221; holds true for situations with a lack of tools, I believe that once you get a screwdriver you don&#8217;t ask &#8220;how do i use this to drive nails&#8221;. A new tool can complement, rather than replace, existing ones. A new tool can both give you a better solution to existing problems (not inserting screws by hitting them really hard) and give you new capabilities that the old tools didn&#8217;t (you can remove screws as well). I think this is the state of Google Wave. It&#8217;s a tool that will make some current processes better, not emailing 12 versions of word documents back and forth, and allow new ones to be developed. This second part is what really excites me, what new things will we start to do with wave once it finds it&#8217;s place in our current workflows. How will we leverage it&#8217;s unique many to many, real time model to create things we couldn&#8217;t easily create before. All of the wonderful examples in the oft linked <a href="http://lifehacker.com/5381219/">Lifehacker article</a> are using wave for things that are currently accomplished with existing communication tools, most using one to one or one to many methods (ie. phone calls or email). And while I think that wave will be a great new tool in these areas, I really want to see what things will we use it for that we aren&#8217;t doing today because the existing tools fall too short to be workable.</p>
<p>So yes it slices, and you can use it for dicing if you want, but it won&#8217;t make thousands of  <a href="http://en.wikipedia.org/wiki/Julienning">Julienne fries</a>. It may, however, help you create a new way to carve up your work.</p>
<p class="akst_link"><a href="http://canyonr.com/?p=43&amp;akst_action=share-this"  title="E-mail this, post to del.icio.us, etc." id="akst_link_43" class="akst_share_link" rel="nofollow">Share This</a>
</p>]]></content:encoded>
			<wfw:commentRss>http://canyonr.com/2009/10/the-ubiquity-of-google-wave/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
