4 ms·
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 Go
by flixic 13y ago
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 http://blog.digg.com/post/45355701332/were-building-a-reader
- dustingetz 13y agoOr, reader is harder to build than they thought.
- jakelevine 13y agohey — we definitely remain committed to doing this. we just won't have it ready for launch. i personally think being the dumb syncing API is a smart play for any business. it's not as sexy but it's a more critical role.