Digg Reader Update • Hacker News Board

Re: Digg Reader Update

#21

Post by mdesq » Mon, Jun 17, 2013, 6:32 PM UTC

olegp wrote: post #18

caycep wrote: post #5

So where does this space stand at the moment? Off the top of my head, I can think of: -this (Digg) -feedly -feedbin -theoldreader There's probably a ton that I am missing

I've tried to include all the Google Reader alternatives here: https://starthq.com/apps/?q=reader

You should add Yoleo[1] to your list. It looks quite promising.

[1]: https://yoleoreader.com/

Re: Digg Reader Update

#22

Post by chourobin » Mon, Jun 17, 2013, 6:32 PM UTC

austenallred wrote: post #20

> Our focus will be on *Android app... And no mention of iOS. Does that mean they're not going for iOS first? If so, that's a very interesting decision.

Post launch so they probably have the iOS app down already.

Re: Digg Reader Update

#23

Post by olegp » Mon, Jun 17, 2013, 6:36 PM UTC

mdesq wrote: post #21

olegp wrote: post #18

Earlier quoted context omitted.

I've tried to include all the Google Reader alternatives here: https://starthq.com/apps/?q=reader

You should add Yoleo[1] to your list. It looks quite promising. [1]: https://yoleoreader.com/

Thanks, done! https://starthq.com/apps/yoleo

Re: Digg Reader Update

#24

Post by publicfig » Mon, Jun 17, 2013, 6:36 PM UTC

austenallred wrote: post #20

> Our focus will be on *Android app... And no mention of iOS. Does that mean they're not going for iOS first? If so, that's a very interesting decision.

They are talking about the next 60 days after initial launch. They should have an iOS app ready. The picture of phone interaction shows iOS as well.

Re: Digg Reader Update

#25

Post by loudandskittish » Mon, Jun 17, 2013, 6:41 PM UTC

da_n wrote: post #16

Chanel_Bunnell wrote: post #12

Earlier quoted context omitted.

Feedbin doesn't have a trial period. Is that right, or am I missing it? Credit card up front seems a bit harsh.

Correct, there is no trial period and it is a bit harsh, but I already decided I wanted to pay for RSS this time around and something about feedbin appealed. Only thing I would like to see it stats, and I suspect Digg Reader will be good at that.

I wish it didn't block videos.

Re: Digg Reader Update

#26

Post by bifrost » Mon, Jun 17, 2013, 6:43 PM UTC

michaelhoffman wrote: post #3

Releasing this less than a week before Google Reader shuts down seems daring. I hope Digg is ready to scale in a big way.

They should have some resources to pull in if they need to, they're smart guys :)

Re: Digg Reader Update

#27

Post by nakedrobot2 » Mon, Jun 17, 2013, 6:43 PM UTC

I haven't tried anything I like, yet. Here are my requirements:

1) fast! 2) both web version and mobile app that syncs with the web version 3) the same or similar interface to Google Reader

It seems Digg might have this eventually (they say they're working on an android app)

TheOldReader doesn't have a mobile app, and it is quite slow. But I like their interface on the web :)

Re: Digg Reader Update

#28

Post by jasonpbecker » Mon, Jun 17, 2013, 6:45 PM UTC

caycep wrote: post #5

So where does this space stand at the moment? Off the top of my head, I can think of: -this (Digg) -feedly -feedbin -theoldreader There's probably a ton that I am missing

Feedwrangler has been getting good buzz too.

Re: Digg Reader Update

#29

Post by jasonpbecker » Mon, Jun 17, 2013, 6:46 PM UTC

uptown wrote: post #14

Anybody got a replacement that'd allow me to continue using the desktop Reeder application as my front-end?

Feedly, Feedbin.me, Feedwrangler [1]

[1]: http://www.macstories.net/news/reeder-to-add-support-for-fee...

Re: Digg Reader Update

#30

Post by flixic » Mon, Jun 17, 2013, 6:48 PM UTC

From their original blog post I had an impression that they will try to mirror Google Reader's API and features: "We hope to identify and rebuild the best of Google Reader’s features (including its API)"[1]

Now they haven't mentioned API at all, they haven't replied to a question about Reeder, and they did put quite a lot of focus on their web and mobile apps.

A conclusion I draw from this is that they don't want to be a dumb syncing API, and just like Twitter, they want to control the clients (their own apps).

[1] http://blog.digg.com/post/45355701332/were-building-a-reader