<< Silverlight DOA On Mac OS X | Home | Microsoft, Sun Endorse Adobe Flash/Flex Paradigm >>

Bloglines vs. Google Reader: The Verdict

I have been running Bloglines and Google Reader side by side for 71 days. Both show up as part of my Firefox home pages, at home and at work. The idea is that I should make them equally available for an extended evaluation period, and whichever one I instinctively go to at the end of the evaluation period wins.

Today, I removed Google Reader from my Firefox home pages. And here's the Bloglines feature that won me over (or kept me there, to be exact):

Notice the "Keep New " checkbox at the lower right corner. It allows me to keep the post as new, so that it will show up the next time I view the same blog. Why would I want to keep the post new? Because it contains information that warrants further examination (in this case, Kyle pointed his readers to a set of pretty good JavaScript videos at Yahoo!Video).

I can't do something similar in Google Readers. The closest thing I can find is the " Mark as read" checkbox underneath each post. However the effect of checking that checkbox isn't very durable. It goes away the next time I read the entry.

Prior to today's decision, I have already accumulated several reasons in favor of Bloglines:

  • In Bloglines, as soon as I click on a subscription in the left pane, all of the unread and keep new entries of that subscription show up in the right pane and everything is marked as read. This allows me to scan my subscriptions very quickly.

    In Google Reader, the posts are marked unread after I click on a subscription in the left pane. I have to go to the right pane and click on each individual posts to mark each as read. This is very clumsy and slowed me down considerably. This puts a little hesitation in to my choosing Google Readers.

    I understand this Blogline feature is quite controversial in REST circles, it not being idempotent and all. But I'll take usability over programming orthodoxy any day.

  • Both Bloglines and Google Readers offer the choice of displaying all feeds or displaying only updated feeds. However, in Google Reader, this is a one click option. During the evaluation period, I switched between the two modes several times, unsatisfied with either of them.

    In Bloglines, this is a three click option which isn't obvious at all. So I did not fiddle with this option during the evaluation period. The end result, my Bloglines experience is more consistent while my Google Reader experience has a split personality.

  • Similar things can be said about Google Reader's one click choice between the expanded view and the list view, a la GMail. I ended up switching between them, unsatisfied with either.

    With Bloglines, I liked the expanded view just fine.

  • Bloglines and Google Reader both offer some vi-like keyboard shortcuts. I never use those in Bloglines, and my experience there is just fine.

    With Google Reader, I ended up trying them (because they are very similar to the keyboard shortcuts in GMail and I use them in GMail all the time) and not liking them. The problem has to do with the way the focus is switched from the left pane to the right pane and back. The commands are simply too complicated. And that somehow became yet another negative for Google Reader.

    I know, I know, this is not fair. But I did not promise a fair evaluation.

All of these, plus Bloglines "Sub with Bloglines" bookmarklet and "Blogroll web service" features, which I use quite heavily, tipped my balance towards Bloglines.

I'm sorry, Google Reader.



Re: Bloglines vs. Google Reader: The Verdict

Hey, Weiqi. "Mark as Read" in Google Reader is sticky, too--the entry doesn't get marked as read again until you explicitly check the box. My reading habits are a bit different which is why I think Reader is a better fit for me. I don't click on each subscription individually. I've broken down my subscriptions into coarser-grained labels. For example, I have a label named "must read" which contains the blogs I read first. I also have a label named "java"; some of the "java" subscriptions are also labeled "must read" but not all (that's the nice thing about labels vs. folders). A few times a day, I start with the "must read" label in expanded view. Often times, it contains 100s of items. I quickly iterate through them using the "j" key. I get through them a little faster than I did with Bloglines; I like that the top of the current entry stays in the same place (I think Bloglines supports this now, too). I used the same process in Bloglines, and I would lose a ton of entries every few days when I would accidentally close my browser or navigate away. It was very frustrating. Reader obviously doesn't have this problem. Reader has a "subscribe" bookmarklet, too, but I don't use it anymore. I use Firefox's built in feed detection (the little orange box in the URL bar). Reader also has a "Next >>" bookmarket in the Goodies section of the settings. If you click it, Reader will send you to the next updated site. You don't even see the Reader UI. Finally, Bloglines's blogroll was nice, but Reader's ability to share individual items is way cooler. You just hit shift+s to share something. Here's my feed: http://www.google.com/reader/shared/07248529942124281245

Re: Bloglines vs. Google Reader: The Verdict

I use Reader's "star" feature to mark those blog items that I want to revisit. Perhaps that would suit your needs?

Re: Bloglines vs. Google Reader: The Verdict

Yeah, that's what I do too. I actually just went the other way b/c adding feeds in bloglines was ok, but GR is quick and I like the way the scrolling works in GR vs. Bloglines...

Bloglines vs. GR sharing

Nice summary, it's the same result I ended up with. I'd add one item. In GR you can share articles you select, but you can't share the subscription list -- and there's no blogroll (of course). Bloglines allows one to share subscriptions. Much nicer. Neither, unfortunately, allow you to create a feed that's defined by a set of subscriptions, there might be a way to do something like that with Yahoo Pipes however.

Add a comment Send a TrackBack