Chris Meller has written up a great review of FeedLounge. He does a great job explaining the way things work and I’m glad to see he thought the interface was easy to use.
There are just a couple of things I wanted to follow up on from his review:
If you’re on the Home page, I think it should refresh the display when you click Home again. … A very simple change to make, but I think it could make the user navigation experience much easier.
Two things here:
- When new items are pushed to the browser there will be no need for the refresh.
- Refreshing the interface each time adds server load and makes it much slower to navigate to a specific item. I think you’ll change your mind about this when you start using the other views. When we implemented the “no refresh” change in-house, it was greeted with a “wow, that is way better response.
When you have an entire tag group selected, there’s no way to tell which of the blogs in that group posted the entry unless you click on it to read it.
Um, in the split screen interface, if you hover over an item it *does* show the blog name. in the 3 column interface the blog name is right below the item title. Not that this won’t ever change or be improved, but that is the current behavior.
What if there were also an option for flagged items under each tag group as well?
You haven’t tried this yet, have you? Add tags to a flagged item then browse that tag on the Tags screen. I think you’ll like what you see there.
Most of the time, the labels for all my tag groups seem to “flicker� up and down a pixel every second or so.
As noted in the forums1, we think this is a Firefox issue. It only happens on Firefox for Windows (as far as we know), and we’re hoping for some help identifying the issue and working around it.
I already can’t find a post I read earlier today…
You mention you haven’t used the History screen – here’s your chance!
- A number of issues mentioned in the reviews have been discussed in the forums. [back]
This post is part of the project: FeedLounge. View the project timeline for more context on this post.