We're building a Google Reader replacement, we'd love your advice.

A bit of background, we're a relatively new digital agency (specializing in the development side of things) based in England, and we've settled upon a Google Reader replacement as our first major project after the simple fact that I didn't find an alternative that I personally liked. Simple, right? Now, we've been working on this for a while - and we're almost ready to open our doors to the public (within the next few days), but before we do so (and possibly have a poor first impression), we'd love to hear what features you'd like to see in a Google Reader replacement.

Anybody who contributes a feasible idea or suggestion will receive a premium account indefinitely, free of charge. And yes, before anybody asks - our primary offering is free (we'll be offering a few premium only features in order to ensure financial stability).

So, any suggestions? You can see a screenshot of our web ui at http://i.imgur.com/vxqhcgO.jpg - and you can sign up for the beta (invites will start going out tomorrow) over at http://yomu.eu/ if you're interested.

-------------------------

For those interested, our technology stack currently consists of the following.

Backend

node.js (express, socket.io, the usual suspects).

Database

NuoDB (formerly NimbusDB).

Why NuoDB over say MySQL or Mongo? Well, I've personally been working with Nimbus for a while - and I love the damn thing. Performance is great, and the ease of scaling is a major selling point.

Hosting

Self-scaling Amazon EC2 infrastructure.

-------------------------

Applications for Android and iOS are already on the roadmap, and are tentatively scheduled for late July.