{"id":120,"date":"2018-04-01T03:36:44","date_gmt":"2018-04-01T03:36:44","guid":{"rendered":"http:\/\/www.samgirotra.com\/blog\/?p=120"},"modified":"2018-05-14T02:27:51","modified_gmt":"2018-05-14T02:27:51","slug":"estimated-times-in-pocket","status":"publish","type":"post","link":"https:\/\/www.samgirotra.com\/blog\/estimated-times-in-pocket\/","title":{"rendered":"Estimated Times in Pocket"},"content":{"rendered":"

Pocket<\/a> – the app that let’s you save articles to read later – just introduced an ‘Estimated Time’ to read feature. It’s subtle, but makes my experience with the service much better. I save a TON of articles to read later, but the number I actually go back to read is shameful. It’s hard to prioritize what to read when you can’t even count the number of articles in your archive – this is where Estimated Time helps. It adds context to my archive and makes it feel less overwhelming. Before, I couldn’t prioritize what to read because it all looked interesting – I was the one who saved them after all! But now I feel the product respects my own context<\/em>. So if I’m on the bus commuting, I’ll go through some of the shorter articles. And if I’m spending a lazy Sunday on the couch, I’ll read New Yorker articles \ud83d\ude42<\/p>\n

I’d love to see the service add even more data-rich features like this. Here’s a few things that would be great to see:<\/p>\n