We have just announced on the Official Google Blog that we will soon retire Google Reader (the actual date is July 1, 2013). We know Reader has a devoted following who will be very sad to see it go. We’re sad too.The problem is, there is no alternate feed reading solution. Google Reader has become the alpha and omega of RSS feed aggregation.
There are two simple reasons for this: usage of Google Reader has declined, and as a company we’re pouring all of our energy into fewer products. We think that kind of focus will make for a better user experience.
To ensure a smooth transition, we’re providing a three-month sunset period so you have sufficient time to find an alternative feed-reading solution.
RSS readers allow you to pull content from multiple blogs and news sites (via 'feeds') and read them in one location. For an information omnivore like me, they are a must have: a way to parse through dozens or even hundreds of blogs daily for new content without having a bookmark for every single blog that might interest me.
As BusinessWeek put it:
But serious RSS users aren’t into it for the luscious jpegged beauty. RSS feeds, taken straight, are a wall of text. That’s useful when you want to let news wash over you, to scan screenfuls of headlines without waiting for extraneous pictures to load. When I want to absorb a lot of information fast—which is to say, always—I don’t have time for Flipboard. I want exactly what Google will be taking away from me this summer.
Lest you think I exaggerate about the sheer volume of content I personally consume via Google Reader, here is a snapshot of the stats from my GR 'Trends' page:
For Google Reader users this is not at all the exception. Reader may have a smaller user-base than other Google tools, but there's no doubt that they are almost all power-users: bloggers, journalists, media-hawks of all stripes. There are several petitions already up at Change.org, one of which has already surpassed 50,000 signatures (sign it!). The Google Reader support forums are choked with wails of agony. And Reader-dependent journalists from every virtually every news organization are noting its passing.
There are, of course, other RSS readers out there. The problem is, even if you don't use Google Reader you probably actually use Google Reader. Google Reader's powerful back-end synchronizes your feeds and the content you have and haven't read across multiple devices. Most feed readers currently on the market, from desktop clients to smartphone apps, take advantage of this by plugging into it. The developers of these readers will now be scrambling to come up with their own back-end solutions before the service sunsets on July 1st.
Should a viable alternative not emerge, this could spell big trouble for the small blogs of the world. I read Tyler Cowen's 'Marginal Revolution' blog every day and would probably remember to check it without a feed reader. But I follow other, smaller blogs, often blogs written by friends, which update irregularly. Heck, if you follow this blog this is the case for you too: I don't update daily, so without some sort of feed you'd have to remember to manually check this blog now and again.
Again, Google Reader is not the only way to do this, but it is the main way people do it. Google Reader has been in service since 2005 and has garnered a substantial following in the intervening eight years. As one blogger tweeted:
The implications of Google's cancellation of its Reader service go far beyond the loss of a useful tool, as a Forbes blogger bitterly notes:
- Drive competing services out of business with a free service (subsidized by a profitable product).
- Cancel free service.
Does Google understand the concept of corporate social responsibility? That seems to be the basic question around the company’s strange decision to shut down a tiny service that serves as a major audience conduit for many thousands of bloggers, citizen journalists, and self publishers.Google's decision is also shaking the faith of myself and many others in the Google eco-system. If Google is willing to pull the plug on Reader, what tool or service that we use might be next to get the axe at the search giant's whim? Perhaps Blogger? If Google is getting out of blogs entirely I'll be forced to move TomNoir.com in its entirety to some other blog service.
Google’s announcement today that it is destroying Google Reader, the most popular RSS syndication tool was a massive blow to the blogging community – and to most of those speaking out tonight via social media, an entirely unnecessary attack on an important corner of the public Internet by a company with more than $50 billion in revenue and a newly-won reputation as a tech giant on the move.
Several voices have pointed out that Google Reader is probably not very profitable for Google. It does serve up some ads, but in a minimalist fashion. Meanwhile, even if it isn't actively developing the service anymore it does have to maintain the back-end servers. So maybe it makes good business sense for Google to put the axe to reader.
Or does it? Google Reader is a wildly successful product by the standards of any ordinary software company. Its user base must number in the hundreds-of-thousands, if not millions. Only to a company that measures web traffic by the hundreds of millions and even billions would this seem like a dismal flop. Google is viewing Reader through the same lens with which it views its other products: as a service to drive ad revenue.
This is a mistake.
If Google's give-it-away-free model doesn't make sense for Google Reader, why not try charging for the service? Google could charge the other feed readers that use its back-end API. Or it could even charge its users. I would pay. Google Reader is absolutely worth, say, $30/year to me.
You hear that, Google? You've got a user base you could actually monetize! If only you will listen before its too late.
Otherwise you're killing off the thriving-but-often-invisible universe of small blogs. You're alienating a base of vocal power-users. And you're shattering those users' faith in your willingness to continue supporting services you've developed.