It’s always good to see new development in the Android RSS sphere. A feature list and roadmap would greatly assist people with evaluating whether it’s ready to trial. More screenshots would also benefit. As a FeedBin user, I’m very glad support is there, but are other aggregators planned? FeedBin, sadly, is a small player in a big field.
I’d do something with the name… way too easy to read it as “Crappy Reader” when you’re scanning a list of search options. Even here, while scrolling my feed, I saw this as ‘oh, someone’s had a crappy experience with their RSS reader, I wonder which one it was.’ Is it going up on Google Play anytime soon?
“Smallish” isn’t a big selling point for me. A wildly competent parser would the big game changer in RSS development. It also tends to become the Achilles heel of reader developments. Someday, someone will bake in a fast Firefox custom tabs implementation directly in their reader with easily selectable ad blocking options and without needing Firefox to be installed (essentially making Firefox their parser). Then they’ll be cooking with butter. They also won’t have to constantly tweak their own parsers or call out to external programs. Thoughts in my head.
I’m gonna keep watch and see where this project goes. 🙂
It’s always good to see new development in the Android RSS sphere. A feature list and roadmap would greatly assist people with evaluating whether it’s ready to trial. More screenshots would also benefit. As a FeedBin user, I’m very glad support is there, but are other aggregators planned? FeedBin, sadly, is a small player in a big field.
I’d do something with the name… way too easy to read it as “Crappy Reader” when you’re scanning a list of search options. Even here, while scrolling my feed, I saw this as ‘oh, someone’s had a crappy experience with their RSS reader, I wonder which one it was.’ Is it going up on Google Play anytime soon?
“Smallish” isn’t a big selling point for me. A wildly competent parser would the big game changer in RSS development. It also tends to become the Achilles heel of reader developments. Someday, someone will bake in a fast Firefox custom tabs implementation directly in their reader with easily selectable ad blocking options and without needing Firefox to be installed (essentially making Firefox their parser). Then they’ll be cooking with butter. They also won’t have to constantly tweak their own parsers or call out to external programs. Thoughts in my head.
I’m gonna keep watch and see where this project goes. 🙂