This is pretty cool!
One tiny feature request / bug report.
I clicked on "Feed Types" on the demo, and was happy that once I select an article, I can use j/k to move between articles. However, if you are on an article and scroll down (e.g. with spacebar), then hit j or k, you go to the next article scrolled down and have to scroll back up to the top. This is a bit awkward. If you go to an article, either it should always go to the top, or it should remember where you were for that particular post -- not whatever you were previously looking at.
Thanks for the bug report! This seems to be a demo-only bug (the demo has some custom state logic since it's all hard-coded instead of doing real queries), but I'll look into why it's inconsistent with the real app.
Update: The bug was in the small amount of state code that's impractical to share with the main app (for now), but it's fixed in this PR and should work correctly in the demo now.
I posted a few months ago about vibe-coding an RSS reader. The mood on the internet seems to be that these apps are buggy and never get finished, so I figured it was worth posting an update. Another thousand commits later, Lion Reader supports every feature I care about, works reliably, has very good performance, and is open for public signups[1].
I've actually been using it for a while, and mostly kept signups closed because of some expensive features like AI summaries (now handled by making users provide their own API keys).
The features are entirely designed around what me and a friend find useful, but I think I have decent taste so consider Lion Reader if they're useful to you as well:
I thought it would be funny to use a demo of the app to describe the features, so if you're curious, all of the features are listed in "articles" here.
I think at this point, every feature I care about is implemented on the web app, although I want to improve how the local caching works and incidentally add offline mode based on that. At some point I might make a native app for Android again, but I don't really have time to validate one.
I'm open to feature requests and pull requests (as long as they include screenshots to demonstrate that the feature works).
Signups require a Google or Apple account as a minimal anti-bot measure.
For example, you can tell Claude Code to run an ML experiment and upload a report to Lion Reader when it's done.
Unfortunately, narration only works in the foreground because we're not a native app. I have ideas for supporting background play but it's very complicated so I haven't got around to it.
The Chrome extension is still in review.
Some features require paid API keys for other services, but they're all optional.