Hacker News new | ask | show | jobs
by swombat 4614 days ago
The problem is not a history of killing failed product, it's a history of killing products that everyone is actually using, without giving it as much of a chance as a company of Google's resources might be expected to, for political reasons rather than practical reasons.

As a couple of good examples: Google Wave was created to give the Rasmussen brothers (creators of Google Maps) something high-profile to do. Then it was launched in a disastrously bad way (closed beta? for a new communication tool meant to replace email?). Then as adoption started to build (but not quick enough to satisfy the political needs of the project), Wave was yanked after just a year.

Google Reader became a cornerstone of the web's infrastructure, a public utility service that cost comparatively little, returned perhaps little other than good will, but ultimately served a purpose for millions of users. But that wasn't enough for Google, so they yanked it.

In both cases, there was no real alternative path offered. Google just made an internal political decision to yank a project, and that's that. The public never even got the option to try and support the project.

Based on the above and other less high-profile examples, I'm not willing to invest my time as an early adopter in a company that has the deep pockets to fund long-shot projects, but doesn't have the balls to follow them through to their exciting conclusions.

Google Wave was a very exciting development with a lot of promise. Google Reader could have been evolved further and become an even more important piece of infrastructure, with all the good will associated with that. Instead, both are now black splotches on Google's reputation, in my view at least.

6 comments

"history of killing products that everyone is actually using"

That's true for amazingly small values of "everyone." It may include you, several people you know, and other people in your line of work, but that's not remotely the same thing.

Hyperbole aside, the point is that it's possible for Google services to be successful but not successful "enough". They're willing to shut down services that have devoted followings. So , whenever you consider investing in a small service from Google, you should understand that could accomplish all its goals and still be shut down.
Hyperbole aside, the point is that it's possible for any company's services to be successful but not successful "enough". All companies are willing to shut down services that have devoted followings. So , whenever you consider investing in a small service from any company, you should understand that could accomplish all its goals and still be shut down.
I used igoogle to load a gmail iframe on my (insanely awesome) custom start page. It really sucks they shut that down.

I was also using the Google Toolbar (do not consume) spelling auto-correct "API". I was doing some really neat stuff with that technology and they shut that down too. Sure, I can't really complain about that one, but the end result is the same...

If you adopt Google technology, prepare for labor intensive migrations, alternative scrambling, and disappointments.

FTFY

If you adopt most any new technology, prepare for labor intensive migrations, alternative scrambling, and disappointments.

The world moves fast, products shut down all the time, but Google is high profile and gets lots of complaints... that's fine, I'm OK with them being held to a higher standard, it'll be good for them in the long run. But, I recently hit a problem because Twitter shut down it's 1.0 API. I'm not running around saying don't use Twitter on every article about them.

Also outside of HN/geek how many people REALLY used Reader? I bet you its less than 0.1% of the overall Google users. I would have done exactly the same in Google's position.

If a feature had been built that only 0.1% of users are using yet is taking up time to run, why keep it?

Several million people who use Android had downloaded Google Reader.
So 900 million Android devices back in July[1] and even if 5 million devices had Android that is a total of 0.55% of all Android users. Still worth it?

[1] http://www.androidcentral.com/larry-page-15-million-android-...

>> "Several million people who use Android had downloaded Google Reader."

That says nothing about usage though. I downloaded a lot of Google apps when I first got an Android device. Most of them I opened once and never again. I think this experience is common with apps.

Had an initial reaction upon seeing this post and came here to "share" only to find that so many have the same reaction. It just smells like a product that Google will be killing at some point in the not-too-distant future.

I get the whole idea behind the current environment to just throw stuff against the wall, see what sticks, then iterate.

That's great for start-ups, but, I would suggest that it is actually a problem when a well-established company does this repeatedly. In addition to Google just appearing flaky (which in itself is not good), customers do lose faith in the company's commitment to its customers/users and to their products in general.

Did anyone continue to run with the Google Wave idea? I'd be interested in using a tool like that, it showed a lot of promise.
Apache Wave (I believe the intial code was contributed by Google): http://incubator.apache.org/wave/source-code.html

I don't think it has gained much traction, though.

Wave was really laggy and required a special chrome frame plugin to run in IE. It was laggy even in chrome.