Instapaper is for readers, Pocket for Mozilla

Reading later is usually a habit that I follow every day when I have some minutes of peace. I add articles and posts to my list in Instapaper from my feed reader, by a browser or via Twitter timeline. Sometimes my reading list became like a /dev/null folder, but with a load of patience and much free time, I successfully complete more reads.

Anyway, I said of Instapaper. I used Read it Later for years before it became Pocket, and I used Pocket too. But after a recent update for their Android app (and the Pinterest’s shopping) I’m definitely switched to Instapaper.

I’d like to highlight that I tried to switch back to Pocket several times, especially after the Mozilla acquisition, but each time I capitulate. Instapaper is for reading, Pocket is for sharing.

Instapaper has some features that in Pocket lacks, features that make reading more comfortable: for example the pagination. Yes, I know, even Pocket have the pagination, can be activated by flipping on the page but, in some cases, the results are damn illegible. Instagram has the pagination progress dots in an article and, in the list, a indicator for post length. Sublime for choice what read.

The highlight, oh yes the highlight. Underline parts of an article, share quotes – automatically or manually, as text or image, add notes, collect, search and archive them is a must have for all happy reader. The killing feature for me.

So, Pocket has other cool stuff if you want to share your posts or if you want to create a public collection, but missing reading power features. Mozilla bought Pocket to create a greedy ecosystem of relevant shared contents to suggest in their next browser version, and it’s a great thing, but I think that Mozilla still needs to invest on Pocket under pure reading profile and I hope that this takes place.

If you want mainly read and store your links and quotes, Instapaper wins hand down. For now.

Collection Categories SoftwareTopic Tags , , , ,

Leave a Reply

Your email address will not be published. Required fields are marked *