So, Google is killing Google Reader.
When I saw that headline on Wednesday evening, I felt a mixture of emotions: anger, sadness, and worry. Anger that Google could shut-down a service that was so personally-valuable to me; sadness that a web-service I've depending upon for years was going away; worry that there might not be an alternative service out there that could fill the same role in all the same ways that the Google Reader ecosystem has.
You see, I've been using Google Reader since 2007. It's the web-app I use more than any others. I've had a dedicated Google Reader pinned-tab open in all my Firefox sessions for as long as I can remember.
I use it every single day. It's the way I read the Internet.
Google Reader is more than just a simple web-app: it's the back-end RSS aggregator service which crawls all the 120+ RSS feeds I follow and centrally stores all the state about what unread (and starred) articles I have. That kind of read-anywhere-sync-to-everywhere workflow is immensely valuable to me because I want to be able to access my news wherever I am and with whatever device is most handy: I use the Google Reader web-app on my home laptop, home desktop, and work desktop machines; I use Reeder on my iPhone; I use gReader on my Nexus 7 Android.
It's been interesting to read the reactions/backlash from the tech community. I found some interesting blog-posts via Twitter:
The Social Web Isn't a Replacement for RSS
Christian Heilmann wrote "RIP Google Reader - I'd Have Paid For You" where we talks about how the social web will never be a replacement for the one-stop aggregation service that Google Reader provides:
Yes, RSS has been declared dead many times and people keep banging on about the social web and that Facebook, Twitter, Reddit and others have replaced the old style of blogging and having an own feed. But I don’t buy it, sorry. Every social network is full of senseless chatter and organised advertising. Social media experts and PR folk make sure that information about certain products and celebrities get read and retweeted. I don’t care about that. I don’t want it. The same way I don’t watch public access channels or randomly surf channels but instead plan what I want to see on TV. Random exploration and finding things by chance is fun, but it is not helping you to keep up to date – it is the ADHD of information consumption.
Moving Towards a Walled-Off Web?
Jonathan Poritsky wrote a fantastic blog-post titled "Reader's End and Google Today", where he points out that this could be the start of a disturbing shift in Google's priorities:
The biggest issue doesn’t seem to be the loss of Reader itself, but the recognition that Google’s priorities have shifted …
But walls have sprouted up. Google can’t access the massive amounts of data people pour into Facebook and Twitter, so they built Google+ as their own social walled garden. Twitter is exerting control over how users experience their product, which shuts out competitors like Instagram (which is owned by Facebook), which can no longer display images inline in tweets. The Web is getting smaller, not bigger, with each company working to become the umbrella under which you experience the Internet. So Google has taken steps to make sure that the Web as users know it exists under their company banner, and Reader doesn’t fit in with that plan anymore.
I was once a Google cheerleader. Like many I believed their goal was to make a better Web for everyone, with the one major tradeoff being that they would sell ads instead of charging users. That may once have been true but the Google of 2013 doesn’t want to build a better Web, it wants to build a better Google. I don’t think that goal is aligned with any of my own.
With this move, Google is seeding a lot of ill-will in the tech community. This feels very much against the "Do No Evil" slogan which Google touts. If Google can shutdown a service as beloved as Reader, then it makes you wonder which services are safe from the chopping-block…
A New Hope: Google Reader Alternatives
Even though Google says that "usage of Google Reader has declined", there's obviously still a lot of people in the tech community who still find great value in RSS and a Reader-like service. And a lot can happen in the next 3 months leading up to the July 1st shutdown.
So, the imminent death of Google Reader could just be trigger-point needed to spark another renaissance in RSS readers like what we had circa 2005-2006.
And it looks like we will have several options. ReplaceReader is a neat little site I found for folks to suggest replacements for Google Reader.
I expect the biggest challenge (for me personally) in finding a suitable replacement for will be finding a solution that I can still (easily) access (and seamlessly sync!) across multiple platforms. I've gotten spoiled-rotten by the native iOS and Android Google Reader clients. And whatever I pick, I want to make sure that I still have some exit-paths in case that service closes-up shop for some reason. Some kind of open-source/self-host option could be nice so that I can control my own data, but then again needing to maintain a DB-backed website isn't really something I want to do anymore.
Tiny Tiny RSS is an open-source self-host option which looks pretty mature. This looks promising if all you need is a simple web interface.
The most interesting option I've seen so far is NewsBlur. It's open-source (on Github) and self-host-able (nice to know I have options) but also has a paid hosted option. And it looks extremely polished and simply gorgeous. It keeps the same simple/functional interface principals as Google Reader while updating the UI for 2013. And there are iOS and Android clients so that I can still access my news on whatever device I want.
I expect (or at least hope) there will be a flurry of activity in the RSS reader space in the next few months leading up to the July 1st shutdown. It will be interesting to see what alternatives the community embraces. I plan to watch the space for a while before committing to any particular option, to see which options rise to the top.
I plan to write a follow-up post in a few months detailing what option I end-up going with…