Google Reader shuts down tomorrow, here’s everything you need to know

In case it’s somehow skipped your mind, Google is going to be turning off Google Reader, it’s popular RSS aggregating service, on July 1st. That’s tomorrow. And if you haven’t taken the proper steps, such as backing up your feeds or syncing them with a suitable replacement, you’re going to lose them.

But never fear, as usual, iDB has you covered. Here’s everything you need to know about this week’s Reader shutdown…

What happened?

Google originally announced that it was going to be shutting down Reader back on March 13. The news came via a blog post titled ‘second spring cleaning.’ It explained that while the service has a loyal following, its usage has dramatically declined over the past few years. Thus, it obviously had to go.

Unsurprisingly, the announcement sent shockwaves through the tech community because at the time, a lot of third-party RSS readers, technology sites and pundits were still dependent on the service. A petition even popped up online to keep Reader running, and it has since collected over 150k signatures.

But as Richard Gringras, Google’s Senior Director of News and Social Products, points out, the shutdown is really just a product of the times. Users are moving from the old model, where they would read the news over breakfast or at the end of the day, to getting news updates live through sources like Twitter.

Reader Alternatives

When news hit that Google was going to be shutting down its RSS service, third party companies came out of the woodwork to announce their alternatives/replacements. We’ve already put together a list of 14 great alternative services, but there are a few that have come to stand out in recent months.

  • Feedly – it seems like Feedly directly benefited from Reader’s impending doom the most— word has it that it’s added over 3 million new users since Google made the announcement in March. It has made a copy of Google’ Reader API, and when the service shuts down tomorrow, its clone will kick in for a “seamless transition.” Bonus, it’s available on Android, iOS and as a plugin for most major browsers.
  • Digg Reader – Digg reinvented itself last summer, following a major selloff and other issues. It’s hard to gauge how well it’s doing now, but it certainly seems to be making a lot of commotion with its new Reader project. The service just went live via a pair of iOS and web apps (and is scheduled to hit Android next month), and it’s capable of syncing your Google Reader feeds in seconds.
  • AOL Reader – AOL, once known as the source for your daily internet news, recently announced that it has an RSS reader of its own in the works. It seems more like a ‘me-too’ effort to try and regain some relevance with mobile users than anything else, but it has the resources to make something good. The down fall is, it’s only available in beta right now, on an invite-only basis, at reader.aol.com.

What do I need to do?

That’s up to you. If you’re ok with losing you’re saved Google Reader feeds, which will likely happen tomorrow when the service shuts down, there’s no rush to do anything. You can simply evaluate which alternative service suits your needs if you’re interested in finding one on your own time without worry.

But if you’d like to save your feeds, and you haven’t backed up or synced them with another service yet, you’re a little more pressed for time. Theoretically, Google could shutdown Reader servers tonight at midnight, taking your feeds with it. So you’ll obviously want to make sure you do something before then.

I would recommend at least syncing them up to an app like Flipboard, Feedly or Digg Reader, which let you sync your feeds by simply logging in with your Google Reader credentials. This way, even if you don’t end up using them later, your feeds will be backed up somewhere in the event you ever want them.

Of course, it’s possible Google could completely reverse course tomorrow and either extend the deadline or cancel the shutdown all together. Stay tuned to iDB for more info.

Questions, comments?