SmoothSpan Blog

For Executives, Entrepreneurs, and other Digerati who need to know about SaaS and Web 2.0.

Feedly Progress Report: Not So Good

Posted by Bob Warfield on August 30, 2013

SadFeedlyI’ve been using Feedly since the demise of Google Reader and wanted to give a progress report on how that’s going.  Not that you won’t have already had to make a decision on an alternate, but perhaps this will be helpful for Feedly if not everyone else.

First the good news:  Feedly is great as a desktop browser app.  I am very satisfied, and if it weren’t for the mobile issues I’ll get to momentarily, I would be a committed and enthusiastic paying customers.

The bad news is all about the Mobile App.  Put simply:  it doesn’t work.  I started out fairly unhappy with Feedly’s mobile app, and I have written about it before.  Initially, it didn’t work at all.  Eventually, they fixed that bug, and now the mobile app doesn’t work because it is too frustrating to be useful.  I waited a reasonable interval before writing this to see if a fix would be forthcoming and whether it was just me.  No, and no are the answers.  You can Google “Feedly Mobile Crashes” and find plenty of references to this–there are even people commenting on Feedly’s Blog about it.

The problem is it crashes frequently.  If I click on every article I want to read, it will easily have crashed at least once every 10 articles.  The problem is, when it crashes, you lose the article you were trying to read.  The sequence goes like this:

1.  Click on article to read it.

2.  It starts loading.

3.  At some point, it may even look like you are done loading the article, Feedly crashes and you’re left staring at the iPad desktop.

4.  You go back into Feedly, and it has already marked the article as “read”.  It’s gone, long gone, and you’ve missed your chance to read it.

At this stage, the Feedly Mobile App is really only useful for clearing out articles you don’t want to read.  You don’t dare try to use it for reading articles you’re interested in, because sooner or later (and mostly sooner in my experience), it’s going to zap your article before you’ve had a chance to read it.  DOH!

It’s annoying as heck, though it hasn’t quite risen to the level where I am ready to drop Feedly altogether.  What it has done is made me spend less and less time reading feeds on my mobile devices (iPad mostly).

The thing that puzzles me is why they haven’t fixed it.  Even if they can’t fix the crashing (looks an awful lot like Safari crashing, which also happens a lot if you try to read Google News), they could change the software so it doesn’t mark the article as “read” until you get safely back into the list of articles without crashing.  That would make it dramatically less frustrating and stressful to use.

Of course I could also ask one more time (as many commenters on other posts about this have), why doesn’t feedly make it possible to simply use their browser version?

I recommend not paying Feedly for their enhanced version until they make a decent mobile app or get out of the way and let us access the service via browser.

One Response to “Feedly Progress Report: Not So Good”

  1. Does the same thing on my Android tablet. Sort of happy you did this as I thought it was my tablet and never dreamed it was the app since it has been occurring after several updates. Thanks.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: