<?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>GLOW Interactive &#124; BLOG &#187; Google</title>
	<atom:link href="http://blog.glowinteractive.com/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.glowinteractive.com</link>
	<description>codify, media, gaming, industry ramblings, finance</description>
	<lastBuildDate>Thu, 02 Feb 2012 19:05:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Google &#8220;Buzzed&#8221; my Inbox. Do I have to answer?</title>
		<link>http://blog.glowinteractive.com/2010/02/google-buzzed-my-inbox-do-i-have-to-answer/</link>
		<comments>http://blog.glowinteractive.com/2010/02/google-buzzed-my-inbox-do-i-have-to-answer/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 22:05:33 +0000</pubDate>
		<dc:creator>Adam Gorode</dc:creator>
				<category><![CDATA[Social Media]]></category>
		<category><![CDATA[GMail]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://blog.glowinteractive.com/?p=664</guid>
		<description><![CDATA[Gmail is my holy grail. It's my online quiet place. And yesterday Google Buzz came and crashed my pad like an old friend looking for a couch. It's noisy, distracting and appears to be duplicating existing services that serve me quite well.]]></description>
			<content:encoded><![CDATA[<p>Gmail is my holy grail. It&#8217;s my online quiet place. And yesterday Google Buzz came and crashed my pad like an old friend looking for a couch. It&#8217;s noisy, distracting and appears to be duplicating existing services that serve me quite well.</p>
<p>It&#8217;s not that I&#8217;m adverse to change, I love it and embrace it. But as of late I feel like Google is throwing a ton of shit at the wall hoping something sticks. Is this a take two on Google Wave?</p>
<p>I get it. Google is trying its damnedest to get into the social space in some meaningful way. But it didn&#8217;t work. Twitter? Maybe they should have just bought them. Google Buzz? You&#8217;re late to the party, I feel like I&#8217;ve seen you before, and I&#8217;m not keen on you crashing my inbox.</p>
<p>I have gone to great lengths to ensure that what I see in my Gmail inbox are things I want to see. My calendar is clean, my contacts organized, and I have filters setup so that the emails in my inbox are relevant. But now, the conversations that Iâ€™d have on facebook or twitter are bleeding into my sanctuary of order. I fear I may soon have no place to hide.</p>
<p>I expect that I will soon develop a filter and adapt to this new noise, but I am not a fan of having this distraction in my Gmail inbox. As much as I&#8217;d love to pretend I can follow twitter/facebook/reader/buzz intently while working, I know that even sometimes I too have to turn off the social media valve and focus on the task in front of me. Google buzz, just knocked down the door that separated my social media conversations and productivity.</p>
<p>I&#8217;m curious how I feel about this tomorrow. Update to follow.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.glowinteractive.com/2010/02/google-buzzed-my-inbox-do-i-have-to-answer/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>A SuperPhone with a Touch of Kryptonite</title>
		<link>http://blog.glowinteractive.com/2010/01/a-superphone-with-a-touch-of-kryptonite/</link>
		<comments>http://blog.glowinteractive.com/2010/01/a-superphone-with-a-touch-of-kryptonite/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 12:05:22 +0000</pubDate>
		<dc:creator>Adam Gorode</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[iPhone]]></category>

		<guid isPermaLink="false">http://blog.glowinteractive.com/?p=368</guid>
		<description><![CDATA[Nearly two months ago, shortly after the release of the Droid and subsequent escalation in chatter with respect to the “Google Phone” I discussed my complete dissatisfaction with the state of the iPhone as it pertained to Apple/AT&#038;T and the impending threat (very serious threat) posed by the Google Phone.]]></description>
			<content:encoded><![CDATA[<p>Nearly two months ago, shortly after the release of the Droid and subsequent escalation in chatter with respect to the “Google Phone” I discussed <a href="http://gorode.wordpress.com/2009/12/03/one-bad-apple/">my complete dissatisfaction with the state</a> of the iPhone as it pertained to Apple/AT&amp;T and the impending threat (very serious threat) posed by the Google Phone.</p>
<p>Here we are just a week past the release of the Google Phone and akin to the iPhone, it is one impressive piece of machinery.</p>
<p>But just like Apple’s iPhone, we need more than good machinery and Google exited the gate with shiny new shoes, high expectations and forgot to tie their laces tripping and falling flat on its face.</p>
<p>Let&#8217;s consider the environment Google was entering. The iPhone, a device launched in 2007 and largely unaltered since its inception continued to dominate as the gold standard for a mobile device. In 3 years when one considers how quickly technology develops and the sheer investment (hundreds of million of dollars) by companies like RIM, Nokia, Motorola and HTC, to develop the “iPhone Killer,” the fact that no phone has come remotely close to dethroning the iPhone is laughable.</p>
<p>The king of all phones however was tied to the peasant of all carriers (AT&amp;T). The truth was that even the best phone was not enough to sway a majority market share to AT&amp;T. People still value network quality over phone functionality.</p>
<p>With this void in the mobile market there appeared to be a shimmering light. Google, a company whose own innovations have enhanced and touched the online experience of nearly every Internet user, was ready to throw its hat into the ring, not just as a software developer but also as a manufacturer/retailer.</p>
<p>Google? Selling their own phones? This will change everything. Right?</p>
<p>At first, things appeared bright. Recent leaks of the “Nexus One” showed a phone with incredible hardware and a great deal of potential. Would the Nexus One “kill” the iPhone? No. But we don’t want an iPhone killer, we want a market mover, a close 2<sup>nd</sup>…anything that doesn’t appear to be developed by someone living under a rock. And this phone seemed to heed that call.</p>
<p>The next big part of this puzzle would the carriers. Would the prayers of Verizon customers be answered? Would Verizon iPhone envy be cured? Kinda. Sorta. Not really… but soon.</p>
<p>T-Mobile was announced to be the first true carrier of the Nexus One with the ability for AT&amp;T users to join in on the fun and a soft availability date for Verizon in the spring (’10).</p>
<p>The final part of this equation would be cost. It was presented that the Nexus One would cost $179 for users with a contract and $529 for an unlocked unchained non-contract phone. Not bad Google.  You even gave us a website to buy the phone. Quick and easy.  Right?</p>
<p>Wait did I say quick and easy? You see I made the same mistake with Google that I made with Apple. I assumed that these innovative companies were vaccinated or immune from the stupid-virus that plagues most cell phone carriers.</p>
<p>Check out what we missed:</p>
<p>1)     If you’re an existing, loyal, returning customer of T-Mobile and ready to sign another new contract they show their appreciate for your returning business by charging you $379 as opposed to $179.</p>
<p>Let’s consider the implications for just a moment. Existing customers, people patient enough to continue using the 2<sup>nd</sup> WORST carrier in nation, the small few who have managed to accept the idea that their cell phone service will be crap are being shut out from buying the Nexus One by inexplicitly charging $379. These are supposed to be the easy sales! WTF??</p>
<p>2)     The next revelation is the early termination fee. I’m sorry, early termination fees. Both Tmobile and Google get a slice of your wallet should you realize this whole experiment was a horrible decision… and wait they take the phone back too.</p>
<p>1. Tmobile:   $200</p>
<p>2. Google:  $350</p>
<p>I have nothing more to say on this matter. Those numbers speak for themselves and that is unacceptable.</p>
<p>It is no wonder the Nexus One only sold 250,000 units in its first week. And it’s sad. This is a fantastic device and Google is a great company. But the steps taken in the launch of this device display the arrogance and disconnect mobile providers and manufactures have with their customers.</p>
<p>Google has a hefty hill to climb as the divide between the Apple ecosystem and Google ecosystem draws ever deeper. Simple pricing, broad carrier coverage and low risk trials would have permitted Google to make significant strides in a battle for customers for its mobile camp.</p>
<p>Every app purchased on a mobile device represents a small investment by a mobile user in their respective mobile ecosystem whether it Blackberry, Android or Apple. Google is late to the party and new to the industry.</p>
<p>If Google plans to challenge Apple in a meaningful way (especially when both phone developers find themselves on the same carrier) it will need to demonstrate as much thought to its mobile services as it has to its other businesses. Fortunately for Google, they are… well Google. And they get more than one shot.</p>
<p>I expect that we will see big changes from both Apple and Google in Spring 2010.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.glowinteractive.com/2010/01/a-superphone-with-a-touch-of-kryptonite/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

