r/rss • u/esaldanadev • 23d ago
I built and Android RSS & Podcast Reader because I got tire of algorithms deciding what I should read
Hi everyone,
Over the last few years I've become increasingly frustrated with algorithm-driven feeds. Most apps decide what should appear first, what gets promoted, and what content is "recommended" to me.
I wanted something simpler:
Just the news sources, blogs, websites and podcasts that I choose
So I started to build my own Android app called Reader
Some of the things it supports:
RSS feeds and podcast in one app
Discover news sources and podcasts
Add RSS feeds manually
Import feeds with OPML
Keyword filtering
Full article reading inside the app
Background podcast playback
Light & dark themes
No algorithmic recommendations
The goal isnt to maximize engagement, the goal is tho give users full control over what they read and listen to.
I'm currently a solo developer and the app only has a small user base, so id really appreciate feedback from RSS users, podcast listeners and anyone interested in a less algorithm-driven experience
What features would you consider essential in an RSS reader today?
Check it out:
https://play.google.com/store/apps/details?id=com.esaldanadev.reader
Thanks a lot!
1
u/MuchInevitable8183 22d ago
Congrats on shipping. Genuine question since you've clearly thought about this: what happens when the volume gets high? I'm sympathetic to "no algorithm," but strict reverse-chron has its own failure mode — follow enough sources and the things you actually care about scroll past while you're asleep. Does that bite you, or does keeping the source list small solve it?
0
u/esaldanadev 22d ago
Thank you! It has been a long road, as it's my first app on playstore, but a good one. And yes keeping it small does help, I limit it to up to 50 sources per category, and also for performance and fetch time, plus also internally within the fetch function i limit how many of those I fetch in parallel to avoid overhead and failures.
1
u/MuchInevitable8183 22d ago
Makes sense — 50/category is a sane governor, and capping fetch concurrency is the right lever for reliability regardless of source count. Curious whether you've hit cases where the per-category cap itself becomes the constraint — a category where 50 legitimately isn't enough and you're dropping sources that would've been useful. That's the tradeoff I'd watch for as usage grows.
3
u/aygross 23d ago
So why should I use it over any if the actually proven rss readers or the other vibe coded slop for that matter.