Five Reading Tools - part I: Pocket

Pocket (formerly: read it later) allows you to save an article / URL to your pocket list for later consumption. The pocket list is not device specific, but kept "in the cloud", so you can access it from everywhere. You can see it as a competitor to Instapaper or Readability.

The main use is, that when I find an article or post interesting (or too long to read on the mobile while on the underground), or just stumble upon a post, but don't have the time to read it right now, I put it on my pocket list.

95% of the time this will be from Feedly [1], the remaining 5% are from Facebook, G+ or  Twitter. Yes, I'm still one of those grumpy old guys from last century, who use RSS.

Once click from Feedly, and it is in my queue.

If find the following important features extremely useful:

Easy to queue

Pocket makes it really easy to put an item into your reading queue or list.

Feedly, for instance, directly supports Pocket, and all you need to do is press the pocket button to send an item to the queue.

All my browsers have extensions that allow me to send the current document/URL to the pocket list.

On Android, Pocket is integrated in the Share menu, so all apps that can share content via the SendTo Intent, automatically support Pocket as well.

iOS introduced a similar share menu (now combined with AirDrop), however, Pocket does not (yet?) support it.

What Pocket does nicely (both on iOS and Android) is to detect that you have a URL in the clipboard, and allows you to add it with just one click. So you can easily copy the URL from the Facebook app or browser, switch to pocket and simply save it there.

Available everywhere

Once an article made it into the pocket list, it can be read from everywhere. PC/Browser, iOS, Android.

I personally do 90% of the actual reading on my iPad, 10% on my Android mobile.

So my pattern is, queue from Android (while on the road) and read on iOS (at home).

Easy to read

The number one reason I queue article to pocket, is that I don't have the time to read them when I discover them (again...commuting on the train / underground). Or the device is to small.

The other reasons is, that pocket (like all the other tools I show in this series) removes all the disturbing gadgets from the web page, and shows only the pure content (+ content related images).

This is how Wikipedia (which is quite clean on the web, to be honest) looks in Pocket [2] on the iPad. You can spot that it does not too well with structured content (the start of almost every Wikipedia entry) but does very well with "regular" writing. (Click both images to see compare)

Once an article is read, you can decide if you want to delete it, or archive it. Either way, when you're done, you should get it of of the queue.

When you decide to archive (which is what I usually do), it does help to add some tags to it (tag icon) before you send it to the archive (check-box icon).

That's how pocket works for me.

You mileage may of course vary.

--

[1] or Google Reader back in the good old days.

[2] I will use the very same Wikipedia entry for comparison in this series.

Beyond Google Reader - Part 5

Maybe the final part... but then again, maybe not.

Yesterday my Feedly account got migrated from Google Reader Backend to the Feedly backend - the Feedly Cloud.

Can be verified at the URL http://www.feedly.com/home#console.

You'll either see Google Reader or feedly cloud as the back end service (in the nice json output you get there).

So on all of my devices (PC, laptop, Android mobile, iPad) I'm on feedly now. Google Reader bookmark and app... unpinned and gone.
Fingers crossed.

I hope that Reedr - still my favorite on the iPad - will use the feedly cloud soon.

Beyond Google Reader - Part 4

So, feedly finally announced that they are building the back-end service for the Google Reader replacement and - more importantly - are working with 3rd party app developers such as Reeder to support them... *before* the sun will set on Google Reader.

Building Feedly | Re-imagine how people keep in touch with their favorite sites.: 

"We have been working behind the curtains with the developers of Reeder,Press, Nextgen Reader, Newsify and gReader as design partners for our Normandy project[1]. Today we are excited to announce that you will be able to access your feedly from all these apps before Google Reader retires and that the access to feedly API will be free. More details soon."

Beyond Google Reader - Part 3

So, only 5 more weeks or so to go before we geeks have to eke out our miserable existence without Google Reader.
As I mentioned in one of my previous posts, I will most probably switch to Feedly.

Here's where I stand today:

• I mostly gave up the Google Reader app on my Android mobile, 99.9% on Feedly.
• On my iPad I do 80% on Reeder, 20% on Feedly... and Feedly's share is increasing.
  Reeder's future is not entirely clear, except they say they plan to continue.
• On the PC I'm also 80% still in Google Reader, 20% in Feedly.

Basically I'm waiting for Feedly to launch their own back-end service, then import (hopefully auto-magically) my Google Reader feeds in there and just continue.

Ah, and in the meantime Digg seems to be progressing with their Reader back-end. Let's hope they'll launch it openly for any reader app out there.

Beyond Google Reader - Part 1

I'm pretty sure this will become a series, so I decided to call this post here part 1 ...

After Google announced the shutdown of Google Reader two days ago, the internet was of course full of rants and stuff. Some even declared RSS dead. Yeah, right... Whatever.

I want to stick to RSS (as a style of receiving and consuming news, articles and posts) for as long as possible. And I need my reader synchronized between devices.

Always.

Here's why.

1. I start with Reeder on my iPad in the morning (at home);
2. then on the train & underground on my commute to work I usually continue reading a lot (or rather quickly browse through the headlines) on my Android Phone using Google Reader (ahem). Interesting articles which I really want to read on a proper screen are save to pocket.
3. And then at work (as well as at home) there is always one browser tab open with Google Reader. 

So I have this one feed of news wherever I am.
Therefore I need the (almost) instant synchronization of the read/unread state between devices. And this is what Google Reader did perfectly.

Google Reader is was not only a front-end / user-interface, but also this great back-end synchronization service (or rather: central repository). Reeder, Feedly, Pulse, Flipboard, ... they are were all relying on this infrastructure.
This now needs to be replicated or picked up by someone else.

A new hope:
In the aftermath of thurday's EOL announcement, Feedly (which I was using a bit already on my Android) said, they were actually anticipating this move by Google, and already starting building their own backend infrastructure, essentially cloning on the Google Reader API. And more importantly, that they will open this to others.

So my hope is now that

1. Feedly will do the backend service 
2. existing clients like Reeder (unbeatably, to me),  Flipboard, ... will use this service and concentrate on the GUI. (This of course includes Feedly, the client, as well)

In the meantime, if you are facing a situation like mine, I suggest you try feedly.

Go and get the Chrome or Firefox plugin, the iOS app, or the Android app. Or all. Here.

Fingers crossed.